Import registrations

Registration data is the one source that says which classA competition category such as 600 Superstock. A class joins riders to races, and championship points accrue in it. each rider races. Load it first, and most of the work later in the weekend disappears.

Choose Value Sources on an entry to inspect its field values. The window shows upstream references and times, plus who made a local edit and when. Imported laps and manual qualifying overrides have separate records. When you clear a manual override, its edit record stays available.

Why registration comes first

To check points for the entered riders, use Season Points on this page. Expand a cell to read its source or missing-data reason. See Speedhive for the next steps.

Timing data does not say which class a rider is in. A qualifying session records a lap against a rider, and the stored class on that row reads Qualifying for every one of them.

Registration data carries the answer, so importing it creates the riders, the classes, the entryOne rider in one class at one event. A rider who races three classes has three entries. records, and the races in one step. A recent WMRRA round loaded as 150 riders, 27 classes, 358 entries and 24 races with nothing flagged.

Import from MotorsportReg

If your club takes entries through MotorsportReg, open Setup → Integrations and connect your account once. After that, open the event and choose Import Registrations on the Entries leaf.

Race Control never sees a MotorsportReg password. You sign in on their page, and they hand back permission.

Files and pasted JSON work without a connection. Live fetching needs a connected MotorsportReg account and a selected organization under Setup → Integrations.

MotorsportReg covers the connection and what a later refresh does.

For an event that uses a Race Control schedule, open Event → Setup to review the captured MotorsportReg products before applying them. Each row shows a readable product name, class, and group. Select Exact Source Fields to inspect all seven values from MotorsportReg when two products look similar. The same dialog shows the Provider ID, Race Control's source key for that exact product.

Use Review Class Aliases when the provider uses a short class name. Choose the local class and inspect Affected Products. The choices apply to this preview; save the exact product decisions after review.

Use Preview Schedule Proposals to review exact class names, Days, and retained schedule audiences. Each destination shows its own class, Day, and race or qualifying runs. An exact product label in the copied schedule can identify a repeated race or both qualifying runs. Qualifying decisions omit warmup runs. Apply Schedule Drafts fills those decisions on screen. Save and apply the product review to update starters.

Products with changed source fields, conflicting labels, or no unique destination stay under Individual Review. Check the reason and choose the decision in the product table. Select Exact Source Fields to inspect all provider values.

For many products, Bulk Product Review filters by the provider's segment text, class, modifier, and group. The matching selection chooses only current unresolved products with distinct displayed names; ambiguous names need individual row selection and exact-field inspection. Choose one disposition and its class or schedule target, then Preview Bulk Decision. The preview shows the exact selected products, destination, reviewed decisions that would be replaced, and products still needing review.

Apply Bulk Draft changes the on-screen decisions. Use Save Product Review and then Apply Reviewed Products to keep them and update starters.

After you save the review, an organization Admin can select Save as Template Defaults. That panel starts with no products selected. Select All Eligible deliberately chooses every reviewed, resolved product and shows excluded and ineligible counts. Preview the exact products and any conflicting existing defaults before saving.

This creates starting decisions in a schedule template. The selected defaults help with future events; they do not change this event. If MotorsportReg changes only a product's event-specific Segment ID, Race Control can still fill its decision when the other six fields identify one product. Review and save the products in each future event before applying them.

Import a saved MotorsportReg snapshot

You can copy a schedule template before importing registrations. Until you capture a source, Event → Setup shows no MotorsportReg products. Your copied schedule is ready. Open Entries and choose Import Saved Snapshot to add the products for review.

On an existing event, open Event → Entries and choose Import Saved Snapshot. Choose MotorsportReg, select a saved snapshot file, and select Preview Snapshot. Read the source event, capture time, full SHA-256 digest, registration statuses, product count, proposed changes, and any Review notices. A notice can explain why two riders have the same race number across events.

Select Apply Snapshot when the file matches the event you intend to update. The result keeps the Review notices visible. You select the file; you do not need to open or paste its contents.

Product Application Checks in Preview affect Apply Reviewed Products in Setup. They do not prevent Apply Snapshot from capturing the source.

For an event linked to MotorsportReg, the same dialog offers Download Current MotorsportReg Snapshot. Save that file when you need a fixed copy of the current provider responses. A saved file can also come from an earlier capture or from reconstruction work. The capture time and file source appear in Event → Setup. A saved snapshot includes MotorsportReg assignments, segments, and attendees together. A simplified entry-list JSON is a different import format and cannot supply the exact product review.

After import, use Event → Setup to review the exact products and apply their race and class decisions. The file import keeps your schedule and published grids. If eligibility changes, review the affected grids before republishing.

For a linked MotorsportReg event, MotorsportReg Starter Eligibility on this page lists source statuses and effective starter decisions. Choose All Assignments to find a rider, then Include or Exclude with a reason. The decision belongs to this event and survives another saved snapshot or MotorsportReg update for the same assignment. Clear restores the current source status. Run Apply Reviewed Products in Event Setup after a decision to recalculate starters, then review affected grids before republishing.

Review a historical workbook reconstruction

Use a separate historical organization and an event without a live MotorsportReg link. Import a saved snapshot, review its products in Event → Setup, then open Entries and select Workbook Reconstruction. Check the source event, capture time, and full frozen source digest. The digest stays visible after activation and reload so you can compare it with the file used in the snapshot preview. Enter a clear label and select Activate Reconstruction.

Wait for the review to finish loading before you select an assignment or edit a claim. This also applies after Reload Review.

After activation, you can return to Event → Setup and select Save Product Review for more whole-product decisions. Follow its Open Entries link, select Workbook Reconstruction, then select Preview Reconstruction and Apply Reconstruction to update the event. Setup does not offer Apply Reviewed Products for an active reconstruction.

Use Find Assignment to locate a captured row. Choose the assignment and compare its original and effective values. Exact Source Fields shows the provider product descriptor. Edit the name, number, vehicle, or transponder when the workbook supports the correction. Name corrections apply to this event's entries and grids.

Reviewed Product Target changes only this assignment's destination. Local Rider can link a claim to an existing MotorsportReg rider; also review its displayed name and number. The review shows the source member ID and the local rider that the current claim uses. Check this link for each workbook name correction before you apply.

Enter a reason and a source citation, such as a workbook sheet and row. Select Save Claim. Claim History retains the actor, time, reason, and source citation. To restore all source values, enter a reason and select Clear Claim. A blank edited text field clears that value.

Select Preview Reconstruction and read the proposed changes. Open Existing Rider Links to check each provider member against the organization rider selected for Apply. If Preview lists New Organization Riders, check each name, number, and member ID. Link the assignment to an existing rider when the workbook identifies one. Use the approval box for each person who needs a new organization record. Apply stays unavailable until you review all proposed riders.

Select Apply Reconstruction after this review. Apply updates entries, starters, vehicles, and qualifying scope. Review affected grids before you regenerate or publish them. If the roster or decisions change, select Reload Review and Preview again.

Use MotorsportReg Starter Eligibility for a historical inclusion or exclusion. Record an assumption as an assumption: a workbook entry does not prove a past provider status. The original saved snapshot stays unchanged.

For a workbook row absent from the capture, open Workbook-Only Assignments. Select an existing MotorsportReg-linked rider and a reviewed product. Enter the reviewed name, race number, vehicle claim, reason, and workbook source citation, then select Add Workbook Assignment. This creates a local ID. It does not supply a provider assignment ID, status, or receipt time. An administrative product can have an active local row without adding a starter.

Leave Race Number blank for an Ignore product when the workbook has no number. Race, qualifying, and practice products require a number. Preview and Apply check the number again if the product review changes.

The review lists active and retired local rows with their source citation, actor, and time. To remove a local row from the next reconstruction, select it, enter a retirement reason, and select Retire Workbook Assignment. The original claim and retirement history remain visible. Preview and apply again after an addition or retirement. To correct a local row, retire it and add a replacement with the corrected source citation.

Remove an unused rider after a correction

Open Riders, find the extra rider, and select Review Cleanup from its row menu. The review lists entries, assignments, or decisions that block removal. It also lists unassigned vehicle records that cleanup will remove. Check the rider and enter a cleanup reason. Then select Remove Unused Rider.

Race Control records the rider and related records with your name and time. Workbook claim history stays available. If the review shows a blocker, correct or retire that reference and review cleanup again.

Late registrations are the normal case

Most clubs have their entry list close to final before the weekend. What is not settled is the tail: riders enter on the day, constantly, and they change classes after that. One observed weekend took ten late registration changes, the last of them after qualifying had run and before the first race.

Race Control exists in large part to make that reaction quick. The old answer was to write a new grid by hand.

The loop has three steps and you will run it more than once a weekend.

1. The rider changes their entry, and MotorsportReg updates.
2. You open Event → Entries and choose Update Registrations.
3. If a grid is affected, you review and republish it.

That button reads Import Registrations until the event is linked to MotorsportReg, and Update Registrations every time after. It is the same button, and it is the one to reach for on a race morning.

A later import finds riders by their MotorsportReg member ID when one is known. It keeps earlier identity decisions and tells you what changed. If a number belongs to a different member in the new event, the import keeps both people and names the conflict in its result. Review that result before you move on.

Refresh the whole event

Update Registrations covers who is entered. When the event itself changed upstream, such as its dates or its races, use the fuller refresh on Setup → Integrations.

Preview MotorsportReg Update there runs the whole import and then throws the result away, so you read the exact additions, removals, and questions first. Update Event applies them.

Enter riders by hand

Manual entry is the full fallback and is always available. Open Riders to add people to your club roster, then open Event → Entries to enter them in classes for one event.

A rider is a person. An entry is that person in one class at one event, and you enter them class by class. A rider who races three classes has three entries, and each entry grids separately.

Enter the rider's full race number, including any letter suffix. Race Control treats letters without regard to case and shows them in capitals: 143f appears as 143F on the roster and grid. A lowercase spelling cannot create a second rider with the same number.

Review historical fallback order

Open Fallback Order to record an order from a historical source. Use Bulk Review to paste several ranks and citations. Preview the effect across the event's races before saving. When you save ranks, saved and public grids keep their existing order. See How grids are ordered for the input columns and review steps.

Check the vehicle for each entry

The Vehicles column shows the vehicleOne motorcycle that MotorsportReg assigned to a rider's class or product. One entry can use different vehicles in different races. that MotorsportReg assigned to each entry. A dash means MotorsportReg supplied no vehicle. One entry can show more than one vehicle when the rider uses a different motorcycle in another race.

Race Control keeps the vehicle with the exact MotorsportReg class or product assignment. It does not use the transponder as the vehicle identity, because the same transponder can move between motorcycles. Change incorrect vehicle data in MotorsportReg, then choose Update Registrations again.

The result counts vehicles recorded or updated and vehicle assignments added or removed. A correction that changes only a vehicle still appears as a change.

Resolve a registration vehicle conflict

Open Event → Setup and read Vehicle Conflict Review. Preview also shows these cases before you capture a saved snapshot. You can capture the source while a vehicle conflict remains.

Each case shows the rider, motorcycles, source products, assignments, and affected race or qualifying run. Compare the vehicle IDs even when the motorcycles have the same year, make, and model. The review stays available after you reload the event.

For a race-entry conflict, two motorcycles claim the same rider's entry in one race. Select Review Product to check the race and class mapping. A product mapping affects every rider assigned to that product. Use Save Product Review after a correction.

Select Review Assignment to inspect one exact assignment in Entries. If the claim is incorrect, choose Exclude, enter the reason, and select Save Decision. Exclude only the incorrect claim. Keep the other assignment included. You can also correct the source in MotorsportReg and capture it again.

For a qualifying-run conflict, one rider claims two motorcycles in the same run. Timing identifies the rider and run. It does not identify the motorcycle that set the lap. If both claims are correct, ask race staff for corrected source evidence. A motorcycle choice or qualifying override does not resolve this conflict.

Return to Setup after a correction. When no vehicle conflicts remain, select Apply Reviewed Products. Race Control checks the current claims again before applying them. A remaining conflict blocks the whole application and keeps the previous starters and grids.

When the import cannot decide

The import never guesses. Identity questions and unusable rows appear for review. Registration vehicle conflicts block Apply Reviewed Products until you correct them. You can still capture the source for review.

Two kinds of question reach you.

Identity questions group into cases on the review screen. A number that matched a different name is one. So is a rider who appears twice under two numbers, and a suffix sibling. You decide each case once, and every later import replays that decision.

Rows nothing can fix stay untouched, and the import names them. A blank race number gives Race Control nothing to key a rider by, and a blank class gives it nowhere to put them. The fix belongs in the source file, and the reconcile queueThe list of imported records that Race Control could not match with confidence. You decide each one, and the decision survives the next import. says so plainly. It offers no action, because none exists.

Check before you move on

Open Event → Overview. It states what is still missing before the event races can take a grid. This is the fastest way to find a class with no entries, or a race with no classes.