upload fixtures referees import

Weekly upload — fixtures and referee marks

How the fixture export and the referee export are loaded, what is read from each, and the order they must go in.


Nothing is written until you approve a preview

Both uploads are two steps: Preview, then approve. The file is held between the two, so what gets committed is byte-for-byte what you previewed — not whatever a second upload happened to contain.

The fixture export

Fixture export (.csv or .xlsx) — the league’s own export, the one whose columns begin Fixture ID, Season, Division, Competition.

The division structure is read out of the file. A team appearing in a division’s fixture is a team in that division, and a division that does not yet exist at that age group is created. There is no separate roster to maintain.

Only Home Score and Away Score are read. Half-time, extra-time and penalty columns are ignored: the ninety-minute score is what drives standings and ratings, and extra time and penalties settle cup progression only. The preview lists the ignored columns by name so you can confirm they were skipped rather than missed.

Withdraw teams that have no fixtures in this file

Tick box. Off by default. Marks as withdrawn any team the file does not mention.

Only tick it for a full league export. Against a partial file — one division, one week — it would withdraw every team the file omits, which is almost the whole league.

The referee export

Referee export (.csv or .xlsx) — the REFEREE export, marked by both clubs.

This file is not valid CSV, and the portal handles it deliberately rather than rejecting it. The two Reasons For Low Mark columns contain commas and line breaks and are not quoted. A conforming reader does not merely lose the comment: it reads the rest of the row shifted by a column, and a score ends up in the Referee column — which is how referee names like “4” and “0” appear in a naive import.

Instead the reader finds record boundaries by the fixture id, anchors the structured columns from both ends, and lets the comment absorb the middle. Anything that still does not add up is reported with its line number rather than imported: a mark recorded against the wrong referee is worse than a mark that is missing.

Upload fixtures before referee marks

Marks tie back to a fixture through the export’s own Fixture ID — the same identifier the fixture file carries. Upload the fixtures for a period before the referee marks for that period, or the marks will have nothing to attach to.

Previous uploads

Every upload is recorded: when, which file, who by, and the counts — rows read, teams new, teams moved, teams withdrawn, divisions touched, plus a note of what was written.

The production log currently shows one upload: FIXTURE_39548.csv, 8,130 rows, 1,023 new teams, 95 divisions, 8,086 fixtures and 878 results written.

Starting again from week one means purging first — see Purging league data. A purge clears clubs, teams, divisions, fixtures and results but keeps the league, its seasons, its age groups and their banding policies.