Reports, referee marks and publications
The exception report for missing results, the referee marks view and its flagging thresholds, and how a structure is handed to the county.
Reports — results not entered
/Members/Reports. Four tiles — results outstanding, divisions affected, the age of the oldest, and how many reports exist — above a table of every division with a fixture whose date has passed and no result recorded.
Columns: age group, division, outstanding, recorded, played to date, the oldest outstanding date, and a Which ones link to the individual fixtures.
Production currently shows 31 outstanding across 21 of 95 divisions, the oldest 10 days old.
Why this has a report of its own
A missing result announces itself nowhere else. The rating engine has nothing to rate those two teams on, and the review reports them as reduced evidence rather than saying a result is missing — so an unreported score quietly makes a banding review less sure of itself without ever saying why. Found in week two it is a phone call; found in March it has already shaped a season’s structure.
Referee marks
/Members/Referees. Marks arrive from the referee export and are shown per referee, with runs of low marks flagged.
Two inputs control the flagging, and both take effect on Apply:
| Field | Accepts | Default | Meaning |
|---|---|---|---|
| Flag marks at or below | 0–100 | 60 | The mark at or beneath which a game counts as a low mark. Marks come from both clubs and are averaged per game. |
| for this many games in a row | 1–20 | 3 | How many consecutive low games make a run worth flagging. One poor mark is a bad afternoon; three in a row is a pattern. |
The page reports “No referee marks have been uploaded” until a referee export has been loaded. At Warrington that is still the case — the fixture export has been uploaded, the referee export has not.
Structure publications and the handover
/Members/Publications. A publication records every division, its teams, its size, its effective date and its version. One is created when the committee ratifies a banding review, or when the season’s opening structure is agreed.
The handover is manual by design of the county’s process. There is no API to push to and no endpoint to pull from. The artefact is an Excel workbook, generated here and keyed in by a person at the other end. Two things follow from that, and both are visible in the product:
- Every restructure costs a human transcription, which is why the workbook’s Changes sheet lists only the teams that moved rather than the whole structure.
- Manual keying introduces transcription errors, which is why divergence detection runs on every sync after a publication rather than being an optional extra.
A divergence is a mismatch between what was published and what came back: a team playing in a division it was not placed in, a team placed with no fixtures generated, or fixtures for a team that withdrew. Found in week two it is an email; found in March it is a lost season.
No structure has been published for the current season yet.