Agree on the decision before collection

Begin the day with a question that somebody can act on. “Monitor the squad” is too broad. “Check whether players with limited match minutes receive the planned high-speed exposure” is specific enough to guide collection, analysis and discussion. Name the person responsible for the decision and distinguish that role from the person checking data quality.

Choose a small set of measures that directly serve the question. Adding another metric should require a reason, a quality check and a clear interpretation. If nobody can explain what would change in response to the value, it may not belong in the daily report. Keep exploratory analysis separate from the operational summary.

Prepare the equipment and the athlete

Assign units consistently, check charging and storage, and confirm that the intended recording mode is active. Inspect vest fit or attachment and follow the device’s operating instructions. For systems requiring venue setup, allow time for calibration and coverage checks. Document the device identifier so that a suspicious pattern can be traced back to the correct unit.

Tell athletes what is being collected, why it matters and who can access it. A monitoring programme works better when the athlete understands the purpose rather than experiencing equipment as surveillance. Offer a clear route for questions and corrections. A practical briefing is not a substitute for the organisation’s legal obligations or appropriate privacy information.

Source notes: The IFAB’s rules on players’ equipment and World Rugby’s equipment resources show why competition-specific requirements must be checked. Permission in one sport or setting does not establish permission in another.

Annotate the session while it still makes sense

Record drill boundaries, work and rest periods, changes in playing area, substitutions and unusual interruptions. A total distance figure cannot later reconstruct whether an athlete spent part of the session coaching, receiving treatment or waiting for a drill to restart. Context recorded at the time is usually more dependable than memory during a busy afternoon.

Keep observations factual. Write “left the drill after reporting calf discomfort” rather than assigning a diagnosis. Health information should be handled through appropriate clinical and privacy processes, not added casually to a broadly shared spreadsheet. Capture only what the monitoring task needs and direct clinical assessment to qualified staff.

Performance staff member listening to an athlete during a trackside session debrief
Debrief note: ask what felt different before explaining what the dashboard appears to show.

Run a quality gate before calculating conclusions

Check athlete identity, recording completeness, session timing and implausible trace segments. Establish a written rule for excluding or flagging unusable data. Missing data should remain visibly missing; replacing an absent recording with zero makes a technical problem look like no training. If an estimate is necessary, label the method and uncertainty.

Inspect raw or less-processed traces when a summary looks unusual and the platform makes them available. Compare anomalies with known drill events or video where appropriate. Keep a concise quality log so recurring faults can be distinguished from athlete-specific changes. A report that arrives slightly later with a clear quality status is more useful than an immediate but misleading ranking.

Use a three-part staff-room summary

Separate observation, interpretation and action. The observation states what was recorded and whether the data passed checks. The interpretation explains plausible reasons in light of the session plan and athlete feedback. The action names what will happen next, who owns it and when it will be reviewed. Keep uncertainty in all three parts where it matters.

A compact decision record
PartUseful wording
ObservationRecorded running exposure was lower than planned; the session trace passed the agreed checks.
InterpretationA changed drill role appears relevant. The athlete reported normal effort and no new concern.
ActionThe coach and physical-preparation lead will review whether additional exposure fits the remaining programme.
ReviewRecord what was completed and revisit the intended stimulus at the next planning discussion.

Do not allow a traffic-light colour to stand in for this reasoning. A red flag can mean a technical fault, an unusual exposure or a possible health concern. Those require very different responses. The report should tell the reader what kind of flag it is and what they are expected to do.

Protect access and keep a retention plan

Limit identifiable athlete information to people with a legitimate role. Use appropriate account controls, review access when staff leave and avoid unnecessary copies in messaging applications. Agree how long different records are needed, how they will be deleted and how athletes can raise a concern. Supplier contracts and export options deserve review before a system becomes operationally indispensable.

Source notes: the UK Information Commissioner’s Office and European Data Protection Board provide data-protection guidance. Health-related information may need additional safeguards. Obtain advice appropriate to your jurisdiction and circumstances.

Audit the workflow, not only the athlete

Review which measures influenced decisions and which merely consumed time. Track recurring quality problems, unexplained missingness and situations where the report disagreed with practical observation. Invite athletes and coaches to describe where the process helps or gets in the way. A monitoring workflow should improve through feedback just as a training programme does.

Finally, check the consequences of decisions. Did the modification achieve the intended exposure? Did the athlete understand the rationale? Was a concern escalated appropriately? A sound process does not guarantee a perfect outcome, but it leaves a transparent record from which staff can learn without pretending that the sensor supplied certainty.

Keep the discussion open

Still unsure what a reading means?

Our FAQ addresses the recurring questions that sit between a sensor trace and a training decision.

Visit the field FAQ ↗