Control Center¶

Used in: 4. Register and build the site · 5. Connect the workbooks · 7. Rehearse · 8. Run the day

Control Center is the operator's console for running a tournament day — one page, covering every registered event, always showing live data (unlike Tournament Hub, it never hides scores while previewing a day before it's publicly live). Open it, pick an event and a day, and the tabs appear, in this order: Mission Control (where it opens), Awards, Attendance, Match Finder, Live Matches, Standings and Teams. Attendance shows only for an event with attendance turned on, and Teams only for a team event whose rosters are published.

No sign-in is needed to view Awards, Match Finder, Live Matches or Standings — they're read-only. Only the actions inside Mission Control (resyncing, forcing the public site live or hidden), marking people in on the Attendance tab and entering scores in Match Finder need an operator to sign in. Signed out, the Attendance tab asks you to sign in instead of showing the list, and no match in Match Finder can be scored.

Installable — from Chrome's install prompt on Android, or "Add to Home Screen" on iOS Safari — so an operator's device can launch straight into it with its own icon, no browser chrome or address bar around it. This is just a shortcut to the same live page; there's no offline mode, so it still needs a network connection to do anything, same as opening it in a regular tab.

Mission Control¶

The operator-only control panel — the one part of Control Center that needs signing in, and the tab it opens on. From top to bottom:

Sign in with the shared operator username/password. This exchanges your password for a session token that lasts 12 hours — the password itself is never stored anywhere. In a browser tab, closing the tab signs you out. Installed on a phone's home screen, Control Center stays signed in until the 12 hours run out or you press Sign out, even if the phone closes the app in the background. The status line reads Signed in until 3:30 PM, with the date added (3:30 AM, Tue, Oct 6) when the sign-in ends on a later day.
Facility sync status — whether each venue's spreadsheet is syncing cleanly, and when it last succeeded. Each row has a Google Sheet link that opens that facility's actual Google Sheet for this event, in a new tab — for checking or correcting a score straight at the source without having to go find it in Drive. Whether it opens editable depends on that sheet's own Google sharing settings, not on Control Center. When a venue's latest sync came from an edit, its row also reads "edit→sync s" — how long that edit took to reach the published data. It is a diagnostic for operators and is hidden when the figure is not a plausible single edit (a full resync, for instance). Under each venue, a second line repeats its matches done and estimated finish (or, once it's done, its actual end) from Live Matches, and adds "stale — may read late" when that venue's data is old enough to make the estimate unreliable. Below the venues, a Live updates line reads push connected when this page is receiving scores the moment they are published, or polling GitHub (push not connected) when it is not. In the second case updates still arrive, just 30–60 seconds slower.
Resync this day now, right under the venues — pulls a fresh copy from the spreadsheet(s) immediately, instead of waiting for the next automatic sync. On a day with more than one venue, Or resync just one facility does the same for one venue. The Use CSV export fallback toggle switches either one to Google's CSV export, if the normal way of reading the sheet fails. The result appears right below, one line per venue: Synced, This attempt failed. Still showing its previous data, or Failed. Nothing published for it yet, then whether it was pushed to open pages or went through GitHub, and how long it took.
Check connection — confirms Cloud Run is reachable and shows its version. When you're signed in it adds a Live push line saying whether Cloud Run is publishing scores to the live push service (on, off, switched off in Control Center, or not available on an older version). Signed out, the line asks you to sign in. This is about Cloud Run's side; the Live updates line under Facility sync status is about this page's own connection. The result appears right under the button, one line each for the response time, the version, which copy of the event registry Cloud Run is using, and live push.
Public site status — the kill switch for Tournament Hub's Live Matches/Standings (this console's own tabs are unaffected and always show live data, for preview). Three states: Auto (goes live automatically ~4 hours before the day's first scheduled match), Force live, or Force hidden — for quietly correcting a bad score before anyone sees it.
Sync method — an emergency switch between Live push + GitHub (the normal way: scores reach open pages in a few seconds) and GitHub only (every score goes through GitHub, so pages catch up within 30–60 seconds). Use it if live updates misbehave: pages stop updating, or show stale scores. Switching to GitHub only asks you to confirm, and either way it takes effect within about a minute. It shows the current method, and it is hidden until you sign in. If Cloud Run has no live push configured at all, it says so and there is nothing to switch.
Scorer links — for an event with score entry turned on: the switch that accepts or stops scorer links, and Issue scorer link. See Scorer links below.
Public pages — launchers for the venue's schedule board and the event's Tournament Hub, both opening in a new tab so the console stays where it is.

Quick outcomes, like signing in or out, switching the public site or the sync method, or "pick a day first", appear as a short message at the top of the screen, wherever you are on the page. Errors stay until you close them or for about nine seconds. Messages from Cloud Run, Google or GitHub are shown in plain words, never as raw data.

The result boxes (resync, Check connection) have a close button, and they clear themselves when you change the event, the day or the tab, so a result never sits under a different day. A resync that finishes after you've moved on reports as a short message at the top instead.

Scorer links¶

For an event whose events.json entry has a scoreEntry setting, Mission Control has a Scorer links section. A scorer link opens the event's scorer page, where staff enter scores for any venue of one day and do nothing else; they never see Control Center.

Accepting / Stopped is a toggle: on is Accepting, off is Stopped. Accepting lets scorer links save scores and be issued. Stopped makes every scorer save fail and refuses new links, within about a minute, while operators can still enter scores in Match Finder. Links issued earlier work again if the switch goes back to Accepting before they expire. The switch only moves between those two states; it never turns score entry on or off, which is a setting in events.json. Until you sign in, the section shows the current state and nothing to press. The toggle and Issue scorer link are also off, with a note, when the event has no scorer page (events/<key>/scorer.html isn't on the site), since a link would open nothing; add the page first.
Issue scorer link for Oct 3 opens a dialog that makes a link for the selected day. It covers every venue of that day and is valid for 24 hours from when it is issued, not until midnight. It can't be issued once the day is over (from 6:00 AM the morning after), or while the switch reads Stopped.
In the dialog, two optional fields, Issued to and Note (at most 40 characters each), say who the link is for: a name, and for example the courts they cover. Issue link issues it; Cancel issues nothing. See Who a link was issued to.
The link appears with Copy, Share (on devices that support it), Show QR and Valid until Mon, Oct 5, 8:30 AM (24 hours), in Manila time. When it was issued to someone, the title names them. Send it, or have the scorers scan the QR code.

A scorer page that is already open finds out about a stop when a save is refused ("Scorer links are stopped for this event. Ask the operator."); one that is reloaded says so as soon as it loads.

Who a link was issued to¶

Both Issue scorer link and Issue desk link open a dialog with two optional text fields: Issued to (a name) and Note (for example Gate A or Courts 3–4). Each is at most 40 characters. Issue link issues the link with whatever is filled in, or with neither. Both are signed into the link, so the holder can't change them. The dialog opens empty every time, so the next link isn't labelled with the last one's name. If a link can't be issued, the dialog says why and stays open with what was typed, to try again.

They show up in three places:

the page the link opens, after the day: · Day 1 · Ana (Gate A);
the markedBy column of the workbook's ATTENDANCE tab, for a desk link: see event attendance;
the note on both score cells of a match, for a scorer link: see score entry.

The label reads Ana (Gate A) with both, Ana with only a name, Desk link (Gate A) or Scorer link (Courts 3–4) with only a note, and Desk link or Scorer link with neither. An operator's own marks and scores in Control Center read Control Center.

The label says who the link was issued to, not who typed. Anyone holding a forwarded link writes under its label, so give each person or desk their own link. A link issued with neither field works the same way, with no label.

Awards¶

The podium tab: once a category's Final and Bronze matches are scored, this tab shows who won gold, silver, and bronze — derived automatically from the match data, nothing to type in separately. Before those matches are played, every placing just reads Pending; nothing is ever guessed.

Overall Champion (dual-meet events only) — a banner at the top naming whichever club has more Round Robin wins overall, with the runner-up's win count shown underneath. If the two clubs are tied, it says so rather than picking one.

Exporting for the ceremony — every category card has an Export image button that downloads a SAGE-branded PNG of that category's podium, ready to hand to an emcee or post on social media. An Export whole tournament button at the top produces a single combined image covering every category at once, arranged as a grid so it stays a reasonable shape regardless of how many categories the event has.

Team events have one podium, Team Championship. Gold is the winner of the Final matchup, silver its loser, and bronze the winner of the Bronze matchup, each decided on total points (or, for an event scored on games won, on matches won and then total points). A placing reads Pending until its matchup is finished. Each medal shows the team name with every player who played for that team listed beneath, A–Z. If the Final or Bronze matchup ends level on points, the card shows a warning naming the matchup's lowest match number and leaves all three placings Pending. Export image and Export whole tournament put each team's name on the picture with its players beneath. On the single-podium image the player list shrinks to fit its row, and a roster too long for even the smallest size ends in "+N more".

A few things the Awards tab is careful about:

A bronze decided by walkover (no bronze match actually needed to be played) goes to that pair like any other bronze, with no score and no label. That holds whether the workbook schedules a Bronze match against a BYE or only lists the round robin's #3 against a BYE in the bronze slots with no match at all.
A twice-to-beat Final is won by the #1 pair winning once or the #2 pair winning twice, and a best-of-3 by whoever wins two. Gold waits until one of them has: a #2 pair that wins game 1 of a twice-to-beat has forced game 2, not won. A game that is no longer needed doesn't count as a match left on the facility's progress card either.
If a match's scores look wrong (e.g. tied, which shouldn't be possible), the card shows a warning naming the match number instead of guessing a winner.
A category with no playoff bracket at all (pure round robin) falls back to its top-three standings, tagged By standings so it's clear where that podium came from. All three placings read Pending until every round-robin match in that category has a score — before then the top three are only the current leaders.

Attendance¶

Staff check-in, for an event whose entry in events.json has an attendance setting. The tab lists everyone playing at each venue that day, grouped by category (or by team, for a team event), with a switch per person. Flip it to mark someone in; it records the time. Above the list:

the number of people in at each venue
Update roster, to bring the list up to date with the workbook now instead of waiting for the next sync
Issue desk link, for an event set to "desks": a link for one day that lets desk staff mark people in from their own phones, with Copy, Share and Show QR. It opens the same dialog of optional Issued to and Note fields as scorer links
Needs attention: names that might be the same person written two ways, people listed twice in one category, and Show withdrawn

Full reference: event attendance.

Match Finder¶

Identical to Tournament Hub's Match Finder — search a pair's name, see their full day of matches with Live/Next Up flags and scores. Useful for an operator fielding "where's my match" questions without having to also pull up Tournament Hub itself. Before a search it lists every match of the day in match-number order (a team event: its team chips, then every matchup, ordered by its lowest match number).

The search box sits just above the list, not in the banner, and on a phone it stays pinned to the top of the screen while you scroll.

Control Center's search also takes a match number: type 42 or #42 to see just that match (for a team event, its matchup card narrowed to that match). A number that isn't on the day says so.

Entering a score¶

For an event with score entry turned on, a signed-in operator can enter, correct or clear a match's score from Match Finder without opening the workbook. See Score entry.

Live Matches¶

A board of every court currently in use, grouped by venue if the event has more than one. Each court shows the category and round of whatever's playing there, both teams' names, and the live score — or "No match playing" for an idle court. This is the same view a wall-mounted screen at the venue would show.

Above the courts, a card per venue shows how many matches are done, how many are left, how many are in play (on a court right now, so not counted as left; done, left and in play add up to the venue's total), and — on the day itself — an estimated finish time and how far ahead of or behind schedule that venue is. The estimate is the operators' own formula: matches left plus idle court slots left, times the scheduled match length, divided by the number of courts. It never counts less than one match length per match still queued on the busiest court, and it keeps working past midnight until 6:00 AM. If a venue's sheet stops syncing, the card says so, because no new scores means the estimate drifts later on its own.

Once every match at a venue has both scores in, its card reads All matches done with the actual end time, and underneath, the scheduled end and how early or late the venue finished (for example "1 h 15 min early"). The actual end is recorded once, the moment the last score first arrives, and every phone and laptop reads the same time. A later Resync this day now doesn't move it. Clearing a score reopens the venue, and it gets a new actual end when the score goes back in.

Standings¶

Win/loss records and rankings by category. For a dual meet, standings are split by club within each category (with a shared win-count summary at the top), and the Bronze/Final rounds — since those pit one club against the other — are shown as a single head-to-head block rather than nested under either club.

Round-robin pairs are ranked by wins, then head-to-head among pairs level on wins, then quotient — the same order as the public event page. The Awards tab's standings fallback uses it too. The workbook's playoff feeders don't: they rank by wins then quotient, so on a head-to-head tie the pair the sheet advances can differ from the one listed first here.

A pair whose names aren't in the sheet yet is listed under its team code (ND_1…) in the round-robin tables, so the standings are complete before the rosters are. Undecided playoff spots read TBD, and the Awards tab never puts a code on the podium.

When a category's round robin is split into brackets, each bracket gets its own small table under a colored Bracket 1, Bracket 2… label, two side by side, so parallel pools read as pools. On desktop, the 1 col button in that category's header stacks its brackets in a single, normal-width column instead (2 cols puts them back); the choice lasts until the page is reloaded. On a desktop screen every category is its own column in one row; scroll sideways for the rest. A long player name is never cut off — its table scrolls sideways instead.

At a team event, Standings has three parts, the same as on the public event page: a table per bracket ranked by points scored, then quotient, then head-to-head points, then pair wins (with the eight quarterfinalists the operators entered in the workbook marked Advances), the playoff matchups — Quarterfinals, Semifinals, Final, Bronze — as full cards, and each bracket's matchups behind a collapsible heading. A matchup is won on total points across its four matches, or, for an event whose teamScoring is "games", on matches won and then total points, with the table showing W, L and Pts — see Tournament Hub § Team events. Live Matches names both teams on each court and shows the running matchup score, and Match Finder searches by team or player.

If a match's team code doesn't match any configured category, a visible warning banner names it rather than silently lumping it into an "Other" bucket — so a data problem in the spreadsheet gets noticed instead of hidden.

Teams¶

For a team event: every team's roster, the same as the event page's Teams tab. Cards start collapsed and open to show each player's level and gender. Match Finder shows a team's roster with its matchups, and finds a player by name from the roster before their lineup is in. A player's result shows their level and gender beside their name.

Technical: Control Center architecture, incl. Awards tab internals · sync pipeline · auth · event attendance · scorer page