13.4 Training Records, Documentation & Program Data Management
Key Takeaways
- Records serve three distinct purposes - programming decisions, legal defensibility, and demonstrating program value - and a record that serves only one of them is usually incomplete.
- A usable session log captures prescribed load and volume, completed load and volume, and the reason for any deviation, because the deviation is the data a facilitator most needs.
- Incident reports must be written the same day, restricted to observed fact, and must never contain a diagnosis or an admission of fault.
- Test records are only comparable when the conditions are recorded alongside the score: equipment, surface, environmental readings, time of day, and tester identity.
- The documentation standard is simple: if an activity is not written down, a facilitator cannot demonstrate later that it happened, which is why screening, consent, supervision, and maintenance records carry disproportionate legal weight.
13.4 Training Records, Documentation & Program Data Management
Quick Summary: The blueprint requires a facilitator to maintain appropriate training records. This section specifies what records a tactical program must actually generate - session logs, test archives, attendance, screening files, incident reports, equipment logs - how each one is used operationally, and the documentation habits that make a program defensible.
Three Reasons Records Exist
Most facilitators keep records for one reason and are then surprised when the records fail at the other two.
- Programming. Without a record of what was prescribed and what was completed, progression is guesswork and workload monitoring is impossible.
- Legal defensibility. In a negligence claim, the question is whether the facilitator met the standard of care. Screening, consent, supervision, instruction, and maintenance records are the evidence. An undocumented screen is, for practical purposes, a screen that did not happen.
- Demonstrating value. Agency budgets are defended with data. Injury rates, test pass rates, and lost-duty days come out of records that someone had to keep prospectively.
A record designed only for programming often lacks the tester identity and environmental conditions that make it legally useful. A record designed only for compliance often lacks the load and volume detail that makes it operationally useful. Design for all three at once.
The Record Set a Tactical Program Needs
| Record | Minimum contents | Primary use |
|---|---|---|
| Pre-participation screening file | Completed PAR-Q+ or agency screen, medical clearance where triggered, date, reviewer | Clearance decision; legal defensibility |
| Informed consent / waiver | Signed, dated, version-identified document | Legal defensibility |
| Session log | Date, session ID, prescribed load and volume, completed load and volume, deviation reason, session RPE | Progression, workload monitoring |
| Attendance log | Personnel present, personnel absent, reason where known | Adherence analysis; programme reach metrics |
| Assessment / test archive | Raw scores, test conditions, equipment, environmental readings, tester identity, protocol version | Trend analysis; standards compliance |
| Injury and incident report | Date, time, location, observed facts, actions taken, witnesses, notifications made | Legal defensibility; injury surveillance |
| Equipment inspection and maintenance log | Item, inspection date, findings, action taken, out-of-service tags issued, inspector | Legal defensibility; capital planning |
| Emergency action plan review log | Rehearsal date, participants, deficiencies identified, corrections | Legal defensibility; readiness |
| Programme documents | Dated mesocycle plans and revisions | Demonstrating deliberate design rather than improvisation |
Session Logs: Record the Deviation, Not Just the Prescription
A log that records only what was written is nearly useless. The high-value entry is the gap between prescription and execution.
| Field | Example | Why it matters |
|---|---|---|
| Prescribed | Trap bar deadlift 4 x 5 @ 275 lb | The plan |
| Completed | 3 x 5 @ 275 lb, fourth set cut | The reality |
| Deviation reason | Structure fire callout at minute 34 | Distinguishes a programming error from an operational interruption |
| Session RPE | 7 | Enables internal workload and acute-to-chronic ratio calculation |
Without the deviation reason, a facilitator reviewing four weeks of incomplete sessions cannot tell whether the program is too long, the operator is unmotivated, or the station is simply busy - and those three problems have three different solutions.
Test Records: The Score Is Not the Record
A fitness test result is only comparable to a previous result if the conditions match, so the conditions are part of the record.
Record alongside every score:
- Protocol version used, since agencies revise batteries.
- Equipment - which sled, which kettlebells, which surface.
- Environmental readings - temperature and, for outdoor testing, wet bulb globe temperature.
- Time of day and time since last shift, since a post-night-shift test is not comparable to a rested morning test.
- Tester identity, since inter-tester reliability on skinfolds, taping, and repetition counting is the dominant error source.
A 1.5-mile run time recorded without noting an 88-degree wet bulb globe temperature reading will be misread as a fitness decline the following spring.
Incident Reports: Same Day, Fact Only
Incident documentation is the record most likely to be read by a lawyer and the one most often written badly.
| Do | Do not |
|---|---|
| Write it the same day, while recollection is accurate | Wait until the end of the week |
| Record what you observed and what you did | Record what you assume happened |
| Use neutral descriptive language: "reported sharp right knee pain after the third repetition" | Diagnose: "tore his meniscus" |
| Note the time, location, witnesses, and every notification made | Speculate about fault, yours or anyone's |
| Record the exact instruction and supervision provided | Add opinions about the athlete's judgment |
| Store it per agency policy and confidentiality rules | Discuss it with uninvolved personnel |
Two specific cautions. First, never write a diagnosis - it is outside the scope of practice and a documented diagnosis by an unqualified provider is itself evidence of practising beyond scope. Second, never write an admission of fault; record facts and let the investigation reach conclusions.
Practical Data Management
- One system, consistently used. A partially adopted digital platform plus a partially maintained paper folder produces two incomplete records.
- Enter data at the point of collection. Reconstruction at the end of the week produces errors and omissions.
- Separate performance data from medical data. Test scores can reasonably be shared with a commander; screening forms and injury reports cannot be posted or circulated.
- Never post identifiable health information. A public leaderboard combining names with medical restrictions is a confidentiality breach even outside a strict HIPAA environment.
- Back up digital records on agency-approved encrypted storage, never on a personal device.
- Follow the agency retention schedule. Retention duration, storage security, and disposal are covered with the legal and ethical material later in this chapter; the point here is that the retention schedule governs, not the facilitator's preference.
Reviewing four weeks of session logs, a TSAC-F finds that a fire crew completed only about 60% of prescribed training volume. The logs record prescribed and completed sets and loads but nothing else. What critical piece of information is missing, and why does it matter?
An operator reports sudden posterior thigh pain during a sled drag and stops. Which incident report entry is professionally and legally appropriate?