Define what each number means
Keep planned distance and recorded distance separate. Planned distance describes the assignment. Recorded distance describes what the athlete or coach entered after the session. If your tool substitutes the prescribed distance when actual distance is missing, that total includes an assumption. Label and review it accordingly.
Decide what a session entry includes. Does the reported distance cover warm-up and cooldown? Are additional runs logged separately? Write the convention where athletes can find it, then apply it consistently. Otherwise one athlete may enter the whole practice while another enters only the main work.
Use one unit when comparing totals, even if athletes enter miles or kilometers. Keep dates attached to individual sessions, and agree which week you are reviewing. A late entry should retain the date of the run so you can distinguish a record correction from new work.
Reconcile a week before interpreting the total
This illustrative worksheet uses invented distances to demonstrate record keeping. It does not prescribe mileage or a rate of progression. Copy the columns into your existing log and add one row per session.
Scroll the table horizontally to see the record-check column.
| Session | Assigned | Recorded | Record check |
|---|---|---|---|
| Monday practice | 4.0 mi | 3.6 mi actual | Coach confirmed the shortened route |
| Tuesday practice | Timed run | Distance unknown | Keep duration; do not invent distance |
| Thursday practice | 3.0 mi | 3.0 mi from assignment | Actual distance still needs confirmation |
| Saturday outside run | No team assignment | 2.0 mi logged | Check it is not also in a workout report |
The numeric entries total 8.6 miles, but only 5.6 miles are explicitly recorded as actual in this example. Another session has unknown distance. Calling 8.6 a complete measured total would conceal both gaps. You can still use the log while keeping those qualifications visible.
Add an owner to each unresolved row: athlete, recording coach, or reviewer. A generic “needs checking” label often survives into the next week because nobody knows who should resolve it.
Use the same short routine after each session
- Identify the session. Match the athlete, date, and assignment before entering a result.
- Record the outcome. Enter actual distance and duration when available. Add a factual note if the assignment changed.
- Separate extra runs. Log work outside the assigned session once, using its own date and distance.
- Confirm the save. Check the visible record or pending-sync status before closing the device.
Agree who records coached practice and who records outside runs. If both athlete and coach enter the same session independently, establish a reconciliation step. Two valid-looking entries can still describe one run.
Keep notes concise: “Route shortened at the closed gate” explains a discrepancy. Sensitive details are unnecessary in a shared mileage log. Use your program's approved process for conversations that require more privacy.
Review missing data before comparing weeks
Start with unresolved sessions, unconfirmed saves, and possible duplicates. Then compare the same athletes over the same date boundaries. A change in the roster can change a team total even when no returning athlete changed their activity.
Ask three practical questions: Which assignments have actual distance? Which rely on the prescribed value? Which outside runs are included? If an answer is unclear, fix the record or carry the uncertainty into your discussion.
Goals and limits should reflect the coach's plan for that athlete. A mileage log does not establish a universal safe weekly amount or an automatic progression rule. A percentage change can direct you to inspect a week; it cannot tell you why the change happened or what the athlete should do next.
Use the review to decide a concrete follow-up, such as clarifying whether cooldown is included, correcting a date, or confirming an outside run. For a broader conversation, use the athlete progress review worksheet.
Keep unknown distance visible
Some assignments are based on time, and some runs have no reliable distance record. Preserve the duration you do know. Avoid converting it into mileage from an assumed pace simply to fill a chart.
Likewise, an unfinished or missing log is not proof that a runner did no activity. Ask for the missing context. A completed status is not proof that every prescribed meter was covered either. These are record states that need an agreed reporting process.
When changing software, test this distinction with one distance-based workout, one time-based workout, and one outside run. Inspect both the individual entries and the weekly total. The spreadsheet comparison can help you decide whether your current workflow already handles these checks well.
How PaceCommand calculates mileage
PaceCommand offers athlete-specific mileage tracking, coach-set weekly goals and limits, completed workout reports, and manual outside-run logging. Weekly summaries combine completed assigned workouts with outside runs. For an assigned workout, actual distance takes precedence; when it is blank, the total uses the prescribed distance from the workout's distance-based parts.
That fallback is useful to understand before relying on a total. A completed workout with changed volume needs an actual-distance report. A duration-only part does not become measured mileage automatically. Avoid recording the same assigned session again as an outside run.
The worksheet above is a reconciliation aid, not a claim that PaceCommand displays each of its columns as a separate report. Complete mileage reports and outside-run entries while connected. The offline practice checklist explains which practice changes can wait in the device queue.