Association Context
Goal
League administration works in the association context. This chapter creates the functional competition structures: season, leagues, registration review, license-register checks, schedule, game-day assignments and ongoing league operations.
Role and Permission
- Association administrator for association master data and full association administration.
- League administration with the function type
League administration. - Referee lead or referee assignment for referee registrations and assignments.
- Administrator for the global register view.
Prerequisites
- Admin initial setup is complete.
- Association
ZauberForest Spielrundeis active. - The league-management access from initial setup works.
- You are signed in to the Admin area in the association workspace.
3.1Understand Association Roles and Review Rights
Goal and Access
Understand which association functions grant operational rights and which functions only document responsibility, contact persons or committees.
This distinction matters before seasons, leagues, registration decisions, license register and referee assignment are maintained. A person may be listed as board member, office contact or committee member without automatically being allowed to edit competition, license or referee workflows.
Role Matrix
| Function type | Typical workspace | Operational effect |
|---|---|---|
| Association administrator | Association | broad association administration |
| League administration | Association | seasons, leagues, registrations, games, results |
| License office / review office | Association | license applications and license register |
| Referee assignment | Association | referee registrations, availability and assignments |
| Board / office / committee | Association contact context | functional contact only unless configured otherwise |
Typical Mistakes
- Treating a contact function as an admin permission.
- Giving broad association administration when a focused review role is enough.
- Forgetting that access also depends on active person and active function.
3.2Create Season
Goal and Access
Create the season that groups leagues, registrations, games, results and public tables.
Example Data
| Field | Value |
|---|---|
| Name | WaldLiga 2026 |
| Association | ZauberForest Spielrunde |
| Status | Active |
| Start / end | according to demo scenario |
Workflow
- Open
Seasons. - Click
Create Season. - Select association, name, status and date range.
- Save.
- Check the public competition page after leagues exist.
Typical Mistakes
| Situation | Meaning |
|---|---|
| Season not selectable later | status or association is wrong |
| Season invisible publicly | no active leagues or teams exist yet |
| Duplicate season | existing season was not reused |
3.3Create Leagues
Goal and Access
Create the leagues inside the season. League settings control age logic, coach requirement, mode and later public table behavior.
Example Data
| League | Season | Coach required | Mode |
|---|---|---|---|
| U13 Lichtungsliga | WaldLiga 2026 | Yes | regular league |
| U16 Tannenliga | WaldLiga 2026 | Yes | regular league |
| Offene Waldliga | WaldLiga 2026 | No | regular league |
Workflow
- Open
Leagues. - Click
Create League. - Select season and association context.
- Enter name, short name, mode and status.
- Configure coach requirement and age/eligibility settings if available.
- Save.
- Check that the league appears in league-management selections.
Public Check
Public display becomes meaningful only after confirmed team registrations and games exist. A newly created league may therefore be technically correct even when it has no public table yet.
3.4Review Team Registrations
Goal and Context Switch
League administration reviews club submissions for teams that want to participate in a league. The club creates the registration; league administration confirms, rejects or requests correction.
Workflow
- Open
League registrationsor the league-team management area. - Filter by season and league.
- Open submitted registrations.
- Check club, team, league, notes and eligibility.
- Decide: approve, reject or request correction.
- Add a concrete note when the club must act.
- Check public effect after approval.
Checklist
| Check | Done |
|---|---|
| Correct season and league selected. | [ ] |
| Submitted team belongs to the expected club. | [ ] |
| Duplicate registrations are avoided. | [ ] |
| Decision note is clear when action is required. | [ ] |
| Approved team appears in the expected follow-up context. | [ ] |
3.5Review Player Registrations
Goal and Context Switch
League administration reviews players submitted by clubs for league player lists. The review confirms whether a player may be used for this league team.
Workflow
- Open player-list or player-registration review for the season and league.
- Filter open submissions.
- Check person, club membership, team assignment, jersey number, position and license hints.
- Approve, reject or request correction.
- Use a concrete note for rework cases.
- Check that approved players appear in the team's league player list.
Typical Mistakes
- Reviewing the wrong season or league.
- Treating a club roster player as automatically league-approved.
- Ignoring missing or questionable license hints.
3.6Review Referee Registrations
Goal and Context Switch
Clubs submit referee profiles for the season. League administration or referee assignment confirms whether the person belongs to the season pool.
Workflow
- Open referee registrations for the season.
- Filter submitted or open registrations.
- Check person, club, referee profile, license hint and notes.
- Approve, reject or request correction.
- Confirm that approved referees become available for assignment planning.
Checklist
| Check | Done |
|---|---|
| Referee profile exists and is active. | [ ] |
| Club and season are correct. | [ ] |
| License hint is understood. | [ ] |
| Decision note is clear when correction is needed. | [ ] |
| Approved profile appears in assignment context. | [ ] |
3.7Check License Register
Goal and Access
Use the license register to understand existing licenses and their usability before deciding player, coach, referee or timekeeper workflows.
Read the Register
| Column / signal | Meaning |
|---|---|
| Person | license holder |
| Type and scope | player, coach, referee, timekeeper or other configured scope |
| Status | draft, submitted, approved, rejected or archived depending on workflow |
| Validity | date range and expiry state |
| Usability | whether the license can currently support the target workflow |
Typical League Checks
- Does the player have a relevant license?
- Is a coach license available when coach requirement is active?
- Does the referee or timekeeper have a usable qualification hint?
- Is a document or review note still open?
3.8Prepare Schedule and Game Days
3.8.1Goal and Access
Prepare games so later contexts can assign referees, send briefings, collect team pages, record game reports and calculate tables.
3.8.2Prerequisites
| Prerequisite | Meaning |
|---|---|
| Season and leagues exist | games need a competition context |
| Clubs and teams exist | home and away teams can be selected |
| Team registrations are approved | games should use confirmed league teams |
| Venues exist | dates and locations become assignable |
3.8.3Understand Demo Schedule
The demo schedule contains normal games, upcoming games, correction cases, rescheduling/cancellation cases and final-review examples. Use the prepared game IDs from the demo scenario when testing downstream workflows.
3.8.4Create or Check Game Manually
- Open
Games. - Select season and league.
- Create or open the game.
- Check home team, away team, date, time and venue.
- Set game status and result status consciously.
- Save.
3.8.5Prepare Game-Day Assignments
Game-day / venue assignments release a game report recorder for all games at a date and location. They do not replace individual club releases for a single game but provide a league-side access path for game-day operation.
- Open the game-day assignment area.
- Select season, date and venue.
- Select the recorder person.
- Save.
- Check that the person sees the assignment in
Record game day.
3.8.6Effect for Downstream Contexts
| Downstream context | What depends on the schedule |
|---|---|
| Club game operations | team pages and game report recorder release |
| Referee context | availability, assignments and briefings |
| Game report recorder | report cockpit and game-day recording |
| Review & approval | submitted report and final decision |
| Tables / statistics | reviewed result data |
3.8.7Project-Team Note: Reset Demo Schedule
Resetting the demo schedule is an internal project-team operation. Do not put seed/reset mechanics into end-user instructions. After any reset, smoke the public competition pages, game report cockpit and the prepared scenario games.
3.8.8Checklist
| Check | Done |
|---|---|
| Season and league are correct. | [ ] |
| Home and away teams are confirmed league teams. | [ ] |
| Date, time and venue are set. | [ ] |
| Game status matches the scenario. | [ ] |
| Game-day recorder assignments are set where needed. | [ ] |
| Downstream pages can open the game. | [ ] |
Outlook
After association setup, clubs continue with their own master data, teams, player lists, referee registrations and game-day submissions.