Game Report Recorder Context

Goal

After club submission, the game report recorder takes over the concrete game report. They find released games, check both team pages, add missing on-site information, enter result, periods, events and add-on sheets, and submit the report for review.

This chapter describes the work in Record game day and in the cockpit Game report maintenance. Club managers use this chapter to understand what happens after their own team-page submission.

Role and Permission

Access is created in two ways:

Direct References

Prerequisites

Subsections

Example Games

The demo contains prepared games for different states. Use these cases when you want to follow the workflow.

8.1Open Games for Recording

Goal

The game report recorder finds all games they are currently allowed to work on. The page separates individual club releases from broader league assignments for a game day and venue. The concrete cockpit opens dynamically under /admin/game-report-workflow/seasons/.../league/.../games/...; always use the action Record or Create, not a manually assembled path.

Workflow

1. Sign in with an account that may record game reports.
2. Switch to the workspace Referee / Official / Recorder if several workspaces are available.
3. In navigation, open Record game day (path: /admin/game-report-recording).
4. Check the table Released games.
5. Check the table Game-day/venue assignments.
6. Open a concrete game with Record or Create.
7. If you come through a game-day/venue assignment, click Open first and then Record or Create on the matching game.

Controls

If both tables are empty, either the club release or a league assignment is missing. Then the club must set a game report recorder in game registration, or league administration must add a game-day assignment.

Expected Result

• Record game day is visible in the matching workspace.
• At least one released game or one game-day/venue assignment is visible.
• The matching game opens through Record or Create in Game report maintenance.

8.2Understand Game Report Cockpit

Goal

The cockpit is the central workspace for one concrete game. At the top it shows matchup, league, date, game status, result and game report status.

Areas

A reviewed game report is locked. Editing actions are then disabled and the interface shows Game report reviewed - editing locked. Editing becomes possible again only when league administration sets the report status to correction required. In this state, team pages show for example View lineup, View coaches or Locked; delete and remove actions are disabled.

Expected Result

• Header area and status badges are understandable.
• The four cockpit areas can be reached through the area navigation.
• A locked report is not edited further.

8.3Check Team Pages

Goal

The game report recorder checks home and away team pages before result and events are entered. This is about the game-day snapshot, not permanent club master data.

Workflow

1. In the cockpit, open the area Team registrations.
2. Check the status cards for home team and away team.
3. Compare the number of lineup entries and coaches per team page.
4. If needed, open Edit lineup, Record on site, Check coaches or Add coach.
5. Check whether coach requirement is active and whether warnings are shown.
6. Check whether a person is both player and coach of the same team page. Such conflicts are marked in the lineup.

Team Page Status

Expected Result

• Home and away team pages are checked.
• Missing or inconsistent information is identified.
• Coach-requirement warnings and player-coach conflicts are classified.

8.4Add On-Site Information

Goal

If a team page is empty or incomplete, the game report recorder adds the actual lineup and coach information on site.

Workflow

1. In Team registrations, open the affected team page.
2. Use Record on site or Edit lineup.
3. Put eligible people into the lineup.
4. Enter jersey number and position as far as known on game day.
5. Click Save and back.
6. Use Add coach if a coach must be added on site.
7. Remove wrong coaches only when it is certain that the entry should not count for the team page.

Special Cases

The game report recorder corrects the game-day snapshot with this. They do not replace permanent club master-data maintenance.

Expected Result

• Missing lineup or coaches are added to the game report.
• The number of players and coaches in the cockpit matches the game day.
• Permanent master-data corrections remain recognizable as separate club work.

8.5Lock or Reopen Late Submission

Goal

After the on-site check, a team page can be completed or opened for another correction.

Use Lock late submission/change when the team page is considered complete on game day. Use Reopen when another correction by club or recorder is needed.

Expected Result

• Team-page status was set consciously or left unchanged.
• Locked team pages are reopened only when a functional correction is needed.

8.6Enter Result

Goal

The result describes the final score and the game status. It is not final table approval yet.

Workflow

1. Open the area Result.
2. Enter Home goals and Away goals.
3. Set the Game status to match the actual game course.
4. Set the Result status to match the work state, for example Provisional.
5. Select the Result type if it is known.
6. Save with Save result.

Result Fields

For later final approval, a confirmed final result must functionally match the period totals. This hard validation belongs to the league decision, not to first entry.

Expected Result

• Final score and status are saved.
• Result data appears in the cockpit header.
• The report remains functionally provisional until the league decision.

8.7Enter Periods

Goal

Periods explain the path to the final score. They are saved in addition to the final result.

Workflow

1. Open the area Periods.
2. Click Create period.
3. Select the period, for example 1st period, 2nd period, 3rd period, Overtime or Penalty shootout.
4. Enter home and away goals for the period.
5. Set sorting if needed.
6. Save and return to the game report.
7. Repeat the step for all played periods.

If overtime or penalty shootout is relevant, it is added as its own period or as an additional add-on sheet.

Expected Result

• All played periods are recorded clearly.
• The period totals functionally match the saved final score.

8.8Enter Events

Goal

Events document goals, penalties and timeouts in the structured game report.

Workflow

1. Open the area Events.
2. Click Create event.
3. Select the type Goal, Penalty or Timeout.
4. Select home or away team.
5. Select the period and enter minute and second as far as known.
6. Select Person 1 or enter a Person 1 snapshot.
7. Add Person 2, Jersey number, Penalty code, Code version and Penalty minutes if needed.
8. Save and return to the game report.

For penalty events, penalty details are functionally required. For goals or timeouts, the matching game, team, time and person information is sufficient.

Expected Result

• Goals, penalties and timeouts are visible as events.
• Penalty events contain understandable penalty details.
• Events are assigned to the matching team page and period.

8.9Enter Add-On Sheets

Goal

Add-on sheets record information that is not sufficiently covered by a normal event.

Workflow

1. Open the area Add-on sheets.
2. Select the matching action.
3. On the form page, check type and game ID.
4. Fill Sorting, Document path and type-specific fields as far as needed.
5. Add an understandable note in Additional content.
6. Click Save and back.
7. In the cockpit, check whether the summary is understandable.

Expected Result

• Required additional information is saved in the matching add-on sheet.
• Document references can be found.
• The summary in the cockpit is understandable.

Mandatory Information

8.10Submit Report

Goal

The game report recorder hands the completed report over to referee review and league administration.

Workflow

1. In the cockpit, check the Review chain.
2. Check team pages, coaches, lineup, result, periods, events and add-on sheets.
3. Open Review & completion.
4. In the card 1. Submit game report, click Submit game report.
5. Check that the report status then shows Submitted.

After submission, the report is visible to referee review and league administration. Reports that are already submitted or reviewed cannot be submitted again.

Expected Result

• Report status is Submitted.
• The report is visible for referee review and league decision.
• The game report recorder changes the report afterwards only when the league opens it for correction.

8.11Classify After Submission

Goal

After submission, the normal entry step is complete. Further decisions happen in separate review contexts.

If an error is noticed after submission, the report is not simply submitted again. League administration sets it to correction required or reopens the affected team page.

Expected Result

• Referee review, league decision and table effect are separate.
• Corrections run through Correction required or a reopened team page.
• Approved data is the basis for table and statistics.

Checklist

Typical Mistakes

• If no game is visible, a club release or league assignment is usually missing.
• If Create appears instead of Record, no game report exists for the game yet.
• If a team page is locked, it must be reopened before changes.
• If coach-requirement warnings appear, check active coach profiles, coach license and whether the person is already entered as player on the same team page.
• If period totals later do not match the final score, the league cannot finally approve the report.
• If Submit game report is disabled, the report is already submitted or reviewed.

Expected Result

• Subsection 8.1 is done when a game report recorder uses the entry through Record game day and can open an own game report cockpit.
• Chapter 8 is done when the game report recorder checks team pages, adds missing on-site information, records report data structurally and hands the report over to referee and league review.
• Club, referee review, league decision, tables and statistics remain understandable as separate downstream contexts.