Track CommandStart by identifying the kind of record
A jumps log should make it clear whether the entry describes a horizontal-jump mark, a bar-height attempt, or a competition result. Those records answer different questions. A coach reviewing a long-jump exercise needs the measured distance and exercise context; a coach reviewing a vault session needs to see the height and outcome of each recorded attempt.
Put the date, event, exercise, athlete, and responsible coach in the session context. Choose units before recording begins. Keep the exercise description alongside the attempts so a mark from one kind of practice is not compared casually with a different exercise.
This guide is a recording template. The coach remains responsible for the session plan and technical instructions; the fields below do not prescribe an approach, bar progression, pole choice, or competition procedure.
Keep horizontal-jump attempts in order
For long jump or triple jump practice, keep one entry per recorded attempt. Store a successful distance with its unit, and preserve a foul or pass as its own outcome. If wind is recorded, keep the actual reading and its context. An unknown reading should remain unknown; entering zero would assert something that was not measured.
| Attempt | Outcome | Mark | Context |
|---|---|---|---|
| 1 | Measured | 5.42 m | Named practice exercise; wind not recorded |
| 2 | Foul | — | Same exercise |
| 3 | Pass | — | No jump recorded |
| 4 | Measured | 5.51 m | Same exercise; recorder checked the value |
Additional fields such as approach steps or a takeoff note can help the responsible coach interpret the exercise. Use them when they are part of your recording process. Adding every possible field to every attempt can make the essential athlete, outcome, and mark harder to capture correctly.
Preserve bar height with every clearance, miss, or pass
For high jump and pole vault, a sequence of outcome symbols is incomplete without the height attached to it. Set the current height carefully, check it when the bar changes, and keep it on each saved entry. A later reviewer should not need to guess which attempts belong to which height.
| Recorded entry | Bar height | Outcome | Review note |
|---|---|---|---|
| 1 | 3.40 m | Clearance | Height recorded with this attempt |
| 2 | 3.50 m | Miss | No clearance recorded |
| 3 | 3.50 m | Pass | Explicit pass; not a miss |
| 4 | 3.50 m | Clearance | Check the athlete and height before saving |
In a practice log, pass and miss communicate different events. Do not convert either into a zero-height result. If an entry was assigned to the wrong athlete or height, correct that entry while the recorder can still confirm what happened.
Vault-specific context can include grip height, pole length, and standards position when the coach chooses to record them. These are descriptive fields, not equipment recommendations. Retain the units and avoid copying a previous athlete’s context without checking it.
Separate practice bests from competition results
A practice clearance or distance belongs in the training record. A competition mark belongs with its meet, event, date, status, and source. Keeping those histories distinct lets a coach discuss progress without implying that a practice mark was achieved at a meet.
- Label practice marks as practice whenever they appear outside the session log.
- For a competition result, retain the meet name, result date, event, unit, and outcome supplied by the source.
- Keep wind or other result context when available; do not manufacture missing values.
- Check the organizer’s result record before using a mark in an external profile or application.
A software PR label summarizes the records available to that software. It is not a governing body’s ratification or a guarantee that a result meets a particular recruiting, ranking, or entry requirement. Check the relevant destination’s current requirements separately when preparing a submission.
Review the sequence before closing the session
Review by athlete and exercise while the coach who recorded the attempts is available. Look for a duplicated entry, an unexpected height change, a pass recorded as a miss, or a successful mark attached to the wrong person. Ask about the source before making a plausible-looking correction.
For practice data, repair the affected entry instead of creating a second successful result. For a competition record, preserve the correction reason and compare the revised mark with the source. After any correction, check the athlete’s displayed bests and any profile or packet that relies on that result.
If two devices were used, reconcile their saved records and queued entries before calling the session complete. A completed screen on one device does not prove that another device has synced its offline attempts.
Use the log in Track Command
Track Command’s field practice board supports measured jumps and vertical-event outcomes, including distinct passes. The shared bar-height setting helps record the current exercise; detailed single-entry fields can preserve additional jumps or vault context while connected. Manual forms and corrections require a connection; the supported practice-board captures use the device queue. Check the height and athlete before each save, especially after switching exercises.
Open the assigned workout while connected before relying on the saved board offline. After reconnecting, keep or reopen the Practice board in the same browser and account to retry queued entries, then resolve any rejected save. Authorized coaches can reopen a completed session, with confirmation, when pending device results still need to be accepted.
Recruiting profiles can include competition results and, when deliberately selected, practice bests. Review those inclusion choices before sharing. A practice mark should remain visibly identified as practice, with enough context for the recipient to understand it.