A meet-week checklist for entries, relays, and results

Create one meet brief with named owners

Start meet week with the organizer’s current information: venue, date, arrival expectations, event schedule, entry deadline, submission method, and contact for corrections. Save the source link or document reference beside the brief. Assign someone to check for updates rather than assuming the version forwarded last week is still current.

Distinguish your team’s plan from the organizer’s accepted entries. A proposed entry, a submitted entry, and an entry visible on the organizer’s final list are separate states in your workflow. Give each state a person responsible for checking it.

Review entries as a team decision

Ask event coaches for proposed entries in a consistent format: athlete, event, seed mark, source of the seed, and any question requiring review. Check athlete identity against the current roster. Similar names and reused spreadsheets deserve a second look before a deadline makes them harder to untangle.

• Confirm the intended event and team division with the organizer’s event list.
• Check that the seed belongs to the athlete and that its unit and source are clear.
• Review schedule conflicts and resolve the team’s proposed changes with the relevant coaches.
• Check the organizer’s current entry limits and acceptance requirements directly.
• Have the designated person submit entries through the organizer’s required service.

After submission, compare the returned entry list with your reviewed plan. Record what was accepted and what remains unresolved. A confirmation email is useful, but the actual accepted athlete/event list is the record that tells staff what to expect.

Keep relay lineups and alternates explicit

Write the relay event, team label, intended running order, and named alternates in one place. A list of four athletes without an order or a team label leaves room for misunderstanding when a program has more than one entry.

Assign one coach to maintain the final lineup. If another coach proposes a change, confirm it with that person and update the shared record. Track who has been told and whether the organizer requires a separate declaration or change request. Follow the organizer’s process; an internal lineup edit is not an external declaration.

• Identify which event and team label the lineup belongs to.
• Check the four intended athletes and their order.
• Name alternates and the coach who makes the final call.
• Confirm the current declaration or change deadline with the organizer.
• Communicate an agreed change to affected athletes and staff.

Make the meet-day handoffs easy to follow

Give each staff member a short assignment for the day: event group, check-in responsibility, location, and who covers a conflict. Include a contact route for a missing athlete or a schedule change. The aim is to make an exception find the right person quickly.

Treat check-in as a recorded observation. Decide whether your team’s check-in field means “reported to our coach” or “confirmed through the organizer’s process,” then use that meaning consistently. An athlete appearing on a team list does not prove that every required meet check-in step is complete.

Keep a small exceptions list for changed entries, lineup revisions, uncertain results, and issues that need follow-up. Record who is handling each item. Avoid rewriting the whole meet plan every time one detail changes; update the affected record and tell the people whose work depends on it.

Reconcile results against their source

When results are available, retain the source and review athlete matches, event names, dates, units, and result status before importing. A blank mark, DNS, DNF, disqualification, and no mark should not become successful zero-valued performances. Preserve the source’s meaning and investigate ambiguous rows.

For timed events, keep the timing method when known. For events with wind information, retain the supplied reading; unknown wind is not zero wind. Check any place or score against the source instead of deriving a confident-looking value from an incomplete excerpt.

• Preview imported rows and resolve unmatched athletes or events.
• Check for an existing result before creating another copy.
• Compare unusually large changes with the original result record.
• Use a correction with a reason when a saved result is wrong.
• Review affected PR displays, qualifying-standard comparisons, and recruiting selections after corrections.

A coach-reviewed import is still a copy of a source result. Track Command does not certify a performance as official or automatically submit corrections to an organizer or federation. Send external corrections through the channel the organizer specifies.

Use Track Command for the team’s working record

Create the meet and maintain athlete entries, seed information, and check-in status in the team workspace. The relay tools support 4×100 and 4×400 lineups with running order and alternates. Keep the organizer’s submission confirmation in your meet-week process alongside those internal records.

Use results import to review athlete and event matching before saving. Competition-result corrections retain a reason and revision history so the staff can understand a changed record. Check the final result display after saving, particularly when a correction changes the athlete’s best.

Configured qualifying standards help the program compare its recorded results with the standards it has entered. Verify the standard, applicable conditions, and source when it matters for a real entry decision. A comparison in the app does not replace an organizer’s acceptance decision.

Close the meet with a short exceptions review

End with three questions: are the accepted entries and lineups accounted for, are the results reconciled, and does every remaining question have an owner? Keep unresolved items visible until they are checked.

Before the next meet, carry forward the useful process changes: a missing contact, a clearer relay label, or an earlier review point. Preserve the completed meet’s history rather than turning its entries into the next meet’s working document.