Published: 26 March 2026
You've installed real-time fatigue monitoring. The technology works. You're getting alerts. Now what?
Most operations stop at detection. They have clear protocols for what to do when someone triggers an immediate intervention alarm during a shift, but no structured process for what happens when the same person triggers alarms repeatedly across multiple shifts. That's where detection without process creates more problems than it solves.
If you identify that someone is chronically at risk but don't have a clear path to help them figure out why and address it, you've just created a documented problem with no solution. Worse, you've created fear in your workforce that being identified means being targeted.
Building an effective assistance process requires thinking through privacy, communication, roles and responsibilities, and what actually happens at each stage. Here's how to do that.
Start with clear identification criteria
You need objective criteria for when someone moves from normal variability into "this person needs assistance" territory. Arbitrary or inconsistent triggers undermine trust in the whole system.
One approach that works: define a Higher Alarm Rate Individual (HARI) as anyone who meets one or more of these criteria:
- Three or more escalation/intervention alarms on three or more shifts within a rotation or week
- Repeated self-reporting to supervisors that they're regularly struggling with fatigue
- Supervisor assessment based on operator behaviour, incident history, fatigue monitoring data, and other risk factors
Notice that this doesn't rely solely on monitoring technology. An operator who's telling their supervisor they're struggling should trigger the assistance process even if they haven't hit the alarm threshold yet. A supervisor who's concerned based on pattern recognition should be able to initiate support even if the data alone wouldn't trigger it.
The criteria should be reviewed regularly. If you're identifying too many people for your support capacity to handle, your thresholds might be too sensitive. If you're not identifying people who clearly need help, they might be too high.
Privacy isn't optional
The causes of chronic fatigue often involve medical conditions, mental health, personal circumstances, and lifestyle factors that are nobody else's business. If operators think their private health information is going to be shared with their supervisor or discussed in safety meetings, they won't engage with your process.
This means your process needs explicit guidance on who has access to what information at each stage. A supervisor having a preliminary conversation needs enough information to identify obvious causes but shouldn't be asking about medical details. A health professional conducting a formal assessment needs complete information but must work with clear boundaries on what gets reported back to operations.
Document these boundaries in your process. Train everyone involved on their responsibilities. Make it clear to operators that there are walls between different stages of the process and that sensitive information doesn't flow back to people making operational decisions.
The exception is when fitness for duty is in question, which should also be clearly defined in your process. But "this person needs medical assessment" is very different from "this person has sleep apnoea," and your process should protect that distinction.
Communication builds trust
Your assistance process should be visible before anyone triggers it. Surprise processes feel like ambushes, even when they're meant to be helpful.
Post the process in break rooms. Include it in employee handbooks. Discuss it during SmartCap training and safety onboarding. When you implement fatigue monitoring, explain not just how the technology works but what happens if someone is identified as higher-risk.
Be specific. Don't just say "we'll provide support." Explain the stages. Explain who's involved. Explain what kinds of outcomes are possible. Explain that the goal is identifying and addressing causes of fatigue, not managing performance.
Some operations have found success making the process transparent enough that operators can self-identify and ask for help before reaching the formal criteria. If someone knows they're struggling and understands that help is available without consequences, they're more likely to engage early.
Define roles clearly
Your process will involve multiple people with different responsibilities. Confusion about who does what creates both gaps in support and inappropriate intrusion into areas outside someone's expertise.
Supervisors are usually the first contact point. They have the relationship with operators and can identify obvious causes through private conversation. But supervisors shouldn't be conducting medical assessments or giving health advice. Their role is to check for simple explanations, provide basic information, and escalate when needed.
A supervisor can ask if someone's been having trouble sleeping in the camp accommodation. They shouldn't be asking about medication or diagnosing sleep disorders.
Health or industrial hygiene teams handle the more formal assessment. They should have training in fatigue causes and access to the monitoring data before engaging with an operator. Their role is systematic investigation of potential causes, referral to medical professionals when appropriate, and coordination of support resources.
Superintendents may not engage directly with assistance but play a critical role in ensuring the process is followed and addressing cases where operators are resistant to participating. If your process includes any mandatory elements (within legal bounds), superintendents handle compliance.
Company medical staff, if available, conduct formal health assessments, coordinate referrals to specialists like sleep clinics, and maintain the privacy wall between medical information and operational decisions. They should know local resources and be able to guide operators through assessment and treatment options.
The key is that each role has clear boundaries. When someone oversteps into areas outside their expertise, it erodes trust and can create liability issues.
A staged approach that scales with severity
%20(6).jpg)
Not every identified case needs the full process. A staged approach matches the level of intervention to what the situation requires.
Stage 1 is a private supervisor conversation focused on identifying obvious explanations. Is there something happening at home? Has the roster been particularly difficult this rotation? Is the camp accommodation working for them? Are they dealing with temporary circumstances like a sick family member?
This conversation has three possible outcomes. First, the operator returns to duties with a follow-up scheduled during the next rotation to see if the issue persists. Second, the operator is temporarily assigned alternative duties while getting medical or other assessment. Third, the operator returns to normal duties with additional controls like pre-scheduled fatigue breaks.
Most cases should resolve at Stage 1. If they don't, you move to Stage 2.
Stage 2 involves technical review of the monitoring data, to confirm that the fatigue-indicating technology is providing accurate data and is able to be used correctly. Sometimes what looks like chronic fatigue is actually equipment or technology problems. Having someone trained in interpreting the monitoring data helps confirm that the identified risk is real and not technical. If the technical review identifies equipment or technology issues, the solution lies with the vendor or your maintenance and IT teams to resolve. If the monitoring data confirms the fatigue risk is real and not technical, you move to Stage 3.
Stage 3 brings in your health or industrial hygiene team for systematic assessment of common causes. This is where a checklist approach works, going through categories of potential causes without immediately jumping to medical referral. Poor sleep hygiene, roster impact, environmental factors, lifestyle factors that the person might not have connected to their fatigue. If Stage 3 identifies causes that can be addressed through operational changes, roster adjustments, or environmental improvements, implement those solutions and monitor results. If the assessment suggests underlying medical issues that require professional diagnosis, you move to Stage 4.
Stage 4 is formal medical assessment, either by company medical staff or through referral to external providers. This might include general practitioner evaluation, sleep studies, or specialist consultations depending on what earlier stages identified as likely causes.
The staged approach prevents over-escalation while ensuring nothing gets missed. It also gives operators multiple opportunities to identify causes and engage with solutions before reaching the most formal stages.
The sunset clause matters more than you think
If your process includes record-keeping about who's been identified as higher-risk, you need a clear mechanism for resetting that status. People who struggled with fatigue for legitimate reasons and successfully addressed them shouldn't be permanently labelled.
One approach is a monthly sunset clause: if an operator demonstrates a clear pattern of reduced events for a full month (or rotation cycle), their “high alarm rate individual” status is cleared. This needs to be automatic, not something they have to request or that requires management approval.
The psychological impact of this is significant. It signals that the process is about solving problems, not building files on people. It gives operators a clear path to "normal" status, which motivates engagement with the support process.
Without a sunset clause, you're creating permanent risk categories that will make people defensive and resistant to participating.
Handling legislation and duty of care
Your process needs legal review before implementation. Privacy laws vary by jurisdiction. Duty of care requirements differ. Some regions have specific regulations about alternative duties and wage protection during medical assessment.
A few common requirements: you may need to ensure that operators don't lose income while participating in the assistance process. You may need to provide alternative duties if someone can't safely perform their normal role during assessment or treatment. You may have specific documentation requirements for health and safety regulators.
Work with legal counsel to ensure your process meets local requirements. This isn't just about protecting the company; it's about protecting the operators who are engaging with your process.
Making it work in practice
The best-designed process fails if it's not followed consistently or if it's used selectively. This requires accountability measures for management, not just operators.
Track not just who's been identified as higher-risk but whether they received the support your process promises. Monitor how long each stage takes. Identify where delays happen and fix those bottlenecks. If your process says Stage 1 happens within 48 hours but operators are waiting a week, your process isn't working regardless of how well it's documented.
Also track outcomes. Are people completing the process? Are they returning to normal alarm rates after intervention? Are there patterns in what causes are most common? This information helps you refine both your process and your broader fatigue management strategy.
The culture piece that makes or breaks everything
All of this is worthless if your workforce thinks that being identified as higher-risk is the first step toward being managed out. This fear is often based on experience with how other safety systems work, where being flagged usually means you're in trouble.
You need to actively counter this assumption. Share success stories where operators got help and their situation improved (with permission and anonymity). Have supervisors talk about the process in safety meetings as something the company does to support people, not catch them. Train everyone involved in the process to approach conversations from a support mindset, not an investigative one.
Consider having someone who's been through the process successfully (and is willing) talk to crews about their experience. Real stories from peers are more credible than management messaging.
The moment your workforce sees someone disciplined or dismissed for something discovered through the assistance process, trust collapses. This doesn't mean ignoring genuine misconduct if it's uncovered, but it means being extremely careful about how you handle information and ensuring that the assistance process maintains clear separation from performance management.
What you're actually building
An effective fatigue assistance process does more than manage immediate safety risk. It signals that your operation takes duty of care seriously. It provides a mechanism for identifying systemic issues like problematic roster designs or inadequate recovery facilities. It creates pathways for operators dealing with health issues to get help they might not have sought otherwise.
But most importantly, it matches your technology capability with your human support capacity. Detection without action is just surveillance. Detection with a clear, supportive, consistently-applied response process is actual risk management.
The operators who trigger alarms repeatedly aren't problems to be solved. They're people experiencing something that's affecting their capacity to manage fatigue, often for reasons outside their control. Your process should help them figure out what's happening and what to do about it.
That's the conversation worth having.
Published: 26 March 2026
Last Updated: 26 March 2026