Maintenance backlog: how to calculate it and read the trend

Backlog is not the list of overdue work orders. It answers a simple question: if no new request came in from today on, how many weeks would your team need to clear everything already in the queue?

That answer tells you whether the team is the right size for the demand. A backlog that keeps growing warns you, weeks in advance, that you'll run short of hands. A backlog that keeps shrinking can mean an idle team, or requests that never become work orders.

The water tank

The easiest way to understand backlog is to picture a water tank. New requests flow in: corrective work, preventive tasks generated by the plan, improvements, requests from operations. What the team completes flows out. The water level is the backlog.

If more comes in than goes out, the level rises. If more goes out than comes in, it drops. What matters to a manager isn't just today's level, but where it's heading.

How to calculate it

The math has two parts:

• Queue: the sum of estimated labor hours for every open work order, in any status: awaiting planning, planned, scheduled, waiting for parts and in progress. Only completed and canceled work orders stay out. (One labor hour is one person working for one hour.)
• Capacity: the labor hours your team can deliver per week. That's the number of technicians × hours per week × a productivity factor.

Backlog (weeks) = queue labor hours ÷ available labor hours per week

The productivity factor exists because nobody spends 100% of a shift with tools in hand. Travel, fetching parts, meetings, training and waiting for clearance all eat into the time. Values between 65% and 80% are common. If you haven't measured yours, start with 70% and adjust once you have time records. The article what to record on a work order explains how to measure it.

Step-by-step example

A fictional team of 4 technicians, 44 hours a week each, with 75% productivity:

• Capacity: 4 × 44 × 0.75 = 132 labor hours per week.

Today's queue:

Work order status	Estimated labor hours
Awaiting planning	90
Planned, no date	180
Scheduled	130
Waiting for parts	40
Total queue	440

Backlog = 440 ÷ 132 = 3.3 weeks. The range most often cited as healthy is 2 to 4 weeks: enough work to plan calmly, without leaving requests waiting too long. You can redo the math with your own numbers in the backlog calculator.

Split it by trade

The overall backlog can hide a serious problem. In the same example, split the team into 2 mechanics and 2 electricians:

Trade	Queue (labor hours)	Capacity (labor hours/week)	Backlog
Mechanical	340	66	5.2 weeks
Electrical	100	66	1.5 weeks
Overall	440	132	3.3 weeks

The overall number sits in the healthy range, but the mechanical side is overloaded and the electrical side has slack. That changes the decision completely: instead of hiring, it may make more sense to train an electrician for simple mechanical jobs, or to outsource only the mechanical peak. Whenever you can, track backlog by trade: mechanical, electrical, instrumentation, refrigeration, metalwork.

Read the trend, not just the number

A 3-week backlog can be great or terrible, depending on where it was a month ago. Plot the weekly value on a chart and look at the shape of the curve:

Shape of the curve	What it usually means	What to do
Stable within the range	Demand and capacity are balanced	Keep it up; use the slack for improvements
Rising steadily	More work comes in than the team can deliver	Reprioritize, outsource peaks, tackle repeat corrective work
Falling steadily	Team larger than demand, or requests outside the system	Check that demand becomes work orders; bring preventive and improvement work forward
Stable, but high	A bloated queue, with old work orders nobody will ever do	Clean up the queue: duplicate, obsolete and ownerless work orders
Peaks and valleys	Planned shutdowns, seasonality or bursts of corrective work	Plan the extra capacity before the peak

When the backlog is high

Overtime is the first idea and almost always the worst: it wears the team out, increases rework and doesn't fix the cause. Before you get there, try these, in this order:

1. Clean up the queue. Duplicate work orders, requests that no longer make sense and jobs done but never closed all inflate the number.
2. Reprioritize by asset criticality. Whatever stops production or affects safety comes first; the rest waits.
3. Tackle repeat corrective work. Equipment that breaks every week keeps feeding the tank. A root cause analysis on it reduces the inflow.
4. Review the preventive plan. Excessive frequencies burn labor hours with no real gain.
5. Don't schedule above capacity. Scheduling 160 labor hours in a week when the team delivers 132 guarantees delays. The schedule has to fit real capacity.
6. Only then outsource the peak or grow the team.

In taskfield, backlog is calculated from open work orders and the estimated hours on each one, by trade, and the weekly curve sits on the dashboard. Nobody has to build the spreadsheet at the end of the month.