Torunit Manual - User contributions [en]

Rounds

2026-10-10T23:56:59Z

Trackinfo: /* Lanes */

{{DISPLAYTITLE:Rounds}}

The '''Rounds''' page defines how athletes advance through qualifying rounds before the schedule is built. If you don't have rounds, you shouldn't see this page.

It operates at the '''GDE''' level — Gender, Division, Event — so different divisions or genders in the same event may use different round structures when necessary to pare down to a final.

Before you have any entrants, the page also allows you to place anticipated participant counts so you can make the plan to calculate heats and advancement.

== Who should use this page? ==

Use the Rounds page when a meet requires more detailed advancement planning than can be handled by the simplified [[Participants]] page.

This may include:

* Preliminary rounds
* Quarterfinals
* Semifinals
* Finals
* Different advancement patterns by division
* Field-event qualifying rounds
* Large championship meets
* Combined-event traveling groups

A meet that conducts every event as a single final may need very little work on this page.

== GDE round planning ==

Each row represents one Gender/Division/Event combination.

For example:

* 100 — Girls — 11–12
* 100 — Boys — 11–12
* Long Jump — Girls — 13–14

This allows the Meet Director to configure each competition group independently.

Rows are identified as:

* '''Track'''
* '''Field'''
* '''Combined'''

The available controls differ by type.

== Entries ==

Enter the anticipated number of athletes for the row.

These anticipated numbers are used to estimate the number of heats and the size of later rounds.

They are planning values and may later be replaced by actual entries.

== Track-event round planning ==

Track rows allow one through four rounds.

Current choices are:

* '''1 Final'''
* '''2 Prelim/Final'''
* '''3 Prelim/Semi/Final'''
* '''4 rounds'''

== 1 Final ==

The event is conducted as a single round.

There is no advancement calculation.

== 2 Prelim/Final ==

Athletes compete in preliminary heats and qualifying athletes advance directly to the final.

The principal settings are:

* Entries
* Lanes
* To next/final
* Q per heat

Torunit calculates the remaining lowercase '''q''' qualifiers.

== 3 Prelim/Semi/Final ==

Athletes advance:

# Preliminary round
# Semifinal
# Final

Additional semifinal controls appear.

These include:

* Semi → Final target
* Semi Q / heat

== 4 rounds ==

A four-round event adds an additional intermediate round.

The current page exposes:

* Preliminary
* Quarterfinal
* Semifinal
* Final

Additional controls include:

* Quarter → Semi target
* Quarter Q / heat
* Semi → Final target
* Semi Q / heat

== Lanes ==

Enter the usable lane or heat capacity for that GDE.

Torunit uses this number to calculate the number of heats.

The number should represent the actual capacity used for that round, not necessarily the total physical lanes at the venue.

For example, a nine-lane facility may intentionally use only eight lanes in a particular championship round. If you are running a distance with waterfall starts and multiple alleys, you might even put a few dozen.

== To next/final ==

Enter the total number of athletes who should advance from the current round.

In a two-round event this is the number advancing from preliminary heats to the final.

In a three- or four-round event it represents the target for the next stage.

Additional target fields appear for the later stages.

== Q — automatic qualifiers ==

Capital '''Q''' represents automatic qualification by finishing place.

Enter the number of automatic qualifiers from each heat.

Example:

<code>3 Q per heat</code>

means that the first three qualifying athletes from each heat advance automatically.

== q — time qualifiers ==

Lowercase '''q''' represents athletes who advance by time rather than by automatic place.

Torunit calculates the required number of lowercase q qualifiers from:

* Number of heats
* Q per heat
* Total advancement target

Example:

If there are three heats and:

<code>2 Q per heat</code>

then six athletes advance automatically.

If the target is eight qualifiers, Torunit calculates:

<code>2 q</code>

additional qualifiers by time.

== Advancement checker ==

Torunit checks the round mathematics as values are entered.

The checker can identify conditions such as:

* Trying to advance more athletes than entered the round
* Automatic Q places producing more qualifiers than the target
* Q per heat exceeding the number of lanes

When the values are valid, the row displays a summary describing:

* Number of heats
* Q per heat
* Number of lowercase q qualifiers

When the values are invalid, the row displays an error message.

Example:

<code>3 Q × 4 heats = 12 automatic qualifiers, but only 8 advance</code>

The advancement settings should be corrected before the meet schedule is considered complete.

== Quarterfinal settings ==

Four-round events expose a separate Quarterfinal advancement section.

=== Quarter → Semi target ===

Enter the number of athletes who should advance from the quarterfinal to the semifinal.

=== Quarter Q / heat ===

Enter the number of automatic qualifiers per quarterfinal heat.

Torunit then checks the advancement calculation for that stage.

== Semifinal settings ==

Three- and four-round events expose semifinal advancement controls.

=== Semi → Final target ===

Enter the number of athletes who should advance from the semifinal into the final.

=== Semi Q / heat ===

Enter the number of automatic qualifiers per semifinal heat.

Torunit checks the resulting automatic and time qualification totals.

== Field-event rounds ==

Field rows use a different competition model than track heats.

Current choices are:

* '''1 Final'''
* '''2 Qual/Final'''

=== 1 Final ===

All entered athletes proceed directly to the final competition.

=== 2 Qual/Final ===

A qualifying competition is conducted before the final.

The field-event row provides settings for:

* Anticipated entries
* Number qualifying to the final
* Number receiving the final three attempts
* Automatic qualifying mark

== Number qualifying to final ==

Enter the number of athletes who should advance from the qualifying round into the final competition.

This is the field-event equivalent of the advancement target.

== Number receiving final three attempts ==

Enter the number of athletes who should receive the final three attempts.

This may differ from the total number initially advancing into the final competition depending on the meet's field-event format.

== Field Q mark ==

Enter an automatic qualifying mark when the competition uses one.

An athlete achieving the automatic Q mark qualifies according to the meet's field-event advancement rules.

The mark should be entered using the format expected by Torunit for that event.

== Combined events ==

Combined-event rows are treated differently from ordinary track and field rows.

A combined-event row records a single anticipated participant count.

The athletes remain together through the chain of component disciplines.

The separate rounds columns are therefore not used in the same way as ordinary track or field events.

== Traveling groups ==

Combined-event divisions may be organized into '''Traveling Groups'''.

A traveling group allows multiple combined-event GDEs to move through the component facilities together.

This is useful when several small combined-event divisions can share the same sequence of stations.

The current design aims for groups near approximately 16 athletes per shared station.

=== Form Traveling Group ===

Check two or more combined-event rows and select:

'''＋ Form Traveling Group'''

Torunit assigns those rows to a common traveling group.

Each group is identified by a color and a label such as:

* Group A
* Group B
* Group C

A summary displays:

* Number of GDEs in the group
* Total anticipated athletes
* Relationship to the approximate 16-athlete target

=== Group size guidance ===

The current interface provides guidance such as:

* '''room to add more'''
* '''good — near target'''
* '''over 16 → engine splits into flights'''

This is planning guidance rather than a competition rule.

=== Add another row to an existing group ===

If the checked rows contain exactly one existing traveling group, newly selected combined-event rows are added to that group.

=== Ungroup Checked ===

Select combined-event rows and choose '''Ungroup Checked''' to remove them from their traveling groups.

=== Release one division ===

A row may also be removed individually from its traveling group using the × next to the group badge.

== Row selection ==

Each GDE row contains a checkbox.

The checkboxes are used by the bulk-copy and traveling-group tools.

Shift-click may be used to select a continuous range of rows.

== Copy checked row to same event ==

Check exactly one source row.

Select:

'''Copy checked row to same event'''

Torunit copies the source settings to the other GDE rows for that same event.

This is useful when several divisions should use identical round rules.

== Copy first checked to checked ==

Check two or more rows.

The first checked row becomes the source.

Select:

'''Copy first checked to checked'''

Torunit copies its settings to the remaining selected rows.

This allows the same structure to be applied to unrelated events or divisions.

== Select Same Event ==

Check one row and select:

'''Select Same Event'''

Torunit selects all rows belonging to the same event.

This is useful before applying a bulk operation.

== Clear Checks ==

Clears the row-selection checkboxes.

It does not intentionally clear the round plan.

== Clear Round Entries ==

Clears the round-planning values on the page after confirmation.

Use this carefully.

The current implementation resets round counts and several default values and clears other row inputs.

Because this action autosaves, the cleared values become the current round plan.

== Min/heat ==

The '''Min/heat''' setting establishes the scheduling gap associated with round heats.

The current default is:

<code>4 minutes</code>

The field accepts quarter-minute increments.

For example:

<code>0.25</code>

represents 15 seconds.

This allows high-volume sprint meets to use smaller per-heat timing increments when necessary.

This value concerns schedule timing rather than qualification mathematics.

== Save Round Plan ==

Select '''Save Round Plan''' to save the current configuration immediately.

The status area may display:

* Unsaved changes...
* Saving...
* Saved ✓
* Save error

== Autosave ==

Changes to GDE rows automatically schedule a save after a short delay.

The following actions also trigger autosave:

* Editing anticipated entries
* Changing round settings
* Changing advancement settings
* Changing the Min/heat value
* Creating or removing traveling groups
* Bulk-copy operations
* Clearing round entries

A manual Save Round Plan button remains available.

== Sort ==

The rows may be reorganized without changing their underlying round settings.

Available sort orders are:

* '''Event → Gender → Division'''
* '''Gender → Event → Division'''
* '''Division → Event → Gender'''

Sorting is a viewing tool. It does not change the event or division identity of a row.

== Top / Return ==

Because the Rounds page can be long, the toolbar contains an '''↑ Top''' button.

Selecting it returns to the top of the page.

The button then changes to:

'''↩ Return'''

Selecting Return restores the previous scroll position.

== Relationship to scheduling ==

The Rounds page tells Torunit how many competition stages must exist before the schedule is constructed.

Its settings influence:

* Number of heats
* Number of rounds
* Size of later rounds
* Qualification structure
* Timing requirements
* Combined-event grouping

The schedule should not invent a different advancement plan.

The Meet Director's explicit round decisions should remain authoritative.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* The page correctly detects invalid track advancement mathematics and marks the row invalid, but the current save function does not appear to block an invalid row from being saved. Invalid round plans should not silently become authoritative.
* Verify whether invalid rows should block only their own save or the entire Round Plan save.
* Verify field-event automatic Q-mark entry format and downstream interpretation.
* Verify the intended distinction between “number qualifying to final” and “number receiving final three attempts” for all supported field-event formats.
* '''Clear Round Entries''' currently clears substantially more than just the number of rounds. Confirm that it is intended to clear anticipated counts, field Q marks, field finalist values, and traveling-group information as well.
* Confirm that the approximate 16-athlete target for combined-event traveling groups remains the desired operational rule.
* The full Rounds page and the simplified rounds controls on [[Participants]] should remain coordinated so they cannot establish contradictory sources of truth.

== See also ==

* [[Participants]]
* [[Create-Meet]]
* [[Venue]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Combined Events]]

[[Category:Meet Director]]
[[Category:Rounds]]
[[Category:Schedule]]
[[Category:Meet planning]]

Micro/Daily Scheduler

2026-10-09T21:04:23Z

Trackinfo:

{{DISPLAYTITLE:Micro/Daily Scheduler}}

The '''Micro/Daily Scheduler''' is the detailed operational scheduling page for a multi-day meet. The naming has taken on both names because it works hand in hand with the [[Macro Scheduler|Macro]] page where schedule blocks are coarsely moved for multiple day meets, but this is essentially a daily full schedule broken down into each little element.

The [[Macro Scheduler]] establishes the large-scale structure of the meet:

* Which day an event occurs
* Which facility it uses
* Its general order
* Its scheduled starting position

The Micro/Daily Scheduler takes those scheduled blocks and exposes the detailed operation inside them.

It is where the Meet Director can examine and refine:

* Divisions within a block
* Individual heats
* Heat capacity
* Heat duration
* Time between heats
* Transitions
* Hurdle changes
* Field flights
* Facility assignments
* Combined-event sequences
* Detailed start times

== Who should use this page? ==

Use the Micro/Daily Scheduler for a multi-day meet after the major schedule structure has been established on the [[Macro Scheduler]].

A normal one-day meet should generally use [[Schedule]] instead.

Micro/Daily is particularly useful for meets where the Meet Director needs detailed control over the way each competition block actually operates.

== Macro and Micro are one schedule ==

Macro and Micro are not separate schedules.

Both are views of the same operational schedule.

A block moved or edited in Micro remains the same competition block that appears on Macro.

Likewise, a block placed on Macro becomes available for detailed operation in Micro.

The purpose of the two pages is different:

'''Macro Scheduler'''
: Places the large pieces.

'''Micro/Daily Scheduler'''
: Controls the detail inside those pieces.

A human decision made on either page should remain authoritative.

Automation may recalculate dependent information, but it should not silently replace a Meet Director's deliberate order, placement, capacity, or timing decision.

== Day navigation ==

Each competition day has its own tab.

Examples:

* Day 1 · Fri Jun 12
* Day 2 · Sat Jun 13
* Day 3 · Sun Jun 14

Select a day to display its detailed schedule.

Only one day's Micro schedule is displayed at a time.

== Overview ==

The '''Overview''' view divides the day's schedule into:

* Track
* Field

This is the easiest way to see the day's overall operating sequence.

Each event appears as a schedule block containing its important competition information.

== Facilities ==

Select:

'''⊞ Facilities'''

to view field events according to the individual physical facilities where they are conducted.

Instead of one general Field column, this view may show facilities such as:

* Long Jump North
* Long Jump South
* High Jump
* Pole Vault
* Shot Put North
* Shot Put South
* Cage
* Javelin

The available facilities originate from [[Venue]].

This view is useful for determining whether each pit, ring, runway, or cage has a physically workable schedule.

== Return to Macro ==

Select:

'''Macro →'''

to return to the [[Macro Scheduler]].

Use Macro when the problem concerns:

* Day
* Broad event order
* Major placement
* Facility
* Large schedule structure

Use Micro/Daily when the problem concerns:

* Heat detail
* Division detail
* Exact timing
* Internal transitions
* Facility operation

== LIVE and LOCKED ==

A day may display one of two states:

* '''● LIVE'''
* '''● LOCKED'''

A LIVE day remains part of the active derived schedule.

A LOCKED day is intended to preserve detailed authored information rather than freely rebuilding that day's schedule from upstream changes.

The locking feature should be used when a day's detailed schedule has reached a point where the Meet Director does not want routine regeneration to replace those decisions.

'''Current implementation note:''' The exact normal-user lock/unlock workflow should be verified before this section is treated as final.

== Meet-level settings ==

Several controls near the top of Micro/Daily apply to the meet rather than only to the currently displayed day.

These settings are shared with other scheduling pages rather than being separate Micro copies.

== Heat gap ==

Sets the standard time between track heats.

The Heat gap is the same underlying value used on [[Rounds]].

Changing it on either page changes the same meet setting.

The value may use quarter-minute increments.

Examples:

* <code>4</code> = 4 minutes
* <code>1.5</code> = 1 minute 30 seconds
* <code>0.75</code> = 45 seconds
* <code>0.25</code> = 15 seconds

A change to Heat gap may require Torunit to regenerate calculated schedule information.

== Hurdle transition ==

Sets the normal amount of time allocated for changing a hurdle configuration.

A hurdle transition may involve:

* Changing hurdle height
* Moving hurdles
* Changing spacing
* Changing the race configuration
* Preparing the next hurdle group

Torunit may use actual hurdle-format information in addition to this meet-level setting.

== Recall warm-up ==

Sets the warm-up period given to field-event competitors who must be recalled from an earlier flight for additional attempts.

For example, if the athletes advancing to the final three attempts come from more than one flight, athletes from an earlier flight may need time to warm up again.

If the final competitors all come from the final flight, no recall may be required.

== Field flights ==

Controls the general field-event seeding policy.

Current choices are:

* '''Balanced'''
* '''Stacked'''

=== Balanced ===

Strong marks are distributed through the available flights.

This provides a more even distribution of competitive ability.

=== Stacked ===

Stronger marks are concentrated toward the final flight.

This can be useful where the Meet Director wants the strongest athletes competing late and wants the final-attempt cut to emerge primarily from the final flight.

== Auto-ripple ==

Controls whether later dependent schedule items automatically move after an earlier change.

When Auto-ripple is on:

* A delay can move later events later.
* Gaining time can allow later events to move earlier.
* An explicit anchor remains fixed.
* Dependent events are recalculated from that anchor.

Ripple should follow human decisions rather than replace them.

== Heat sizing ==

The Heat sizing control selects which participant counts are used to determine heat structure.

Current choices are:

* '''ANTICIPATED'''
* '''REAL'''

=== ANTICIPATED ===

Uses the planning figures entered before registration is complete.

This allows the schedule to remain stable while registrations are still arriving.

=== REAL ===

Uses actual registered participant counts.

Switch to REAL when registration is complete enough that the Meet Director wants the operating schedule based on the athletes who are actually entered.

Actual counts may still be displayed while ANTICIPATED remains the sizing authority.

== Per-day timing settings ==

Each day also has settings that apply specifically to that day's operation.

These include:

* First track event
* First field event
* Fixed
* First call
* Check-in
* Warmup

== First track event ==

Displays the currently scheduled first Track competition of the day.

This is derived from the operational schedule.

== First field event ==

Displays the currently scheduled first Field competition of the day.

== Fixed ==

Indicates that the day's detailed timing contains explicit time anchors that should be preserved.

A fixed time represents a Meet Director decision.

If earlier activity makes that time impossible, Torunit should identify the conflict rather than silently changing the fixed time.

== First call ==

Sets how many minutes before competition the first call should occur.

Example:

<code>30</code>

means the first call occurs 30 minutes before the applicable competition time.

== Check-in ==

Sets the normal advance time associated with athlete check-in.

The exact check-in sequence may vary according to the event and Clerk of Course operation.

== Warmup ==

Sets the normal field-event warm-up allowance for the day.

This affects the amount of operating room required between field competitions using the same facility.

== Understanding a schedule block ==

Each competition appears as a schedule block.

A block represents an operational portion of the schedule rather than merely the name of an event.

A block may contain:

* Event
* Round
* Gender
* Division
* Athlete count
* Heat or flight count
* Start time
* Duration
* Facility
* Combined-event relationship
* Hurdle requirements
* Implement information
* Internal heat timing
* Warnings
* Detailed settings

== Event name ==

The event name is the primary heading of the block.

Internal Torunit event-family codes are converted to their public event names for display.

== Round ==

Where applicable, the competition round is included with the event name.

Examples:

* 100 Prelims
* 200 Semifinals
* 800 Final

Round identity matters because different rounds may have different:

* Participant counts
* Lane capacities
* Advancement structures
* Scheduling requirements

== Combined-event parent ==

A combined-event component may identify its parent combined event.

Examples:

* DEC · 100
* HEP · HJ
* PENT · SP

The component is still scheduled on its actual physical facility.

For example:

* A Decathlon Shot Put component uses a Shot Put ring.
* A Heptathlon High Jump component uses a High Jump facility.
* A Decathlon 100 uses the Track.

See [[Combined Events]].

== Facility ==

The block may display the physical facility where it is assigned.

Facility assignment should correspond to the facilities established on [[Venue]].

== START HERE ==

A linked sequence may identify the first operational stage with:

'''▶ START HERE'''

This helps identify the entry point into a chain of dependent events.

== Division and gender composition ==

A block may contain several Gender/Division groups.

Examples:

* G 9–10
* B 9–10
* G 11–12
* B 11–12

For each group, Micro may show:

* Anticipated athletes
* Real athletes
* Number of heats
* Effective capacity

These values explain how Torunit arrived at the block's heat structure.

== Anticipated versus real counts ==

Where both values are available, the block may show the planned and actual entry counts together.

This allows the Meet Director to see whether reality is significantly different from the schedule assumption.

A large difference may justify changing Heat sizing from ANTICIPATED to REAL.

== Combining divisions ==

Where permitted, two or more divisions may be combined operationally into the same race.

Combining divisions does not necessarily combine their:

* Results
* Scoring
* Records
* Qualification status

It means they compete together operationally.

The Meet Director's explicit decision to combine divisions should remain authoritative.

== Unganging divisions ==

A previously combined race may be separated back into its individual divisions.

Changing the combination may alter:

* Heat count
* Athlete distribution
* Block duration
* Later schedule times

Dependent calculations should be rebuilt while preserving unrelated human decisions.

== Borderline heat decisions ==

Torunit may identify a division whose athlete count lies just beyond the normal preferred heat size.

The Meet Director may be offered a choice such as:

* '''Combine into one'''
* '''Split into two'''

This is intentionally a human decision rather than an arbitrary automatic choice.

Once made, the choice should remain stored until the Meet Director changes it.

== Heat breakdown ==

A schedule block can be expanded to show its detailed internal sequence.

Track blocks may display individual heats.

The detailed rows may include:

* Heat number
* Gender/division
* Athlete count
* Start time
* Estimated duration
* Setup or transition rows

This detailed sequence is the Micro portion of the schedule.

== Editing a heat time ==

Individual heat start times may be edited.

An edited heat time is an explicit Meet Director decision.

Later dependent heats should ripple from the change.

The system should not silently restore the previous automatically generated time.

== Block Settings ==

Select the '''⚙''' in the event block header to open:

'''Block settings'''

The Block Settings dialog allows detailed schedule preferences to be established at three levels:

* Block
* Division
* Heat

This provides progressively more specific control without requiring every value to be manually entered for every heat.

== The inheritance system ==

Micro/Daily uses inheritance.

A more specific setting inherits from its parent unless the Meet Director provides an explicit override.

The hierarchy is:

'''Calculated or meet default → Block → Division → Heat'''

For example:

* Meet heat gap = 4 minutes
* Block gap = blank → inherits 4 minutes
* Division gap = 5 minutes → that division uses 5
* Heat 3 gap = 7 minutes → Heat 3 uses 7

Blank does not mean zero.

Blank means:

'''Use the inherited value.'''

The settings dialog displays the inherited value so the Meet Director can see what will actually be used.

== Block-level settings ==

Block-level settings apply to every appropriate division and heat in the block unless overridden at a lower level.

Available block preferences currently include:

* Division order
* Capacity
* Heat duration
* Gap after
* Transition before
* Transition after

== Division order ==

Controls the order in which the divisions inside the block compete.

A Meet Director may deliberately move divisions into the desired operating order.

The saved human order overrides the automatic order.

Divisions that are newly added or not explicitly listed should remain present rather than being discarded.

They follow the explicitly ordered divisions until the Meet Director places them.

== Reordering divisions ==

The Block Settings dialog allows the division order to be changed.

The current interface supports:

* Moving a division earlier
* Moving a division later
* Dragging divisions
* Reversing the order

After saving, the block should use that order when constructing its detailed heat sequence.

== Capacity ==

Capacity determines the maximum number of athletes assigned to a heat for the applicable scope.

A block-level capacity applies to each division unless that division has its own capacity override.

The number of heats is then calculated separately for each division.

Example:

Suppose a block contains:

* Girls 11–12 — 41 athletes
* Boys 11–12 — 55 athletes

with an effective capacity of 9.

Torunit should calculate each division independently:

* Girls: <code>ceil(41 / 9)</code>
* Boys: <code>ceil(55 / 9)</code>

and then combine the resulting heat counts into the block.

The athlete totals should not be combined first and divided afterward.

== Division-level capacity ==

A division may have its own capacity.

Example:

Block capacity:

<code>9</code>

Girls 11–12 capacity:

<code>8</code>

Boys 11–12 capacity:

blank

The Girls division uses 8.

The Boys division inherits 9.

== Heat-level capacity ==

An individual heat may also have its own capacity.

This allows unusual operational circumstances to be represented without changing every heat in the division.

For example:

* Heat 1 capacity — 9
* Heat 2 capacity — 9
* Heat 3 capacity — 8

If the explicit capacities are insufficient to hold all athletes, Torunit should create another inherited-capacity heat rather than silently exceeding a Meet Director's stated limit.

== Heat duration ==

Controls the expected competition duration of the applicable heat.

The value is entered in minutes and may use quarter-minute increments.

Example:

<code>1.25</code>

represents 1 minute 15 seconds.

A blank value inherits the duration from the parent level.

== Gap after ==

Controls additional time following the heat before the next dependent heat begins.

This can represent the normal operating interval between heats.

A blank value inherits the parent gap.

== Transition before ==

Adds explicit operational time before the applicable heat.

Possible uses include:

* Hurdle adjustment
* Equipment setup
* Start-line change
* Crew movement
* Other required preparation

Transition time becomes part of the real schedule sequence rather than merely an informational note.

== Transition after ==

Adds explicit operational time after the heat.

Possible uses include:

* Equipment clearing
* Hurdle reset
* Moving starting equipment
* Facility conversion
* Other required work

== Division-level settings ==

Each division represented in the block may have its own settings.

A division-level setting overrides the corresponding block-level value only for that division.

Other divisions continue to inherit the block value.

== Heat-level settings ==

Each individual heat may have its own settings.

Heat settings are the most specific level.

An explicit heat value overrides both:

* Block setting
* Division setting

for that heat only.

== Understanding inherited values ==

Each field in the settings dialog displays its inherited value.

For example:

'''Capacity'''

<code>Inherited: 9 athletes per heat</code>

'''Heat duration'''

<code>Inherited: 1.25 minutes</code>

'''Gap after'''

<code>Inherited: 4 minutes</code>

If the Meet Director is satisfied with that value, leave the override blank.

Enter a value only when the selected block, division, or heat should behave differently.

== Saving Block Settings ==

Select:

'''Save settings'''

to save the current Block, Division, and Heat preferences.

The settings are associated with the block's permanent Block UID rather than its temporary position in the schedule.

This means moving the block should not create a new block or lose its detailed settings.

After saving, the current implementation reloads the page so the detailed schedule can be recalculated from the new values.

== Cancel ==

Select:

'''Cancel'''

to close the Block Settings dialog without saving the current edits.

== Heat distribution ==

When heat capacities are known, Torunit distributes the division's athletes across the required heats.

The current detailed heat system attempts to balance athletes among the heats without exceeding each heat's effective capacity.

An explicit capacity should therefore be treated as a limit, not merely a suggestion.

== Detailed timing calculation ==

The detailed heat timeline incorporates:

* Transition before
* Competition duration
* Gap after
* Transition after

These pieces are inserted into the timeline in sequence.

For example:

<code>
Transition before
Heat
Gap after
Transition after
Next heat
</code>

Changing one element affects the start of the dependent elements that follow.

== Hurdle events ==

Hurdle events may require substantially more internal scheduling detail than ordinary flat races.

Different divisions may require different:

* Race distances
* Hurdle heights
* Hurdle spacing
* Number of hurdles
* Setup configuration

Micro/Daily displays the resolved configurations represented within the block.

== Hurdle configuration groups ==

Where different participating divisions require different hurdle formats, the block may show each applicable configuration.

The information may include:

* Distance
* Hurdle specification
* Divisions
* Number of athletes

== Hurdle resets ==

If the block contains more than one hurdle configuration, Torunit may insert hurdle reset time between the affected groups.

These transitions are operational time.

They must affect the schedule that follows rather than being displayed merely as a warning.

== Unresolved hurdle formats ==

If Torunit cannot match an athlete group to a known hurdle format, the block may display a warning.

Examples include:

'''⚠ distance TBD'''

or an unmapped-format warning.

An unresolved hurdle format should be corrected before the schedule is treated as operationally complete.

== Human hurdle order ==

When no human division order has been entered, Torunit may use the operational order provided by the hurdle/barrier data.

Once the Meet Director explicitly changes the division order, that saved order becomes authoritative.

The hurdle transitions must then be recalculated around the human-selected order.

== Throwing implements ==

Throwing-event blocks may display the implement specifications required by the divisions in that block.

This may include events such as:

* Shot Put
* Discus
* Hammer
* Weight Throw
* Super Weight
* Javelin

Different divisions may require different implement weights.

Displaying those requirements in the operating schedule helps officials prepare the next competition correctly.

== Javelin implements ==

Javelin blocks may display the applicable implement weight and the divisions using it.

This information is derived from the meet's actual division/event requirements rather than being merely a generic event label.

== Field events and flights ==

Field-event blocks may contain one or more flights.

A flight is an operational subdivision of the field competition.

The detailed schedule may include:

* Flight number
* Number of athletes
* Check-in
* Warm-up
* Competition start
* Competition duration
* Seed range

== Authoritative field-flight plan ==

The field-flight plan is generated by the server.

Micro/Daily should display that plan rather than independently inventing a different flight structure in the browser.

This prevents the Overview and Facilities views from disagreeing about when a flight actually competes.

== Final-attempt cut ==

Where the field-event format includes a cut to additional attempts, the flight plan may also include the timing of that cut.

The number of athletes receiving additional attempts is determined by the meet's competition format.

== Recall from an earlier flight ==

If finalists come from an earlier flight, the schedule may include recall warm-up time before those athletes resume competition.

The Recall warm-up meet setting controls that allowance.

== Facilities view ==

Facilities view shows each physical field facility as its own operating timeline.

Each facility may display:

* Its scheduled events
* Event start times
* Duration
* Flights
* Collision status

== clear ==

A facility marked:

'''clear'''

does not currently contain a detected time collision.

== empty ==

A facility marked:

'''empty'''

has no competition assigned in the current view.

== Collision warning ==

A red collision warning means two events overlap on the same physical facility.

That conflict must be resolved before both events can operate as scheduled.

== Moving an event between facilities ==

A field-event row may be dragged from one compatible facility to another.

The change updates the block's facility assignment.

The corresponding Overview block should remain synchronized with the same operational block.

== Editing a facility start ==

The start time shown beside a facility event may be edited directly.

That block becomes the anchor for the facility sequence.

Dependent later blocks can then ripple from it.

== Facility ripple ==

Facility ripple reflects the way a real field venue operates.

If a competition ends late:

* Later events move later.

If the facility becomes available early:

* Later events may move earlier.

The Meet Director's edited event remains the anchor.

The dependent schedule follows it.

== Five-minute operating boundary ==

Facility ripple currently places dependent blocks on the next available five-minute boundary.

This provides practical operating times while still allowing significantly finer control than the coarse Macro layout.

== Warm-up protection ==

Torunit checks whether a field event has enough preparation and warm-up time after the preceding event using the same facility.

A warning may appear if the next competition starts too early.

Combined-event components may require additional handling time.

== Focus on group ==

For linked sequences, particularly combined events, Facilities view may provide:

'''Focus on group'''

Select a group to show the facilities relevant to that chain.

This can make it easier to follow one traveling group through a complicated multi-facility day.

== Combined-event chains ==

Combined-event athletes move through a sequence of component events.

The Micro/Daily Scheduler preserves that chain identity.

A combined-event component is displayed at the real facility where it occurs while remaining connected to its parent combined event and traveling group.

== Chain navigation ==

Linked stages may contain controls allowing the Meet Director to jump directly to another component of the same sequence.

This is useful when the stages of a chain are separated by time, facility, or day.

== Holding ==

Blocks that do not yet have a valid place in the operational schedule remain visible in '''Holding'''.

Holding is not deletion.

It means:

'''This block still needs a path into the schedule.'''

Nothing should silently disappear because it has not yet been placed.

== Every GDE needs a path ==

The Holding section follows an important rule:

'''Every Gender/Division/Event combination must have an operational path.'''

If Torunit cannot place one, the block should remain visible for the Meet Director to resolve.

== First legs ==

Combined-event and linked-event chains identify the first actionable leg separately.

The Holding area presents:

'''▶ Place these first'''

These are the entry points from which the dependent sequence can be established.

== Later train legs ==

Dependent later legs are grouped separately.

Because they normally follow from the first leg, they are collapsed by default to reduce clutter.

Select:

'''Show later train legs'''

to inspect them.

== Standalone blocks ==

An ordinary unlinked event may also appear in Holding.

It remains visible as a standalone block until it receives a valid schedule placement.

== Schedule items ==

The Meet Director may insert non-competition items into the Track or Field sequence.

Examples:

* Opening Ceremony
* Awards
* Lunch
* Officials Break
* Track Maintenance
* Presentation
* National Anthem

A schedule item has:

* Name
* Duration
* Optional fixed start

== Fixed custom item ==

If a custom schedule item is given a specific start time, it becomes a fixed schedule anchor.

If the fixed time is cleared, the item may once again flow with the dependent schedule.

== Saving ==

Micro/Daily saves detailed edits to the operational schedule.

Different types of edits may save immediately or cause the page to regenerate.

Changes that affect derived heat or flight structure may cause a page reload.

== Permanent block identity ==

Detailed preferences are stored against the permanent Block UID.

They are not supposed to depend on the block's current position.

This is important because:

* A block can move.
* Its time can change.
* Its facility can change.
* Earlier blocks can ripple it.

None of those actions should turn it into a different competition block.

== Inheritance and NULL values ==

An unset preference is intentionally stored as no override.

This allows Torunit to distinguish:

'''Use the inherited value'''

from:

'''The Meet Director explicitly entered a value.'''

That distinction is essential to the Block → Division → Heat model.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* Verify that every Block, Division, and Heat setting displays the actual value that the calculation engine will use, not merely a display approximation.
* Verify that block capacity is applied separately to each division before the heat totals are added together.
* Verify division-level capacity overrides only the selected division.
* Verify individual heat capacities remain hard limits and that overflow creates another heat rather than exceeding the override.
* Verify all Block, Division, and Heat settings survive save, reload, Macro movement, and schedule regeneration.
* Verify manual division ordering always remains authoritative.
* Verify hurdle setup and transition calculations are recalculated from the real human-selected division order.
* Verify hurdle transitions continue to use actual hurdle-format data.
* Verify individual heat-time edits ripple only the dependent rows that follow.
* Verify ANTICIPATED → REAL switching changes derived heat math without destroying explicit human placement, order, capacity, or timing decisions.
* Verify Facilities and Overview always show the same operational start and facility after an edit.
* Verify facility ripple never moves the Meet Director's explicit anchor.
* Verify field flights always use the server-authored flight plan.
* Verify field-flight recall and final-attempt timing remain correct after flight changes.
* Verify Holding continues to expose every unplaced GDE and no regeneration path silently discards one.
* Verify combined-event first-leg and later-leg classification remains correct when a component is moved back to Holding.
* Verify the LIVE / LOCKED state has a clear normal-user workflow if locking is intended to be exposed to Meet Directors.
* The detailed settings code contains fallback race-duration estimates based mainly on event distance when no stored duration is available. Confirm that these fallback estimates can never override better authoritative event or Meet Director data.
* Continue treating <code>schedule_blocks</code> and permanent Block UID as the authoritative operational identity rather than introducing another parallel schedule representation.

== See also ==

* [[Macro Scheduler]]
* [[Rounds]]
* [[Venue]]
* [[Combined Events]]
* [[Schedule]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Schedule]]
[[Category:Multi-day meet]]
[[Category:Meet operations]]

Micro/Daily Scheduler

2026-10-09T21:03:46Z

Trackinfo:

{{DISPLAYTITLE:Micro/Daily Scheduler}}

The '''Micro/Daily Scheduler''' is the detailed operational scheduling page for a multi-day meet. The naming has taken on both names because it works hand in hand with the [[Macro|Macro Scheduler]] page where schedule blocks are coarsely moved for multiple day meets, but this is essentially a daily full schedule broken down into each little element.

The [[Macro Scheduler]] establishes the large-scale structure of the meet:

* Which day an event occurs
* Which facility it uses
* Its general order
* Its scheduled starting position

The Micro/Daily Scheduler takes those scheduled blocks and exposes the detailed operation inside them.

It is where the Meet Director can examine and refine:

* Divisions within a block
* Individual heats
* Heat capacity
* Heat duration
* Time between heats
* Transitions
* Hurdle changes
* Field flights
* Facility assignments
* Combined-event sequences
* Detailed start times

== Who should use this page? ==

Use the Micro/Daily Scheduler for a multi-day meet after the major schedule structure has been established on the [[Macro Scheduler]].

A normal one-day meet should generally use [[Schedule]] instead.

Micro/Daily is particularly useful for meets where the Meet Director needs detailed control over the way each competition block actually operates.

== Macro and Micro are one schedule ==

Macro and Micro are not separate schedules.

Both are views of the same operational schedule.

A block moved or edited in Micro remains the same competition block that appears on Macro.

Likewise, a block placed on Macro becomes available for detailed operation in Micro.

The purpose of the two pages is different:

'''Macro Scheduler'''
: Places the large pieces.

'''Micro/Daily Scheduler'''
: Controls the detail inside those pieces.

A human decision made on either page should remain authoritative.

Automation may recalculate dependent information, but it should not silently replace a Meet Director's deliberate order, placement, capacity, or timing decision.

== Day navigation ==

Each competition day has its own tab.

Examples:

* Day 1 · Fri Jun 12
* Day 2 · Sat Jun 13
* Day 3 · Sun Jun 14

Select a day to display its detailed schedule.

Only one day's Micro schedule is displayed at a time.

== Overview ==

The '''Overview''' view divides the day's schedule into:

* Track
* Field

This is the easiest way to see the day's overall operating sequence.

Each event appears as a schedule block containing its important competition information.

== Facilities ==

Select:

'''⊞ Facilities'''

to view field events according to the individual physical facilities where they are conducted.

Instead of one general Field column, this view may show facilities such as:

* Long Jump North
* Long Jump South
* High Jump
* Pole Vault
* Shot Put North
* Shot Put South
* Cage
* Javelin

The available facilities originate from [[Venue]].

This view is useful for determining whether each pit, ring, runway, or cage has a physically workable schedule.

== Return to Macro ==

Select:

'''Macro →'''

to return to the [[Macro Scheduler]].

Use Macro when the problem concerns:

* Day
* Broad event order
* Major placement
* Facility
* Large schedule structure

Use Micro/Daily when the problem concerns:

* Heat detail
* Division detail
* Exact timing
* Internal transitions
* Facility operation

== LIVE and LOCKED ==

A day may display one of two states:

* '''● LIVE'''
* '''● LOCKED'''

A LIVE day remains part of the active derived schedule.

A LOCKED day is intended to preserve detailed authored information rather than freely rebuilding that day's schedule from upstream changes.

The locking feature should be used when a day's detailed schedule has reached a point where the Meet Director does not want routine regeneration to replace those decisions.

'''Current implementation note:''' The exact normal-user lock/unlock workflow should be verified before this section is treated as final.

== Meet-level settings ==

Several controls near the top of Micro/Daily apply to the meet rather than only to the currently displayed day.

These settings are shared with other scheduling pages rather than being separate Micro copies.

== Heat gap ==

Sets the standard time between track heats.

The Heat gap is the same underlying value used on [[Rounds]].

Changing it on either page changes the same meet setting.

The value may use quarter-minute increments.

Examples:

* <code>4</code> = 4 minutes
* <code>1.5</code> = 1 minute 30 seconds
* <code>0.75</code> = 45 seconds
* <code>0.25</code> = 15 seconds

A change to Heat gap may require Torunit to regenerate calculated schedule information.

== Hurdle transition ==

Sets the normal amount of time allocated for changing a hurdle configuration.

A hurdle transition may involve:

* Changing hurdle height
* Moving hurdles
* Changing spacing
* Changing the race configuration
* Preparing the next hurdle group

Torunit may use actual hurdle-format information in addition to this meet-level setting.

== Recall warm-up ==

Sets the warm-up period given to field-event competitors who must be recalled from an earlier flight for additional attempts.

For example, if the athletes advancing to the final three attempts come from more than one flight, athletes from an earlier flight may need time to warm up again.

If the final competitors all come from the final flight, no recall may be required.

== Field flights ==

Controls the general field-event seeding policy.

Current choices are:

* '''Balanced'''
* '''Stacked'''

=== Balanced ===

Strong marks are distributed through the available flights.

This provides a more even distribution of competitive ability.

=== Stacked ===

Stronger marks are concentrated toward the final flight.

This can be useful where the Meet Director wants the strongest athletes competing late and wants the final-attempt cut to emerge primarily from the final flight.

== Auto-ripple ==

Controls whether later dependent schedule items automatically move after an earlier change.

When Auto-ripple is on:

* A delay can move later events later.
* Gaining time can allow later events to move earlier.
* An explicit anchor remains fixed.
* Dependent events are recalculated from that anchor.

Ripple should follow human decisions rather than replace them.

== Heat sizing ==

The Heat sizing control selects which participant counts are used to determine heat structure.

Current choices are:

* '''ANTICIPATED'''
* '''REAL'''

=== ANTICIPATED ===

Uses the planning figures entered before registration is complete.

This allows the schedule to remain stable while registrations are still arriving.

=== REAL ===

Uses actual registered participant counts.

Switch to REAL when registration is complete enough that the Meet Director wants the operating schedule based on the athletes who are actually entered.

Actual counts may still be displayed while ANTICIPATED remains the sizing authority.

== Per-day timing settings ==

Each day also has settings that apply specifically to that day's operation.

These include:

* First track event
* First field event
* Fixed
* First call
* Check-in
* Warmup

== First track event ==

Displays the currently scheduled first Track competition of the day.

This is derived from the operational schedule.

== First field event ==

Displays the currently scheduled first Field competition of the day.

== Fixed ==

Indicates that the day's detailed timing contains explicit time anchors that should be preserved.

A fixed time represents a Meet Director decision.

If earlier activity makes that time impossible, Torunit should identify the conflict rather than silently changing the fixed time.

== First call ==

Sets how many minutes before competition the first call should occur.

Example:

<code>30</code>

means the first call occurs 30 minutes before the applicable competition time.

== Check-in ==

Sets the normal advance time associated with athlete check-in.

The exact check-in sequence may vary according to the event and Clerk of Course operation.

== Warmup ==

Sets the normal field-event warm-up allowance for the day.

This affects the amount of operating room required between field competitions using the same facility.

== Understanding a schedule block ==

Each competition appears as a schedule block.

A block represents an operational portion of the schedule rather than merely the name of an event.

A block may contain:

* Event
* Round
* Gender
* Division
* Athlete count
* Heat or flight count
* Start time
* Duration
* Facility
* Combined-event relationship
* Hurdle requirements
* Implement information
* Internal heat timing
* Warnings
* Detailed settings

== Event name ==

The event name is the primary heading of the block.

Internal Torunit event-family codes are converted to their public event names for display.

== Round ==

Where applicable, the competition round is included with the event name.

Examples:

* 100 Prelims
* 200 Semifinals
* 800 Final

Round identity matters because different rounds may have different:

* Participant counts
* Lane capacities
* Advancement structures
* Scheduling requirements

== Combined-event parent ==

A combined-event component may identify its parent combined event.

Examples:

* DEC · 100
* HEP · HJ
* PENT · SP

The component is still scheduled on its actual physical facility.

For example:

* A Decathlon Shot Put component uses a Shot Put ring.
* A Heptathlon High Jump component uses a High Jump facility.
* A Decathlon 100 uses the Track.

See [[Combined Events]].

== Facility ==

The block may display the physical facility where it is assigned.

Facility assignment should correspond to the facilities established on [[Venue]].

== START HERE ==

A linked sequence may identify the first operational stage with:

'''▶ START HERE'''

This helps identify the entry point into a chain of dependent events.

== Division and gender composition ==

A block may contain several Gender/Division groups.

Examples:

* G 9–10
* B 9–10
* G 11–12
* B 11–12

For each group, Micro may show:

* Anticipated athletes
* Real athletes
* Number of heats
* Effective capacity

These values explain how Torunit arrived at the block's heat structure.

== Anticipated versus real counts ==

Where both values are available, the block may show the planned and actual entry counts together.

This allows the Meet Director to see whether reality is significantly different from the schedule assumption.

A large difference may justify changing Heat sizing from ANTICIPATED to REAL.

== Combining divisions ==

Where permitted, two or more divisions may be combined operationally into the same race.

Combining divisions does not necessarily combine their:

* Results
* Scoring
* Records
* Qualification status

It means they compete together operationally.

The Meet Director's explicit decision to combine divisions should remain authoritative.

== Unganging divisions ==

A previously combined race may be separated back into its individual divisions.

Changing the combination may alter:

* Heat count
* Athlete distribution
* Block duration
* Later schedule times

Dependent calculations should be rebuilt while preserving unrelated human decisions.

== Borderline heat decisions ==

Torunit may identify a division whose athlete count lies just beyond the normal preferred heat size.

The Meet Director may be offered a choice such as:

* '''Combine into one'''
* '''Split into two'''

This is intentionally a human decision rather than an arbitrary automatic choice.

Once made, the choice should remain stored until the Meet Director changes it.

== Heat breakdown ==

A schedule block can be expanded to show its detailed internal sequence.

Track blocks may display individual heats.

The detailed rows may include:

* Heat number
* Gender/division
* Athlete count
* Start time
* Estimated duration
* Setup or transition rows

This detailed sequence is the Micro portion of the schedule.

== Editing a heat time ==

Individual heat start times may be edited.

An edited heat time is an explicit Meet Director decision.

Later dependent heats should ripple from the change.

The system should not silently restore the previous automatically generated time.

== Block Settings ==

Select the '''⚙''' in the event block header to open:

'''Block settings'''

The Block Settings dialog allows detailed schedule preferences to be established at three levels:

* Block
* Division
* Heat

This provides progressively more specific control without requiring every value to be manually entered for every heat.

== The inheritance system ==

Micro/Daily uses inheritance.

A more specific setting inherits from its parent unless the Meet Director provides an explicit override.

The hierarchy is:

'''Calculated or meet default → Block → Division → Heat'''

For example:

* Meet heat gap = 4 minutes
* Block gap = blank → inherits 4 minutes
* Division gap = 5 minutes → that division uses 5
* Heat 3 gap = 7 minutes → Heat 3 uses 7

Blank does not mean zero.

Blank means:

'''Use the inherited value.'''

The settings dialog displays the inherited value so the Meet Director can see what will actually be used.

== Block-level settings ==

Block-level settings apply to every appropriate division and heat in the block unless overridden at a lower level.

Available block preferences currently include:

* Division order
* Capacity
* Heat duration
* Gap after
* Transition before
* Transition after

== Division order ==

Controls the order in which the divisions inside the block compete.

A Meet Director may deliberately move divisions into the desired operating order.

The saved human order overrides the automatic order.

Divisions that are newly added or not explicitly listed should remain present rather than being discarded.

They follow the explicitly ordered divisions until the Meet Director places them.

== Reordering divisions ==

The Block Settings dialog allows the division order to be changed.

The current interface supports:

* Moving a division earlier
* Moving a division later
* Dragging divisions
* Reversing the order

After saving, the block should use that order when constructing its detailed heat sequence.

== Capacity ==

Capacity determines the maximum number of athletes assigned to a heat for the applicable scope.

A block-level capacity applies to each division unless that division has its own capacity override.

The number of heats is then calculated separately for each division.

Example:

Suppose a block contains:

* Girls 11–12 — 41 athletes
* Boys 11–12 — 55 athletes

with an effective capacity of 9.

Torunit should calculate each division independently:

* Girls: <code>ceil(41 / 9)</code>
* Boys: <code>ceil(55 / 9)</code>

and then combine the resulting heat counts into the block.

The athlete totals should not be combined first and divided afterward.

== Division-level capacity ==

A division may have its own capacity.

Example:

Block capacity:

<code>9</code>

Girls 11–12 capacity:

<code>8</code>

Boys 11–12 capacity:

blank

The Girls division uses 8.

The Boys division inherits 9.

== Heat-level capacity ==

An individual heat may also have its own capacity.

This allows unusual operational circumstances to be represented without changing every heat in the division.

For example:

* Heat 1 capacity — 9
* Heat 2 capacity — 9
* Heat 3 capacity — 8

If the explicit capacities are insufficient to hold all athletes, Torunit should create another inherited-capacity heat rather than silently exceeding a Meet Director's stated limit.

== Heat duration ==

Controls the expected competition duration of the applicable heat.

The value is entered in minutes and may use quarter-minute increments.

Example:

<code>1.25</code>

represents 1 minute 15 seconds.

A blank value inherits the duration from the parent level.

== Gap after ==

Controls additional time following the heat before the next dependent heat begins.

This can represent the normal operating interval between heats.

A blank value inherits the parent gap.

== Transition before ==

Adds explicit operational time before the applicable heat.

Possible uses include:

* Hurdle adjustment
* Equipment setup
* Start-line change
* Crew movement
* Other required preparation

Transition time becomes part of the real schedule sequence rather than merely an informational note.

== Transition after ==

Adds explicit operational time after the heat.

Possible uses include:

* Equipment clearing
* Hurdle reset
* Moving starting equipment
* Facility conversion
* Other required work

== Division-level settings ==

Each division represented in the block may have its own settings.

A division-level setting overrides the corresponding block-level value only for that division.

Other divisions continue to inherit the block value.

== Heat-level settings ==

Each individual heat may have its own settings.

Heat settings are the most specific level.

An explicit heat value overrides both:

* Block setting
* Division setting

for that heat only.

== Understanding inherited values ==

Each field in the settings dialog displays its inherited value.

For example:

'''Capacity'''

<code>Inherited: 9 athletes per heat</code>

'''Heat duration'''

<code>Inherited: 1.25 minutes</code>

'''Gap after'''

<code>Inherited: 4 minutes</code>

If the Meet Director is satisfied with that value, leave the override blank.

Enter a value only when the selected block, division, or heat should behave differently.

== Saving Block Settings ==

Select:

'''Save settings'''

to save the current Block, Division, and Heat preferences.

The settings are associated with the block's permanent Block UID rather than its temporary position in the schedule.

This means moving the block should not create a new block or lose its detailed settings.

After saving, the current implementation reloads the page so the detailed schedule can be recalculated from the new values.

== Cancel ==

Select:

'''Cancel'''

to close the Block Settings dialog without saving the current edits.

== Heat distribution ==

When heat capacities are known, Torunit distributes the division's athletes across the required heats.

The current detailed heat system attempts to balance athletes among the heats without exceeding each heat's effective capacity.

An explicit capacity should therefore be treated as a limit, not merely a suggestion.

== Detailed timing calculation ==

The detailed heat timeline incorporates:

* Transition before
* Competition duration
* Gap after
* Transition after

These pieces are inserted into the timeline in sequence.

For example:

<code>
Transition before
Heat
Gap after
Transition after
Next heat
</code>

Changing one element affects the start of the dependent elements that follow.

== Hurdle events ==

Hurdle events may require substantially more internal scheduling detail than ordinary flat races.

Different divisions may require different:

* Race distances
* Hurdle heights
* Hurdle spacing
* Number of hurdles
* Setup configuration

Micro/Daily displays the resolved configurations represented within the block.

== Hurdle configuration groups ==

Where different participating divisions require different hurdle formats, the block may show each applicable configuration.

The information may include:

* Distance
* Hurdle specification
* Divisions
* Number of athletes

== Hurdle resets ==

If the block contains more than one hurdle configuration, Torunit may insert hurdle reset time between the affected groups.

These transitions are operational time.

They must affect the schedule that follows rather than being displayed merely as a warning.

== Unresolved hurdle formats ==

If Torunit cannot match an athlete group to a known hurdle format, the block may display a warning.

Examples include:

'''⚠ distance TBD'''

or an unmapped-format warning.

An unresolved hurdle format should be corrected before the schedule is treated as operationally complete.

== Human hurdle order ==

When no human division order has been entered, Torunit may use the operational order provided by the hurdle/barrier data.

Once the Meet Director explicitly changes the division order, that saved order becomes authoritative.

The hurdle transitions must then be recalculated around the human-selected order.

== Throwing implements ==

Throwing-event blocks may display the implement specifications required by the divisions in that block.

This may include events such as:

* Shot Put
* Discus
* Hammer
* Weight Throw
* Super Weight
* Javelin

Different divisions may require different implement weights.

Displaying those requirements in the operating schedule helps officials prepare the next competition correctly.

== Javelin implements ==

Javelin blocks may display the applicable implement weight and the divisions using it.

This information is derived from the meet's actual division/event requirements rather than being merely a generic event label.

== Field events and flights ==

Field-event blocks may contain one or more flights.

A flight is an operational subdivision of the field competition.

The detailed schedule may include:

* Flight number
* Number of athletes
* Check-in
* Warm-up
* Competition start
* Competition duration
* Seed range

== Authoritative field-flight plan ==

The field-flight plan is generated by the server.

Micro/Daily should display that plan rather than independently inventing a different flight structure in the browser.

This prevents the Overview and Facilities views from disagreeing about when a flight actually competes.

== Final-attempt cut ==

Where the field-event format includes a cut to additional attempts, the flight plan may also include the timing of that cut.

The number of athletes receiving additional attempts is determined by the meet's competition format.

== Recall from an earlier flight ==

If finalists come from an earlier flight, the schedule may include recall warm-up time before those athletes resume competition.

The Recall warm-up meet setting controls that allowance.

== Facilities view ==

Facilities view shows each physical field facility as its own operating timeline.

Each facility may display:

* Its scheduled events
* Event start times
* Duration
* Flights
* Collision status

== clear ==

A facility marked:

'''clear'''

does not currently contain a detected time collision.

== empty ==

A facility marked:

'''empty'''

has no competition assigned in the current view.

== Collision warning ==

A red collision warning means two events overlap on the same physical facility.

That conflict must be resolved before both events can operate as scheduled.

== Moving an event between facilities ==

A field-event row may be dragged from one compatible facility to another.

The change updates the block's facility assignment.

The corresponding Overview block should remain synchronized with the same operational block.

== Editing a facility start ==

The start time shown beside a facility event may be edited directly.

That block becomes the anchor for the facility sequence.

Dependent later blocks can then ripple from it.

== Facility ripple ==

Facility ripple reflects the way a real field venue operates.

If a competition ends late:

* Later events move later.

If the facility becomes available early:

* Later events may move earlier.

The Meet Director's edited event remains the anchor.

The dependent schedule follows it.

== Five-minute operating boundary ==

Facility ripple currently places dependent blocks on the next available five-minute boundary.

This provides practical operating times while still allowing significantly finer control than the coarse Macro layout.

== Warm-up protection ==

Torunit checks whether a field event has enough preparation and warm-up time after the preceding event using the same facility.

A warning may appear if the next competition starts too early.

Combined-event components may require additional handling time.

== Focus on group ==

For linked sequences, particularly combined events, Facilities view may provide:

'''Focus on group'''

Select a group to show the facilities relevant to that chain.

This can make it easier to follow one traveling group through a complicated multi-facility day.

== Combined-event chains ==

Combined-event athletes move through a sequence of component events.

The Micro/Daily Scheduler preserves that chain identity.

A combined-event component is displayed at the real facility where it occurs while remaining connected to its parent combined event and traveling group.

== Chain navigation ==

Linked stages may contain controls allowing the Meet Director to jump directly to another component of the same sequence.

This is useful when the stages of a chain are separated by time, facility, or day.

== Holding ==

Blocks that do not yet have a valid place in the operational schedule remain visible in '''Holding'''.

Holding is not deletion.

It means:

'''This block still needs a path into the schedule.'''

Nothing should silently disappear because it has not yet been placed.

== Every GDE needs a path ==

The Holding section follows an important rule:

'''Every Gender/Division/Event combination must have an operational path.'''

If Torunit cannot place one, the block should remain visible for the Meet Director to resolve.

== First legs ==

Combined-event and linked-event chains identify the first actionable leg separately.

The Holding area presents:

'''▶ Place these first'''

These are the entry points from which the dependent sequence can be established.

== Later train legs ==

Dependent later legs are grouped separately.

Because they normally follow from the first leg, they are collapsed by default to reduce clutter.

Select:

'''Show later train legs'''

to inspect them.

== Standalone blocks ==

An ordinary unlinked event may also appear in Holding.

It remains visible as a standalone block until it receives a valid schedule placement.

== Schedule items ==

The Meet Director may insert non-competition items into the Track or Field sequence.

Examples:

* Opening Ceremony
* Awards
* Lunch
* Officials Break
* Track Maintenance
* Presentation
* National Anthem

A schedule item has:

* Name
* Duration
* Optional fixed start

== Fixed custom item ==

If a custom schedule item is given a specific start time, it becomes a fixed schedule anchor.

If the fixed time is cleared, the item may once again flow with the dependent schedule.

== Saving ==

Micro/Daily saves detailed edits to the operational schedule.

Different types of edits may save immediately or cause the page to regenerate.

Changes that affect derived heat or flight structure may cause a page reload.

== Permanent block identity ==

Detailed preferences are stored against the permanent Block UID.

They are not supposed to depend on the block's current position.

This is important because:

* A block can move.
* Its time can change.
* Its facility can change.
* Earlier blocks can ripple it.

None of those actions should turn it into a different competition block.

== Inheritance and NULL values ==

An unset preference is intentionally stored as no override.

This allows Torunit to distinguish:

'''Use the inherited value'''

from:

'''The Meet Director explicitly entered a value.'''

That distinction is essential to the Block → Division → Heat model.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* Verify that every Block, Division, and Heat setting displays the actual value that the calculation engine will use, not merely a display approximation.
* Verify that block capacity is applied separately to each division before the heat totals are added together.
* Verify division-level capacity overrides only the selected division.
* Verify individual heat capacities remain hard limits and that overflow creates another heat rather than exceeding the override.
* Verify all Block, Division, and Heat settings survive save, reload, Macro movement, and schedule regeneration.
* Verify manual division ordering always remains authoritative.
* Verify hurdle setup and transition calculations are recalculated from the real human-selected division order.
* Verify hurdle transitions continue to use actual hurdle-format data.
* Verify individual heat-time edits ripple only the dependent rows that follow.
* Verify ANTICIPATED → REAL switching changes derived heat math without destroying explicit human placement, order, capacity, or timing decisions.
* Verify Facilities and Overview always show the same operational start and facility after an edit.
* Verify facility ripple never moves the Meet Director's explicit anchor.
* Verify field flights always use the server-authored flight plan.
* Verify field-flight recall and final-attempt timing remain correct after flight changes.
* Verify Holding continues to expose every unplaced GDE and no regeneration path silently discards one.
* Verify combined-event first-leg and later-leg classification remains correct when a component is moved back to Holding.
* Verify the LIVE / LOCKED state has a clear normal-user workflow if locking is intended to be exposed to Meet Directors.
* The detailed settings code contains fallback race-duration estimates based mainly on event distance when no stored duration is available. Confirm that these fallback estimates can never override better authoritative event or Meet Director data.
* Continue treating <code>schedule_blocks</code> and permanent Block UID as the authoritative operational identity rather than introducing another parallel schedule representation.

== See also ==

* [[Macro Scheduler]]
* [[Rounds]]
* [[Venue]]
* [[Combined Events]]
* [[Schedule]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Schedule]]
[[Category:Multi-day meet]]
[[Category:Meet operations]]

Participants

2026-10-09T20:51:23Z

Trackinfo: /* See also */

{{DISPLAYTITLE:Participants}}

The '''Participants''' page records the number of athletes the Meet Director expects to enter each '''GDE''' gender, division, and event 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. On meet day, your '''COC''' Clerk of the Course will deal with actual heats based on the athletes who actually check in.

== Who should use this page? ==

The Participants page is primarily intended for one-day meet scheduling with no rounds, your most common meet format.

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.

You will also use this page to set your size limits.

== 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:

<code>2 = prelim + final</code>

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:

<code>2 Q</code>

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:

<code>8</code>

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.
* <code>participants.blade.php</code> contains its own inlined event-block renderer while <code>participants/_event-block.blade.php</code> 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.

== See also ==

* [[Create-Meet]]
* [[Venue]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]

[[Category:Meet Director]]
[[Category:Schedule]]
[[Category:Meet planning]]

Create-Meet

2026-10-08T20:59:35Z

Trackinfo: /* Hide from Public View */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Qual Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction. If you want to limit entry to members of a certain organization, that will be selectable on the Financial page under entry requirements, and this will duplicate that action rather than making you work for it. Rather than being an enforced limitation, the text you write in the box will be a warning the entrants will see before entering.

There is a component where you can make entry subject to your approval. Such requests will be sent to your contact email.

==== Approval ====

By checking this box under the Meet Format will route all entries back to the Meet Director (or you can designate someone else to handle this). You will need to approve each entry, or team entries in bulk before the entry is finalized.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed. This is loosely enforced, that we are expecting some derivative of what you write within the name of the team entering. So the team might have a formal name, you might have just entered the team or school name or even abbreviation, the system will be looking for some component of what you have written.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Hide from Public View ==

In some meets coaches or athletes might use our entry information to game the system by employing a strategy of avoiding competition or entering a weak event simply because scoring places remain unoccupied. Hiding that information will make it harder to cynically put just "a body" in a poorly attended event just to cross a finish line for points or awards. You can select to hide the specific names of the entrants by checking entries or hide the overall pool with numbers.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Create-Meet

2026-10-08T20:49:58Z

Trackinfo: /* Seeding */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Qual Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction. If you want to limit entry to members of a certain organization, that will be selectable on the Financial page under entry requirements, and this will duplicate that action rather than making you work for it. Rather than being an enforced limitation, the text you write in the box will be a warning the entrants will see before entering.

There is a component where you can make entry subject to your approval. Such requests will be sent to your contact email.

==== Approval ====

By checking this box under the Meet Format will route all entries back to the Meet Director (or you can designate someone else to handle this). You will need to approve each entry, or team entries in bulk before the entry is finalized.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed. This is loosely enforced, that we are expecting some derivative of what you write within the name of the team entering. So the team might have a formal name, you might have just entered the team or school name or even abbreviation, the system will be looking for some component of what you have written.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Hide from Public View ==

In some meets coaches or athletes might enter a weak event simply because scoring places remain unoccupied. Some people feel this is gaming the system, cynically putting just "a body" in a poorly attended event just to cross a finish line. Some people want to avoid making the effort when they know they will be defeated by particular athletes. By hiding this information, you prevent them using the attendance information as part of their entry strategy. You can select to hide the specific names of the entrants, entries or overall pool numbers.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Create-Meet

2026-10-08T12:01:41Z

Trackinfo: /* Qual Open */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Qual Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction. If you want to limit entry to members of a certain organization, that will be selectable on the Financial page under entry requirements, and this will duplicate that action rather than making you work for it. Rather than being an enforced limitation, the text you write in the box will be a warning the entrants will see before entering.

There is a component where you can make entry subject to your approval. Such requests will be sent to your contact email.

==== Approval ====

By checking this box under the Meet Format will route all entries back to the Meet Director (or you can designate someone else to handle this). You will need to approve each entry, or team entries in bulk before the entry is finalized.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed. This is loosely enforced, that we are expecting some derivative of what you write within the name of the team entering. So the team might have a formal name, you might have just entered the team or school name or even abbreviation, the system will be looking for some component of what you have written.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Team Entry Board

2026-10-08T11:05:55Z

Trackinfo: /* Team Entry Board */

== Overview ==

The '''Meet Entry Board''' is the Team Leader's workspace for entering athletes into a track and field meet.

It brings the team's athlete roster and the meet's available events together on one page, allowing the Team Leader to organize entries, assign athletes to events, manage relay teams, and review the team's participation.

The board is designed around direct interaction: select athletes, drag them into events, review their assignments, and make corrections without navigating through a series of separate entry forms.

Individual events and relays are managed from the same board, with additional controls for relay team composition and running order.

== 1. The Entry Board ==

The board has two principal working areas:

=== Athlete Roster ===

The roster displays the athletes associated with the Team Leader's team.

Athlete cards can be selected individually or in groups for entry into events.

The roster provides several ways to organize athletes:

* '''By Division:''' Groups athletes by their competition division.
* '''A–Z:''' Lists athletes alphabetically.
* '''By Seed:''' Organizes athletes by their recorded performance marks where applicable.

Each athlete also has an entry tally showing their current participation in the meet.

The tally includes individual events and relay membership, so the Team Leader can see how many events an athlete has entered.

=== Meet Events ===

The event area displays the events offered by the meet, organized into event types and competition divisions.

Each event contains the applicable gender and division groupings, providing a destination for athlete assignments.

The event board supports individual track events, field events, and relay events.

== 2. Selecting Athletes ==

Athletes can be selected from the roster before being assigned to an event.

'''Single selection:''' Click an athlete's card.

'''Multiple selection:''' Hold Command on a Mac, or Ctrl on a Windows computer, while clicking additional athletes.

'''Range selection:''' Use Shift-click to select a continuous group of athletes.

Selected athletes are visually highlighted.

This makes it possible to work with multiple athletes without repeating the same selection process for every entry.

== 3. Entering Athletes in Individual Events ==

To enter an athlete in an individual event:

# Locate the athlete in the roster.
# Locate the desired event and competition division.
# Drag the athlete into the event's entry area.
# Review the athlete's appearance in that event.

Multiple selected athletes can be used where the event's assignment controls support group entry.

The athlete's entry tally reflects their participation.

=== Removing an Individual Entry ===

Each assigned athlete has an '''X''' control beside their name in the event area.

Clicking X removes that athlete from the event.

The entry board updates to reflect the change.

=== Seed Marks ===

Seed marks provide performance information used when organizing entries and preparing competition seeding.

The board includes seed-mark-based sorting where applicable, allowing athletes to be reviewed by performance rather than solely by name or division.

Seed marks should be checked for accuracy before the meet's entry deadline.

== 4. Relay Entries ==

Relays use the same entry board as individual events, but a relay requires a team lineup rather than a collection of independent individual entries.

A relay team includes:

* A team designation, such as Team A.
* The relay event, division, and gender.
* Assigned runners.
* Running-leg positions.
* Alternate athletes, where applicable.

=== Creating a Relay Team ===

Locate the relay event and the appropriate division.

Athletes can be assigned through the board's relay entry workflow. The relay editor provides the detailed controls for organizing the team.

The relay team is displayed in the event area once its members are assigned.

=== Opening the Relay Editor ===

Click the relay event or an assigned athlete's name to open the relay editor.

The editor allows the Team Leader to review and modify the lineup.

=== Assigning Running Legs ===

For a standard four-leg relay, the editor provides four runner positions.

Athletes can be moved between positions to establish the intended running order.

For example:

{| class="wikitable"
|-
! Leg
! Athlete
|-
| 1
| First runner
|-
| 2
| Second runner
|-
| 3
| Third runner
|-
| 4
| Anchor runner
|}

The Team Leader can change the running order as necessary.

=== Alternates ===

The relay editor also provides positions for alternate athletes.

Alternates are associated with the relay team but are distinguished from the runners assigned to the four competition legs.

=== Removing a Relay Athlete ===

There are two ways to remove an athlete from a relay.

'''From the main entry board:''' Click the X beside the athlete's name.

'''From the relay editor:''' Remove the athlete from their assigned position.

Both methods update the relay membership.

Removing one athlete does not automatically remove the other runners or dismantle the relay team. The remaining athletes retain their assigned positions until the Team Leader changes them.

=== Saving Relay Changes ===

Relay membership and running-leg assignments are stored as team information.

Saved assignments remain available when the page is reloaded.

== 5. Division and Available Athletes ==

The relay editor distinguishes between athletes already assigned to the relay and athletes available for assignment.

The '''Available''' area displays eligible athletes who have not already been assigned to the selected relay.

When an athlete is assigned to a relay position, that athlete is removed from Available.

When an athlete is removed from the relay, the athlete returns to Available.

This synchronization prevents the same athlete from being inadvertently assigned twice within the same relay lineup.

The Available list is specific to the selected relay's competition division.

== 6. Entry Tallies ==

Each athlete's roster card includes a tally of their meet participation.

The tally accounts for individual-event entries and relay memberships.

For example, an athlete entered in the 100 meters and assigned to a 4×100 relay has two event participations.

When an entry is added or removed, the tally updates to reflect the athlete's current assignments.

Relay membership is counted from the relay team rather than requiring a separate individual-event entry for each relay runner.

== 7. Sorting and Reviewing Entries ==

The board offers multiple ways to inspect the roster and event assignments.

=== Division View ===

Useful when preparing entries for age-group or divisional competition.

=== Alphabetical View ===

Useful when locating a particular athlete or reviewing a team roster.

=== Seed-Mark View ===

Useful when comparing athlete performances and reviewing likely competition placement.

Before completing meet entries, the Team Leader should review each event to confirm that the correct athletes have been entered.

Relay lineups should receive additional review because both team membership and running order matter.

== 8. Recommended Entry Workflow ==

A practical workflow for preparing a team's meet entries is:

# '''Review the roster.''' Confirm that the athletes expected to compete are present.
# '''Organize by division.''' Work through the competition divisions to reduce assignment errors.
# '''Enter individual events.''' Assign athletes to their selected track and field events.
# '''Review seed marks.''' Check performance information where applicable.
# '''Build relay teams.''' Assign runners and alternates to the appropriate relay divisions.
# '''Set relay running order.''' Open each relay editor and arrange the competition legs.
# '''Review entry tallies.''' Look for athletes with missing or unexpected assignments.
# '''Make corrections.''' Use the X controls or relay editor to remove or rearrange athletes.
# '''Perform a final review.''' Check each event and relay before the entry deadline.

== 9. Important Operating Rules ==

=== Individual Entries and Relay Membership Are Different ===

An individual-event entry represents an athlete competing in a particular event.

A relay entry represents a team, with athletes assigned to specific positions within that team.

The board presents both in a common interface, but relay membership and running order are maintained as team information.

=== Removing a Runner Does Not Remove the Team ===

A relay team can remain in place even when its runner positions are empty.

This allows a Team Leader to rebuild or revise a lineup without creating a new team designation.

=== Running Order Is Explicit ===

A relay runner's position is meaningful.

Moving an athlete between legs changes the lineup; removing an athlete should not automatically shift the remaining runners into different legs.

=== Saved Entries Survive Reloading ===

Entry assignments are intended to be persistent, not temporary arrangements that exist only in the browser.

Reloading the entry board should reproduce the saved individual entries and relay memberships.

== 10. Troubleshooting ==

{| class="wikitable"
|-
! Situation
! What to do
|-
| An athlete is missing from Available
| Check whether the athlete is already assigned to the relay or belongs to a different division.
|-
| A relay athlete is in the wrong leg
| Open the relay editor and rearrange the runners.
|-
| An athlete should not be in an event
| Click the X beside the athlete's name.
|-
| A relay needs another runner
| Open the relay editor and assign an eligible athlete from Available.
|-
| A relay needs an alternate
| Use the alternate positions in the relay editor.
|-
| An entry looks incorrect after editing
| Reload the board and check the saved state. If the discrepancy remains, report it to the meet administrator.
|}

== 11. Summary ==

The Team Leader Meet Entry Board provides a unified workspace for preparing a team's track and field entries.

It combines athlete selection, event assignment, roster sorting, seed-mark review, relay team management, and entry tallies.

The goal is to let Team Leaders prepare and correct meet entries directly, while preserving the distinction between individual participation and the more detailed structure of a relay team.

----

'''Documentation status:''' Initial operating guide based on the current entry-board workflow and relay demonstrations. Entry deadlines, eligibility enforcement, submission confirmation, fee handling, and administrative override procedures should be documented separately after their behavior is verified.

Team Entry Board

2026-10-08T11:05:35Z

Trackinfo: Created page with "= Team Entry Board = == Overview == The '''Meet Entry Board''' is the Team Leader's workspace for entering athletes into a track and field meet. It brings the team's athlete roster and the meet's available events together on one page, allowing the Team Leader to organize entries, assign athletes to events, manage relay teams, and review the team's participation. The board is designed around direct interaction: select athletes, drag them into events, review their assi..."

= Team Entry Board =

== Overview ==

The '''Meet Entry Board''' is the Team Leader's workspace for entering athletes into a track and field meet.

It brings the team's athlete roster and the meet's available events together on one page, allowing the Team Leader to organize entries, assign athletes to events, manage relay teams, and review the team's participation.

The board is designed around direct interaction: select athletes, drag them into events, review their assignments, and make corrections without navigating through a series of separate entry forms.

Individual events and relays are managed from the same board, with additional controls for relay team composition and running order.

== 1. The Entry Board ==

The board has two principal working areas:

=== Athlete Roster ===

The roster displays the athletes associated with the Team Leader's team.

Athlete cards can be selected individually or in groups for entry into events.

The roster provides several ways to organize athletes:

* '''By Division:''' Groups athletes by their competition division.
* '''A–Z:''' Lists athletes alphabetically.
* '''By Seed:''' Organizes athletes by their recorded performance marks where applicable.

Each athlete also has an entry tally showing their current participation in the meet.

The tally includes individual events and relay membership, so the Team Leader can see how many events an athlete has entered.

=== Meet Events ===

The event area displays the events offered by the meet, organized into event types and competition divisions.

Each event contains the applicable gender and division groupings, providing a destination for athlete assignments.

The event board supports individual track events, field events, and relay events.

== 2. Selecting Athletes ==

Athletes can be selected from the roster before being assigned to an event.

'''Single selection:''' Click an athlete's card.

'''Multiple selection:''' Hold Command on a Mac, or Ctrl on a Windows computer, while clicking additional athletes.

'''Range selection:''' Use Shift-click to select a continuous group of athletes.

Selected athletes are visually highlighted.

This makes it possible to work with multiple athletes without repeating the same selection process for every entry.

== 3. Entering Athletes in Individual Events ==

To enter an athlete in an individual event:

# Locate the athlete in the roster.
# Locate the desired event and competition division.
# Drag the athlete into the event's entry area.
# Review the athlete's appearance in that event.

Multiple selected athletes can be used where the event's assignment controls support group entry.

The athlete's entry tally reflects their participation.

=== Removing an Individual Entry ===

Each assigned athlete has an '''X''' control beside their name in the event area.

Clicking X removes that athlete from the event.

The entry board updates to reflect the change.

=== Seed Marks ===

Seed marks provide performance information used when organizing entries and preparing competition seeding.

The board includes seed-mark-based sorting where applicable, allowing athletes to be reviewed by performance rather than solely by name or division.

Seed marks should be checked for accuracy before the meet's entry deadline.

== 4. Relay Entries ==

Relays use the same entry board as individual events, but a relay requires a team lineup rather than a collection of independent individual entries.

A relay team includes:

* A team designation, such as Team A.
* The relay event, division, and gender.
* Assigned runners.
* Running-leg positions.
* Alternate athletes, where applicable.

=== Creating a Relay Team ===

Locate the relay event and the appropriate division.

Athletes can be assigned through the board's relay entry workflow. The relay editor provides the detailed controls for organizing the team.

The relay team is displayed in the event area once its members are assigned.

=== Opening the Relay Editor ===

Click the relay event or an assigned athlete's name to open the relay editor.

The editor allows the Team Leader to review and modify the lineup.

=== Assigning Running Legs ===

For a standard four-leg relay, the editor provides four runner positions.

Athletes can be moved between positions to establish the intended running order.

For example:

{| class="wikitable"
|-
! Leg
! Athlete
|-
| 1
| First runner
|-
| 2
| Second runner
|-
| 3
| Third runner
|-
| 4
| Anchor runner
|}

The Team Leader can change the running order as necessary.

=== Alternates ===

The relay editor also provides positions for alternate athletes.

Alternates are associated with the relay team but are distinguished from the runners assigned to the four competition legs.

=== Removing a Relay Athlete ===

There are two ways to remove an athlete from a relay.

'''From the main entry board:''' Click the X beside the athlete's name.

'''From the relay editor:''' Remove the athlete from their assigned position.

Both methods update the relay membership.

Removing one athlete does not automatically remove the other runners or dismantle the relay team. The remaining athletes retain their assigned positions until the Team Leader changes them.

=== Saving Relay Changes ===

Relay membership and running-leg assignments are stored as team information.

Saved assignments remain available when the page is reloaded.

== 5. Division and Available Athletes ==

The relay editor distinguishes between athletes already assigned to the relay and athletes available for assignment.

The '''Available''' area displays eligible athletes who have not already been assigned to the selected relay.

When an athlete is assigned to a relay position, that athlete is removed from Available.

When an athlete is removed from the relay, the athlete returns to Available.

This synchronization prevents the same athlete from being inadvertently assigned twice within the same relay lineup.

The Available list is specific to the selected relay's competition division.

== 6. Entry Tallies ==

Each athlete's roster card includes a tally of their meet participation.

The tally accounts for individual-event entries and relay memberships.

For example, an athlete entered in the 100 meters and assigned to a 4×100 relay has two event participations.

When an entry is added or removed, the tally updates to reflect the athlete's current assignments.

Relay membership is counted from the relay team rather than requiring a separate individual-event entry for each relay runner.

== 7. Sorting and Reviewing Entries ==

The board offers multiple ways to inspect the roster and event assignments.

=== Division View ===

Useful when preparing entries for age-group or divisional competition.

=== Alphabetical View ===

Useful when locating a particular athlete or reviewing a team roster.

=== Seed-Mark View ===

Useful when comparing athlete performances and reviewing likely competition placement.

Before completing meet entries, the Team Leader should review each event to confirm that the correct athletes have been entered.

Relay lineups should receive additional review because both team membership and running order matter.

== 8. Recommended Entry Workflow ==

A practical workflow for preparing a team's meet entries is:

# '''Review the roster.''' Confirm that the athletes expected to compete are present.
# '''Organize by division.''' Work through the competition divisions to reduce assignment errors.
# '''Enter individual events.''' Assign athletes to their selected track and field events.
# '''Review seed marks.''' Check performance information where applicable.
# '''Build relay teams.''' Assign runners and alternates to the appropriate relay divisions.
# '''Set relay running order.''' Open each relay editor and arrange the competition legs.
# '''Review entry tallies.''' Look for athletes with missing or unexpected assignments.
# '''Make corrections.''' Use the X controls or relay editor to remove or rearrange athletes.
# '''Perform a final review.''' Check each event and relay before the entry deadline.

== 9. Important Operating Rules ==

=== Individual Entries and Relay Membership Are Different ===

An individual-event entry represents an athlete competing in a particular event.

A relay entry represents a team, with athletes assigned to specific positions within that team.

The board presents both in a common interface, but relay membership and running order are maintained as team information.

=== Removing a Runner Does Not Remove the Team ===

A relay team can remain in place even when its runner positions are empty.

This allows a Team Leader to rebuild or revise a lineup without creating a new team designation.

=== Running Order Is Explicit ===

A relay runner's position is meaningful.

Moving an athlete between legs changes the lineup; removing an athlete should not automatically shift the remaining runners into different legs.

=== Saved Entries Survive Reloading ===

Entry assignments are intended to be persistent, not temporary arrangements that exist only in the browser.

Reloading the entry board should reproduce the saved individual entries and relay memberships.

== 10. Troubleshooting ==

{| class="wikitable"
|-
! Situation
! What to do
|-
| An athlete is missing from Available
| Check whether the athlete is already assigned to the relay or belongs to a different division.
|-
| A relay athlete is in the wrong leg
| Open the relay editor and rearrange the runners.
|-
| An athlete should not be in an event
| Click the X beside the athlete's name.
|-
| A relay needs another runner
| Open the relay editor and assign an eligible athlete from Available.
|-
| A relay needs an alternate
| Use the alternate positions in the relay editor.
|-
| An entry looks incorrect after editing
| Reload the board and check the saved state. If the discrepancy remains, report it to the meet administrator.
|}

== 11. Summary ==

The Team Leader Meet Entry Board provides a unified workspace for preparing a team's track and field entries.

It combines athlete selection, event assignment, roster sorting, seed-mark review, relay team management, and entry tallies.

The goal is to let Team Leaders prepare and correct meet entries directly, while preserving the distinction between individual participation and the more detailed structure of a relay team.

----

'''Documentation status:''' Initial operating guide based on the current entry-board workflow and relay demonstrations. Entry deadlines, eligibility enforcement, submission confirmation, fee handling, and administrative override procedures should be documented separately after their behavior is verified.

Create-Meet

2026-10-07T22:29:05Z

Trackinfo: /* Qual Open */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Qual Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction. If you want to limit entry to members of a certain organization, that will be selectable on the Financial page under entry requirements, and this will duplicate that action rather than making you work for it. Rather than being an enforced limitation, the text you write in the box will be a warning the entrants will see before entering.

There is a component where you can make entry subject to your approval. Such requests will be sent to your contact email.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed. This is loosely enforced, that we are expecting some derivative of what you write within the name of the team entering. So the team might have a formal name, you might have just entered the team or school name or even abbreviation, the system will be looking for some component of what you have written.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Create-Meet

2026-10-07T22:28:05Z

Trackinfo: /* Invite teams */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Qual Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction. If you want to limit entry to members of a certain organization, that will be selectable on the Financial page under entry requirements, and this will duplicate that action rather than making you work for it. Rather than being an enforced limitation, the text you write in the box will be a warning the entrants will see before entering.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed. This is loosely enforced, that we are expecting some derivative of what you write within the name of the team entering. So the team might have a formal name, you might have just entered the team or school name or even abbreviation, the system will be looking for some component of what you have written.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Create-Meet

2026-10-07T22:22:53Z

Trackinfo: /* Qual Open */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Qual Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction. If you want to limit entry to members of a certain organization, that will be selectable on the Financial page under entry requirements, and this will duplicate that action rather than making you work for it. Rather than being an enforced limitation, the text you write in the box will be a warning the entrants will see before entering.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Create-Meet

2026-10-07T21:45:35Z

Trackinfo: /* Conditional Open */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Qual Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction. If you want to limit entry to members of a certain organization, that will be selectable on the Financial page under entry requirements, and this will duplicate that action rather than making you work for it. The text you write in the

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Venue

2026-10-06T02:53:24Z

Trackinfo: /* Venue maps */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

To Run It asks how many physical facilities will actually be used for each type of field event offered by the meet. This will become public information. Competitors want to know what they will be using.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own. Temporary pole vault runways are becoming more common. Some competitors will want to know what they are jumping off of.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

Sometimes the Weight Throws will have their own cages, or share the Shot Put ring. If a Weight Throw is conducted outdoors for an Indoor meet, that might be a good item to note.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition throwing at each other.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]] below.

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:52:39Z

Trackinfo: /* Conditional conflicts */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

To Run It asks how many physical facilities will actually be used for each type of field event offered by the meet. This will become public information. Competitors want to know what they will be using.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own. Temporary pole vault runways are becoming more common. Some competitors will want to know what they are jumping off of.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

Sometimes the Weight Throws will have their own cages, or share the Shot Put ring. If a Weight Throw is conducted outdoors for an Indoor meet, that might be a good item to note.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition throwing at each other.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:50:06Z

Trackinfo: /* Field-event facilities */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

To Run It asks how many physical facilities will actually be used for each type of field event offered by the meet. This will become public information. Competitors want to know what they will be using.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own. Temporary pole vault runways are becoming more common. Some competitors will want to know what they are jumping off of.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

Sometimes the Weight Throws will have their own cages, or share the Shot Put ring. If a Weight Throw is conducted outdoors for an Indoor meet, that might be a good item to note.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:48:50Z

Trackinfo: /* Weight Throw — Shares Hammer cage */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own. Temporary pole vault runways are becoming more common. Some competitors will want to know what they are jumping off of.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

Sometimes the Weight Throws will have their own cages, or share the Shot Put ring. If a Weight Throw is conducted outdoors for an Indoor meet, that might be a good item to note.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:45:10Z

Trackinfo: /* Javelin */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own. Temporary pole vault runways are becoming more common. Some competitors will want to know what they are jumping off of.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:43:45Z

Trackinfo: /* Javelin */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own. Temporary pole vault runways are becoming more common. Some competitors will want to know what they are jumping off of.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:43:08Z

Trackinfo: /* Pole Vault */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own. Temporary pole vault runways are becoming more common. Some competitors will want to know what they are jumping off of.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:41:53Z

Trackinfo: /* High Jump */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:41:18Z

Trackinfo: /* Horizontal Jumps */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:38:18Z

Trackinfo: /* Pole Vault */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

* North
* South
* Home Straight
* Back Straight

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:37:44Z

Trackinfo: /* Field-event facilities */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:35:43Z

Trackinfo: /* Wind readings */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:30:58Z

Trackinfo: /* Use Imperial Measurements (ft/in) */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:23:53Z

Trackinfo: /* 6 attempts */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:22:34Z

Trackinfo: /* 3 attempts */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:17:01Z

Trackinfo: /* Cage names */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one throwing cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:16:37Z

Trackinfo: /* How many throwing cages will you use? */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T02:10:47Z

Trackinfo: /* Lanes to exclude */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T01:37:50Z

Trackinfo: /* Number of oval lanes */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T01:31:44Z

Trackinfo: /* Number of oval lanes */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T01:28:30Z

Trackinfo: /* Relationship to Create-Meet */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet venue is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-06T01:25:54Z

Trackinfo: /* Relationship to Create Meet */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create-Meet ==

The primary meet facility is initially identified on [[Create-Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A separate cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

'''Current implementation note:''' Full multiple-location configuration is being developed. The Venue system is intended to become the authoritative location for configuring all physical competition locations used by a meet.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Venue

2026-10-05T22:46:58Z

Trackinfo: /* Who should use this page? */

{{DISPLAYTITLE:Venue}}

The '''Venue''' page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

== Who should use this page? ==

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

* Track lanes
* Multiple field-event facilities
* Throwing cages
* Facility conflicts
* Field-event competition format
* Venue maps
* Public and practice access

Creating a detailed interactive venue map is '''optional'''. See [[Interactive Map Designer]].

== Relationship to Create Meet ==

The primary meet facility is initially identified on [[Create Meet]].

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

* A stadium for track and field events
* A separate cross-country course
* A road-race course
* A separate race-walk course
* A throwing facility at another location

'''Current implementation note:''' Full multiple-location configuration is being developed. The Venue system is intended to become the authoritative location for configuring all physical competition locations used by a meet.

== Saving ==

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

== Track ==

=== Number of oval lanes ===

Enter the number of lanes available around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under '''Lanes to exclude''' rather than reducing the total number of oval lanes.

=== Number of sprint lanes ===

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

* 8 oval lanes
* 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

=== Lanes to exclude ===

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

<code>1,8</code>

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

* Surface damage
* Construction
* Equipment obstruction
* Safety concerns
* A temporary meet-specific restriction

== Throwing cages ==

=== How many throwing cages will you use? ===

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

=== Cage names ===

When more than one cage is available, give each cage a useful name.

Examples:

* North
* South
* Stadium
* Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

* Cage North
* Cage South

Use names that officials and meet staff will recognize.

=== How will you divide them? ===

When multiple cages are available, indicate the general way they will be used.

Current choices are:

* '''Men/Women'''
* '''Hammer/Discus'''
* '''Divisions'''
* '''Other'''

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

== Field-event competition format ==

=== Attempts per event ===

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

* '''3 attempts'''
* '''4 attempts'''
* '''3+3'''
* '''3+2+1'''
* '''6 attempts'''

==== 3 attempts ====

Each competitor receives three attempts.

==== 4 attempts ====

Each competitor receives four attempts.

==== 6 attempts ====

Each competitor receives six attempts.

==== 3+3 ====

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

'''How many advance to final?'''

Enter the number of competitors who should receive the additional three attempts.

==== 3+2+1 ====

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

* How many get the last 3 attempts?
* How many advance to the final round?
* What order should be used for the final round?

The final-round order may currently be:

* '''First place first'''
* '''First place last'''

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

=== Use Imperial Measurements (ft/in) ===

Select this when field-event measurements should be displayed or recorded using feet and inches.

When this is not selected, Torunit may use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level.

== Field-event facilities ==

Torunit asks how many physical facilities will actually be used for each type of field event offered by the meet.

Only facilities relevant to the meet's selected events need to be configured.

For example, a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

=== Horizontal Jumps ===

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

If more than one facility will be used, give the facilities useful names.

Examples:

* North
* South
* Home Straight
* Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

=== Wind readings ===

Select '''Wind readings''' when wind measurements will be taken for the applicable horizontal-jump events.

Wind measurement requirements depend on the competition and governing rules.

=== High Jump ===

Enter the number of High Jump facilities that will be used.

If more than one High Jump pit is available, name the individual facilities.

Examples:

* HJ North
* HJ South

These become separate physical resources that Torunit can consider during scheduling.

=== Pole Vault ===

Enter the number of Pole Vault facilities that will be used.

If more than one Pole Vault pit is available, name the individual facilities.

=== Shot Put ===

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

* Shot North
* Shot South
* Upper Ring

=== Javelin ===

Enter the number of Javelin facilities or sectors that will be used.

If more than one is available, name the individual facilities.

=== Weight Throw — Shares Hammer cage ===

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

== Facility conflicts ==

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

* '''Hard conflicts'''
* '''Conditional conflicts'''

== Hard conflicts ==

A '''hard conflict''' means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose '''Add'''.

The conflict appears as a chip below the controls.

Examples might include:

* A javelin sector crossing the track
* A throwing sector overlapping another throwing area
* A runway occupying an area required by another event
* Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

== Conditional conflicts ==

A '''conditional conflict''' describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

# The first facility or event
# The available distance in metres
# The second facility or event
# '''Add'''

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition.

The current Venue page refers to the map's Measure tool for determining available distances.

See [[Interactive Map Designer#Measuring distances]].

== Venue maps ==

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional [[Interactive Map Designer]].

== Add a venue map ==

Venue maps may currently be uploaded as:

* JPG
* JPEG
* PNG
* PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

* Facility Map
* Parking Map
* Bus Drop-off
* Team Camp Map
* Spectator Entrance Map

=== Label your upload ===

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

* Facility Map
* Team Parking
* Bus Drop-off
* Competition Areas
* Spectator Parking

=== Show on public ad page ===

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

=== Upload Map ===

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

== Uploaded maps for this meet ==

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

=== Map name ===

The map's label may be changed after upload.

=== Show on ad page ===

Controls whether that individual map is publicly displayed.

=== View ===

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

=== Save ===

Saves changes to the map's name or public-display setting.

=== Delete ===

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

== Interactive Facility Map — Optional ==

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

'''Most meets do not need to create an interactive map.'''

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

* Competition facilities
* Entrances
* Parking
* Bus drop-off
* Team camps
* Clerk of Course
* Warm-up areas
* Medical facilities
* Restrooms
* Concessions
* Awards
* Security locations
* Volunteer locations
* VIP areas
* Emergency access
* Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see '''[[Interactive Map Designer]]'''.

{{Note|The Torunit interactive mapping system is under redevelopment. The existing map editor is documented separately so this Venue article does not depend on the implementation of a particular map editor.}}

== Public facility information ==

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

=== Is this facility ever available for public use? ===

Select:

* '''Yes'''
* '''No'''

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

=== What hours? ===

Enter the times during which the facility is normally available.

Example:

<code>Weekdays 6–8am, Sat 2–6pm</code>

Hours may be approximate if access varies.

=== Under what circumstances? ===

Explain any restrictions or requirements associated with public use.

Examples include:

* Prior approval required
* Fee required
* Coach supervision required
* Team use only
* Seasonal restrictions
* School-hours restrictions
* Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

=== Public access contact ===

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

* Name
* Email
* Phone

This contact concerns access to the facility rather than general questions about the current meet.

=== Last updated ===

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

== Practice facilities available ==

Identify specialized facilities that may be available for practice.

Current selections are:

* Pole Vault
* High Jump
* Throwing Cage
* Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

== Multiple competition locations ==

Some meets use facilities at more than one physical location.

Examples include:

* Track and field at a stadium with Race Walk on a separate course
* A road race beginning away from the stadium
* Cross Country at a separate course
* Throws conducted at a secondary field
* Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

'''Current status:''' Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

== How Venue information affects scheduling ==

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

* Available track lanes affect heat capacity.
* Separate sprint and oval lane counts may produce different capacities.
* Excluded lanes reduce usable capacity.
* Multiple pits, rings, runways, or cages may allow simultaneous field events.
* A single shared facility prevents incompatible simultaneous use.
* Hard conflicts prohibit combinations that cannot safely operate together.
* Conditional conflicts describe combinations whose simultaneous use depends on available space.
* Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility '''can physically support'''.

The scheduler determines when those resources will actually be used.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* '''Multiple competition locations''' are not yet fully implemented.
* The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
* The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
* The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
* Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
* Venue should remain usable without requiring the Interactive Map Designer.

== See also ==

* [[Create-Meet]]
* [[Interactive Map Designer]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Combined Events]]
* [[Registration]]
* [[Live Meet]]

[[Category:Meet Director]]
[[Category:Meet setup]]
[[Category:Venue]]

Create-Meet

2026-10-05T22:40:25Z

Trackinfo: /* Conditional Open */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Conditional Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction. If you want to limit entry to members of a certain organization, that will be selectable on the Financial page under entry requirements, and this will duplicate that action rather than making you work for it.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Create-Meet

2026-10-05T22:36:42Z

Trackinfo: /* Meet format */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

==== Conditional Open ====

Allows public entry to anyone who meets your restrictions, so selecting this will open a menu. If you make your meet open to say high school divisions, visiting athletes from out of state might enter as opposed to closing the meet and only inviting certain local teams. If you want your meet restricted to only women, we could actually do that in the Gender menu but this will duplicate that restriction.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

Create-Meet

2026-09-16T19:59:14Z

Trackinfo: /* Pins */

{{DISPLAYTITLE:Create Meet}}

First of all, thank you for being a person to take the initiative to host a meet. It is because of people like you that this sport can survive. The '''Create Meet''' page is the beginning of that process. It establishes the basic identity, competition structure, participants, events, entry rules, and operating preferences for your meet.

The information entered here is used throughout Torunit. The settings selected on the next several pages may affect the conduct of your meet, including registration, scheduling, seeding, field-event administration, scoring, the public information we use to advertise your meet, and later your own Meet Director control pages.

== Before beginning ==

The you should have, at minimum:

* A meet name
* A competition date or dates
* You need a track or a primary facility
* The applicable rulebook
* The divisions being offered
* The events being offered

A red asterisk identifies a required setting.

== Saving and Meet ID ==

The Create Meet page saves changes automatically.

After a valid meet is first saved, Torunit creates a six-character '''Meet ID'''. When the page then reloads with that Meet ID, that is your code identifier through out ToRunIt. You shouldn't need to use it again here, that personalization should follow throughout this meet, but it will be useful to recall everything you did this year, when you want to copy it next year.

Other Meet Director pages remain unavailable until the meet has been saved and a Meet ID has been created.

A small '''Saved ✓''' notice appears after a successful autosave. If the save fails, Torunit displays '''Save failed'''.

== Public information ==

=== Meet Name ===

This the public and internal name of the meet. Keep it simple and memorable. You might have a title sponsor, because we all need money to come from somewhere, but realize your name could be truncated in various places and in people's minds. Foot Locker became the memorable name for the first National Championship Cross Country Championships. If you use Joe's Auto Sales presents the Hometown Relays, your meet could become known as Joe's rather than the Hometown Relays . . . presented by Joe's Auto Sales.

Enter the complete name by which you would like the meet to be identified. If it is just your school vs another school or your own intersquad meet, name the participanting teams.

A Meet Name is required.

=== Meet Date ===

We need to know when the meet will happen. Next to that date are a few modifiers.

==== Multi-day ====
When '''Multi-day''' is selected, the first date will become the '''Start Date'''.

An '''End Date''' field appears to select the last date
* If no End Date has been entered, Torunit initially copies the Start Date into the End Date field

It could take you weeks to months to prepare for your meet, we are only concerned with days actual competition will take place.

Unchecking Multi-day hides and clears the End Date.

==== Rounds ====

A meet may be multi-day without using rounds. A one-day meet may also use rounds.

Rounds means athletes need to qualify to advance to the final.

Select this when one or more events advance through multiple rounds, such as:

* Preliminary
* Quarterfinal
* Semifinal
* Final

This selection adds the rounds-planning portion of the scheduling workflow applicable to the meet.

==== Additional running location/course ====

Select this when the meet uses an additional running venue or course beyond the primary track facility. You don't need it if the throwing cage is across the street, but if you have a second track or events off campus, this will create a means to schedule them separately.

Possible examples include:

* A cross-country course
* A road-race course
* A separate race-walk course
* A second running facility

=== Contact Name ===

The name of the public contact for the meet.

This could be you; the Meet Director, or another person you designate to answer public questions.

=== Public email ===

The email address displayed or used for public meet inquiries.

This should be an address the meet organization is prepared to monitor. It can be different from your personal email.

=== Public phone ===

The telephone number displayed or used for public meet inquiries. It can go to a different contact person.

=== Public description ===

A short public description of the meet. If you have a document or a flyer, you will be given an opportunity to put that in on your public page later. This is a place to edit that content if you do not have prepared materials.

This may include information such as:

* The purpose or level of the meet
* Who may enter
* Special features
* Important general instructions

Detailed entry rules and operational instructions should be placed in their appropriate settings or later meet information pages rather than crowded into this field.

=== Website ===

The official public website for the meet or host organization.

Enter the complete address, including:

<code>https://</code>

You don't need a website, you will get a meet advertising page hosted on torunit.com which should contain all the information someone will need to enter the meet. Tthe information on that page will come from what you answer as you create the meet. You can redirect to your torunit.com page. Being listed will automatically include your listing in [[Find a Meet]].

=== Copy settings from another meet? ===

This area is intended to begin a new meet using settings from an existing meet. As we mentioned above, you can copy last year's meet or copy another meet's settings and yours can be copied by anybody else. Exchanging ready-made meet formats could save a lot of time, or duplicate the same mistakes over and over. Look at the success of a meet before copying that meet's settings. You will still need to make your meet your own by changing the date, that will allow you to bring last year's information forward. You are still responsible for making any changes to make this year's meet your own.

==== I have a Meet ID ====

This is where you insert the 6 character Meet ID of the meet you intend to copy.

==== Let me search ====

If you don't know what the Meet ID you want to copy is, use [[Find A Meet]].

Intended for locating a previous meet without already knowing its Meet ID.

'''Current status:''' The current page contains the button, but the supplied page code does not show an attached action.

=== Brief note to help other directors ===

A short description of the meet format. If you have designed a good set up for say, your state's particular set of events and order, give it a name to save other Meet Directors that initial set up.

The stored field is named '''Format description'''.

This is intended to help another director understand the nature of the meet when reviewing or copying its settings.

Examples:

* Two-day youth championship with preliminaries
* Four-team Wisconsin high school double dual-scoring meet
* Open all-comers meet with rolling schedule

Hint: If you don't have a meet to copy, here is a way to look for it in [[Find a Meet]].

== Facility ==

=== Facility name ===

The name of the primary competition facility.

Begin typing the facility name and select the correct location from the location search. Google will help suggest names to make finding your location easier.

Torunit stores the selected facility name, geographic coordinates, and location identifier. If someone else has held a meet at this facility, you will find their information to use or modify. What you save will help others who follow you to the same facility.

The Facility name is required.

=== Pins ===

When you have selected a facility, a map will pop up.

The map provides separate pins for:

* '''M''' — Main Entrance
* '''B''' — Bus Drop-off
* '''P''' — Parking

Drag each pin to the exact location that should be communicated to the appropriate users.

The Main Entrance pin establishes the location of the venue. If you don't have a main entrance to point people to, you can use your check in table or the start or finish line where you want people to find your meet. The bus and parking pins identify distinct arrival locations that maps can guide people to.

Be specific about where you place your '''B''' — Bus Drop-off so it is on the correct curb in the correct direction. Bus drivers need to maneuver to drop on the correct side of the road.

=== Environment ===

Identifies the competition environment. This will control what you see below. If you are doing a Cross Country meet (frequently abbreviated as XC) select that alone, you won't see track events, for example. You can select more than one if that fits your meet.

==== Outdoor ====

A conventional outdoor track-and-field meet. If you are doing external, non-stadia track events like a shot put in the city square or the pole vault on the beach, still include the event as a track event but select the additional venue where you can schedule the special event later.

==== Indoor ====

An indoor track-and-field meet with a shorter track, sometimes fewer lanes, more laps.

==== XC ====

A cross-country meet.

==== Road ====

An external or non-stadia Road event. Include road races, marathons and road race walks.

Environment affects which events, facilities, measurements, and competition rules may apply.

=== Confirmed venues ===

When you have confirmed your location, this displays the facilities currently attached to the meet as a confirmation we got it right.

A venue appears as a labeled chip. Select the × on a chip to remove that venue.

Removing the primary venue also clears its stored name and location information. Be careful or you get to start over.

=== Add another venue ===

Intended to attach another facility or course to the meet. You can use a different track or a cross country course in a park, a pole vault at the local shopping mall or a road racing course all as part of your big event.

== Divisions ==

The Divisions section defines the groups eligible to compete.

A division may represent age, school level, classification, ability, or another grouping used by the meet. A lot of divisions potentially overlap. They are grouped so differen formats for different organizations are adjacent to one another. If you are working under a specific organization (AAU, USATF, WMA, NSGA) be sure to choose the divisions for that organization. Athletes should then automatically sort into the correct divisions.

=== Available divisions ===

The left list contains divisions available for selection. If you don't like our divisions, go ahead and make your own.

Multiple divisions may be selected before choosing '''Add →'''.

=== Add → ===

Adds the highlighted divisions to the meet.

Added divisions appear in '''Selected divisions'''.

=== Clear ===

Removes all currently selected divisions from the meet.

'''Use this carefully'''. Clearing the list changes the division structure used by later event and participant configuration.

=== Selected divisions ===

Displays the divisions included in the meet.

Each selected division appears as a chip.

Selecting a chip allows it to be included in a multi-division configuration action. Command, Control, or Shift may be used to select more than one chip.

The × removes that division.

The gear opens division-specific configuration.

=== Configure Selected ===

Opens configuration for the selected division or divisions.

This permits multiple divisions to be configured together.

Division-specific configuration may be used when divisions do not all offer the same events or genders.

=== Division gears ===

The gear symbol inside a selected division opens configuration for that one division. This is where you can adjust a division with a different event list. Most will use it to uncheck events that are for the other divisions in the meet, but you can also add events specifically for this division by pressing Add From Catalog.

Use meet events will select all events in the meet, which is already the way you will find the division when you open the gears menu.

Select all turn all events back on. Clear turns all events off, making it easier to select just a few. M only and F only also let you select all events for one gender or the other, or both giving you a starting point to make your selections.

When you close the menu, the system will remember your selections.

After you have made and adjustment it will appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

We have tried to make most common divisions available. If we don't have what you need already, go ahead and make your own. Enter the name of a division not already available in Torunit. Later we will try to learn from what is missing.

====Define====
If your parameters for that new division fit into birthdates calculating ages or gender selection, give us those parameters:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used. We need to know the division name we are making the definition for.

=== Add Custom ===
When you are done, the Add Custom button adds the new custom division you created to the meet.

== Events ==

The Events section defines the events offered by the meet.

Track events and field events are automatically placed into separate selected-event columns.

=== Available events ===
Event names are abbreviated to take up minimum space on a cel phone screen. We assume you will understand the events you intend to offer. On public pages we have links to expand the abbreviations and wikipedia links that explain the events. Yeah, I wrote a lot of those wikipedia articles.

The left event list contains the events and [[event families]] available for selection.

An event family is identified with a star and represents a related group of events rather than one isolated event.

Click to highlight the ones you want to include. Multiple events may be selected. Select '''Add →''' when you are satisfied. You can still add more.

====Add====

Adds the highlighted events to the meet.

Torunit identifies each selected item as a track event or field event and places it in the appropriate selected-event area.

====Clear====

Removes all selected track and field events.

'''Use this carefully.''' The event list is used to build division-event-gender combinations and later scheduling data.

=== Selected track events ===

Displays the running events included in the meet.

Track-event chips may be dragged to change their order.

The stored order may be used by later meet processes as the meet's event order.

Select × to remove an event.

=== Selected field events ===

Displays the field events included in the meet.

Select × to remove an event.

=== Include Legacy Events ===

Expands the list of events to show older event definitions for imperial measured distances (other than the Mile) that are normally hidden from the available-event list.

=== Include Combined Events ===

Loads combined-event definitions into the available-event list.

Examples may include:

* Decathlon
* Heptathlon
* Pentathlon
* Triathlon
* Other rulebook-defined combined events

Selecting a combined event makes its component-event structure available to later configuration and scheduling.

=== + Create Custom ===

Opens the custom combined-event editor.

A custom combined event may include:

* Event name
* Short name
* Gender
* Environment
* Description
* Ordered component events

The current code requires at least three and no more than fifteen component events.

=== New event name ===

Enter the name of an event that is not already available.

=== Define… ===

Opens the custom event definition dialog.

The event name must be entered first.

The exact custom-event fields should be documented after the custom-event editor is finalized.

=== Add Custom ===

Adds the typed custom event to the meet.

== Cross Country, Road and Triathlon Events ==

When Cross Country, Road or Triathlon is selected as a Competition Environment, the Events area changes from the normal Track and Field event selector to a race-based configuration. If you have multiple environments checked, track will remain and the other environments wil open in a window below.

The Meet Director defines the races that will be offered. Each race can have its own distance, participating divisions and genders, team-scoring rules, and relay configuration. If you only create one race distance it will be applied to all divisions.

=== Race distance offered ===

Use '''+ Race distance''' to add each race that will be offered.

Enter the published race distance and select the unit. Distances may be entered in meters, kilometers or miles.

Examples:

* Cross Country 5 km
* Cross Country 3 km
* Road 10 km
* Road 1 mile

There is no requirement that every division run the same distance unless you define it so.

The first race added initially applies to all currently selected divisions. Additional races can then be assigned to the appropriate divisions using the gear control. Open the menu and subtract divisions who do not do this distance. Or clear the checks and add from the blank slate.

=== Divisions and genders ===

The gear beside a race controls which of the meet's selected divisions are
eligible for that race.

For each division, Boys/Men and Girls/Women may be enabled independently.

The Division selection on the left side of Create Meet establishes the universe of divisions available to the meet. The race gear determines which of those divisions actually participate in this particular race.

Example:

A Road meet may offer:

* 5 km — all divisions
* 10 km — older divisions
* 1 km — 14-and-under divisions

The race gear is the authority for these race-specific assignments. Without adjusting the gear menu, all divisions are selected.

=== Team scoring ===

Enable '''Team scoring''' when individual finishes in this race will also be combined into a team result. In the XC environment, it will default to the typical 5 scoring, 2 offsetting, 7 athlete team composition. All numbers can be changed.

The available settings include:

; Max
: Maximum number of athletes associated with a scoring team for this race.

; Score
: Number of finishers whose places count toward the team score.

; Displace
: Additional finishers who do not score for their own team but may affect the scoring places of runners from other teams.

; B+
: Number of additional B, C or later teams permitted when the meet allows more than one scoring team from the same organization. You can leave this as a zero and only the primary A team can be entered.

A common Cross Country configuration is 7 athletes, 5 scorers and 2 displacers. Other meets may use configurations such as 5 athletes with 3 scorers and 2 displacers.

These settings define how a team result is formed. They are separate from the meet's general points-for-place Scoring Configuration.
If you wish to limit the number of teams in any race you will get the opportunity to do so in the [[Participants]] page of this meet creation process where you start setting up your schedule.

=== Relay ===

Enable '''Relay''' when several athletes or components combine to produce one race result.

Essentially a Marathon Relay, an [[Ekiden]] or a [[Paarlauf Relay]] would fit into a relay configuration.

Specify the number of legs and the number of members of the team. These values do not have to be identical.
Each leg has its own distance and unit selector. It will default to the first distance entered until you enter a different distance. Mathematically the sum of all legs should match the distance of the race before you can leave the page.

If a relay is first created without individual leg distances, Torunit may divide the declared total distance evenly as a starting value. The Meet Director may then change the individual legs.
Unequal legs are permitted.

Examples include:

* 4 × 1 km
* 5 km + 8 km + 7 km + 6 km + 4 km
* Ekiden-style road or Cross Country relays

Torunit compares the sum of the entered legs with the declared race distance.
If the totals do not agree, the race displays a warning and the Meet Director
must correct the configuration before leaving the page.

=== Triathlon and other component races ===

Triathlon uses the same race-authoring concept but the components may use
different disciplines.

A race may contain components such as:

* Swim — 1 km
* Bike — 20 km
* Run — 10 km

The component names are not intended to be limited permanently to Swim, Bike and Run. This structure can also support other ordered disciplines such as kayak, skiing, snowshoeing or repeated disciplines. Only two components would be a biathlon.

The sequence entered by the Meet Director defines the competition. Using the relay section, the events could be conducted as a relay

=== Multiple Competition Environments ===

More than one Competition Environment may be selected for the same meet.
For example, a meet may include Outdoor Track and Cross Country, or Outdoor Track and Road. Or all three.

When multiple environments are selected, Torunit shows the appropriate authoring tools for each environment. Selecting just Cross Country, Road or Triathlon will remove Track and Field events when a Track environment is also selected. On the schedule page you will get the ability to schedule each facility independently.

=== Participants and race sections ===

Create Meet defines what races are offered.

The Participants page is where anticipated entries and race capacity are used to
determine how many physical races, sections or waves may be required.

For example, if 41 teams are entered and the desired capacity is approximately
20 teams per race, Torunit may propose three races. The Meet Director may adjust
that proposal.

Cross Country uses race or section terminology. Road events may use wave
terminology. These operational splits belong in Participants and Schedule rather
than in the Create Meet race definition.

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules. You could get some bum off the street, like me, wanting to enter.

An open meet is not necessarily unrestricted. Membership, age groups, age verification, entry limits, qualifying marks can still limit your entries at your choosing. You can also impose deadlines. And entry fees will still apply.

==== Closed ====

Restricts entry to invited teams and individuals.

Selecting Closed displays the '''Invite teams''' field where you can name the teams eligible to enter your meet.

=== Invite teams ===

Lists the teams invited to a closed meet.

Enter one team per line or separate team names with commas. A list may also be pasted from a spreadsheet.

The invited-team list is required when the meet is Closed.

=== Numerical Limits ===

Opens the Numerical Limits dialog.

These settings control the maximum size of the meet and how entries are accepted when demand exceeds available space.

==== Max Participants (total) ====

The maximum number of individual participants permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Teams ====

The maximum number of teams permitted in the meet.

Leaving the field blank means no limit is specified here.

==== Max Participants per Team ====

The maximum number of participants accepted from one team across the meet.

==== Max Participants per Division per Team ====

The maximum number of participants from one team who may enter a particular division.

==== Max Participants per Event — All events same ====

Applies one maximum participant count to every event.

==== Max Participants per Event — By event ====

Opens the Per-Event Limits editor.

This permits different limits for different events.

Examples:

* 24 athletes in the 100 metres
* 16 athletes in the pole vault
* 32 athletes in cross country

==== Max per Team per Event ====

Limits the number of entries one team may submit in each event.

==== First Come, First Served ====

When a limit is reached, entries are accepted in the order in which they were received.

==== Superior Marks ====

When a limit is reached, stronger submitted marks receive preference.

The method used to compare marks should follow the event type and meet rules.

==== Impose Qualifying Marks ====

Requires entries to satisfy qualifying standards.

The actual standards are entered through the Qualifying Marks settings.

==== Appeal to Meet Director ====

Permits an entry decision to be referred to the Meet Director. These questions will come to the public contact.

More than one decision method may currently be selected.

=== Rulebook ===

Identifies the principal rules governing the meet.

Available selections are:

* '''WA''' — World Athletics
* '''USATF''' — USA Track & Field
* '''NFHS''' — National Federation of State High School Associations
* '''NCAA''' — National Collegiate Athletic Association
* '''AAU''' — Amateur Athletic Union
* '''Other'''

The selected rulebook may affect event definitions, divisions, implement specifications, advancement, scoring, and other meet behavior.

==== Other ====

Opens a dialog requesting the organization name.

Use Other when the governing rules are not represented by the listed rulebooks.

=== Gender ===

Identifies the gender groups offered by the meet.

Available selections are:

* '''Both'''
* '''Boys/Men'''
* '''Girls/Women'''

This is the meet-wide starting selection. Individual division-event combinations may later be configured more narrowly.

=== Combine divisions ===

Indicates whether Torunit may combine different divisions in competition.

==== Yes ====

Different divisions may be placed together where permitted.

Results and scoring may still need to remain separated by division.

==== No ====

Divisions should ordinarily compete separately.

This setting describes the meet's general policy. A later explicit scheduling decision may still require specific treatment.

=== Combine genders ===

Indicates whether boys/men and girls/women may compete together where permitted.

==== Yes ====

Gender groups may be combined operationally.

Results, records, scoring, or qualification may still need to remain separated.

==== No ====

Gender groups should ordinarily compete separately.

=== Implement Inspection required ===

Identifies whether throwing implements must be inspected before competition.

==== Yes ====

Implement inspection is required.

Selecting Yes displays the inspection timing controls.

==== No ====

Torunit does not treat implement inspection as a required meet process.

==== Begin ====

Sets how far in advance implement inspection begins.

Enter a number and select:

* Minutes
* Hours

The current label defines the offset as the amount of time '''before the first throw'''.

Example:

* Begin 60 minutes before first throw
* Begin 2 hours before first throw

== Display preferences ==

=== Clock ===

Controls how meet times are displayed.

==== AM / PM ====

Displays times using a twelve-hour clock.

Examples:

* 8:00 AM
* 4:30 PM

==== 24-hour ====

Displays times using a twenty-four-hour clock.

Examples:

* 08:00
* 16:30

This is a meet-wide preference intended for schedules and public displays.

=== Name order ===

Controls how participant names are displayed.

==== First Last ====

Displays the given name before the family name.

Example:

: Jesse Owens

==== Last, First ====

Displays the family name first.

Example:

: Owens, Jesse

This is a meet-wide display preference.

== Scoring ==

=== Scoring meet ===

Indicates whether team or participant points are calculated.

==== Yes ====

The meet uses scoring.

The scoring configuration may be opened to define the point system.

==== No ====

The meet is non-scoring.

Results may still be produced, but Torunit does not apply a meet point schedule.

=== Configure Scoring ===

Opens the scoring dialog.

==== Scoring Mode ====

===== Points per place =====

Assigns points according to finishing place.

The current default sequence is:

<code>10,8,6,4,2,1</code>

===== Dual / Multi-dual =====

Uses dual-meet scoring.

The current default track and field sequence is:

<code>5,3,1</code>

The current default relay value is:

<code>5</code>

In a multi-dual, each team is scored head-to-head against every other team.

==== Track points ====

Comma-separated points awarded by finishing place in track events.

==== Field points ====

Comma-separated points awarded by finishing place in field events.

A setting may apply the same point schedule used for track events.

==== Relay points ====

Comma-separated points awarded by finishing place in relay events.

== Qualifying marks ==

=== Qualifying marks required ===

Indicates whether qualifying standards are used.

==== Yes ====

The meet uses qualifying marks.

==== No ====

No qualifying standard is required by this setting.

=== Configure Qualifying Marks ===

Opens the Qualifying Marks dialog.

Qualifying marks are organized by:

* Division
* Event
* Male mark
* Female mark

The available rows are built from the selected divisions and events. If a division has its own event configuration, only those configured events are shown for that division.

=== Download CSV Template ===

Downloads a file intended to be completed outside Torunit.

=== Upload Completed CSV ===

Imports qualifying marks from a completed CSV or text file.

=== Open Manual Editor ===

Displays the qualifying-mark table for direct entry.

Blank marks are not saved. Entering one or more marks causes the meet to be treated as using qualifying standards.

== Seeding ==

The seeding setting defines the meet's general ordering method.

=== Seeded ===

Uses submitted or verified marks to organize competitors according to the meet's seeding rules.

=== Slow to Fast ===

Orders sections or heats from slower entries to faster entries.

=== Fast to Slow ===

Orders sections or heats from faster entries to slower entries.

=== All Comer ===

Uses an all-comers approach rather than conventional performance seeding.

The exact operational effect may depend on later scheduling, check-in, and Clerk of Course procedures.

== Membership ==

=== Membership required ===

Indicates whether participants must hold membership in a specified organization.

==== Yes ====

Membership is required.

A membership organization should be selected or entered.

==== No ====

No organization membership is required by this setting.

The precise membership fields should be documented after confirming the current membership dialog and save behavior.

== Age verification ==

=== Age verification required ===

Indicates whether participant age must be verified by an approved organization or process.

==== Yes ====

Age verification is required.

An age-verification organization should be selected or entered.

==== No ====

No separate age-verification requirement is imposed by this setting.

The precise age-verification fields should be documented after confirming the current dialog and save behavior.

== Relationship between divisions and events ==

Selecting divisions and events establishes the meet-wide possibilities.

The gear configuration for a division may narrow those possibilities by defining which events and genders are offered for that division.

The resulting combinations are commonly described within Torunit as division-event-gender combinations.

A division does not necessarily offer every event selected for the meet.

== Navigation after setup ==

After Torunit creates the Meet ID, the Meet Director may proceed to the other meet-development pages.

The appropriate next page depends on the meet and the director's workflow. Information entered on Create Meet remains available for later review and correction.

== Current implementation notes ==

The following controls appear incomplete or require review in the supplied page version:

* '''I have a Meet ID''' has no visible attached action.
* '''Let me search''' has no visible attached action.
* '''Add another venue''' currently displays a notice rather than completing an additional-venue search.
* '''Include Legacy Events''' appears twice with the same internal identifier.
* Some custom division and custom event behavior requires confirmation against the live page.
* Membership and age-verification dialog details require confirmation before definitive documentation.
* Some settings may save correctly even where their downstream operational effect has not yet been completed.

These notes describe the current page version and should be removed or revised as the affected controls are completed.

== See also ==

* [[Meet Director]]
* [[Meet Director Home]]
* [[Venue]]
* [[Participants]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Micro/Daily Scheduler]]
* [[Registration]]
* [[Financials]]

[[Category:Meet Director]]
[[Category:Meet setup]]

About

2026-09-10T17:48:29Z

Trackinfo:

'''To Run It''' is an intended modernization of meet management technology. io It uses communication tools available through the internet to accomplish tasks in close to real time.

We have built a system where you can operate your entire meet from cel phones, pads and commonly available technology. This will probably stress these devices beyond their normal capacity without you taking measures to mitigate that. A phone being used continuously for hours is going to drain the battery and get hot. If a phone has issued with those problems already under normal use, under stress, continuous usage will amplify those problems. We wil suggest having external batteries (power banks), chargers and plans to use a back up device in place of a device having issues.

Being dependent on the internet, you will need good connectivity in your stadium or venue. If it is not available from local cel sites, we strongly recommend you supplement with service that effectively can deliver the data at the speeds you want.

As we say in the [[privacy policy]], we are user supported as opposed to being advertiser supported. Because we are working over the internet, we don't know who you are. Before we advertise a meet to the public and perform our functions, we need some assurance you are a legitimate operator. We will ask to put a substantial hold on a credit card. We hope that will discourage people from using our services with bad intent. The credit card hold will only be used to pay back the athletes who got screwed and our part in making for a bad experience. If you are a legitimate operator, at the end of the day, you get your deposit back. If we collect your entry fees, ultimately we will be sending you your own money back (minus our fees). If your meet has not entry fees, you might need to pay our fees directly to get your deposit back. If our deposit is too much of a financial hardship, you can introduce yourself and appeal the hold.

2027 is our beta test year. It's our learning process to see what we have been testing will do at scale. We are charging minimal rates. We want your feedback. If something doesn't seem right, if our "user interface" is awkward or confusing, tell us. We are a small company. We can't guarantee a direct response but your input is helping.

For the future, we hope to assemble a package of hardware to support what our software does. With WIFI repeaters, phones, batteries, cameras and display boards all coordinated to work with the system, it will be something you can rent for your meet then pack up and send to the next meetprinters, that needs it.

We do not know what our real rates will become yet, for the service or for the rental package, or how many packages we can assemble. We are still learning what all this implementation will take.

Privacy policy

2026-09-10T17:35:15Z

Trackinfo: Created page with "'''To Run It''' collects personal information necessary for sorting your data for track and field, running and walking events. We are supported by usage fees a Meet Director pays us and includes those fees as part of the entry fees you pay to participate in their meet. That means we are not advertiser supported. There are no advertiser links or data mining elements built into our code. What we embed in your device is necessary for our purposes to make your participa..."

'''To Run It''' collects personal information necessary for sorting your data for track and field, running and walking events. We are supported by usage fees a Meet Director pays us and includes those fees as part of the entry fees you pay to participate in their meet.

That means we are not advertiser supported. There are no advertiser links or data mining elements built into our code. What we embed in your device is necessary for our purposes to make your participation in one of these events as fulfilling as possible. You can control what communication we will send you.

At some point in the future we might create a section to direct you to advertising about products that might help you in your participation in one of our events. If such sections come into existence, we will keep it completely separated from the the operating code for the site and you will know you are entering such a section at your choice. The operating code will always remain clean of any external embeds.

About

2026-09-10T17:33:39Z

Trackinfo:

'''To Run It''' is an intended modernization of meet management technology. io It uses communication tools available through the internet to accomplish tasks in close to real time.

We have built a system where you can operate your entire meet from cel phones, pads and commonly available technology. This will probably stress these devices beyond their normal capacity without you taking measures to mitigate that. A phone being used continuously for hours is going to drain the battery and get hot. If a phone has issued with those problems already under normal use, under stress, continuous usage will amplify those problems. We wil suggest having external batteries (power banks), chargers and plans to use a back up device in place of a device having issues.

Being dependent on the internet, you will need good connectivity in your stadium or venue. If it is not available from local cel sites, we strongly recommend you supplement with service that effectively can deliver the data at the speeds you want.

As we say in the [[privacy policy]], we are user supported as opposed to being advertiser supported.

2027 is our beta test year. It's our learning process to see what we have been testing will do at scale. We are charging minimal rates. We want your feedback. If something doesn't seem right, if our "user interface" is awkward or confusing, tell us. We are a small company. We can't guarantee a direct response but your input is helping.

For the future, we hope to assemble a package of hardware to support what our software does. With WIFI repeaters, phones, batteries, cameras and display boards all coordinated to work with the system, it will be something you can rent for your meet then pack up and send to the next meetprinters, that needs it.

We do not know what our real rates will become yet, for the service or for the rental package, or how many packages we can assemble. We are still learning what all this implementation will take.

Privacy notice

2026-09-10T16:54:45Z

Trackinfo:

Privacy notice

2026-09-10T12:15:02Z

Trackinfo:

Privacy notice

2026-09-10T12:12:34Z

Trackinfo:

'''To Run It''' collects personal information necessary for sorting your data for track and field, running and walking events. We are supported by usage fees a Meet Director pays us and includes those fees as part of the entry fees you pay to participate in their meet. That means we are not advertiser supported. There are no advertiser links or data mining elements built into our code. What we embed in your device is necessary for our purposes to make your participation in one of these events as fulfilling as possible. You can control what communication we will send you.

At some point in the future we might create a section to direct you to advertising about products that might help you in your participation in one of our events. If such sections come into existence, we will keep it completely separated from the the operating code for the site and you will know you are entering such a section at your choice.

Privacy notice

2026-09-10T12:06:17Z

About

2026-09-10T11:57:44Z

Trackinfo: Created page with "'''To Run It''' is an intended modernization of meet management technology. io It uses communication tools available through the internet to accomplish tasks in close to real time. Being dependent on the internet, you will need good connectivity in your stadium or venue. If it is not available from local cel sites, we strongly recommend you supplement with service that effectively can deliver the data at the speeds you want."

'''To Run It''' is an intended modernization of meet management technology. io It uses communication tools available through the internet to accomplish tasks in close to real time. Being dependent on the internet, you will need good connectivity in your stadium or venue. If it is not available from local cel sites, we strongly recommend you supplement with service that effectively can deliver the data at the speeds you want.

Participants

2026-09-09T22:54:07Z

Trackinfo: /* Who should use this page? */

{{DISPLAYTITLE:Participants}}

The '''Participants''' page records the number of athletes the Meet Director expects to enter each '''GDE''' gender, division, and event 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. On meet day, your '''COC''' Clerk of the Course will deal with actual heats based on the athletes who actually check in.

== Who should use this page? ==

The Participants page is primarily intended for one-day meet scheduling with no rounds, your most common meet format.

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.

You will also use this page to set your size limits.

== 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:

<code>2 = prelim + final</code>

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:

<code>2 Q</code>

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:

<code>8</code>

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.
* <code>participants.blade.php</code> contains its own inlined event-block renderer while <code>participants/_event-block.blade.php</code> 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.

== See also ==

* [[Create Meet]]
* [[Venue]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]

[[Category:Meet Director]]
[[Category:Schedule]]
[[Category:Meet planning]]

Participants

2026-09-09T22:52:27Z

Trackinfo: /* Who should use this page? */

{{DISPLAYTITLE:Participants}}

The '''Participants''' page records the number of athletes the Meet Director expects to enter each '''GDE''' gender, division, and event 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. On meet day, your '''COC''' Clerk of the Course will deal with actual heats based on the athletes who actually check in.

== Who should use this page? ==

The Participants page is primarily intended for one-day meet scheduling with no rounds, your most common meet format.

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:

<code>2 = prelim + final</code>

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:

<code>2 Q</code>

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:

<code>8</code>

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.
* <code>participants.blade.php</code> contains its own inlined event-block renderer while <code>participants/_event-block.blade.php</code> 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.

== See also ==

* [[Create Meet]]
* [[Venue]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]

[[Category:Meet Director]]
[[Category:Schedule]]
[[Category:Meet planning]]

Participants

2026-09-09T22:28:49Z

Trackinfo:

{{DISPLAYTITLE:Participants}}

The '''Participants''' page records the number of athletes the Meet Director expects to enter each '''GDE''' gender, division, and event 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. On meet day, your '''COC''' Clerk of the Course will deal with actual heats based on the athletes who actually check in.

== 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:

<code>2 = prelim + final</code>

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:

<code>2 Q</code>

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:

<code>8</code>

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.
* <code>participants.blade.php</code> contains its own inlined event-block renderer while <code>participants/_event-block.blade.php</code> 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.

== See also ==

* [[Create Meet]]
* [[Venue]]
* [[Rounds]]
* [[Schedule]]
* [[Macro Scheduler]]

[[Category:Meet Director]]
[[Category:Schedule]]
[[Category:Meet planning]]