We never rewrite results. We recompute them.

„Why did yesterday’s score change?“ Because an official football result occasionally still gets corrected after the final whistle — a disallowed goal, a VAR decision, a goalscorer reassignment, an awarded result. In a prediction game, points, a table and a matchday winner all hang on that number.

• Most display systems silently overwrite the old number. For a live ticker that’s fine. For a prediction game it isn’t: whoever won the matchday yesterday loses it today — with no explanation.
• Tipperoo overwrites nothing. Results live in a log that is only ever appended to (append-only). A correction is appended, and the affected tables are recomputed from it — traceably.
• You see the reason, not just the new number: „Matchday 7 was recalculated after an official correction.“ Your tips are never touched.
• And we only score a result once it’s confirmed — not the first time it shows up somewhere.

Why an official result still gets corrected after full time

Corrections after the whistle are rare but real, and almost never because someone was careless. They are part of football’s normal business.

The most common reasons, all from the game itself:

• A goal is reassigned — own goal instead of scorer, or the other way round. Often it doesn’t change the result, but it very much changes a side question („who scores the first goal?“).
• A goal is disallowed after the fact — offside, handball, a VAR decision that lands after the celebration. A 2:1 becomes a 1:1.
• An official revision by the governing body — a correction to the official result days after the match.
• An awarded result — an appeal, an ineligible player, an abandonment graded after the fact.

How often does this happen? We deliberately give no figure. We have no sourced number, and inventing one would be the exact opposite of what this article is about. What matters isn’t how rare it is; it’s that it’s not never — and a prediction game has to be built for exactly that case.

What most systems do: silently overwrite

The usual answer to a correction is to replace the old number with the new one — no note, no trace. For a display-only product that’s perfectly fine: for a live ticker or a news page all that counts is that the right number is there in the end. Nobody won anything there yesterday.

In a prediction game the number isn’t a display value but the basis of a standing: points, a ranking and a matchday winner all hang on it. Swap it silently and you retroactively change who’s leading — and nobody can see that, or why, it happened.

This isn’t a dig at one provider; it’s a question of construction. A system that only displays may overwrite. A system that scores may not.

What a silent correction does to a league

In a league a wrongly shown number isn’t a blemish, it’s a reversed matchday. Someone led on Saturday evening, posted it in the group, sent the screenshot — and on Monday someone else is suddenly on top. Unannounced. With no reason given.

A prediction game’s real capital isn’t the feature list, it’s trust in the table. A single unexplained shift is enough: once you couldn’t tell why your matchday win vanished, you stop trusting the table blindly.

So a correction is the most dangerous moment in the whole game. That is exactly where we started.

Provisional vs. confirmed: why we only score a result that’s actually settled

On Tipperoo a result is provisional during and just after a match — points count only once it’s confirmed. That’s the first line of defence against wrong tables: we never score on a single, unchecked snapshot.

„Confirmed“ means, concretely: a second, independent source reports the same result — and only then do we score. If that second source is briefly unavailable, we don’t guess — we score only if the result stayed stable over a wait and passed our sanity checks. If the sources disagree, we hold the result back and don’t score at all — better right a minute later than wrong right now.

The live table you watch during a match — the points moving in front of your eyes, the race in the chart — is explicitly labelled provisional and never touches the official record. It’s the exciting part; the confirmed table is the reliable one.

When a cup result with extra time and penalties actually counts as final — and what the difference between 90 minutes and the full result means for your tip — is here: Does extra time count in a prediction game?

Append-only: we overwrite nothing, we append and recompute

On Tipperoo results live in a running log that is only ever added to — never overwritten (append-only). No result is changed in place. When an official correction comes, we don’t delete the old number: we append the correction as a new event and recompute the affected tips and tables from it.

That has a property you can’t see in a table but which carries everything: the table is always the sum of the log, never a hand-edited number. You can replay the computation from the log at any time and get exactly the same result. There is no intermediate state known only to someone with database access.

And the recompute is tightly scoped: when a match is corrected, exactly the tips on that one match and exactly the affected matchdays and tables are recomputed — no other match, no other league. Your tips themselves are never touched. Only the points for the one corrected match are re-awarded; everything else stays character for character as it was.

What you see: „Matchday 7 recalculated after an official correction“

When an already-published table changes, you see exactly that — a note above the table, not a silently jumped number. Every correction that moves a standing you’ve already been shown writes a note and shows it to you:

• „Matchday 7 was recalculated after an official correction.“
• „Matchday 7 was recalculated after a VAR decision.“
• „A postponed match was added — matchday 7 updated.“

The affected tip also shows „points changed“, and the reason always traces to a concrete event — nothing happens anonymously. You see not just that something changed, but why, where, and that your tips are safe.

And when we still get it wrong

Even the most careful build doesn’t rule out a mistake of our own — so we wrote down beforehand what we do then. No promise never to be wrong, but a firm plan for when we are.

• If the data runs wrong (not merely late), we halt scoring rather than serve a wrong table. A stale state is fine and catches itself back up; a wrong one never is. While we’ve halted, you honestly see „Paused“ — not a live tick over a frozen number.
• We tell the affected league ourselves. When a standing that was already up changes, the league hears it from us — before a member asks. We never change a standing silently; the log makes silence a choice, so the rule is to speak.
• We show the receipt: which match, old → new, which matchday — and that the tips were never touched.
• If it was our bug, we say so plainly — not „the data source was at fault“. A bug on our side is our bug.
• And we never fake a certainty we don’t have. „We don’t know yet“ is allowed and honest. A confident wrong answer is not.

On matchday your table should simply be right — and on the rare day something isn’t, you should see exactly what we do.

If you’re planning a league right now and want to know which decisions come first — matches, people, points, deadline, invites, missed matchdays — they’re here: How to set up a prediction game.

You can’t create your league on Tipperoo yet; we launch with the season. Today you can already seal a Saison-Orakel — a short prediction for the WhatsApp group, 30 seconds, no account needed. And sign up for the waitlist; we’ll tell you in good time.

The correction and confirmation flows described here reflect how Tipperoo is built (as of 29 July 2026). „VAR“ refers to general football matters. Not affiliated with the DFL, the Bundesliga or the Premier League.