Keep it current

The connection is ongoing, not a one-time copy. Integrations marks calendar events already linked to Race Control and offers Preview MotorsportReg Update.

Preview shows the proposed additions, removals and questions before anything changes. Update Event then applies them. Use the labelled provider IDs when comparing source records.

On Event › Entries › Starter Eligibility, the review shows each assignment's source status and effective starter decision. Choose All Assignments to find a rider. Open the row's action menu and use Include or Exclude with a reason when the race-day starter decision differs from MotorsportReg. Race Control records who made the choice and when; Clear returns to the current source status.

An update retains a decision for the same assignment. It asks for review if the source status changes and suspends the decision if the member or product changes. After you save or clear a decision, the next live check applies safe starter changes. Select Check Now in Registration Alerts to check immediately. For a saved snapshot, select Update Race Starters in Registration Review. Review affected grids before regenerating or republishing.

Read the review summary

For a schedule-owned event, Preview counts each current product once:

  • Already reviewed means the saved event decision still matches. A change only to spaces at the start or end of a name keeps the review when the provider IDs match and the reviewed destination is clear.
  • Defaults await event review means a copied default is ready to check.
  • Needs a new decision means no saved decision matches. Preview identifies products that differ from a saved default. Review their exact fields in Registration Review.

Assignment counts and source notices describe the imported data. They are not counts of product decisions. Identity Conflicts names riders who need a number or identity check in Entries.

Each warning names the incoming rider and the other riders involved. A shared-transponder warning shows both riders' names and numbers. Registration Alerts also lists the products and known physical runs.

Separate reviewed runs permit shared use. The same run or an unknown run needs review. Race Control keeps the organization transponder link and each rider's separate identity. Reviewed practice without a scheduled destination is supporting information only. It does not assign that transponder to every run. The same warning appears after Update Registrations.

Product Application Checks lists the checks that must pass before you select Update Race Starters in Registration Review. Apply Snapshot can still capture the source while those checks need attention.

Source Information groups row notices by cause. Open a group to see every affected row. For missing vehicle numbers, it shows each source assignment ID, rider, and product when those rows match the notice count. A missing vehicle number in both MotorsportReg number fields keeps that assignment out of usable race entries.

A practice Orbits run can include a rider without a race number when the rider has a clear transponder. It can recover a blank practice transponder from the same rider's eligible reviewed registrations in this event: use the selected bike's device, or the rider's single device when no bike was selected. Missing or conflicting devices need review. See practice run export.

Source notices also appear after a linked update. Check the update result separately.

The same summary appears when you preview a saved registration snapshot. Preview again after copying a template or saving product reviews to see the remaining work.

Update an existing live-linked event

On Event Imports, preview the linked event and select Update Event. This fetches current MotorsportReg registrations and applies safe starter changes when the event's required product mappings are already reviewed. Changes that need review remain in Registration Alerts. A first import still needs its initial product review. Saved grids need explicit review and regeneration.

What a refresh protects

Open a rider, entry, or event row's action menu and choose View Sources to check a value in Data Sources. Schedule Template and Registration Review also have a View Sources button for event metadata. The window lists each field's current value and the upstream value, provider reference, import time, and fetch time when saved.

Local edits show who made the edit and when. Not recorded means that the saved data has no record for that detail. A refresh keeps local edit records. The window stays open when the list updates.

On Entries, the same window shows each imported lap and the manual qualifying override. When you clear that override, Race Control records who cleared it and when.

A refresh preserves your schedule, your physical waveA group of classes that starts together, with a gap before the next group starts. layout, and your qualifying assignments. It preserves any race name you have written yourself, even while MotorsportReg keeps updating that race classes, starters, and exact vehicleOne motorcycle that MotorsportReg assigned to a rider's class or product. One entry can use different vehicles in different races. assignments.

The event name, dates, and track follow MotorsportReg until you edit that particular field. A local name entered during creation is already an organizer edit. After you edit one, Race Control keeps your version silently and stops following upstream for it. The date range counts as one field.

When a field you are still following really changes upstream, Race Control applies it and reports the exact before and after.

Warning

A refresh updates who is entered. It never regenerates a published gridThe starting order for one race. Race Control generates a grid, and you publish it when it is ready to show riders.. Races whose entries changed are counted under Updates on the Grids leaf, where you review the change and decide.