How to use — the short version

1. Load a roster — paste one player per line (number name, birthday) and click Load roster, or tap Load Demo Players to try it out with ten fictional kids.
2. Eval — tap a player, dictate or type a note, Cmd+Enter saves. Tap a 1–5 chip only when you're already certain.
3. Score it — Data tab → Copy export → paste into any Claude chat → copy its reply into the Step 2 box → Apply scored data.
4. Draft — the board ranks everyone out of 15; click Draft on a row as players are taken.
5. Protect your data — Data tab → Download backup .json before leaving the field, and always open the app the same way so your saved work is there.

Everything below is the detail behind those five steps.

Phase 1 — Eval

1. Open the app at https://draftnight.pages.dev — works on any device, and on an iPad you can Add to Home Screen from Safari's Share menu. Fully offline instead? Double-clicking index.html or running ./serve.sh (http://localhost:8765) still works. Whatever you choose, use the same method every time.
2. Paste the draft-board tab straight out of the spreadsheet, header row included, and click Load roster. It is read as columns: names, birthdays, last season's stats, and a Notes column of whatever the coaches know. Columns the app doesn't recognise are ignored, so there is nothing to trim first. Put several notes in one cell separated by  | , and lead one with Coach Name: to attribute it.
   
   No spreadsheet? One player per line still works: 12 Jake Sandoval, 2014-03-15, number and birthday both optional.
   
   A row the app can't line up with the header is skipped and named rather than guessed at, and you stay on this screen until you've read the warning. An unreadable birthday is not fatal — that player just loads with a blank age. If you already started, the app reopens where you left off; use Edit roster on the Data tab to change the list. Just exploring? Load Demo Players loads ten fictional 7–9-year-olds instead.
3. Players start in List view; switch to Grid with the toggle next to the filter box.
4. Tap a player. Add as many notes per player as you want — each one saves on its own.
5. The cursor lands in the Note box automatically. Trigger macOS dictation — on most MacBooks that is the mic key (F5) on the function row; check yours in System Settings → Keyboard → Dictation — then speak. On an iPad, tap the mic button on the on-screen keyboard instead. Cmd+Enter saves the note.
6. Tap a 1–5 chip only when you're already certain. A chip beats voice, typed, and the AI.
7. Move between players with ‹ / ›, the Jump to player box, or the ← / → keys. Esc closes the card.
8. Nothing needs saving — every note, edit, and chip writes immediately.
9. Before leaving the field: Data tab → Download backup .json. Clearing browser data wipes the session and this file is the only way back. Restore backup on the same tab reads it back in.

Phase 2 — Hand-off to Claude

10. Data tab → Copy export for a small roster, or Download export .txt and attach the file for a big one. The hint under the buttons tells you which. Either way the payload carries its own scoring instructions.
11. Send it to any Claude session — a brand-new one is fine, it needs no memory of this project. Send it as-is. Do not send the backup .json instead; that is your restore file and has no instructions in it.
12. Copy Claude's reply into the Step 2 box and click Apply scored data. Code fences or extra chatter around the JSON are handled.
13. Read the confirmation — it names any player it couldn't match. Then check the Draft tab.
14. If this fails, skip it. The board still ranks on the chips you tapped. You lose the summaries, not the tool.

Phase 3 — Draft

15. Opens sorted by Total, Available only, top three outlined.
16. Row reads: rank, name, one-line AI summary, then HIT / SPD / DEF and TOT.
17. Search matches names, numbers, transcripts, and AI summaries. Sort by any category to fill a specific hole.
18. When a player is taken, click Draft on the row. No modal opens. To reverse it, filter to Drafted only and click Undo.
19. Click the row body for the full card — complete summary, the verbatim phrase behind each score, all transcripts, and tappable overrides.

Reading the markers

• * on a total — incomplete. Some category was never scored. The player still ranks on the total he has.
• Dashed amber tile — low confidence. Worth a look before you trust it.
• — in a tile — no evidence captured for that category. Never guessed at.
• Age badge (e.g. 11y 4m) — computed from the birthday, shown as of today. When two players have the same total, the younger one ranks first, and players with no birthday sort last within a tie. Sort: Age (youngest) ranks the whole board by age. Age never influences a score — it is a tie-breaker for you, not an input to the AI.
• Prior-season line — the OPS chip on each row, with its rank out of however many players actually have a season (15/87, not 15). Sort: Spring OPS and Sort: Spring AVG rank the board on last season instead of the eval. Open the card for the full line: games, average, OPS, RBI, extra-base hits, each with its rank.
• No season — a no Spring 2026 badge and a dimmed chip. That is missing information, not a bad line: those players never rank as a zero, and they sort last on the prior-season sorts rather than at the bottom. Their card says so in words.
• Coach intel — anything imported in the Notes column shows on both the eval card (above the note box, so you read it before you dictate) and the draft card. It is secondhand, so it can only fill a category you said nothing about, and never beats a manual chip. Availability and logistics in an intel note — missed weeks, an injury, wanting to catch — never move a score.

If something goes wrong