How to keep a useful field-event practice log

Record the context before the first mark

A useful field-event practice log lets another coach reconstruct the session without asking the person who held the clipboard. Start with the date, event, group, responsible coach, and intended exercise. For throws, include the implement weight and the unit used for measurements. If the implement changes, record the change before entering another attempt.

Keep the exercise description separate from the measured outcome. The description explains what the coach planned; the attempt row records what happened. A list containing only each athlete’s best distance loses the order of the attempts, the unsuccessful attempts, and the context behind that best.

Choose a recording unit before practice and display it in the heading. A bare value such as 14.20 becomes ambiguous when coaches later combine a paper sheet, a phone note, and a meet export.

Use one row for each recorded attempt

For a paper or spreadsheet version, add columns for the session date, event, exercise, implement weight, recorder, and a short note. You can put shared context in the sheet header when it truly applies to every row. If a coach hands the sheet to someone else, the new recorder should be able to identify both the athlete and the next row.

The row numbers above describe a practice log. They do not determine competition attempt allowances or how an organizer administers a meet. Keep the organizer’s competition records and your practice capture process separate.

Keep a foul, a pass, and a missing entry distinct

Record an unsuccessful measured-event attempt as a foul when that is the outcome the coach is recording. Record a pass when the athlete did not take that attempt. Leave an unrecorded attempt unresolved until someone checks it. These choices should not all appear as zero metres, because zero hides the reason no mark is present.

• Measured mark: store the value with its unit and implement context.
• Foul: preserve the attempt’s place in the session without inventing a valid mark.
• Pass: record the explicit decision to pass without attaching a successful distance.
• Missing entry: ask the recorder what happened before assigning an outcome.

Agree on these labels with the staff at the start of the session. If the wrong label is entered, correct that entry rather than adding a second row that makes one attempt look like two.

Write notes the next coach can use

Use notes for context that changes the interpretation of the record. Examples include a different implement, a change in the planned exercise, an interrupted recording sequence, or a value that still needs confirmation. Keep a coach’s chosen cue in its own short field when available, so the measured result remains easy to scan.

Avoid using an attempt note as a general athlete file. Personal information that is unrelated to the recorded exercise makes the log harder to review and easier to share accidentally. When a note says that a mark needs checking, include who will check it and which source or recorder they should consult.

At a handoff, tell the next coach which athlete and attempt come next. A useful handoff sounds like: “Sample Athlete has three entries saved; the fourth attempt is next, and the implement is unchanged.”

Check the device before and after the session

Open the correct workout while connected before moving to an area with unreliable signal. Confirm the account, assigned athletes, exercise, and shared implement setting. A saved offline board can help continue a session that the device has already opened; it cannot retrieve a new workout that was never loaded.

• Before practice: open the session and verify the athlete list and exercise.
• During practice: watch the device’s saved and queued states, and keep uncertain entries visible for review.
• After reconnecting: keep or reopen the Practice board in the same browser and account to retry queued results. Resolve rejected entries before marking the session complete.
• Before changing devices: check that the first device has no remaining unsynced results.

Do not clear browser storage while results are pending. Ordinary sign-out keeps the account-scoped outbox on that device; sign back into the same account to recover it. If a session was completed before a device synced, an authorized coach can use the confirmed Reopen action to accept pending results, then review and complete the session again.

Review comparable marks in Track Command

Track Command’s practice board presents athletes and their attempts together, with measured marks, foul and pass outcomes, and implement context for throws. Set the shared context for the exercise, enter each athlete’s result, and review the recent entries while the session is still fresh. Use the single-entry workflow when a result needs more detail or correction; those manual forms and edits require a connection. The board’s saved captures use the device queue.

Compare like with like during the review. A practice-best indicator points to a result worth checking; the label alone does not establish that the implement, exercise, or recording conditions match a previous session. Keep practice bests separate from competition PRs and retain the context when discussing either.

Finish with a short reconciliation: each athlete has the intended entries, obvious duplicates are resolved, outcomes are understandable, and the outbox is clear. If an entry remains uncertain, assign a follow-up instead of quietly promoting it to the program’s best-mark list.