A 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. is an ordered list of criterionOne rule that orders riders, such as qualifying lap time. A grid configuration applies its criteria in order. entries. Race Control applies them in order to decide who starts where.
Tiers, not a blended score
This is the part worth reading twice, because it is what makes a grid match club practice.
Race Control does not score each rider and sort by the total. It works in tierA group of riders that the same criterion ordered. Riders with no data for a criterion fall to the next tier, behind everyone the criterion placed. steps.
Every rider with data for the first criterion grids first, sorted by it. Riders with no data for that criterion form the next tier, below all of them, sorted by the second criterion. The last tier is registration order.
A rider who crashed in qualifying therefore grids behind every rider who set a lap. They do not get mixed in among them. That is the ordinary club convention, and it is why tiers matter more than the criteria list.
Tie-breaks
A tie breaks by the next criterion in the list. A missing value sorts last.
If the criteria run out, Race Control breaks the tie by registration time, and then by race number. Two runs of the same data can never disagree, so a regenerated grid is stable.
What is available today
- Qualifying lap time, the default first criterion.
- Previous event at the same track.
- Current class season points, which needs a confirmed standings snapshot from Speedhive.
- Registration order, the final tier.
Previous-season points, overall points, previous-round finish, and a seeded random draw are not built.
Ordering criteria
List criteria in the order you want Race Control to apply them. Best qualifying lap puts every rider who set a valid lap ahead of the riders who did not. Current class points needs a confirmed Speedhive standings import. Best lap, previous event at track uses the most recent earlier event at the same track. The next criterion only orders riders that the earlier criterion could not separate.
A qualifying lap belongs to the rider
A lap belongs to the rider, not to one entry. It carries to that rider other entries in the same qualifying groupA label that says which classes one bike can plausibly race. A rider's qualifying lap carries to their other entries in the same qualifying group..
A lap set directly in a class always beats a lap carried into it. See Tracks and classes for how to label the groups.
Qualifying aggregation
This setting chooses a lap when more than one qualifying session is eligible.
- Best Across Sessions uses the fastest valid lap. This is the default.
- Most Recent Session uses the best lap in the latest eligible scheduled session. Upload order does not change which session is latest.
For example, a rider sets 1:40 in Q1 and 1:42 in Q2. Best Across Sessions uses 1:40. Most Recent Session uses 1:42. If the rider misses Q2 or records no valid lap there, Most Recent Session does not use the older Q1 lap. The usual qualifying carry can still supply a lap from the latest eligible carried session. If neither source supplies a lap, the next criterion applies.
Race Control skips a cancelled session without a classification. A cancelled session with a classification keeps its recorded evidence. Race Control uses the race's assigned sessions and, where available, the registered motorcycle's reviewed runs. A manual qualifying time keeps its existing priority.
Qualifying carry
This setting controls which entered classes can use one rider's lap.
- Same session uses only a qualifying session tagged for the class being gridded.
- Same group also accepts a lap from another entered class with the same qualifying-group label. This is the usual choice when several race classes qualify together.
- Any class accepts any eligible qualifying lap for that rider. Use this only when motorcycle or class differences do not make the comparison unfair.
An individual class can inherit the effective race setting or override it on Setup → Classes.
Untimed qualifying fallback
This applies only after every configured criterion is exhausted.
- Registration order puts all remaining riders into one tier, earliest registration first.
- Missing before no time first places riders who have no eligible qualifying appearance, then riders who appeared but recorded no valid lap. Registration order sorts each group. Race Control always says Missing; it does not use an unexplained abbreviation.
Fallback class order
This changes only the final untimed tier. Intermixed registration order sorts all remaining riders together. Reverse declared class blocks keeps classes in separate blocks and starts with the last class declared for that wave. Timed riders remain intermixed.
Reviewed historical fallback order
To reconstruct an order from a historical source, open Event → Entries and choose Fallback Order. Use Single Entry to record one decision or Bulk Review to review several decisions together.
A fallback rankA reviewed historical ordering key for one event entry, which can apply in several races. Lower ranks come first within the final fallback group; they do not request grid positions. is a positive ordering key. Lower ranks come first. It is not a requested grid position.
Ranks apply after all configured criteria, within the existing Missing or no-time group and class order. Ranked entries precede unranked entries in that group. Equal ranks and unranked entries keep registration order. A rank does not change timed positions or points positions. Manual position overrides still apply.
Enter several ranks
- Choose Bulk Review.
- Enter a shared source if the rows use the same document.
- Paste spreadsheet rows with these columns: Number, Class, Rank, Citation, and optional Reason.
- Choose Add Pasted Rows.
- Check each resolved rider and class.
- Correct each row that shows an error.
Copy tab-separated cells from your spreadsheet. You can include the column headings or omit them. Include the full rider number and suffix. Number and class must match exactly and identify one entry. Race Control does not match by surname or create an entry. If a row does not resolve, select its entry from the row's list.
Use Add Row to select an entry without pasting.
Record the exact race, wave, and row in each citation. The shared source and row reason combine with that citation into the saved reason. The final reason must contain 1–200 characters. Shorten the wording yourself if it exceeds this limit; Race Control does not truncate it.
A blank rank is incomplete. It does not remove a rank. Use Remove Rank in the single-entry list for removal. Duplicate entries, unavailable entries, invalid ranks, and missing citations block the review. Different entries can have equal ranks.
Review and save
- Choose Preview Ranks.
- Read the changes for every affected race.
- Check each rider's Position Details.
- Choose Save Reviewed Ranks when the full review is correct.
The default comparison is Current Computed Order against the proposed order. Choose Saved Grid to compare the proposed order with the saved grid. Check its Draft or Published state. That comparison can include timing or entry changes that are separate from your rank decisions.
A decision applies to the event entry in every race it enters, even when its citation names only one race. The preview identifies races where timing or another criterion makes the rank ineffective. Partial coverage can move unranked riders too. Check those changes before saving. A partial count does not establish that the historical grid is complete.
Correct any preview error before saving. If entries, ranks, or grid inputs change after the review, choose Preview Again. Race Control saves the complete reviewed batch together. An unchanged row does not add another history record.
Use History to read replaced and removed decisions. Stale means the entry is unavailable or its rider or class changed. Review that entry before saving a new rank. Registration receipt times remain unchanged.
When you save ranks, saved and public grids keep their existing order. Review and regenerate the affected grids separately. Published grids require confirmation before regeneration. See Generate and publish grids.
Wave placement
Gap rows between waves leaves the chosen number of completely empty grid rows between each wave. A value of 1 leaves one blank row.
Fixed start rows starts each wave on the exact one-based rows you enter, such as 1,7,13. Use this only when the club's published procedure fixes wave starts to grid rows; otherwise a gap is easier to maintain when field sizes change.
Where the settings attach
Set a default for your club on Setup → Grid Configuration. To change one event, open Event → Setup, edit Grid Configuration, and choose Save Event Config. Use Organization Default clears the event override.
A race uses its own explicit configuration, then the event configuration, then the organization default. The event screen names the effective source and counts races with their own overrides. Those races keep their policies when you change the event configuration.
On Event → Grids, open one race to see its effective settings and source: Race Override, Event Default, Organization Default, or Built-in Default. Edit Grid Configuration opens the race editor. Save Configuration saves a complete ordering override; Cancel discards the draft. Equal values still count as an explicit override.
To restore race ordering inheritance, choose Use Event Default, Use Organization Default, or Use Built-in Default, according to the source shown. Read the confirmation. When you clear the ordering override, the race inherits placement again and keeps independently saved wave composition. The race keeps its classes and physical wave assignments. Legacy composition stored only in the cleared ordering override inherits again.
When you save or restore settings, saved grids stay the same. Review and regenerate to apply them. Published grids require explicit confirmation.
A schedule template made from an event keeps its explicit event policy. When you copy that template, an event with its own policy keeps it. An event without one receives the template policy. Template races without their own policies inherit the target event policy or organization default.
When you edit a race's classes or waves, its ordering policy keeps inheriting the event or organization default. Those edits save wave composition independently from ordering settings.
Why each rider has a position
Race Control stores the details behind each position with the grid. In Position Details, you can read the lap time and session, the points total, or the fallback that placed the rider.
Staff can review those details when they need to explain the order. The public sheet shows the starting order and omits staff-only reasons for manual overrides. Race Control also stores a copy of the configuration that produced the grid. A later settings change cannot rewrite a grid you already published.