Schedule templates

A schedule template is your club's reusable blueprint for a race weekend. It belongs to the organization, not to a season. Build it once under Setup → Schedule Templates, then apply it from Event → Setup. A template can create races for a Race Control Schedule event, or schedule races already imported from MotorsportReg Race Segments. The resulting Days, sessions, and races belong to the event. You can adjust them without changing the template or another event.

Copy into an event

Open Event → Setup. Template Start Date starts with the event's reviewed start date. You can change it for an exception. Planned Day Dates shows each Day before you select Preview Copy. Check the resolved preview, then select Copy Template Into Event.

For Race Control Schedule, the copy shows matching template decisions in MotorsportReg Product Review. Review any changed product, then save the event's decisions before applying them.

For MotorsportReg Race Segments, import registrations first. The template keeps those imported races and adds their schedule and configuration. It checks each race's number, Day, and full provider class list, including classes with no registrations. This does not require a separate product review.

The template and event must use the same Race Structure Source. If the preview shows Template Application Blocked, compare Template Expects with Current Provider. Choose or edit the template, or correct the provider setup and import again.

Use Choose Or Edit Template or Review Provider Import for the correction. Then preview again. You cannot override these differences. Race Control checks compatibility again when you apply.

If any Day falls outside the event date range, correct the event dates with Edit Event Dates or choose another start date. Preview and Copy stay disabled until the dates fit. For a provider event that lists only Friday, keep the Friday start and correct the event end date to include the weekend. Reload Setup after the correction to use the updated range.

Create a template

Select Add Schedule Template, then choose New Template for a blank schedule or From Existing Event to reuse an event. For an existing event, select the source event and Continue. The builder follows these steps.

1. Give the template a name. Check Race Structure Source and Event Grid Template.
2. Build or review its Days, sessions, and race configuration.
3. Review optional exact MotorsportReg product defaults when that step is present.
4. Review the schedule and product targets, then select Save Template.

Select a numbered step to return to it or jump ahead. Your edits stay in the builder until you save. The step controls and bottom actions stay visible while the current step scrolls. Save checks the complete template.

For MotorsportReg Race Segments with no product defaults, the builder moves directly from Schedule to Review. Back returns to Schedule. If the draft already has product defaults, it keeps that step so you can review, correct, or remove them. Race Control Schedule keeps all four steps. Orbits settings remain in the session editor for either source.

From Existing Event reads the event as it is now, including organizer changes after an import or earlier template copy. It preserves session times and durations, class order and waves, laps, qualifying links, race names, points multipliers, explicit grid ordering and layouts, and reviewed MotorsportReg and Orbits defaults. Registration lists, timing, results, published grids, and rider overrides remain with the source event.

You can start with an incomplete event. Under Unscheduled Source Races, choose a Day and Schedule Race, or select Exclude This Race. Exclusion also removes product defaults targeting that race when you save. Review each race's qualifying selections and select Qualifying Requirements Reviewed. An empty selection means that class requires no qualifying session. Resolve reported references and configuration issues before saving.

In a race session's editor, Race Name is separate from the schedule session name. Review Points Multiplier, Race Grid Template, and Use Explicit Grid Ordering. Leave explicit ordering unchecked to use the target event policy or organization default.

In Details, Use Explicit Event Grid Ordering sets a template event default. An extracted template keeps the source event's explicit policy. Copy applies it only when the target event has no event override.

Use Track Default and Use Event Or Track Default preserve layout inheritance. A selected layout must match the future event track. Edit and Clone open this builder directly.

For a qualifying product default, select every scheduled run that product allows. If QP1 runs twice, select both runs when both can set the rider's grid time. The list shows each run's Day and start time so you can tell runs with the same code apart. A practice product can select one optional session. You can review and change these defaults on Event → Setup after you copy the template.

A numbered step shows an issue count when its draft needs correction. Open that step to read the issues. You can still move between steps while fixing them. Review shows each Day's sessions and product targets. When you edit a template, it also shows the added, changed, and removed items with their before and after values. A renamed session key or changed product descriptor appears as a removal and an addition.

Each Day header shows a filled triangle and its session count. Select the Day header to show or hide its contents. A newly added Day opens immediately. Use a Day Label such as Saturday or Sunday so staff can recognize it when it is copied into an event.

The compact session table shows start time, code, name, key, type, and race. Its clock follows the organization's Time Display setting under Setup → Settings.

Select a value to edit it in place. Press Enter or select elsewhere to keep a text, time, or race number change. Select Add Session or a row's Edit button to use the full session editor. Press Enter in an input to accept that editor. A new or cloned session appears in the table after you accept it.

Enter start times as 24-hour HH:MM, such as 13:05. The table shows the organization's selected clock format after you save the time.

Select Save Template or Save Changes in the builder to store your edits.

If you close the builder with changes, choose Cancel to return, Discard to close without saving, or Save to store the template. A failed save keeps your edits available. Escape in an inline field cancels that field's current edit.

The red X removes an item only after you confirm its name.

Race waves start at 1 in this builder, as they do on the event's race editor. The class picker works the same way: select classes, drag selected rows into order, and use Starts new wave to create another physical start. Classes with the same wave number start together; choose their shared-start order in the selected setup. The Available Classes catalog keeps every matching class in alphabetical order. Selected classes stay checked there.

Use Find available classes to search the catalog. A selected class also appears in the separate ordered setup for waves and qualifying choices.

Select Select Qualifying Sessions for a class to open a focused table with each session's Day, start time, readable name, and schedule code. Use Select All or Select None for all the offered sessions. The count shows how many are selected. The dialog title, bulk actions, and Done stay visible while the choices scroll. Selected summaries include the Day and start time, so two runs named Q1 remain distinct.

Keep the Combined choice when the club-wide grid merge rule is right for that wave. The first race you add starts with race number 1 even if the Day already has other sessions.

A session's stable key is an internal connection inside the template. Use a short descriptive value such as saturday-ultralight-qualifying; riders never see it. The session code is the short schedule label, such as Q1 or WU3, that Race Control also uses to suggest a timing-file destination. Race classes can select one or more qualifying sessions that contain the same class.

If a source schedule writes Q1: Expert Open, enter Q1 as the Session Code and Expert Open as the Name. The colon only separates the two in that source. Display names remain the names staff and riders read.

Practice, qualifying, and warmup sessions show every organization class as a checkbox list. Use Select All or Select None for the common bulk cases. Select Clone on a session row to open a new prefilled session immediately after it; Race Control gives the copy distinct internal and Orbits identifiers, and Cancel discards the draft.

Sessions display by start time, even when you create or clone them in another order. Sessions without a time display last.

MotorsportReg product defaults

A motorsportreg productA registration choice identified by its MotorsportReg segment, class, and group fields. Review how an event uses each product. describes a registration choice from MotorsportReg. A default tells a future event how to use that choice. Defaults are optional. Leave this step empty if you review products separately for every event.

For a connected event, review its captured products in Event → Setup first. Then save selected reviewed decisions to the template. This keeps the exact provider fields attached to the captured product.

To fill a new or edited rule from stored source fields, select Use Captured Product in the rule dialog. Choose an event and product, check all seven matching fields, then select Use Descriptor. This reads the stored capture; it does not refresh MotorsportReg. Choose the disposition and targets in this template before selecting Add Product Rule for a new rule or Save Rule for an edit. Cancel in the picker or rule dialog leaves the enclosing draft unchanged. An event with no current captured products does not appear in the picker.

The table shows Disposition, Segment, Class Short, Group Short, and Target. Select a value to edit it. Select Edit for the complete rule in a dialog. Cancel in that dialog discards its changes. Accepted changes remain in the builder until you select Save Template or Save Changes. The rule dialog's Cancel and Save Rule actions stay visible while its fields scroll.

Save Rule accepts a full rule edit. Save Targets accepts qualifying choices into that rule or event review. Neither action applies registrations.

Choose what the product does

The product dispositionHow Race Control uses a MotorsportReg product: race eligibility, qualifying, practice, or Ignore. Its target names the local race or sessions. controls how an event uses the registration choice.

If QP1 runs twice, select both runs when both can set the rider's grid time. Day and start time distinguish runs with the same code. Use Select All or Select None in the qualifying selector for the bulk cases. Cancel and Save Targets stay visible while the choices scroll. The selected summary also includes each run's Day and start time.

The race class must also allow the qualifying session. Product targets alone do not change a race class's qualifying choices.

Read the matching fields

These fields come from MotorsportReg. They identify the product; they do not rename a Race Control class or session.

Copy these values exactly. Capitalization, spaces, and blank values affect matching. Race Control first compares all seven fields. If only Segment ID changes, it can reuse a default when the other six fields identify one unique product in both the template and current capture. Changed or ambiguous products need event review.

Target identifies the local race or sessions that use the product. A race target also needs a local class that belongs to that race. Session targets show their Day, start time, name, and code so you can recognize them.

Review each event

A copied default fills the event's product review. It does not confirm or apply registrations. Check the decisions in Event → Setup, then select Save Product Review and Apply Reviewed Products when the review is ready. Event source fields stay read-only so you can compare them with MotorsportReg.

Template changes affect future copies. Events already using the template keep their own schedules and reviewed product decisions.

Export an Orbits run

Select Orbits XML Export in a session only when you need that session in the Orbits XML download. Then select Configure to open the run settings. Leave Orbits Group, Orbits Run Name, or Short Name blank to use the default shown below the field. They follow the session code or key as you edit the session. Type a value to keep it fixed. These settings name the exported Orbits run.

Finish Method selects manual finish or finish at the scheduled race laps. Start Method selects Flag or First Passing, which sets when Orbits starts the run clock.

MotorsportReg Group Names are exact group names from MotorsportReg. Put one on each line. They label the XML class field; reviewed MotorsportReg product bindings select the riders. They are not Race Control classes.

For a practice or warmup run, Audience Source Qualifying Run can name a qualifying session in this template. The copied run uses that qualifying run's reviewed product audience. Choose the source explicitly; a similar name or Group does not create a link. The source key is saved with the template for later event copies.

After you copy a template, open Event → Setup. In Orbits Run Rosters, review the exact product audience and eligible rider count for each run. An existing practice or warmup copy can choose an Audience Source Qualifying Run and select Save Audience Sources. That link applies only to this event. Group-match counts show XML label matches only. To change a label for this event, choose Group names and select Save XML Group Labels.

These selections apply to this event only. To use them for later events, an Admin selects Preview XML Class Label Defaults. The preview lists the old and new Groups for each changed run, with assignment counts. It also shows how many runs would have no matching provider Group labels. Rider counts do not change.

Review the list, then select Apply XML Class Label Defaults. This changes the source template for future copies. It does not change events that already have a copy. If the template or MotorsportReg data changes before you apply, preview again.

MotorsportReg Groups can contain riders from several products. Check each run's intended product audience before promoting its Group labels. Matching counts alone do not prove the XML roster is correct. Group defaults change XML class labels for future copies; they do not change the reviewed rider audience.

Why template edits do not change events

Select Edit on a template to rename it or change it for future events, then select Save Changes. When you copy a template into an event, Race Control creates the event's own Days, sessions, class setup, and qualifying links. It creates races for Race Control Schedule or configures imported Race Segments races. The event keeps that copied schedule, so a later template edit cannot change it. Select Clone when you want a different reusable starting schedule.

Select Delete Schedule Template when the organization no longer needs a reusable template. Events already created from it keep their schedules.

Copy it into an event

Open the event's Setup leaf, choose the schedule template, review its resolved dates and counts, and select Copy Template Into Event. Copying works only while the event has no schedule or earlier template copy. Race Control Schedule requires no existing races. Race Segments requires compatible imported races without organizer changes. After the copy, make event-specific changes under Schedule or Races.

For a Race Control Schedule MotorsportReg event, return to Event → Setup after the copy. Review every captured MotorsportReg product, save those decisions, and apply them. Riders exist from the initial capture; this apply creates the class-specific event Entries and starter rosters.

Reuse reviewed MotorsportReg products

After you save the product review in Event → Setup, an organization Admin can select Save as Template Defaults. Choose the schedule template for a future event and preview the rules before saving. The list shows products that would add a new rule, already have the same rule, conflict with an existing rule, or cannot use a race, class, or session in that template. Select the products you want to reuse. Review any conflict before choosing to replace its existing rule.

Race Control copies the exact product fields from the captured MotorsportReg data. You do not need to type provider IDs. Products that still need review or are absent from the latest capture cannot become defaults. When you save defaults, Race Control does not change this event or an earlier copy.

In a future event, Race Control first checks all seven product fields. MotorsportReg gives the same product a new Segment ID for each event. Race Control then uses the other six fields when they identify one saved rule and one product in the new event. A product with changed fields or more than one possible match needs your review. After you copy the template, check and save all starting decisions in that event before you apply them. You do not need to import the event a second time.

If you save a later event's reviewed product as a default, Race Control checks for a saved rule with the same six fields. It updates that rule. If the decisions differ, the preview asks you to choose whether to replace the saved rule. If more than one rule or product has those six fields, Race Control cannot choose a rule for you.