GFY — team scramble site

A one-page site for the GFY golf weekend — now a 2-day team scramble. The page is static; all live data comes from one Google Sheet that anyone in the group can edit. Publish the sheet once, paste a few ids into config.js, and the site updates itself every 60 seconds.

No servers, no accounts, no build step. If you can edit a spreadsheet, you can run this site.

The site is tabbed — the sticky nav bar is the tab list (Home, Board, Field, Calcutta, Money, Next Year, Rooms, Schedule, Pairings, Rules, Champions, Shame, Photos). Switching tabs doesn't reload the page, and each tab has its own deep link (yoursite.com/#calcutta, #nextyear, #rooms, …) — safe to bookmark or text someone straight to a section.

One-time setup

1. Create the sheet from the template

Go to drive.google.com and upload tools/gfy-template.xlsx (drag it into the window).
Double-click the uploaded file, then File > Save as Google Sheets. Work in the Google Sheets copy from here on; the .xlsx can be deleted.
Run the polish script to set up checkboxes, dropdowns, and colors — the template ships its checkbox columns as plain TRUE/FALSE text (only possible to fix now that you're in a Google Sheet; an xlsx file can't hold a real Sheets checkbox). In the Google Sheet: Extensions > Apps Script, clear the placeholder code, paste in the full contents of tools/sheet-polish.gs from this repo as Code.gs, then run polish() from the function dropdown and click Run. Authorize when prompted. polish() applies checkbox validation to the checkbox columns — the deposit column on Field, the settled column on Ledger, the collected column on Calcutta, and the invited/responded columns on Invites (NOT handicap — that column is a typed number, not a checkbox; the polish script repairs it if a broad column-conversion swept it up by mistake) — without changing any cell values. It also sets up the warn-mode status dropdowns, Field/Rooms coloring, and builds the START HERE tab, all in the same run. (Rooms has no checkbox columns — no checkbox step needed there.) Safe to re-run any time (see Polish script, below, for re-running after edits).

If the boxes come in unticked after polish() runs — whether Sheets renders an imported TRUE/FALSE string as a ticked box depends on the xlsx→Sheets import and hasn't been checked against the real thing — select the data cells of the affected column(s), one at a time, and Insert > Checkbox by hand. Never the handicap column.
The sheet has 13 tabs along the bottom (Info, Course, Field, Scores, …, Invites, Rooms). Each has a bold header row and a few sample rows showing the shape. Keep the header rows exactly as they are. Replace the sample rows with real data.
Teams, captains, and the team column. Each row's team cell holds its captain's name — including the captain's own row, which names himself (so a captain's row always reads player == team). That's how the site knows who's on whose team: every row sharing a team value is one roster; the player whose name matches the team value is the captain. since is the player's first GFY year — it powers seniority badges and the rookie tag, and only needs to be filled once, the year they join.

2. Publish the sheet to the web

In the Google Sheet: File > Share > Publish to web.
In the dialog, set the first dropdown to Entire document and the second to Comma-separated values (.csv). (Both matter.)
Click Publish, confirm, and copy the link Google shows you.

3. Find your PUB_ID ← the step people get wrong

The link from step 2 looks like:

https://docs.google.com/spreadsheets/d/e/2PACX-1vTxAMPLEtoken.../pub?output=csv
                                       ^^^^^^^^^^^^^^^^^^^^^^^^
                                       this long token is PUB_ID

PUB_ID is everything between /d/e/ and /pub. It always starts with 2PACX-.

This is NOT the id in your browser's address bar when you're editing the sheet. The edit URL (/spreadsheets/d/1AbCd…/edit) contains a different, shorter id that will not work. If the site ever shows an empty leaderboard while the sheet clearly has data, this mix-up is the cause 90% of the time. If your PUB_ID doesn't start with 2PACX-, you copied the wrong one.

4. Find each tab's gid

In the normal editing view of the sheet, click a tab at the bottom (say, Course).
Look at the browser address bar. It ends with #gid= followed by a number, e.g. …/edit#gid=1837552901.
That number is the gid for the tab you have selected. Click each of the 13 tabs in turn and write down each number. The first tab is usually 0.

5. Share the photo folder (optional)

Create a folder in Google Drive for the weekend's photos.
Right-click it > Share > under General access choose Anyone with the link as Viewer.
Open the folder; the address bar reads …/drive/folders/1aB2cD3e…. The token after /folders/ is your DRIVE_FOLDER_ID.

If the folder is not shared this way, the site's Album section shows a Google permission error inside the frame — it will not fail loudly. Open the live site in a private/incognito window to check it the way guests see it.

6. Paste it all into `config.js`

Open config.js — every field has a comment showing the exact expected format. Fill in:

PUB_ID — from step 3
GID — one number per tab, from step 4
DRIVE_FOLDER_ID — from step 5, or leave ""

Easiest way to edit without any tools: open the file on github.com, click the pencil icon, paste, Commit changes. The live site updates itself about a minute later.

7. Check your work

Start with the health strip — it's the first thing to check, no URL tricks required. A one-line strip fixed at the bottom-right of the live site (collapsed by default; tap to expand) calls out anything the sheet gets wrong: unmatched score captains, duplicate captains, blank years, cells it can't parse as a price or handicap, and similar. It only ever appears when there's something real to flag — an unconfigured or fully offline site shows no strip at all rather than a fabricated warning. If a team is missing from the board or a number looks off, check the strip before anything else.

For the full picture, open the live site with ?debug=1 on the end of the address:

https://<your-pages-url>/?debug=1

A panel appears listing every tab as OK (with a row count), EMPTY, or FAILED with the reason, plus the same health warnings as the strip above. Thirteen OK lines means the plumbing is done (the site reads its 13 configured tabs; extra tabs like START HERE and Form Responses are ignored by it). Remove ?debug=1 and hand out the link.

Phones: open the link in Safari/Chrome, then Share > Add to Home Screen. It installs like an app, icon and all.

The Admin vault (emails)

Everything published from the main GFY sheet is public — that's the whole mechanism this site runs on (see the warning under "The invite list," below). Two kinds of information can never go on that sheet: email addresses, and why someone isn't getting invited back. Both live in one place: a second, completely separate Google Sheet — the GFY Admin sheet (its template: tools/gfy-admin-template.xlsx → Drive → Open as Google Sheet) — that is never published to the web, ever.

The GFY Admin sheet holds:

Every email address you have for everyone, one row per person — as many addresses per person as you have (email_alt for a second one, work, personal, whatever).
A do-not-invite (DNI) list: name + the reason, in plain language, so future-you remembers why next year.

Three rules:

Never click File → Share → Publish to web on the Admin sheet. Doing so makes every address and do-not-invite reason public.
Keep it a separate file — never a tab of the public GFY sheet. The public sheet publishes "Entire document", so any new tab auto-publishes.
The public Invites tab tracks who/when/status — names only, never an email address in any cell (the checker below watches for this).

The pairing rule. Whenever you add someone to the DNI list in GFY Admin, also set status to out on their Invites row in the public sheet, in the same sitting. The two rows are a pair: GFY Admin says why (privately), the public Invites row says that (so the site actually suppresses them). One without the other is a gap — DNI-only means the site still quietly counts them as needing an invite; Invites-only means next year's operator has an exclusion with no memory of why.

Before every send round

Admin sheet → Contacts tab → File → Download → CSV. Save it OUTSIDE this repo folder (e.g. Downloads — the checker refuses in-repo paths).
npm run presend -- ~/Downloads/<the file>.csv --vault-url <admin sheet URL> [--extra-gid responses=<gid>] — the optional --extra-gid scans an extra published tab (e.g. the Form's responses tab) for leaked addresses; npm run check-gids prints that gid on its "no config entry" line if you don't have it handy.
Fix anything it lists (do-not-invite violations block. Unpaired do-not-invite names block too — give them their out row on Invites first so the site suppresses them; "missing from vault" means collect that address first). Log each send in SendLog.

The pre-send checker automates the DNI cross-check for you: everyone marked DNI in GFY Admin should be out in Invites, and nobody about to get an invite email should be sitting on the DNI list — it flags DNI names with active invite rows AND unpaired DNI names missing their out row.

Skipped the checker? Then at minimum re-read the do_not_invite column before sending. That list exists because someone once had a reason.

Replies (Gmail loop)

When invite replies come in: authenticate Gmail once via /mcp in a Claude session, then ask for a reply scan. You get a review list (name, address, snippet — in the conversation only, never written to a file); you approve; responded gets ticked on the Invites tab. If the scan errors with an auth failure, re-run /mcp — a failed scan never means "no replies".

Rooms fill in paid order

The Next-Year room queue orders people by paid_date (real dates — ISO like 2026-08-20 preferred). Blank or unparseable dates sort last. Ties on the same day keep sheet order.

Polish script (run after big sheet edits)

tools/sheet-polish.gs → Extensions → Apps Script on the LIVE sheet → paste → run polish(). Safe to re-run any time — re-running never changes cell values (the first run repairs the handicap column and autofills Course — both one-time, evidence-gated). To verify idempotence after an Apps Script edit: run polish() twice in a row and confirm no cell value changed between runs (File → Version history).

Re-running polish() also rebuilds the START HERE tab and reorders the sheet tabs by season — during the event week, tabs appear as START HERE, Scores, Field, Pairings; off-season shows START HERE, Field, Invites, Rooms. START HERE's rebuild includes:

Captain scoring links — one row per current-season team (from Field's team column), each a ready-to-text link straight to that team's scorer.
Form Team dropdown — the same team list, one per row, meant to be selected and pasted directly into the Google Form's Team dropdown options.
A reminder that team names freeze once those links go out — renaming a team after captain links are sent means updating Scores' team values to match, or the writer can no longer find that team's rows.
If an old sheet still has a value pasted in the retired "Scoring form URL" cell, polish() never drops it silently — it carries the value forward under a "old value preserved below, copy it to Info!" label until you move it over yourself (see Live scoring below).

Pairings also has an optional start column — the hole a group starts on for a shotgun round; leave it blank for tee-time rounds and the site renders exactly as it always has.

The polish script also OWNS conditional formatting on Field and Rooms — it replaces all conditional-format rules on those two tabs each run. Don't hand-add your own coloring there; it will be erased.

Sheet edits reach the site in roughly 1–6 minutes (Google republishes ~every 5 minutes; the site refreshes every 60 seconds). During a round, that's fast enough to keep the board honest — just don't panic-refresh.

Live scoring

During the tournament, each captain scores their own team's card straight from their phone at a link generated just for them. The Google Form is still there as the no-JS fallback (same validation, same sheet). Neither one replaces the paper scorecard — see below.

What a captain sees

Each team gets one link — .../gfy/#score?team=<Team> — generated for you (see "Captain links," below) and never hand-typed. First open shows a one-time "Scoring for <Team> — <roster>" confirmation; after that, that link (or a bare #score) resumes straight to that team's card. To switch teams (a captain covering two teams, or Riley filling in), tap "Not your team?" on that one-time confirmation screen before confirming, or — once on the card — tap "not you? switch" in the sticky header at any time; both open the same standing "Who's scoring?" picker.

Once a captain has opened their own link at least once, the Leaderboard page also carries a quiet "Enter scores — Team <Team>" button beside the year picker — a fast way back into the card without re-typing the link. It only appears on phones that have opened their captain link; a browser that never confirmed a team sees nothing there.

The card is 18 cells, Out and In. Tap a hole, tap the score — it sends immediately, no confirm screen, no undo timer, so a tap that ends up in a pocket can never strand a send. The cell itself is the receipt: ▮ on the sheet (confirmed) · ⇡ saved on phone (queued or sending, not confirmed yet) · ▲ (the sheet disagrees with this phone — see below) · ! (rejected — shows the sheet's exact reason, with a retry button; "text Riley" shows up after two retries still fail). Re-tapping an already-scored hole names the current value on the sheet first — tap a number to replace it — nothing overwrites silently.

Offline is expected, not an error. Saving to the phone never waits on a signal — a tap always lands instantly, bars or no bars. Copy states the truth plainly: queued scores live on this phone and send next time this page is open with signal. If two phones ever send different numbers for the same hole, the site never auto-picks a winner — it shows both numbers and waits for a person to resolve it: two plain-word buttons, "Keep the sheet" or "Replace with mine." Neither one resends anything on its own. If the real answer is a third number — not the sheet's, not the phone's — tap "Keep the sheet" first, then tap the cell again; that reopens the ordinary entry sheet, where the new number goes in like any other tap.

The paper scorecard is the tournament's system of record. Keep it, and turn it in, exactly like every year before this — the phone scorer and the Form are both a convenience layer on top of the sheet, not a replacement for the card in your pocket. If the card ever disagrees with the phone or the sheet, the card wins.

Before score_endpoint exists on the Info tab (i.e., before the setup below is finished), every scoring link is honestly inert — it reads "Scoring opens at the tournament." and, only if form_url is already pasted, a "Score via the form" link underneath. Never a dead button, never a guess. (The public "Enter scores" button that used to open the sheet directly is gone for good — see the retired SHEET_EDIT_URL comment in config.js. Scoring only ever runs through a captain's link or the form now.)

One-time setup

Create the form with these four questions, in order:
- Team (dropdown, menu items hand-filled at draft night — one item per team captain; copy the FORM TEAM DROPDOWN block from START HERE, built by polish() from the season's Field tab, one line per option)
- Round (dropdown, menu items: 1, 2)
- Hole (dropdown, menu items: 1, 2, 3, …, 18)
- Team score (Number, validation: "Between 1 and 19")
In the form's Settings, make sure Collect email addresses is set to 'Do not collect' and 'Restrict to users in your organization / require sign-in' stays OFF — collecting emails would publish every submitter's address on the public responses tab. The 'Do not collect' setting stays the primary defense; npm run presend -- … --extra-gid responses=<gid> can now scan that tab after the fact (detection, not prevention).
Link responses: In the form settings, click Responses → link responses to the GFY spreadsheet (Responses → Link to Sheets → Select existing spreadsheet → pick the GFY sheet file).
Paste the triggers: Extensions → Apps Script (on the LIVE sheet) → copy tools/sheet-triggers.gs from the repo and paste it into the script editor (same project as the polish script is fine) — use File → New → Script file and paste there; do not clear or paste over Code.gs, that's the polish script. Save, then run setup() from the function dropdown and click Run. Authorize when prompted. setup() checks the Scores tab's headers first and refuses to install anything (throws, no triggers touched) if it's shaped wrong — a team column missing (or a legacy player column in its place), or any of h1..h18 missing. Fix the headers and re-run.
Deploy the Web App: still in Extensions → Apps Script, Deploy → New deployment → gear icon → Web app → Execute as Me, Who has access Anyone → Deploy → authorize → copy the Web app URL (ends in /exec). Full walkthrough + a CORS proof — run it before the draft-night drill and before sharing any link: tools/spike-scorer-cors.md. Once this URL has gone out to captains, never redeploy with "New deployment" again — that mints a different URL and silently orphans every captain link and every score_endpoint value already handed out. To ship a sheet-triggers.gs code change afterward, use Manage deployments → edit (pencil) → Version: New version → Deploy instead — same URL, new code.
Save the config to the Info tab (not the old START HERE cell — that one's retired; see the polish note above if you're upgrading a sheet that still has a value pasted there). Add two rows to Info (key in column A, value in column B):
- score_endpoint → the /exec URL from step 4.
- form_url → the form's shareable link (blue Send button in the form editor → copy the short URL). This is the fallback link the site shows before score_endpoint is configured, or if a captain prefers the form UI directly.
Then re-run polish() — it rebuilds START HERE's Captain scoring links and Form Team dropdown blocks from the current Field roster. Confirm it landed: open the live site with ?debug=1 — the panel's last line reads score endpoint: OK (<year>, <N> teams) once configured (it reads score endpoint: not configured before this step, and never counts toward the tab-report's OK total either way).
Check the timezone: On the LIVE sheet, open File → Settings and confirm the time zone is set to America/Boise (used for paid_date stamps — see Collecting for next year, below).

Captain links & the Form's Team list

Every current-season team's scoring link and Form-dropdown entry are generated for you on START HERE — never hand-typed:

Re-run polish() (Extensions → Apps Script → run polish()) any time the roster changes. It rebuilds two blocks from the live Field tab: CAPTAIN SCORING LINKS (one ready-to-text link per team) and FORM TEAM DROPDOWN (the same team list, meant to be selected and pasted directly into the Form's Team question options).
Paste these lists exactly — never retype them by hand. A retyped name that doesn't match the Field team value byte-for-byte is a team the live-scoring writer can never find.
Team names freeze the moment these links go out. Renaming a team afterward means updating every one of that team's rows on Scores to match, or the writer silently stops finding them.

The draft-night drill (SC-DRILL) — blocking, before any link is texted

Do not text a single captain link, or hand out the form, until this drill has passed live against the real deployed endpoint (~25 minutes):

Pre-flight — Scores/Field/Info headers present, first_tee year correct, sheet timezone correct, score_endpoint pasted into Info, sheet sharing restricted to named editors only, and SHEET_EDIT_URL confirmed gone from config.js.
The 15-tap sweep — one submission per team, every one using round 2 / hole 13 / score 6 (hole ≠ score on purpose — a transposition mistake can't accidentally pass the check). Verify 15× ok verdicts AND 15× h13 = 6 on the Scores tab, and record the observed sheet-to-published-CSV lag in the ledger.
Pocket test — tap a score, lock the screen for 2 minutes; it must land.
Airplane test — enter 3 holes with the phone offline; all three must land exactly once when signal returns.
Clobber test — send a differing value for the same hole from a second browser; confirm it renders the conflict state (not a resend), then hand-fix it in the sheet and confirm it doesn't bounce back.
Round-toggle spring test — the manual round toggle is momentary; after one submission it must spring back to the derived default round on its own.
Per-round canary — Riley submits one real score at each round's first tee.

Cleanup (S15): clear every sweep-created cell and delete the sweep-created rows outright — an emptied row still ghosts on the board.

How it works

When someone submits the form (or a captain's phone POSTs to score_endpoint directly), the same validator writes the score to the Scores tab (matching the team by name, case-insensitive) — the form trigger marks its response row with a status, and the site scorer reads the equivalent verdict back straight from the server response:

applied / ok — score was valid and written to Scores.
applied (replaced <old>) — same as above, but a DIFFERENT number was already sitting in that cell; the mark preserves the value it displaced. Last write still wins — this is an audit trail, not a block.
rejected: no Team answer — check the form's question titles — the writer couldn't match a "Team" question in the submission at all, usually because a question title got renamed.
rejected: team not in roster for <year> — the Team answer didn't match any captain in that year's Field tab. This also self-diagnoses a stale first_tee in Info: if the wrong year is scoping the roster lookup, every submission rejects this way — check Info first.
rejected: … — other validation failures (invalid round, hole out of range, invalid score, a round total already on that row, Info first_tee unreadable, etc.). Resubmit the hole
rejected: busy — resubmit — a submission collided with another (both sent at the exact same moment). Resubmit; the document lock ensures they serialize.
rejected: internal error — usually means a tab was renamed or is missing (the writer needs Scores, Field, and Info with their standard headers) — check those, and see Extensions → Apps Script → Executions for the exact error. The status cell itself carries the first 80 characters of the error.

The responses sheet (auto-created by Google Forms) has a status column added by the trigger — open it to audit which submissions applied and which were rejected. A repeated client_id+submission is recognized and answered the same way again rather than written twice, so a retried send or a drained queue entry can never double-apply.

When someone ticks the deposit checkbox on the Field tab, a trigger fires onDepositEdit() and stamps today's date (in the sheet's time zone) into the paid_date cell — only on the first tick; re-ticking never overwrites a date that's already there, and unticking never erases it. Paid order on the Next Year board follows paid_date.

Names — the one convention

Field.player, Invites.player, Rooms.player (and the vault's Contacts.player) carry first + last name, spelled identically everywhere — the site matches them by exact normalized text, so "Wade B." on Rooms will not match "Wade Boggs" on Field. Scores.team and Pairings follow the team label (the captain's name), not player names. That label freezes once captain scoring links go out (START HERE's Captain scoring links block) — renaming a team afterward means updating its team value on Scores to match, or the live-scoring writer can no longer find that team's rows.

Year to year

New season: add rows with the new year in each tab — old years stay for the archive, and a year picker appears on the leaderboard automatically.
Scores: one row per team per round, keyed by the captain's name in the team column (not a per-player row). Fill holes h1…h18 as they're played; blanks are fine mid-round. If you only have round totals, add r1 and r2 columns to the Scores tab and put totals there instead. A few guards make this forgiving on a phone:
- a blank hole cell means "not played yet" — a 0 is read the same way (no score), never as a hole-in-zero;
- if the same team's round gets entered twice (someone double-taps "submit," or two people fill it in at once), the rows merge instead of colliding — it's normal, not an error;
- round labels can be typed as words ("Round One", "Round Two") or digits (1, 2) — either reads correctly.
Update first_tee in the Info tab (ISO format with timezone offset, e.g. 2027-08-14T09:00:00-06:00) — the countdown and calendar button follow it. No code changes needed for a new year.

Collecting for next year

The Next Year tab runs off next season's rows in the Field tab, added whenever someone pays — you don't wait for the season to turn over:

Add a row with next year in the year column and the payer's name.
Tick their deposit checkbox.
Type the date it landed into paid_date.

(Once the triggers are installed, ticking the deposit checkbox stamps paid_date automatically — type it by hand only to backdate.)

That's it — no other columns need filling in yet. The site builds the paid list ordered by paid_date, earliest first (this is also the room- assignment order — see Rooms, below); a paid row with no date sorts after the dated ones. The public Owing list is deliberately narrow: it only shows people who already have a next-year Field row and haven't paid yet — add someone's row as soon as you know they're in, even before the deposit lands, so the board can nudge them by name. Everyone earlier in the process (invited, responded, no reply yet — see "The invite list," below) stays off the public board and only shows up under ?admin=1.

If someone isn't coming back, set status to out on their next-year Invites row (once you're using Invites at all for that season) or their next-year Field row (honored only when Invites has no rows yet for that season — see below) — they drop off the Next Year board without deleting any history. A current-season status of out is a different thing entirely: it only changes how someone shows on the Field tab itself (a "not returning" note); it has no effect on the Next Year board.

The invite list

The Invites tab tracks next season's outreach — who was emailed, who wrote back, who still needs a nudge — separate from who's actually paid (that's the Field tab, above). Its columns: year, player, invited, responded, status.

⚠ NEVER put email addresses (or anything sensitive) in this spreadsheet — every published tab is publicly fetchable. Emails live in the separate, never-published GFY Admin sheet.

The workflow:

Add everyone you might invite back to Invites, with next year in year.
Send your invite email (mail-merge off the GFY Admin sheet, or just BCC everyone — the published sheet doesn't send anything itself and must never hold the addresses).
Tick invited for everyone you emailed.
Tick responded as replies land.

The Next Year board turns this into a funnel — paid, responded, invited, still needs an invite — so you can see at a glance who's stuck and where (the counts are public; the names behind responded/invited/still-needs-an- invite are ?admin=1-only — see below). Someone who's already paid always shows as paid, even if you also ticked invited/responded for them; paid is the highest stage.

Where out/declined belongs. Once you've added ANY row to Invites for a season, Invites becomes the authoritative place for that season's out/declined — a status value left over on someone's Field row for the same season is ignored (and flagged on the health strip) rather than acted on. If you haven't touched Invites for a season at all yet, Field's own status is honored instead, so the tab still works standalone. In short: once you're using Invites, put out/declined there, not on Field. declined (this season only) shows under ?admin=1 and comes back into consideration on its own next season; out suppresses silently and for good.

If you leave the Invites tab unconfigured or empty, the Next Year board just runs the plain paid/owing view with no funnel line — nothing else changes.

Adding the Invites tab to a sheet you already built

If your GFY sheet predates this feature (it only has the original 11 tabs), add the 12th tab yourself — no need to rebuild from the template:

In the Google Sheet, click + at the bottom to add a sheet, and name it exactly Invites.
Paste the header row into row 1: year, player, invited, responded, status.
Select the invited and responded columns, one at a time: Insert > Checkbox (same one-time step as Field.deposit).
Click the new tab, copy its gid from the address bar (#gid=…, same as step 4 above), and paste it into config.js as GID.invites.

Rooms

The Rooms tab tracks lodging assignments — who's in which room, at which property. Its columns: year, property, room, player. The sheet only ever stores assignments; the site derives everything else (the paid-but-not-yet- placed queue, the health flags, the admin memory lens).

Add one row per person per room:

Row-per-assignment: year, property (e.g. "Bear Creek Lodge"), room (any label the property uses — "1", "3B", "Loft"), player.
A lodging guest who isn't a tournament player — someone's plus-one, a kid — gets a row too: prefix their name with guest: (e.g. guest:Pat). The site strips the prefix and shows a small (guest) mark instead; guests are never flagged as unknown or unpaid, because they were never expected to be on the Field/paid list in the first place.

The Rooms view groups everyone by property, then room (names are public — this is a find-your-bed page), with a "Paid, not yet assigned" queue underneath: the same paid-order list Next Year uses, minus whoever already has a room. A filter box on the page narrows the whole view by name as you type; that's a browser-side convenience, it never touches the sheet.

Which year's rooms show? Whichever year has the newest rows in the tab — but never older than the current season, so Rooms can serve the event that's about to happen (unlike Next Year/Invites, which are always about next year specifically). Add rows for next year's lodging whenever you like and the anchor follows them forward, same as Invites can run ahead. The Rooms header displays the anchor year (e.g., "Rooms — 2026") so you see at a glance which year's assignments you're looking at; blank-year rows default to the tab's own maximum year and render alongside other rows for that year.

Health flags (site-side, automatic, on the same health strip as everything else):

The same player assigned to two different rooms.
A player assigned a room who isn't on the paid list yet — "assigned but not paid," worth a text before they show up and find someone else's bag on the other bed.
A name with no matching Field history and no guest: prefix — probably a typo, or someone who needs the guest: prefix.

Add ?admin=1 to the URL and each assigned player who stayed somewhere the year before gets a small "had: Property · Room" note next to their current assignment — handy for spreading people around without digging through last year's sheet by hand.

Would-pay, on the Calcutta board

Payouts figure on gross score by default — set the Info tab's calcutta_basis key to net to figure them on net instead, though a scramble roster (the normal case here, with a captain and no per-player handicap to net against) always forces gross regardless of that key.

Next to each lot on the Calcutta board, a small second line answers "if the tournament ended this second, what would the owner collect?" — the exact same math as the Payout table further down the same page, just surfaced earlier (never a separate calculation that could quietly disagree with it). It reads "Wins if it ended now" while the tournament's still going, and flips to "Won" once every card is in. Four situations get their own plain-language text instead of a dollar figure: no owner at all reads "unsold"; a team that hasn't posted a single hole yet reads "waiting on cards"; a team that's posted but landed outside the paying spots reads "—"; and, while the Course tab's pars are incomplete, every owned, scored lot reads "awaiting pars" instead (see below). None of this changes what an owner owes for the lot itself — the board says so directly: "You owe the price regardless."

While the Course tab's pars are incomplete, nothing on the site makes a rank claim off the raw stroke count — there's no fair way to compare an 18-hole total against a still-short one, so standings pause instead of quietly ranking off it. You'll see it in three places: the leaderboard's Pos column shows "—" for every team (its To-par column also relabels itself "Total", since it can't back a to-par figure either); the Calcutta payout panel replaces the payout table with "Payouts wait on the Course tab — standings need all 18 pars." and its basis line reads "Paused · Course pars incomplete"; and each owned, scored lot's would-pay line reads "awaiting pars" as above. Money already collected or owed — the pot, rake, payable total, top bid, outstanding balances — is unaffected; only rank claims pause. The fix is the same everywhere: fill in the missing or invalid par cells on the Course tab — the health strip names the exact hole.

If a team has to withdraw mid-tournament, set that player's current- season Field status to wd. The board excludes them from the Projected → Final flip (so one incomplete card doesn't hold the rest of the field at "Projected" forever), flags it on the health strip, and marks the team with a small WD tag on the board. Nothing needs to be deleted — their partial card and their Calcutta lot both stay exactly as they were.

When something looks wrong

Symptom	Likely cause
Empty leaderboard, sheet has data	Wrong PUB_ID (edit-URL id instead of the published `2PACX-…` id) — see step 3
One section empty, rest fine	That tab's gid is wrong or missing in `config.js` — run `npm run check-gids` to diff `config.js` against the live sheet's tabs
Team missing from board	The captain's name in Scores' `team` column doesn't match any team in Field — check the health strip, it names the mismatch
Edits don't show up	Google republishes on a short delay — wait ~5 min; also check File > Share > Publish to web is still active
Album shows a permission error	Drive folder not shared "Anyone with the link" — step 5
Link shows every team, not just mine	the link's team doesn't match this season's Field roster (stale bookmark/typo/pre-draft link) — pick your team once, or re-copy your link from START HERE after the draft
Anything else	Check the health strip, then add `?debug=1` to the URL and read the panel

Admin quick edits (cheat-sheet)

The things an operator actually touches most years, in one place:

Want to...	Edit...
Change the event date	Info tab, `first_tee` (ISO format with timezone offset, e.g. `2027-08-14T09:00:00-06:00`)
Set lodging arrangements	Rooms tab — one row per person per room; `guest:Name` for non-players
Change a team / its captain	Field tab, the `team` column — the captain's own row always has `player == team`
Enter a Calcutta bid	Calcutta tab — one row per team lot: `team`, `owner`, `price`; tick `collected` once the pot's been paid
Change the house rake	Info tab, `calcutta_rake` — a plain percentage number (`10` = 10%); if the real intent is "no rake," use `0` explicitly, don't leave it blank or type words
Record a podium finish	Champions tab — place 1/2/3 (blank = 1st, old rows fine) + players = that team's roster, any separator. Backfill history and the podium + draft badges light up.
Add a scouting note	Field tab, `strengths` column — optional; shows on the public #draft board next to the player.
Run draft night	Field tab, `team` column — filling a player's team cell IS drafting them; the site's Draft tab follows live; the pool empties as you type. Afterward, re-run `polish()` and copy the FORM TEAM DROPDOWN block from START HERE into the Form's Team dropdown.

Vault: see "The Admin vault (emails)" further up — one authoritative section.

For whoever maintains this

index.html                    the whole app (HTML + CSS + JS, no build step)
config.js                     the only file you edit routinely
tools/make_template.py        regenerates tools/gfy-template.xlsx
tools/make_admin_template.py  regenerates tools/gfy-admin-template.xlsx (the never-published vault template)
tools/sheet-polish.gs         Apps Script sheet hygiene — checkboxes, dropdowns, Course autofill (see above)
tools/sheet-triggers.gs       Apps Script live-scoring triggers — form writer + paid_date stamp (see above)
tools/presend-check.mjs       the pre-send checker — vault diff, DNI check, email-leak watchdog (see above)
tools/check_template.py       drift check: xlsx templates vs their generators (npm run check-template)
tools/gid-check.mjs           drift check: config.js gids vs the live published sheet (npm run check-gids)
fixtures/                     sample CSVs mirroring the 13 tabs, incl. edge cases
test/smoke.mjs                headless render test against the fixtures

Run the test before deploying any change:

npm install
npm test        # the last line must read TALLY TOTAL with zero failures

Local preview (config.js does not load right from a double-clicked file — always use a local server):

python3 -m http.server 8000     # then open http://localhost:8000

Name		Name	Last commit message	Last commit date
Latest commit History 190 Commits
assets		assets
docs		docs
fixtures		fixtures
test		test
tools		tools
.gitignore		.gitignore
README.md		README.md
config.js		config.js
index.html		index.html
package-lock.json		package-lock.json
package.json		package.json
task-11-report.md		task-11-report.md

Navigation Menu

Repository files navigation

GFY — team scramble site

One-time setup

1. Create the sheet from the template

2. Publish the sheet to the web

3. Find your PUB_ID ← the step people get wrong

4. Find each tab's gid

5. Share the photo folder (optional)

6. Paste it all into `config.js`

7. Check your work

The Admin vault (emails)

Before every send round

Replies (Gmail loop)

Rooms fill in paid order

Polish script (run after big sheet edits)

Live scoring

What a captain sees

One-time setup

Captain links & the Form's Team list

The draft-night drill (SC-DRILL) — blocking, before any link is texted

How it works

Names — the one convention

Year to year

Collecting for next year

The invite list

Adding the Invites tab to a sheet you already built

Rooms

Would-pay, on the Calcutta board

When something looks wrong

Admin quick edits (cheat-sheet)

For whoever maintains this

About

Releases

Packages

Contributors

Languages

Folders and files

Latest commit

History

Repository files navigation

GFY — team scramble site

One-time setup

1. Create the sheet from the template

2. Publish the sheet to the web

3. Find your PUB_ID ← the step people get wrong

4. Find each tab's gid

5. Share the photo folder (optional)

6. Paste it all into config.js

7. Check your work

The Admin vault (emails)

Before every send round

Replies (Gmail loop)

Rooms fill in paid order

Polish script (run after big sheet edits)

Live scoring

What a captain sees

One-time setup

Captain links & the Form's Team list

The draft-night drill (SC-DRILL) — blocking, before any link is texted

How it works

Names — the one convention

Year to year

Collecting for next year

The invite list

Adding the Invites tab to a sheet you already built

Rooms

Would-pay, on the Calcutta board

When something looks wrong

Admin quick edits (cheat-sheet)

For whoever maintains this

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

6. Paste it all into `config.js`