LigaWerk

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 Spielrunde is 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 typeTypical workspaceOperational effect
Association administratorAssociationbroad association administration
League administrationAssociationseasons, leagues, registrations, games, results
License office / review officeAssociationlicense applications and license register
Referee assignmentAssociationreferee registrations, availability and assignments
Board / office / committeeAssociation contact contextfunctional 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

FieldValue
NameWaldLiga 2026
AssociationZauberForest Spielrunde
StatusActive
Start / endaccording to demo scenario

Workflow

  1. Open Seasons.
  2. Click Create Season.
  3. Select association, name, status and date range.
  4. Save.
  5. Check the public competition page after leagues exist.

Typical Mistakes

SituationMeaning
Season not selectable laterstatus or association is wrong
Season invisible publiclyno active leagues or teams exist yet
Duplicate seasonexisting 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

LeagueSeasonCoach requiredMode
U13 LichtungsligaWaldLiga 2026Yesregular league
U16 TannenligaWaldLiga 2026Yesregular league
Offene WaldligaWaldLiga 2026Noregular league

Workflow

  1. Open Leagues.
  2. Click Create League.
  3. Select season and association context.
  4. Enter name, short name, mode and status.
  5. Configure coach requirement and age/eligibility settings if available.
  6. Save.
  7. 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

  1. Open League registrations or the league-team management area.
  2. Filter by season and league.
  3. Open submitted registrations.
  4. Check club, team, league, notes and eligibility.
  5. Decide: approve, reject or request correction.
  6. Add a concrete note when the club must act.
  7. Check public effect after approval.

Checklist

CheckDone
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

  1. Open player-list or player-registration review for the season and league.
  2. Filter open submissions.
  3. Check person, club membership, team assignment, jersey number, position and license hints.
  4. Approve, reject or request correction.
  5. Use a concrete note for rework cases.
  6. 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

  1. Open referee registrations for the season.
  2. Filter submitted or open registrations.
  3. Check person, club, referee profile, license hint and notes.
  4. Approve, reject or request correction.
  5. Confirm that approved referees become available for assignment planning.

Checklist

CheckDone
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 / signalMeaning
Personlicense holder
Type and scopeplayer, coach, referee, timekeeper or other configured scope
Statusdraft, submitted, approved, rejected or archived depending on workflow
Validitydate range and expiry state
Usabilitywhether 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

PrerequisiteMeaning
Season and leagues existgames need a competition context
Clubs and teams existhome and away teams can be selected
Team registrations are approvedgames should use confirmed league teams
Venues existdates 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

  1. Open Games.
  2. Select season and league.
  3. Create or open the game.
  4. Check home team, away team, date, time and venue.
  5. Set game status and result status consciously.
  6. 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.

  1. Open the game-day assignment area.
  2. Select season, date and venue.
  3. Select the recorder person.
  4. Save.
  5. Check that the person sees the assignment in Record game day.

3.8.6Effect for Downstream Contexts

Downstream contextWhat depends on the schedule
Club game operationsteam pages and game report recorder release
Referee contextavailability, assignments and briefings
Game report recorderreport cockpit and game-day recording
Review & approvalsubmitted report and final decision
Tables / statisticsreviewed 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

CheckDone
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.