Key Takeaways
- Reactive maintenance charges its hours to time nobody counts, so the operation reads a run of successful rescues while you read a year with holes in it.
- Most of the cost sits in the waiting rather than the work. Three call-outs can take thirty evenings, because any evening could be the one.
- What a planned operation gives back first is the choosing of the hour, and an hour you offered lands differently from one that was taken.
The exhaustion has a schedule attached to it, and nobody has printed it. Advice about maintenance burnout goes after the coping instead: sleep, boundaries, a firmer handover at the end of a shift. All of it aims at the person, while the damage is done by a rota that lets any hour become a working one. You know the shape of it, the phone at eleven at night, the line down, boots on while the house stays asleep.
Why does reactive maintenance take more out of you than the hours suggest?
Because the cost gets charged to time nobody measures. Work inside a shift shows up in a schedule, a timesheet and a report. Work at two in the morning shows up nowhere. So the operation experiences a reactive month as a run of jobs that got done, and you experience it as a month you did not get.
Two people can read that same month completely differently and both be right. Your operations manager sees equipment restored and work orders closed. You see the birthday you left early, the Sunday that went, and the flatness that arrives when rest keeps getting interrupted rather than shortened.
That flatness is measurable. Safety Science put it at 52.9% of aircraft maintenance technicians reporting some level of fatigue in 2024, correlated with workload and with lower quality of life away from the job. Aviation runs tighter rosters than most plants, and the pattern still turns up.
What actually costs more, the call-outs or the waiting for them?
The waiting. A call-out takes the hours it takes and then it ends. Staying available takes every hour it might have happened in, which is all of them. So counting call-outs understates the cost, usually by a lot.
Three call-outs in a month sounds manageable. Spread across four weeks, those three take thirty evenings, because you spent all thirty reachable. You skipped the theatre tickets. You had one drink instead of two. You drove separately so you could leave. None of that gets recorded as maintenance work, and all of it was.
Researchers have measured the state rather than the events, and the finding is blunt. Environmental Health published a review in 2004 in which 68% of on-call workers said being on call had a negative effect on their life outside work. The phone didn't have to ring for that to be true.
What the arrangement takes is easy to see once you stop counting only the call-outs:
- The evenings you stayed reachable, which is all of them
- The plans you made smaller so they would survive an interruption
- The sleep that got broken rather than shortened
- The part of your attention that stays on the plant while you stand in your own kitchen
Is maintenance burnout a personal failing or a scheduling fact?
A scheduling fact, and you have probably filed it under character. It never gets raised because it arrives disguised as a compliment. You are the person who handles things. That is true, you earned it, and it is also doing a job a rota should be doing.
Managers tell us the same thing, and they start with the birthdays. They talk about what the last few years have done to their marriage, and about the version of themselves their kids have met. Reactive maintenance costs marriages, childhood memories and mental health, and any account of it that stops at lost output has described the smallest part of what is owed.
None of it gets escalated either, because escalating means asking for a change that looks like more trouble than what you already absorb. The arrangement works, in the narrow sense that the machines run and the reports go out. Absorbing is quieter than asking, so it gets absorbed, and after a few years it becomes the job description.
The distinction worth holding onto is this. Being someone who handles things is an identity, and it is yours. Having no way for tonight to be handled without you is a rota. Somebody decided how work gets scheduled here, and decisions can be made again.
Does a planned operation actually give you your evenings back?
It gives back the choosing of the hour first, and that was the part costing the most. The work does not disappear. A job booked for Tuesday morning and the same job at midnight take similar effort and land in very different places.
Broderick's Handmade describe getting more done with the same resources after going live. Same resources means the same people, so that gain showed up as slack in a week that had none.
Three honest limits, because a piece promising your life back would be doing what the last system did. The change costs hours before it returns any, and the first come out of the evenings you are protecting. Some equipment fails without warning whatever anyone schedules, so some nights will still go wrong. And the trades hold up better than the discourse suggests. The Washington Times, covering a 2025 CDC study in JAMA Network Open, reported manual workers in manufacturing and construction self-reporting lower frequent or extreme distress than several office-bound groups. Maintenance burnout is real and specific, and the specific thing is the on-call arrangement.
Go back to the call at eleven. The expensive hours were the thirty evenings you stayed ready, and you have spent years counting the other ones. How the cycle breaks is a longer argument, made elsewhere. What matters here is narrower: the share of your hours that you chose can move, and it moves sooner than it looks from inside a bad week.
Maintenance burnout is the shape of a schedule. Schedules get rewritten.
