Fatigue is one of the few hazards that reports on itself — if you let it. It is also the one where the reporting rate says more about the organisation's culture than about the actual level of the hazard. A low fatigue report count is not good news. It is usually no news at all.
The form is the message
People read a form as a statement of what the organisation expects. Small wording choices carry more weight than any amount of policy text elsewhere.
- "Why were you fatigued?" asks the reporter to account for themselves. "What in the roster or the operation contributed?" asks about the system. Same information; entirely different implication.
- Free text before checkboxes tells people their situation is what matters. Checkboxes first tell them they are being categorised.
- Required fields are a statement about what you consider essential. A mandatory field the reporter cannot answer honestly turns the whole form into an obstacle.
- The word "incident" anywhere on a fatigue form raises the stakes. Fatigue is usually a condition, not an event.
None of this is manipulation. It is removing the accidental signals that suggest a report will be read as an admission.
What happens next matters more
The single strongest predictor of whether someone files a second report is what happened after the first one. Not whether the problem was solved — people are realistic about rosters — but whether they were told anything at all.
Feedback is not a courtesy. It is the mechanism that keeps the reporting system alive.
A short, specific reply — this is what we found, this is what we changed, or this is why we could not change it — costs a few minutes and does more for reporting rates than any awareness campaign. Silence teaches the opposite lesson very efficiently.
Reading fatigue data without over-reading it
Individual fatigue reports are weak evidence about individuals and strong evidence about patterns. The useful analysis is aggregate: which pairings, which rotations, which times of day, which combinations of duty and standby recur across many reports.
One report from one crew member on one difficult night tells you very little. Fourteen reports clustering around the same rotation tells you something you can act on — and can defend to whoever has to approve the roster change.
Two questions worth asking your safety office
How many fatigue reports did we receive last quarter, and how many of those reporters received an individual response? If the second number is much smaller than the first, that is the thing to fix before touching anything else.
The uncomfortable part
A reporting system that works will surface things you would rather not know, including patterns that point at commercial decisions. That is the point. An organisation that only receives comfortable reports has not built a reporting culture — it has built a filter, and the filter is the fear of what happens next.
If fatigue is affecting your wellbeing beyond the operational context, your organisation's occupational health provider or peer support programme is the right place to start — those conversations sit outside the reporting system entirely.
Want to look at your own reporting form together? Book a demo and we'll walk through it with your own setup.