Upload your Excel track notes file (.xlsx). Each sheet should be one circuit. AI will parse every sheet and create track guides.
For the Castle Combe starter or any JSON file — use Import JSON Backup in the section below, not this uploader.
Export your entire database as JSON for backup, or import a previously exported JSON to restore or merge data.
| FL | FR | RL | RR | |
|---|---|---|---|---|
| LS Bump | ||||
| HS Bump | ||||
| Rebound |
Renames a car name across all sessions, guides, and KB entries. Use this to fix typos or merge duplicates (e.g. "BMW M3" → "BMW E36 M3").
Excel track notes, JSON backup restore, and guide import tools.
Corner names, distances and sector boundaries are read from the circuit definition at parse time, so a stored analysis keeps whatever was current when it was parsed. Re-parse pending only touches files older than the current parser version, so it is safe to run any time — but after editing corner data in Circuits every file already matches, and nothing is pending. Use Re-parse ALL once you have corrected corner names, distances or geometry.
Boundaries sit at points of maximum speed — the end of a straight, where braking for the next corner begins — pooled across every stored file for the layout and saved onto the corner each one precedes. That gives every file the same sectors, so times can be compared between drivers. Evidence is shared between layouts where the approach is shared; a corner you have set by hand is never overwritten. Run after a re-parse, then re-parse again so stored analyses pick the new boundaries up.
Cars granted to race teams by their owners. Car owners manage this from the Car tab.
Teams manage cars across multiple owners. Adding a member gives them access to all team cars automatically.
Non-admin chat and WhatsApp interactions — requests, responses, write changes, and token usage.