The strongest case for additional maintenance staffing is not that you are tired, even if you are. It is that current capacity creates measurable business risk and avoidable cost.
Measure demand
Track corrective hours, PM hours, project hours, callouts, waiting time, contractor hours, and backlog age.
A reliable one-person routine turns this into a standard rather than a judgment call: Use a simple monthly summary rather than trying to build a perfect labor model.
If corrective work consumes 70 percent of available hours and PM compliance falls, the capacity problem becomes visible.
Use measure demand to make the next shutdown more productive. Jobs that require access, parts, contractors, or long isolation should be prepared in advance with scope, materials, drawings, permits, and acceptance criteria. A lone technician cannot afford to spend rare downtime searching for basic information.
Price the consequences
Management compares labor cost against expected benefit.
The fastest way to make this useful is to attach it to the work itself: Estimate downtime cost, contractor premiums, overtime, delayed projects, repeat failures, and risk from uncovered shifts.
A second salary can look different beside the annual cost of emergency vendor callouts and lost production.
The maintenance value of price the consequences increases when you can trend it. Even simple counts – repeats per month, hours waiting for parts, missed PMs, callouts, or downtime minutes – reveal whether the plant is improving. Trend direction is often more persuasive than one dramatic event.
Propose the role you actually need
Another general technician is not always the best answer.
Treat this as part of the repair, not as optional paperwork afterward: Identify the gap: electrical coverage, mechanical strength, night-shift response, planner function, automation skill, or PM capacity.
A complementary mechanical technician may provide more resilience if your own strength is controls and electrical work.
When propose the role you actually need depends on another department, make the dependency explicit. Record whether you are waiting for production access, purchasing, IT, engineering approval, a contractor, or a part. A visible blocker prevents delayed work from being mistaken for forgotten work.
Practical application
Take one recent maintenance event that relates to how to justify a second technician. Reconstruct what you knew at the beginning, before resets, part changes, or production explanations influenced the diagnosis. Then review the event through three lenses from this chapter: measure demand, price the consequences, and propose the role you actually need. Write down where your real response matched the method and where it depended on memory, urgency, or luck.
Use the examples as prompts rather than scripts. For measure demand, the chapter showed: If corrective work consumes 70 percent of available hours and PM compliance falls, the capacity problem becomes visible. For price the consequences, it showed: A second salary can look different beside the annual cost of emergency vendor callouts and lost production. Decide on one practical change you can make before the same type of event returns – a measurement point, spare, label, note, backup, callout rule, PM task, or escalation contact.
Chapter action checklist
☐ Identify one current weakness related to how to
justify a second technician.
☐ Choose one change that can be implemented without new
software or budget.
☐ Decide what evidence should be recorded the next time this
situation occurs.
☐ Identify the point where you would stop and escalate rather
than continue alone.
☐ Add any resulting repair, documentation, spare, training, or
management action to the visible backlog.