For clubs & series organisers
Run your series on the data you already generate
Your meetings are already imported and your classes already have pages. A coordinator can score a championship under any points system you like, build a handicap grid from real race pace, and fix the class records that timing sheets got wrong, and all of it is reversible. Or do the whole lot by asking, through the MCP server your AI assistant can connect to.
Coordinator access is granted by hand, one class at a time.
Your class already has a page
Every class that has ever run at a New Zealand circuit meeting in this archive has its own page: its lap records at each circuit, its highest-rated drivers, its history year by year, and where its drivers came from and went next. Nobody had to enter any of it.
So the starting point is not a blank system to populate. It is a record of your series that already exists and is mostly right, and a set of tools for the parts that are not.
There are 2,022 active classes in here and 168 of them are sub-classes hanging off a parent, because a real series splits by engine capacity or by era and the records need to follow that split rather than fight it.
| Class | Results |
|---|---|
| Formula First | 10,662 |
| BMW E30 | 9,515 |
| Dual Sprints | 9,449 |
| Pre 65 | 8,617 |
| Central Muscle Cars | 6,731 |
Score a championship on your own rules
Points systems are all different and mostly not negotiable, so nothing here is preset. You define the points for each finishing position, a fastest-lap bonus and how far down the field it applies, an attendance point, a multiplier for a double-header round, and how many worst results get dropped, either by race or by round total, because those are not the same thing.
Co-drives are a toggle too: an enduro pairing either scores as one entry, or the points split to both drivers and merge with their solo races.
Standings are worked out from the actual results each time they are asked for, so there is no separate scoring step to forget after a meeting, and correcting a result corrects the table.
| Rd | Circuit | Date |
|---|---|---|
| 1 | Teretonga Park | 06 Jan 1991 |
| 2 | Levels Raceway | 20 Jan 1991 |
| 3 | Ruapuna Park | 03 Feb 1991 |
| 4 | Manfeild Autocourse | 17 Feb 1991 |
| 5 | Baypark Raceway | 03 Mar 1991 |
Fix what the timing sheets got wrong
An archive built from decades of timing exports has real problems in it: the same driver entered under three spellings, a combined grid filed as one class, a car running in the wrong category all weekend. A coordinator for your class can fix all of that directly, scoped to your class and nobody else's.
Every change is logged and reversible. That is the part that matters, and it is why coordinators are trusted with it: a class reassignment repoints the record without ever overwriting the original timing string, so an undo is exact rather than a best effort.
- Approve who is whoDrivers claiming their own record in your class come to you, along with the corrections they propose to their name, country and home track.
- Split and merge the classesCreate sub-classes under your series, rename one, retire one that never ran again. And move results in bulk: one race, one meeting, or a whole class at once.
- Undo anythingEvery action lands in an audit list with the exact rows it touched, so a reassignment made in error is one click back.
Build a handicap grid from real race pace
If you run handicap races, the hard part is that a driver's single best lap is not their race pace, and the gap between the two differs per driver. This works it out from their own history, taking their average lap against their best lap and pulling it toward the average for that class at that circuit when a driver has little history. Then it turns that into start offsets.
It also corrects for traffic, since the quickest car starts last and loses time getting through the field, and it accounts for the first lap being slower than the rest. Paste your entry list in and it resolves the names against their history; type a time next to a name and that overrides it.
Calibrated against 243 real handicap races. Being straight about it: from a cold start expect a finishing spread around 25 to 30 seconds, which is honest but not as good as an experienced handicapper adjusting round by round. Pace prediction hits a wall at about 6% and no amount of arithmetic gets past it.
| Input | Where it comes from |
|---|---|
| Best lap | Their own history at this circuit |
| Race pace factor | Their average lap ÷ best lap |
| Class × circuit mean | Calibrated live, not hardcoded |
| Traffic correction | +6.7% fastest, −3.3% slowest |
Or just ask for it in plain English
Everything on this page can also be done by talking to it. Momentum publishes an MCP server (Model Context Protocol, the open standard for connecting an AI assistant to a system it can read and act on). A coordinator adds it to whichever assistant they already use and works their class in a conversation: ask why a lap record is showing the wrong name, get the answer with the evidence, and have the fix applied.
Because MCP is an open protocol, it is not tied to one product. Assistants that support it include Claude, ChatGPT and Gemini, and anything else that can add a remote MCP server by URL. Setup is a little different in each, but the tools and the rules are identical whichever you pick.
It is the same authority as the workspace, not a second one, so it is limited to the same classes and follows the same rules. Nothing changes without showing you first. Every request to alter data comes back as a preview of exactly what would change and how many rows, and it only goes ahead once you agree. Merging two drivers, or moving a whole class at once, needs that preview first and cannot be done in a single step.
Access is by an admin-issued key, one per coordinator, which you collect once from your own dashboard and can have revoked at any time. There is a daily limit on how many changes it can apply, and every call is logged.
- “Why is the Manfeild record not Kenny’s?”It checks the ranking the site uses against every one of that driver’s laps, and tells you which ones are not counted and why. Usually the lap is real and filed under the wrong sub-class.
- “Move his 2019 results into Open Class.”It comes back with the exact races and the row count before anything happens. You say yes, and it applies and tells you how to undo it.
- “Set up the winter series, 25-18-15, drop the worst round.”Championships, rounds and points schemes as well: it can build the season, add the meetings that score and read you the standings.
What it costs
Nothing. There is no club subscription, no per-series fee and no charge for the coordinator tools. Your meetings are imported whether anyone asks or not, because the archive wants them anyway.
What coordinator access needs is a conversation, not a payment. It carries the ability to edit shared records such as driver identities and class assignments, so it is granted by hand, one class at a time, to someone the class already knows. There is no self-serve button for it on purpose.
If your meetings are missing, or a series you run is filed wrongly, that is worth telling us regardless of whether you want the tools.