MotorsportReg

MotorsportReg is the source Race Control trusts for rider identity and for which classA competition category such as 600 Superstock. A class joins riders to races, and championship points accrue in it. each rider races. It is the most valuable connection to make.

Connect once

Open Setup → Integrations → MotorsportReg and connect your account. You sign in on the MotorsportReg site, and they hand permission back. Race Control never sees your password.

The connection belongs to your club and lasts until you remove it.

Populate classes before your first event

With an organization selected, open Setup → Classes and select Import From Previous Event. Choose a MotorsportReg event, then review its configured classes. Classes with no registrations are included. You can change local names, correct settings, and clear rows before saving.

The import saves MotorsportReg provider associations with the selected classes. It preserves existing associations and explicit Unmapped choices, and creates no event or registrations. Tracks and classes explains the review, optional fields, and CSV alternative.

Start an event from the calendar

With the connection in place, you can build an event from the MotorsportReg calendar instead of a blank one. Include Past Events loads completed rounds. Race Control remembers this choice and the selected event while you move through this browser session.

Choose the upstream event and select Preview Registrations. The review dialog names the event and dates, shows which registration statuses are included, and counts both registrations and MotorsportReg products before anything is created. You can enter a short local event name, such as Round 3, while the full MotorsportReg title remains visible above it. Select the season for the event, then check Public Pages.

New imported events start Disabled while you review dates, schedule, products, and grids. Select Enabled when the round is ready for the public site. Choose Create Event when the summary is right. Later imports keep the public-page choice saved on your event.

The preview also shows the exact start and end values from MotorsportReg. If both values describe Friday but the title lists more than one day, a notice asks you to review the dates. Enter the approved last day in Local End Date, or leave it blank to use the source value. The date must be on or after the source start date. Race Control does not calculate dates from a title. Your correction stays in place when you import the event again.

Race Control then matches or creates the season and track, creates the event with the reviewed local name or the MotorsportReg title and dates, and imports the registrations. The completion dialog groups any questions by cause instead of listing the same message for every rider. It also gives you the correct next step for your club's race structure.

If a later event gives one race number to a different MotorsportReg member, Race Control keeps the two people separate. The import result names the reused number and shows a provisional local suffix for the new rider. The event uses the number MotorsportReg supplied; the suffix only keeps the club's rider records distinct. Check the named riders before relying on the roster.

If the same member changes race number next round, the new event shows the current MotorsportReg number while the club's Rider record stays linked to that person. Event Overview shows the club, MotorsportReg, and Orbits numbers when they differ. Confirm the right event number there; Race Control records who confirmed it and when.

For a Race Control Schedule club, the first capture creates the people on Riders immediately. Event → Entries stays empty until Race Control knows which MotorsportReg products belong to which classes and races. That is expected: copy the schedule template, review the products in Event → Setup, and apply them to create the class-specific Entries and race starters.

For a qualifying product, select every run that the registered bike can use. The choices show the Day and start time when a QP group runs more than once. Open the qualifying selector to use Select All or Select None. Cancel and Save Targets stay visible while the choices scroll. The selected summary includes each run's Day and start time.

Race Control then compares eligible laps from those runs and names the run that set the grid time. A lap from another registered bike does not carry into that race entry. Check the race's qualifying sessions on Event → Races too; both choices must allow the run.

This match assumes the rider used the bike registered for that qualifying product. The timing CSV identifies the rider and run, but cannot confirm the bike actually used.

If two bike claims target one race entry, or one rider has two bikes assigned to the same qualifying run, registration Preview or Apply Reviewed Products can stop with an error. Event Setup shows the error in a red banner. A saved snapshot Preview shows it inside the import window. A failed Apply keeps the previous entries and starters.

The current error describes the conflict but does not name the rider or bikes. Inspect the MotorsportReg assignments and the product targets in Setup. Correct an incorrect target there, or correct the bike assignment in MotorsportReg and load the updated registrations. If both bikes ran in one qualifying run, the passing CSV cannot identify which bike set each lap. Resolve that attribution before applying the products. A qualifying override cannot bypass this registration check.

MotorsportReg supplies rider identity, class names, and registration time. It does not supply your timed schedule. For a Race Control Schedule club, open the event's Setup leaf next, copy an organization schedule template into the event, and review the captured MotorsportReg products there. Other clubs can continue to build or import the event schedule in their usual way. Schedule templates explains how to build and reuse that organization blueprint.

The product defaults reference explains Disposition, Segment, Class Short, Group Short, matching fields, and Target. Event review keeps captured source fields read-only. You edit the event's disposition and targets, then save and apply the reviewed decisions.

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.

For a compatible linked event, preview runs the real import and then discards it, so you read the exact additions, removals, and questions before anything changes. Update Event then applies them. Provider IDs are support details. They open in a dialog from a Provider ID button, and you never need to decode one to complete an import.

On Event → Entries, MotorsportReg Starter Eligibility shows each assignment's source status and effective starter decision. Choose All Assignments to find a rider. 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 saving or clearing a decision, run Apply Reviewed Products in Event Setup to recalculate race starters and grid readiness, then review affected grids before 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.
• 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 Setup.

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. Product Application Checks lists the checks that must pass before you select Apply Reviewed Products in Setup. 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 entries. A group of 200 such rows is one source condition to inspect, not 200 product decisions.

The same groups appear after a linked update. They do not by themselves mean the update failed. Other review actions and product application checks stay in separate sections.

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.

What a refresh protects

Use Value Sources beside a rider, entry, or event to check a value. Event Setup also has this button. 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.

This is worth knowing before you press it, because the answer is generous.

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.

Who owns your race structure

Clubs split into two camps here, and Race Structure Source on Setup → Integrations says which one yours is. It describes how your club already works, so it is a setup decision you make once.

MotorsportReg Race Segments. MotorsportReg describes the races. An import creates and refreshes your physical races and their starter rosters from the registration data. Choose this when your entry form is where a race first exists.

After importing registrations, you can apply a compatible schedule template from Event → Setup. It keeps the imported race identities and adds their schedule and configuration. Create that template from a completed event under Setup → Schedule Templates. See Schedule templates for the creation flow and compatibility checks.

Race Control Schedule. Your club owns the races, most often from a schedule template. MotorsportReg supplies registration and eligibility only, and an import maps entries onto races Race Control already holds. An apply never rewrites your race structure. Choose this when your race list is settled before entries open.

You can change the setting later, and it is safe to do so, but you rarely want to. Events already linked to MotorsportReg keep the interpretation they were linked under, and the new choice reaches only the next event you link.

Select a source, then choose Save Race Structure Source. Your unsaved choice stays selected if an event import finishes updating the page.

When Race Segments cannot import your products

Race Control checks the products before it imports an event or updates registrations. The preview shows race assignments, practice and qualifying assignments, excluded assignments, and assignments that need product review. Known practice and qualifying products do not create race entries.

If the preview says Race Control Schedule Required, review the product names in the warning. For a new event, cancel the preview. Choose Race Control Schedule under Race Structure Source. Click Save Race Structure Source. Open the preview again. After you create the event, copy a schedule template and review the products in Event → Setup.

A number inside a product name does not always identify a race in your schedule. Race Control blocks the import when it cannot account for the products or when different segments would become one race. It saves no partial import. If the products describe your races in another way, contact support with the product names.

For an event already linked with the Race Segments setting, contact support. If you change the organization setting, that event keeps its saved interpretation.

Fetch registrations on Event → Entries applies this check too. An incompatible source clears the previous preview. Open Setup → Integrations → MotorsportReg to review the products and choose the appropriate flow.

Recover an incomplete first import

If registration capture fails after the event is saved, the result says Event Saved. Registration Capture Incomplete. Your event, season, track, and reviewed details are saved. Select Try Import Again to finish the import in the same event. You can also close the result and reload Integrations; the linked event keeps its recovery notice until a registration import succeeds.

Previously saved registrations remain available if an update fails. Each attempt reads current MotorsportReg data and keeps an import record.

Wait for a preview

The Preview window shows your selected event while MotorsportReg responds. If it cannot load, select Try Preview Again. Your event selection stays in place.

A successful preview keeps the reviewed registrations for ten minutes. Create or Update uses those registrations once. Open Preview again to review new provider data. If the review expires, open Preview again before importing.