Once you have loaded qualifying timing, you generate grids for the whole event at once. You never do it blind.
On Event → Overview, the Races list shows two different counts. Eligible riders counts the distinct riders on a race's current roster; a rider entered in two classes counts once. Current Grid shows rider positions on the saved grid. If those counts differ, open the grid and review the next grid before you publish an update. The saved grid does not change when registrations or race setup change.
Choose the compact Published link in a race's Current Grid column to open its public grid in a new tab. The arrow beside the label indicates the new tab.
Generate the whole event
Open Event → Grids and choose Review Ready Grids. Race Control runs your grid configurationThe ordering criteria, qualifying policies, and wave placement settings that decide who starts where. Set the organization default under Setup, an event override under Event → Setup, or a race override under Event → Grids. for every race in the event. Each race uses its own qualifying sessions. Its grid templateThe shape of the starting grid at one track: how many rows, how many positions in each row, and which side pole is on. comes from its race override, event selection, or track default, in that order.
To change ordering for this event, open Event → Setup and edit Grid Configuration. Races with their own ordering overrides keep those overrides. After a settings change, review the affected grids and regenerate them. Saved grids keep the policy that produced them until you do so.
Race Control saves nothing yet. What you get is a review. If a wave cannot fit, the race row tells you its rider count, where that wave starts, how many empty rows precede it, and how many template rows remain. Check the race roster, template rows, gap between waves, and any rider position decisions before you generate again. A template can have more total positions than riders and still be too short after a required gap.
Read the before and after
Each race shows its Day and date so repeated race numbers remain distinct. Choose Details to read its riders, or Show All Details to open every visible race. Hide All Details closes them. The Wave column uses physical wave numbers starting at 1 and shows old and new waves when they differ. You can check waves before you save any grid.
- Before is the current gridThe starting order for one race. Race Control generates a grid, and you publish it when it is ready to show riders., or the words this grid was empty when there is none.
- After is the grid Race Control would generate now.
- A per-position difference marks every rider who moved, entered, or dropped.
- A row marked Updated shows a changed race number, rider name, or class name. It shows the old and new text even when the position stays the same.
This is the confirmation surface. Read the differences, not the positions. A grid that moved one rider and a grid that changed completely look alike until you read what moved.
Ready, waiting, and the override
A race is ready when you have assigned every qualifying session it needs, and each one has an imported classification. You can also record a session as cancelled or waived, which makes the race ready without it.
Race Control selects the ready races that changed. Races that are waiting start unselected and name the sessions they are missing.
Warning
When you generate a grid before its qualifying has run, Race Control falls back to the next criteria. That means points where you have them, then registration order. That grid looks finished and is not. The override exists for a cancelled session, not for impatience.
To generate one anyway, tick the readiness override on that race after reading what it is missing.
Publish
The review header carries Select All, Today Only, and Clear, with a running count of how many races are selected. Today Only picks the races running today, which is how a club that grids one morning at a time works. Select All suits a club that qualifies once and prints the whole weekend.
To save without publishing, choose Save as Drafts. The review keeps your selection and open details, then shows All races so the saved drafts stay visible. You can publish the same selection after checking it. When you reopen a review with no changes, it selects its ready drafts.
Deselect any race you are not ready to publish, then publish the rest. A published grid is visible to riders immediately.
Each replacement carries a revision number, which is the current one plus one. Riders see that number. It is how a rider holding a printed grid knows their copy is out of date. Enter 0 to clear the public marker. A first grid is a hidden revision 0.
Race Control keeps the revision and the timestamp unchanged when nothing a rider can see has changed.
The review names the timing source frozen into each grid. That is an Orbits file, a Speedhive provisional classification, a manual override, or a combination when several sessions contributed.
Regenerate a published grid
Race Control always asks before it regenerates a published grid. No data import, registration refresh, or class correction ever rewrites a grid riders have already read.
To change one race's grid configuration, open it under One race and choose Edit Grid Configuration. The summary identifies whether it uses a race override, the event default, the organization default, or the built-in default. Save the settings, then review and regenerate the grid. See How grids are ordered for inheritance and reset behavior.
When something changes underneath a published grid, the race appears under Updates and reads Update available. Review Update takes you to the same before and after screen.
This is the busiest path on a race morning. A late registration lands through Update Registrations on Event → Entries, and every race that rider touches turns up here for you to read and decide. See Import registrations.
To check a saved draft on paper, open One race and choose Print Draft. The page shows the full grid, including empty rows, and marks it as a draft. Only staff with event access can open it. The grid stays unpublished when you print it.
Open the event page and choose Print all grids to print every published grid with a page break after each one. One race prints from its own page.
Print from your browser. The printed page is the deliverable, and there is no separate export.
The online grid expands across a desktop screen so you can read long race names and rider details. On a phone it stays compact. A printed grid uses the paper layout at any screen size.
When a grid comes out wrong
Work through it in this order.
- Check the race has classes and the classes have entries, on Event → Entries.
- Check the race is bound to the right qualifying session, on Event → Races.
- Check the qualifying classification actually loaded, on Event → Schedule.
- Check that race's criteria and their source, on Event → Grids. Change the club default on Setup → Grid Configuration when it must apply to all races that inherit it.
In Position Details, check why each rider starts where they do. It shows the lap time and session, points, fallback order, or a manual override. The public grid shows the starting order without staff-only reasons. When a rider can use two qualifying runs, the quicker eligible lap in the same qualifying tier sets the order. The grid names the run that supplied it. If two runs share a code, the Day and start time distinguish them.