Referee Ombuds Office Context

Goal

The referee ombuds office context explains how review office and league administration functionally close a submitted game report. The focus is the review chain in the game report cockpit, referee feedback, correction returns and the final league decision.

This chapter is not an instruction for entering the game report. Report data is maintained in the game report recorder context; here the decision is made whether the report goes back for correction or counts as reviewed.

Role and Permission

Direct References

Prerequisites

Subsections

Example Games

The examples help with trying the workflow in the demo application. In a real season, use your own games, people and venues.

10.1Review Game Report and Make League Decision

Goal

The league decision answers a functional question: can the submitted game report stand as it is, or must it be returned for correction with a concrete note?

Referee feedback is a review signal. An objection does not automatically return the report, and open feedback does not technically block the league decision. Review office or league administration must consciously classify open, confirmed or objected feedback.

Workflow

1. Sign in as review office, league administration or an authorized association role.
2. Switch to the association workspace.
3. In navigation, open Review & approve and then Review game reports.
4. Select season and league.
5. Open the game report cockpit for the matching game.
6. Switch to Review & completion.
7. Read the Review chain first.
8. If needed, open the detail anchors Submission, Referee review and League decision.
9. Evaluate referee feedback and report data.
10. Decide between Correction required and Set as reviewed.

Path note: /admin/game-report-workflow

Read Review Chain

The Review chain connects submission, referee review and league decision. The tiles jump directly to the matching cockpit areas.

The review chain recommendation names the next useful step:

Evaluate Referee Feedback

In 2. Referee review, the league sees all feedback for assigned referees.

Check an objection against result, periods, events, lineup, coach entries and add-on sheets. If the objection has been functionally resolved, you can record that in the decision comment and still approve the report.

Set Correction Required

Use Correction required when the report should be reworked by the game report recorder.

1. In 3. Make league decision, open the Correction note field.
2. Describe concretely what must be changed or added.
3. Click Correction required.
4. Check that the review chain then shows Correction in progress or a correction status.

The Correction note is mandatory. It must be concrete enough for the game report recorder to act without another question.

Review Correction Again

After a correction return, the game report recorder edits the report and submits it again. Then you review the same report again in the game report cockpit.

A correction loop should stay short. If the rework is not functionally sufficient, the new correction note must be more precise than the previous one.

Set Report as Reviewed

Use Set as reviewed when the report can be functionally closed.

1. Check the review chain.
2. Check result, team data, events and add-on sheets.
3. Check referee feedback and comments.
4. Add a Comment (optional) if needed.
5. Click Set as reviewed.
6. Check that the review chain shows Completed or status Reviewed.

Final review means: from the league's perspective, the report is closed. Normal entry actions are locked afterwards.

Understand Locking Effect

A finally reviewed report affects several downstream contexts.

If an error is discovered after final review, this is no longer a normal referee-feedback process. The league must consciously decide whether a formal correction, administrative change or separate communication is needed.

Controls

Typical Mistakes

Checklist

Expected Result