Club Game Operations
Goal
Club game operations cover everything a club prepares for league participation and game day: team registrations, league player lists, referees and officials, referee season registrations, coach/license interpretation, proxy availability, game registrations and team pages.
Role and Permission
- Club administrator for club-wide submissions and corrections.
- Team manager for assigned team workflows where configured.
- League administration as downstream review and decision body.
Prerequisites
- Club workspace is active.
- Club master data, teams, people, roster players, coaches and officials are prepared.
- Season and leagues exist.
- League administration has opened the relevant registration windows or workflows.
Chapter Overview
| Section | Topic |
|---|---|
| 5.1 | Register and manage teams for a league |
| 5.2 | Prepare league player list |
| 5.3 | Prepare referees, officials and recorders |
| 5.4 | Referee registrations for the season |
| 5.5 | Classify coach requirement and licenses |
| 5.6 | Set referee availability by proxy |
| 5.7 | Prepare game registrations and team pages |
5.1Register and Manage Teams for a League
5.1.1Goal and Context Switch
The club submits one of its teams for a concrete league. League administration later reviews the registration. The team is not considered approved until the league decision is complete.
5.1.2Example Data
| Club | Team | League |
|---|---|---|
| Feldberg Füchse | Feldberg Füchse U13 | U13 Lichtungsliga |
| Tannenhang Dachse | Tannenhang Dachse U16 | U16 Tannenliga |
| Kinzigtal Kauze | Kinzigtal Kauze Offen | Offene Waldliga |
5.1.3Register Team
- Sign in as club administrator.
- Switch to the club workspace.
- Open
League registrations. - Select season and league.
- Choose the team.
- Add a note if needed.
- Submit the registration.
5.1.4Club Check After Submission
Check that the registration appears with the expected status and that the selected league, team and club are correct.
5.1.5Further Team Actions
| Action | Use |
|---|---|
| edit draft | correct data before submission |
| submit | hand over to league review |
| withdraw / cancel | remove a registration according to workflow rules |
| respond to correction | adjust the registration and resubmit |
5.1.6Classify League Reaction
| League decision | Meaning for the club |
|---|---|
| Approved | team can be used in league player lists and schedule contexts |
| Correction required | club must change or clarify data |
| Rejected | team is not admitted for this league |
5.2Prepare League Player List
5.2.1Goal and Context Switch
The club submits players from the team roster to the league player list. The league decides whether each registration is accepted.
5.2.2Example Data
Use prepared roster players such as Nilo Fuchsfarn, Tilda Quellenstern, Kora Kauzbach or Mika Murmelschilf depending on team and league.
5.2.3Open Player List
- Open
Player lists. - Select season, league and team.
- Check existing registrations and their statuses.
5.2.4Register Player
- Select a roster player.
- Enter jersey number and position if required.
- Check license hints.
- Submit or save according to workflow state.
5.2.5Deregister Player
Use deregistration only when a player should no longer belong to the league list. Keep a note if the reason must be visible for league administration.
5.2.6Club Check After Saving
The list must show the expected player, status, jersey number, position and license hint. Approval remains a league decision.
5.3Prepare Referees, Officials and Recorders
5.3.1Goal and Boundary
The club prepares people who may later act as referees, timekeepers, officials or game report recorders. This preparation does not itself create a concrete game assignment.
5.3.2Example Data
| Role | Example |
|---|---|
| Referee | Oak Referee |
| Timekeeper | prepared club official |
| Game report recorder | scorer.waldrand@example.test |
5.3.3Create Referee / Official Profile
- Open the club person or official profile area.
- Select the person.
- Activate the relevant profile or role.
- Maintain license or qualification hints if available.
- Save.
5.3.4Check Roles and License Hints
License hints support planning but do not replace the league decision or assignment. Referee assignment later checks availability, role conflicts and actual game-day needs.
5.4Referee Registrations for the Season
5.4.1Goal and Context Switch
The club submits prepared referee profiles to the season pool. League administration or referee assignment reviews them.
5.4.2Register Referee for Season
- Open
Referee registrations. - Select the season.
- Select the prepared referee profile.
- Add notes if needed.
- Submit the registration.
5.4.3Club Check After Submission
Check status, season, person, club and note. A submitted referee is not automatically approved.
5.4.4Further Actions
| Action | Meaning |
|---|---|
| edit draft | change before submission |
| submit | send to league review |
| respond | answer a correction request |
| withdraw | remove the registration if allowed |
5.5Classify Coach Requirement and Licenses
5.5.1Goal and Boundary
The club understands whether the league requires coaches and whether prepared coach/license data can support later team-page submission. License decisions remain in the review-office workflow.
5.5.2Check Club Data
- Check active coach profiles.
- Check license hints and validity.
- Check whether the league requires coaches.
- If a license is missing, use the license application workflow.
5.5.3Downstream Contexts
| Context | What happens there |
|---|---|
| Coach context | read coach pool and license hints |
| License and review office | apply for and decide licenses |
| Game report recorder context | select coaches on the concrete team page |
| Review & approval | classify warnings before final report decision |
5.6Set Referee Availability by Proxy
5.6.1Goal and Boundary
The normal case is that referees and officials maintain their own availability. The club may enter availability by proxy when the feedback was received outside the system.
5.6.2Workflow in Club Workspace
- Open
Open tasks>Referee availability. - Select season and person.
- Open the relevant date and venue.
- Set
Available,Not availableorUnknown. - Add a note that the entry was made by proxy if useful.
- Save.
5.6.3Checklist
| Check | Done |
|---|---|
| Correct person selected. | [ ] |
| Date and venue match the feedback. | [ ] |
| Status reflects the real answer. | [ ] |
| Proxy note is understandable. | [ ] |
5.7Prepare Game Registrations and Team Pages
5.7.1Goal and Functional Boundary
Before game day, the club prepares its team page for a concrete game. It selects coaches, lineup and optionally a game report recorder. After submission, the recorder and later review contexts continue the workflow.
5.7.2Prerequisites
| Prerequisite | Meaning |
|---|---|
| Game exists | schedule was prepared by league administration |
| Team registration approved | club team belongs to the league |
| Player list prepared | selectable players exist |
| Coaches prepared | coach selection and requirement warnings can be checked |
| Recorder pool prepared | game report recorder can be selected if needed |
5.7.3Open Game Registrations
- Open
Game registrations. - Select season and league.
- Find the relevant game.
- Open the team page for home or away side.
5.7.4Create Team Page
Create the team page if it does not yet exist. Check matchup, date, team side and status before entering data.
5.7.5Enter Coaches
- Open the coach area.
- Add prepared coaches.
- Check coach requirement warnings.
- Save.
5.7.6Set Game Report Recorder
Select a prepared recorder from the club pool for this concrete game if the club is responsible for providing one. League-side game-day assignments remain a separate access path.
5.7.7Save Lineup
- Add players from the league player list or available snapshots.
- Maintain jersey numbers and positions.
- Check player-coach conflicts.
- Save and return to the cockpit.
5.7.8Submit Team Page
Submit when lineup and coaches are ready for game day. After submission, changes are possible only through the allowed correction or reopen path.
5.7.9Status and Downstream Context
After club submission, the Game report recorder context continues. There, both team pages are checked, on-site data is added and the actual game report with result, periods, events and add-on sheets is recorded.
5.7.10Checklist
| Check | Done |
|---|---|
| Correct game and team side opened. | [ ] |
| Coaches entered or warning understood. | [ ] |
| Game report recorder selected if needed. | [ ] |
| Lineup saved. | [ ] |
| Team page submitted or intentionally left in draft. | [ ] |
| Next context is understood. | [ ] |
Expected Result
The club can register teams, maintain league player lists, prepare officials and referees, submit referee registrations, classify coach/license needs, set proxy availability and prepare team pages for game day.
Typical Mistakes
- Confusing team roster with league player list.
- Assuming submitted registrations are already approved.
- Forgetting license or coach requirement warnings.
- Selecting the wrong season, league, game or team side.
- Expecting a team page to stay editable after submission or final review.
Review Criteria
- Club submissions reach the correct league-review contexts.
- League player and referee registration statuses are understandable.
- Game-day team pages can be handed over to the game report recorder context.