View source for Create-Meet

{{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 participants.

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.

=== Public phone ===

The telephone number displayed or used for public meet inquiries.

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

=== 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 formats could save a lot of time, or duplicate the same mistakes over and over.

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

Intended for copying from a known meet when its Meet ID is available.

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

==== Let me search ====

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 high school dual-scoring meet
* Open all-comers meet with rolling schedule

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

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. The bus and parking pins identify distinct arrival locations that maps can guide people to.

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

=== Add another venue ===

Intended to attach another facility or course to the meet.

'''Current status:''' The current control displays a notice that additional venue/course search will use the map picker, but the additional-location workflow is not yet connected.

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

=== Available divisions ===

The left list contains divisions available for selection.

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

Opens configuration for one division.

A division with a reduced event list may appear with a yellow tint, indicating that its event offering differs from the full meet event list.

=== New division name ===

Enter the name of a division not already available in Torunit.

=== Define… ===

Opens the custom division parameters before adding the new division.

A custom division may be defined with:

* Minimum Age
* Maximum Age

The name must be entered before the Define button is used.

=== Add Custom ===

Adds the typed custom division to the meet.

If division parameters are needed, use '''Define…''' before or in conjunction with adding the division.

== Events ==

The Events section defines the events offered by the meet.

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

=== Available events ===

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.

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

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

Shows older event definitions that are normally hidden from the available-event list.

Use this only when the meet requires an event retained for compatibility with older Torunit data or an earlier event definition.

'''Current-page note:''' The supplied page markup contains the Include Legacy Events control twice with the same internal identifier. This may create unpredictable behavior and should be reviewed.

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

== Meet configuration ==

=== Meet format ===

Controls who may submit entries.

==== Open ====

Allows public entry according to the meet's registration and eligibility rules.

An open meet is not necessarily unrestricted. Membership, age verification, entry limits, qualifying marks, deadlines, and fees may still apply.

==== Closed ====

Restricts entry to invited teams.

Selecting Closed displays the '''Invite teams''' field.

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

More than one decision method may currently be selected.

=== Environment ===

Identifies the competition environment.

==== Outdoor ====

A conventional outdoor track-and-field meet.

==== Indoor ====

An indoor track-and-field meet.

==== XC ====

A cross-country meet.

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

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