Reading the statistics
Everything on the analysis screens is derived from the recorded events. Nothing is typed in twice.
One source of truth
Radjeno stores no score column, no goal tally, no shooting percentage. It stores the event log — what happened, to whom, and when — and every number on every screen is computed from it. That is why correcting a mistake on a match timeline corrects the player page and the season table at the same time, and why the two can never disagree.
A match
A recorded match opens on four tabs:
- Summary — the score, how it progressed, and each side's totals.
- Players — what each player on the team sheet did: goals, shots, saves, and the rest of the catalogue.
- Shots — where shots were taken from, if zones were recorded.
- Timeline — every event in order. This is also where a mis-tap is corrected.
Players
A player's page gathers everything the log names them in, across the season: their shooting, their discipline, and how their contribution moved from match to match.
Keepers are found by what they did, not by a position column. Whether a player appears under Goalkeepers is decided by whether they have saves or goals conceded — which is the only rule that works for a keeper who is a left back next week.
The season
The team screen aggregates the whole season: results, totals, and trends across the matches played. Fixtures with a typed-in final score are included, because they were played — they simply contribute a score and no player detail.
Correcting a match
Mis-taps happen at speed on a sideline. Open the match, go to Timeline, and fix the event there. Because every screen reads the log rather than a stored summary, the correction reaches the player pages and the season table immediately.