Participants

The Participants page records the number of athletes the Meet Director expects to enter each event, division, and gender combination.

These anticipated numbers are used by Torunit to estimate heat sizes and build the initial one-day schedule.

The figures entered here are planning numbers. They are not the final entry list.

Who should use this page?

The Participants page is primarily intended for one-day meet scheduling.

Use it before building the schedule when the actual entry list is not yet complete.

The Meet Director should make the best reasonable estimate of how many athletes will compete in each event, division, and gender.

Torunit uses those estimates to create appropriately sized schedule blocks before final entries are available.

Anticipated participants

Each event is displayed with one entry field for every applicable division/gender combination.

For example:

100 — Girls 11–12
100 — Boys 11–12
100 — Girls 13–14
100 — Boys 13–14

Enter the anticipated number of athletes for each combination.

A blank field is treated as zero.

Why anticipated numbers matter

The schedule uses these numbers when calculating the expected size of an event.

Examples:

8 anticipated athletes may require one heat.
23 anticipated athletes may require several heats.
A field event with 40 anticipated athletes may require substantially more time than one with 8 athletes.

These are planning assumptions. Later real entries may replace the anticipated figures.

Event totals

Torunit adds the division/gender values within each event and displays the total anticipated entrants for that event.

This allows the Meet Director to see quickly whether an event is expected to be small or unusually large.

The event total changes as the individual anticipated counts are edited.

Track and field layout

The page is divided into three columns on larger screens:

Track — running (1)
Track — running (2)
Field events

On smaller screens the columns collapse into a single column.

The two track columns are a display convenience. They do not represent separate tracks.

Maximum athletes per heat

Track events include a max/heat setting.

This allows the Meet Director to override Torunit's normal heat-capacity calculation for a particular event.

Auto

Leave the field blank, or use zero, to allow Torunit to determine the heat capacity automatically.

The current page describes the automatic behavior as:

Sprint events — generally one athlete per usable lane
Distance events — generally two athletes per lane using waterfall-style capacity

The exact heat calculation may also depend on later schedule and facility settings.

Manual override

Enter a number when a specific event should use a different maximum number of athletes per heat.

Examples might include:

A waterfall race where the Meet Director wants a smaller field
A special meet format
A facility-specific operating limit
A local rule or safety restriction

A manual value overrides the normal automatic calculation for that event.

Saving

Anticipated participant counts save automatically after editing.

Torunit waits briefly after an edit before sending the updated values.

The status area may display:

Saved
Save failed
Save error

Save all

The Save all button immediately saves the current anticipated participant values.

It is useful after making several changes or before leaving the page.

If round settings are open, Save all also saves those currently enabled round settings.

Rounds on a one-day meet

A one-day meet may still use qualifying rounds.

If Has rounds was selected when the meet was created, eligible events display a + rounds control.

The current Participants page exposes the rounds control only for:

Non-field running events of 400 metres or shorter
Short hurdle events of 200 metres or shorter

Not every event is therefore offered a rounds control on this page.

+ rounds

Select + rounds to open the round-planning fields for that event.

When open, the control changes to:

− rounds

The available fields are:

Rounds
Advance per heat (Q)
Prelim heats
Target finalists
Lanes / capacity

Rounds

Enter the number of competition rounds.

The displayed example identifies:

2 = prelim + final

For more complex multi-round planning, see Rounds.

Advance per heat (Q)

Enter the number of automatic qualifiers advancing from each heat.

Capital Q represents qualification by place.

For example:

2 Q

means the first two qualifying athletes from each heat advance automatically.

Additional qualifiers may be selected by time depending on the meet format.

Prelim heats

Enter the expected number of preliminary heats.

This number should be consistent with the anticipated entries and lane or capacity setting.

Target finalists

Enter the total number of athletes intended to advance to the final.

Example:

8

for an eight-athlete final.

Lanes / capacity

Enter the usable number of lanes or the applicable capacity for the event.

This is used when determining how many competitors can be placed into each heat.

Closing the rounds panel

Selecting − rounds closes the panel and disables round planning for that event.

The current implementation immediately clears the enabled-round status for the event when the panel is closed.

Do not close the panel merely to reduce screen clutter if the event is intended to retain its rounds configuration.

Relationship to the full Rounds page

Participants contains a simplified one-day rounds editor.

The separate Rounds page provides more detailed GDE-level planning, including:

More than two rounds
Q and q calculations
Separate advancement targets by round
Field qualifying rounds
Combined-event planning
Traveling groups
Bulk copy tools

Use the simpler Participants controls when the one-day meet only needs straightforward round planning.

Use the full Rounds page when the meet requires detailed advancement logic.

Current implementation notes

The following items should be reviewed as Torunit development continues:

The simplified rounds editor does not currently show the same advancement-math validation used by the full Rounds page.
Verify whether the hard-coded rounds-eligible event list should also include relays or other event types.
Closing an open rounds panel immediately disables that event's rounds configuration; confirm that this user behavior is intended.
participants.blade.php contains its own inlined event-block renderer while participants/_event-block.blade.php also exists. The two have already diverged; the partial does not contain the newer max/heat control. The duplicate implementation should be consolidated or the unused partial removed.
The relationship between manual max/heat overrides and later per-round lane/capacity settings should remain a single clear source of truth.