Super-Events

Purpose

Explain how to use a super-event when one physical race or contest should feed results into two or more separate division events.

What a Super-Event Is

A super-event is a container for a combined competition.

Common example:

You still want separate Girls 3200m and Boys 3200m events for scoring, reports, and entries.
But on meet day you actually run one physical race called Combined 3200 Meter Run.
In 2Timer, the combined race is the super-event.
The girls and boys events remain the sub-events underneath it.

This lets operators time or import the race once, while still keeping separate division results where they matter.

When to Use It

Super-events are most useful when:

two or more T&F division events are run together on the track
XC divisions share one physical race but still need separate results
road races combine categories in one timed start but still want split result views

They are less useful when the competition is truly one event with no need to split results later.

How the Data Is Organized

2Timer treats the records differently depending on what you are doing:

Super-event: the combined race or contest operators interact with on race day
Sub-events: the underlying division events that keep entries, scoring, and separate placements

Important rule:

Entries belong to the sub-events, not the super-event itself.

That means:

add or import athletes into the girls, boys, varsity, JV, or other sub-events
do not build the roster directly on the super-event

How to Create One

Go to Events.
Select at least two standalone events that should be run together.
Choose Create Super Event.
Give the combined container a name and event number.
Save it.

2Timer creates a new top-level super-event and links the selected events underneath it as sub-events.

How Timing and Results Flow

For running events, the normal operator workflow is:

Keep entries on the sub-events.
Send the super-event to FinishLynx or import results using the super-event’s event number.
Let 2Timer route each result row into the correct sub-event.

In practice, 2Timer uses bibs and the meet setup to separate the combined race back into the right division event.

What Operators Edit Where

As a rule of thumb:

edit entries and roster membership on the sub-events
enter or import combined race results at the super-event level
review separate placements and scoring on the sub-events

On the Entries/Results side, 2Timer can show:

a combined super-event view
the normal individual sub-event view

Scoring and Places

The super-event itself is a container. It does not become the scored event.

Team scoring stays on the sub-events.
Division-specific places still come from the sub-events.
The super-event can show a combined order for operator review and reporting.

This means you can run one race physically while still preserving separate girls/boys, varsity/JV, or other division outcomes.

FinishLynx Notes

Super-events are especially useful with FinishLynx:

EVT export sends one combined event block to Lynx.
LIF import can take a result file for the super-event and route rows back into the correct sub-event.

For field-event LFF import, there is one important limitation:

a super-event can only route LFF marks automatically when it has exactly one sub-event

If a field super-event contains multiple sub-events, import the field results into the specific sub-event instead.

Markers and Sessions

For timed workflows, treat the super-event as the race that is actually being run.

Put race-day timing markers on the super-event, not on the sub-events.
Use the super-event when the combined race is what should be timed or imported.

Sub-events remain the right place for the separate roster and scoring structure.

Common Problems

Problem	Likely Cause	Fix
Cannot add an entry to the super-event	Super-events are read-only for roster membership	Add the athlete or relay to the correct sub-event instead
Results imported but landed in the wrong division	Routing data was incomplete or ambiguous	Check bib numbers, relay identity, gender, and division setup
Combined result looks right but team scoring is missing	Scoring does not happen on the super-event container	Review the sub-event results and scoring setup
LFF import will not route a field-event super-event	The super-event has more than one sub-event	Import into the specific field sub-event, or use only one sub-event under that container

Good Uses

Combined girls and boys 3200m in track & field
Combined varsity and JV XC race with separate reporting
Combined road-race categories that still need separate downstream views

Metadata

Last Updated: 2026-03-29
Version: 0.1
Status: Active

2Timer Help