Running Match Day
Four workspaces carry the operational load once matches exist: Facilities & Venues, Scheduler, Command Center, and Match Officer (plus the full-screen Live Score surface). This chapter walks through them in the order you use them.
1. Facilities & Venues — /workspaces/event-admin/facilities
Section titled “1. Facilities & Venues — /workspaces/event-admin/facilities”Before anything can be scheduled, the event needs somewhere to play.
- A venue is a location (a sports hall, a school, a park).
- A court is a playable surface inside a venue (Court 1, Table 3, Pitch A). A court belongs to a venue and, optionally, to a sport.
Every save runs schedule-safe relationship validation. You cannot delete a venue or court that still has matches assigned to it without dealing with those matches first.
2. Scheduler — /workspaces/scheduler
Section titled “2. Scheduler — /workspaces/scheduler”The “Schedule Command Queue.” Roles: Scheduler, Event Admin, Super Admin.
Creating a match by hand
Section titled “Creating a match by hand”For League, Friendly, and any ad-hoc match. The guided form asks for the sport, category, the two participant entries, venue, court, and start/end time. On submit InTourney validates:
- every relationship belongs to this event and category,
- the end time is after the start,
- there is no venue, court, or participant conflict at that time,
- the match’s lifecycle state allows the change.
A manually-created fixture can also be deleted (Event Admin only) while it has not started. Bracket-generated matches are wired into an advancement graph, so those go through Clear & regenerate on the Generate step, not here.
Rescheduling
Section titled “Rescheduling”Matches in draft, ready for scheduling, scheduled, published, or postponed can be rescheduled. The form asks for the new time, venue, court, and a reason (which is recorded and — for a published match — drives the public “schedule change” notice). Rescheduling a postponed match automatically returns it to scheduled.
Conflicts
Section titled “Conflicts”The queue flags any venue/court or participant double-booking. Resolve them by rescheduling one of the clashing matches.
Example — the scheduler places three badminton first-round matches at 09:00, but Hall A only has Court 1 and Court 2. Trying to save the third on Court 1 at 09:00 is blocked: “That time would create a venue or court conflict.” Moving it to 09:40 clears the flag.
3. Command Center — /workspaces/command-center
Section titled “3. Command Center — /workspaces/command-center”One screen for everything that needs attention right now. It surfaces:
- Venue/court conflicts — double-bookings to resolve.
- Delay impact — when one match runs late, which later matches on the same court are affected.
- Matches awaiting a result, results under review, and anything disputed.
If nothing is wrong, it simply says “Nothing needs attention right now.”
4. Match Officer — /workspaces/match-officer
Section titled “4. Match Officer — /workspaces/match-officer”A mobile-first match list for officers on venue duty. Roles: Match Officer, Event Admin, Super Admin.
It shows the match-day matches (published, scheduled, check-in open, ready to start, ongoing). For the next match you get quick status actions, and two links per match:
- Live Score — the full-screen scoring surface (below).
- Match Details — documentation, internal comments, officer assignment, and the complete lifecycle action set.
5. Live Score — full-screen scoring
Section titled “5. Live Score — full-screen scoring”Opened from Match Officer or Match Details. Designed for a phone or tablet at the court:
- Start the match first. Point entry is only accepted while the match is ongoing (or paused / under review). If the match is still scheduled, the point buttons are disabled and a note points you to Start Match in the Match flow panel. Tapping points on a match that is not ongoing is what produces the message “N points could not be applied (match/set state changed)”.
- Big Add point and Undo buttons for the selected side. The score updates as you tap and stays put — no refresh needed.
- Switch the side you are scoring. Use Add Set for the next game, or Delete Set N to remove the most recent set if it was added by mistake (only while the match isn’t finished/published).
- You never pick the winner. The set winner and the match winner are worked out from the score and the category’s ruleset (for badminton: first to 21, win by 2, cap at 30, best of 3). When the deciding set finishes, a “Match complete — X wins 2–0” banner appears with a single Finish & publish result button. (A collapsible Correct manually option is there for retirements, disqualifications, or a score the rules can’t resolve.)
- Works offline — points are queued and sync automatically when the connection returns. It tells you how many points are pending, syncing, or failed (a failure means the match or set state changed under you — e.g. the match was finished on another device).
- The screen stays awake while it is open.
The match lifecycle
Section titled “The match lifecycle”Every match has a status. The transitions available at any moment depend on the current status.
Normal flow
Section titled “Normal flow”scheduled / published │ Start Match (officer takes the court) ▼ ongoing ⇄ paused ──▶ finished ──▶ result published │ ▲ └──▶ under review ┘| Action | From → To | Notes |
|---|---|---|
| Start Match | scheduled / published → ongoing | Records the actual start time. Do this first — point entry in Live Score is disabled until the match is ongoing. |
| Pause Match / Resume Match | ongoing ⇄ paused | |
| Finish Match / Finish & publish result | ongoing → finished (→ result published) | The winner is recorded automatically from the score. Result is provisional until published. |
| Send for Review | finished → under review | Optional check before publishing |
| Confirm and Publish Result | finished / under review → result published | The winner is pre-filled from the score; publishing is the final, public result and advances the bracket. Only an Event Admin / Super Admin can publish (a Match Officer’s tap finishes the match with the winner recorded, ready for an admin to publish in one click). |
Side branches
Section titled “Side branches”| Action | From → To | Notes |
|---|---|---|
| Mark Disputed | finished / under review → disputed | Requires confirmation; raises an urgent alert |
| Resume Review | disputed → under review | After the dispute is addressed |
| Postpone Match | scheduled / published → postponed | Reschedule it later from the Scheduler |
| Cancel Match | scheduled / published → cancelled | |
| Mark Walkover | scheduled / published / ready to start → walkover | Requires selecting the winner; counts as a real result |
Undo steps
Section titled “Undo steps”Available on the Match Details page (Match Actions), for the common “oops”:
| Action | From → To | Notes |
|---|---|---|
| Undo Start | ongoing / paused → scheduled | Clears the recorded start time. Set scores stay. Any Match Officer. |
| Reopen Match | finished / under review → ongoing | Reopens for more play; clears the end time and derived winner. Event Admin only. |
| Restore Match | cancelled → scheduled | Event Admin only. |
| Reopen Result | result published → under review | Event Admin only. For a single-elimination bracket the winner is pulled back out of the next round first — blocked if that match has already started. Standings are recomputed. Not supported for double elimination (mark it Disputed instead). |
| Undo Walkover | walkover → scheduled | Event Admin only. Same advancement retraction as Reopen Result. |
A double-elimination published result cannot be reopened directly — mark it Disputed, or use Undo Phase / Clear & regenerate if nothing downstream has started.
Example — one badminton match, start to finish
Time Officer action Status What else happens 09:00 Start Match Ongoing Actual start time recorded 09:00–09:35 Tap Add point in Live Score (games go 21–15, 19–21, 21–17); one mis-tap fixed with Undo; Wi-Fi drops, points queue offline and sync on reconnect Ongoing Each game’s winner is recorded automatically as it is decided; live score shows on the public match page and the venue display board 09:35 Third game reaches 21–17 → “Match complete — Andi Pratama wins 2–1” banner → tap Finish & publish result Result Published Winner taken from the score — no dropdown. Bracket advances Andi to the quarter-final; “result published” posts to the public Match Updates feed If a line call is contested at 09:36, the officer taps Mark Disputed instead — it appears on the Command Center as urgent, an Event Admin reviews it, then uses Resume Review → Confirm and Publish Result to close it.
What the public sees
Section titled “What the public sees”Only status changes a spectator cares about appear on the public Match Updates feed: postponed, cancelled, disputed, result published, and walkover. Internal operating states (ongoing, paused, finished-but-not-published) are not announced — a finished match still shows as Provisional publicly until the result is published.
Scores and documentation (Match Details)
Section titled “Scores and documentation (Match Details)”On /workspaces/matches/<match-number> you can also:
- Enter set scores and add sets, or record a ranking result for time-trial / score-ranking categories.
- Assign officials to the match.
- Attach documentation (photos, score sheets, files — with a size and type allowlist). Each asset has a Delete button — the uploader or an Event Admin can remove a wrong file.
- Leave internal comments for other staff (not public). A note can be Deleted by its author or an Event Admin.
- Read the match’s own audit history.
Revising an already-published result is restricted to Event Admin and Super Admin.
Keeping the reports current
Section titled “Keeping the reports current”Publishing results keeps standings, brackets, and medals up to date automatically. After a bulk correction you can force a refresh from Reports → Standings / Brackets / Medal Tally (see Draw & Match Generation).