A session template stores the configuration for one practice, qualifying, or race session. It belongs to the organization. It can include duration, classes, race laps, physical waves, grid settings and Orbits export settings. Its Day, start time, position and number are chosen in the schedule.

Create a session template

Open Setup › Session Templates. An Admin can select Add Session Template to start a new configuration, or From Existing Schedule to extract reusable configurations and link the original schedule's sessions to them.

To extract repeated configurations from a schedule, see Extract session templates.

An unlinked schedule session offers Save as Session Template to create a library record from its configuration. A linked session offers Open Session Template to edit its existing source and Save as New Session Template to create a separate configuration. Both save-as actions open a new draft and leave the schedule row's source link and local overrides unchanged. A new library record does not attach an unlinked session to it.

The editor has six steps: Session, Classes & Rules, Names & Numbering, Orbits, MotorsportReg Defaults and Review. Select a step to jump to it, or use Back and Continue. When you move between steps, the editor keeps one draft.

In Session, give the configuration a Template Name and set its type and duration. Choose classes and race rules in Classes & Rules. Set generated session labels in Names & Numbering. In Orbits, enable Orbits XML Export to show the export settings and Orbits label patterns directly.

Track Layout is optional. Keep Use Event Layout to use each destination event's layout, or choose a catalog layout that belongs to the destination's track family. Linked schedule sessions inherit this setting from the source. An individual session can override it; select Use Template Value on that field to restore inheritance.

For a race, choose its qualifying session templates beside its classes in Classes & Rules. For an Orbits practice, Rider Roster in Orbits uses Assigned MotorsportReg Products by default. You can select a qualifying configuration to use its reviewed riders instead. The schedule links that reference to sessions on the selected Day.

A practice can have a name such as Friday Practice or Warmup. Its name and code do not change its type or rider rules. Use the existing Generated Session Code pattern for labels such as P{group_number}, FP{group_number} or WU{group_number}.

In Orbits, set Require Bike Numbers beside Rider Roster when every rider in that practice run needs a number. Practice allows blank numbers unless this requirement is enabled. The number requirement and rider roster are separate choices.

Under Qualifying Requirements by Class, each selected race class has one row with its saved requirements. Select Select Qualifying Templates on that row to choose qualifying configurations that include the class. Choose No Qualifying Required when the class needs none. Not Configured means you have not recorded a choice for that class; it is different from choosing none.

The row shows one selected template by name, or a count when several are selected. Open the selector to inspect every choice. View Details shows each saved qualifying template in its own row beneath its class.

Apply Selection updates that class in your session template draft. Other classes keep their choices. Cancel or Escape closes the selection dialog without applying its changes. Select Save Session Template in Review to save the whole template. If you cancel the main editor and discard its changes, the saved requirements stay unchanged.

In MotorsportReg Defaults, review the product defaults that belong to this configuration.

Use registration defaults to review a product's disposition and targets.

Choose This Session Template as the target to use the session created from this configuration. Each schedule supplies its Day and start time. An Ignore product has no target.

Open Review and select Save Session Template. Validation checks the whole draft and takes you to the step that needs a correction. Cancel closes the editor. If you have unsaved changes, choose Save, Discard or Cancel. Save in that prompt also checks and saves the whole draft.

Build a different schedule from an existing one

See Extract session templates for extracting configurations and cloning the source schedule.

Generated and custom values

See Set generated session labels for the steps.

Use and maintain the library

See Reuse session configurations for placement, timing conflicts and library maintenance.

Override one inherited field

Edit a linked session in the schedule template to change one field locally. Other fields continue to follow the library. The session editor identifies the source and shows Use Template Value beside each overridden field. Select it to restore that field's current library value. Other overrides stay in place. Save the schedule template to keep your local changes.

An older schedule with an unavailable source keeps its last resolved settings. Events already created from a schedule template keep their event configuration; later library edits do not rewrite them.