I took two days off last year and expected my body to catch up. I slept in both mornings. No calls, no tones, nothing but a normal house. I felt fine by day three. My recovery numbers didn't move at all. That was the moment it landed for me: rest isn't recovery. And the shift schedule everyone points to as the fix for firefighter fatigue isn't the whole problem it looks like.
Rest isn't recovery. And the shift schedule everyone points to as the fix for firefighter fatigue isn't the whole problem it looks like.
The schedule does matter. Here's what the research shows.
Let's be fair to the departments doing the work. Schedule structure has a real, measurable effect on sleep. In one study, moving a department from a 24/48 to a 48/96 rotation improved total sleep time, sleep efficiency, and insomnia scores at the three-month mark in a lower call-volume setting (IJERPH, 2026). Other comparisons have found that a steady 24/48 tends to produce better sleep quality than a rotating Kelly-day pattern, because it gives the body more consistent circadian anchoring.
So if you're a chief weighing 24/48 against 48/96 against a Kelly rotation, you're not wrong to care. Those choices move the average. The mistake is believing the average is the answer.
Why the schedule is a blunt, population-level lever
Hours worked isn't what wrecks a nervous system. Disruption is. A tone at 2am costs you more than the hour you're on the call. It pulls you out of deep sleep, and your body spends the rest of the night trying to get back to a state it never reaches. Run that four times in a 24-hour shift and you can come off duty having slept seven hours on paper and recovered from almost none of it.
That load doesn't clear the moment the shift ends. Studies tracking heart rate variability, a well-established signal of how your autonomic nervous system is recovering, have found meaningful suppression that persists into the days after a 24-hour shift, not just during it (Int. J. of Occupational Safety and Ergonomics, 2023). Your heart rate can look normal while the deeper recovery signal is still flat. That's why a firefighter can take four days off and still get flattened by an ordinary Tuesday. The recovery never actually happened. They just weren't at work while it didn't happen.
Here's the part a schedule can't touch: two firefighters on the exact same rotation can walk off it carrying completely different loads. Age, sleep disorders, a second job, a new baby, a bad run of calls, individual physiology. The roster treats them as identical. Their bodies aren't. Change the schedule for the whole department and you've moved the average while the person who's actually in trouble stays invisible.
Hours on duty is the wrong number
Every department knows its shift length down to the minute. Almost none can tell you what a shift costs a specific person's nervous system, call to call, night to night. That's the measurement gap. Without that number, every schedule change is a guess wearing a policy's clothes, and you won't know if it worked for the people who needed it most until something breaks.
It matters because poor recovery doesn't stay in the body. Research on firefighter sleep has tied disrupted sleep directly to higher rates of depression, anxiety, PTSD, and burnout, with poor sleep acting as a factor that amplifies the risk, not just a symptom of it. The firefighter who isn't recovering usually gets read as someone who isn't trying hard enough. That isn't weakness. It's a body doing exactly what a body does when nobody is watching the right number, and there is a way through it.
What to measure instead: individual-baseline recovery
The useful signal isn't the schedule. It's recovery, tracked on an individual baseline over time. Heart rate variability has been described across the research as a valid, practical way to assess day-to-day recovery and readiness in tactical and firefighting populations (Frontiers in Public Health, 2020). The key word is individual.
This is where most consumer wearables fall down for first responders. A Garmin or a WHOOP compares your numbers to a population average built for someone who sleeps eight uninterrupted hours a night. Your people don't. Held against the wrong baseline, the number is noise. Held against a person's own baseline, tracked across shifts and recovery days, it starts to show drift early, before the person feels it, before it costs them anything.
To be clear about what that is and isn't: this is awareness and monitoring, not treatment. It doesn't diagnose anything. It surfaces a pattern so a firefighter and a department can act on it early. That's the difference between managing a schedule and monitoring the person working it.
What departments should ask before the next schedule change
- Do we know how our people are actually recovering, or only how many hours they worked?
- Are we measuring against an individual baseline, or a consumer-wearable population average built for someone who isn't a first responder?
- Would a schedule change let us see whether recovery improved for the people most at risk, or just move a department-wide average?
- Is what we're using awareness and early monitoring, or is it waiting for a crisis to disclose itself?
If you can't answer the first one, the schedule decision is still a guess. Get the recovery number on an individual baseline, and the next schedule decision is grounded in what's happening to your people instead of an assumption about their hours.
That individual-baseline approach is what we're building at Neurovus. If you're a chief who wants to see what it looks like before committing to anything, we run a no-cost pilot. That's the honest next step, and it starts with measuring the thing the schedule never could.