Answers built for real CTBA workflows

Some accounts are intentionally light: after sign-in they see read-only modules such as fixtures, results, standings, teams, and news—useful for supporters, alumni, or sponsors who should not edit rosters or finances but may need an authenticated view because of visibility rules.

Association-level roles create competitions and manage their lifecycle. Clubs enter teams through registrations and approvals workflows in the dashboard. Once teams are confirmed, those sides become eligible for fixture generation, match operations, and standings. Status fields on competitions and registrations make it clear what still blocks participation.

Association staff maintain venues and use them when scheduling. Fixtures can be generated in structured batches (for example round-robin) from confirmed teams, time windows, venues, and rules, then edited (tip-off, venue, publish, postpone, cancel) by authorised roles. Typical fixture states include draft, scheduled, published, live, postponed, completed, and cancelled. Club logistics views consume the published schedule for match-day preparation.

Scores and forfeit or overtime flags live on the match record tied to each fixture. When matches are completed and results finalised, competition standings are rebuilt automatically so ladders reflect real games. The same data can feed public results and standings pages while hiding anything not marked for publication.

A transfer moves a player’s registration from one CTBA club to another inside an active transfer window. The player or an authorised person submits a request; the releasing club approves; the receiving club confirms; association administrators advance the case; the president may approve or reject at the executive gate when your rules require it; clearance is recorded and the transfer becomes active on its activation date. While a transfer is pending or under post-clearance lock, roster and lineup rules may block match selection to protect competition integrity.

Requests fail if no window is open, if the club has exhausted per-window limits on mid-season windows, if another transfer is already in progress for that player, or if the player has outstanding fees (waived for emergency windows). Players under eighteen require recorded parent or guardian acknowledgement, and date of birth must be on file for age checks.

The association models fees and invoices at association, club, team, or player level depending on configuration. Clubs and teams pay or upload proof of payment (POP) against those obligations. Treasurers review POP queues, approve or reject with reasons, and finance activity leaves an audit trail. Categories can include registration, league entry, team fees, fines, referee payments, and more—exact products depend on how CTBA configured billing.

Documents attach to owners such as the association, a club, a team, a competition, or a player profile. Upload and download rights mirror dashboard permissions: operational staff see what they need for their job; the public only sees items explicitly published for anonymous download. Competition-specific document endpoints also exist where enabled.