Maintenance Backlog: How to Calculate Weeks-to-Clear and the Crew Size You Need

Monday Morning, and the List Didn't Get Shorter

It's the first Monday of the quarter, and the open work order count in your spreadsheet is 187. Last quarter it was 140. Nobody on the crew has been slacking — if anything, everyone worked a Saturday in March to catch up. But the number keeps climbing, a little more every month, and the explanations you've been giving upward ("we're short-staffed," "we had a bad run of breakdowns") are starting to sound like excuses even to you.

Here's the thing: a backlog that grows every month almost never means your crew isn't working hard enough. It means the hours of work coming in are larger than the hours of work your crew can physically clear — and no amount of hustle changes that arithmetic. What it needs isn't a pep talk. It needs a number: how many weeks would it take to clear the backlog at your current crew size, and how many people would it take to clear it on a schedule you can defend.

This article walks through the maintenance backlog calculation that answers both questions, with a worked example you can run against your own numbers today.

What Counts as Backlog Hours (and What Doesn't)

Before you can calculate anything, you need one number: total backlog hours. This is not the same as your open work order count, and treating it as the same number is the most common mistake in backlog tracking.

A backlog of 187 work orders could be 400 hours of work or 1,200 hours of work, depending on job size. Counting tickets tells you almost nothing about how long it will take to clear them. Counting hours tells you everything.

To build an honest backlog-hours figure:

• Include every open work order that is ready to work — parts on hand, approvals done, nothing blocking it. A work order waiting on a part isn't a crew-capacity problem yet; it's a procurement problem, and mixing the two muddies the calculation.
• Use the estimated labor hours for each job, not the elapsed calendar time it's been sitting open. A job that's been open six weeks because it kept getting bumped is still, say, a 3-hour job.
• Include both PM and corrective/reactive work orders in the backlog pool if your crew works both from the same hours budget — which, in most SMB shops, they do.
• Exclude planned future PMs that aren't due yet. Backlog is work that should already be done, not your whole maintenance calendar.

Sum the estimated hours across every job that qualifies, and you have your starting number: backlog hours.

The Weeks-to-Clear Formula

Once you have backlog hours, the formula itself is simple:

Weeks to clear = Backlog hours ÷ Net available hours per week for backlog work

Net available hours is the part most teams get wrong, because it isn't just "crew size × 40 hours." It's what's left over after two subtractions:

1. Non-wrench time. Technicians don't spend their whole shift turning wrenches — travel between work areas, documentation, parts runs, and safety meetings all eat into the hours on the clock.
2. New incoming demand. Every week brings new PM due dates and new reactive calls. Those have to be worked too, and they compete with backlog for the same crew hours.

So the fuller version of the formula looks like this:

Net available hours/week = (crew size × scheduled hours/week × wrench-time share) − new incoming demand hours/week

If that number is positive, your backlog shrinks over time, and dividing backlog hours by it tells you how many weeks until it's clear. If that number is zero or negative, your backlog will not shrink no matter how long you run it — you're adding work faster than you can remove it, and the only fixes are more capacity, less incoming demand, or both.

A Worked Example: Clearing a 420-Hour Backlog

Here's how the numbers work in practice.

Starting point:

• Backlog hours: 420 (summed from ready-to-work PM and corrective jobs)
• Crew: 4 technicians, scheduled 40 hours/week each
• Wrench-time assumption: for this example, assume technicians spend about 60% of a scheduled shift on direct hands-on work, with the rest consumed by travel, paperwork, and parts runs. This is a planning assumption for the example, not a published benchmark — your own ratio may run higher or lower, and it's worth measuring rather than guessing.

Total crew wrench-time capacity = 4 techs × 40 hrs × 0.60 = 96 hours/week

Scenario A — heavy incoming demand. New PM and reactive work this week totals 100 hours.

Net available for backlog = 96 − 100 = −4 hours/week

The crew is underwater before they touch a single backlog item. This is the shop from the opening scenario: hardworking, and still losing ground every week. No weeks-to-clear number even applies here — the backlog grows indefinitely until something changes.

Scenario B — lighter incoming week. New PM and reactive work drops to 70 hours (a realistic week, not a heavy one).

Net available for backlog = 96 − 70 = 26 hours/week

Weeks to clear = 420 ÷ 26 ≈ 16.2 weeks

That's the honest answer with the current crew: four months to clear the backlog, assuming incoming demand stays at the lighter level the whole time. If incoming demand spikes back to 100 hours in any of those weeks, the clock resets.

How Many Technicians You Actually Need

Sixteen weeks might not be acceptable — a backlog that size often includes safety-relevant or production-constraining jobs that shouldn't sit for four months. So the next question is the staffing one: how many people does it take to clear this on a schedule you choose?

Rearranging the same formula to solve for crew size:

Hours needed/week = (Backlog hours ÷ target weeks) + incoming demand hours/week

Crew size needed = Hours needed/week ÷ (scheduled hours/week × wrench-time share)

Continuing the example: say you want the 420-hour backlog cleared in 8 weeks, not 16.

Hours needed/week = (420 ÷ 8) + 70 = 52.5 + 70 = 122.5 hours/week

Crew size needed = 122.5 ÷ (40 × 0.60) = 122.5 ÷ 24 ≈ 5.1 technicians

In practice, that means adding one technician — bringing the crew to five — plus a modest amount of overtime or a short-term contractor to cover the remaining fraction, for roughly the eight-week catch-up window. It does not mean permanently doubling headcount. Once the backlog is cleared, the ongoing crew-size question becomes a different, steadier calculation: how many technicians does it take to handle incoming demand alone, with no backlog drag.

There's no universal "healthy" backlog target in weeks that applies to every plant — the right target depends on how much risk a job sitting open represents for your operation, your assets' criticality, and your own tolerance for schedule slip. Set the target first, then let the formula tell you the crew size, rather than picking a crew size and hoping the backlog cooperates.

Why Backlog Keeps Growing Even When the Crew Works Overtime

This is the pattern worth naming explicitly, because it's the one that burns out maintenance managers: overtime treats a symptom the formula shows you isn't the real variable.

If net available hours is negative — as in Scenario A above — overtime can make a dent, but it doesn't fix the underlying imbalance unless it's sustained indefinitely, which crews can't do without burning out. The actual fix is one of three things: increase crew hours (more people, not more overtime), reduce incoming demand (longer PM intervals where justified, or eliminating low-value PM tasks), or both. [For more on right-sizing PM intervals so they're not manufacturing unnecessary backlog demand, see the related guide on coordinating PM schedules with production.]

A backlog spreadsheet that only tracks ticket counts hides this entirely. A number going from 140 to 187 looks like a motivation problem. The same data converted to hours and run through the formula above looks like what it actually is: a capacity shortfall with a specific, calculable size.

The Maintenance Backlog Calculation Your Work-Order Count Can't Do

Most CMMS platforms will report an open work-order count, and some will sum estimated hours if you've entered them consistently. Very few will walk you through weeks-to-clear or the crew-size question — because that calculation sits one layer above the work order itself, in planning and staffing, not in dispatch.

That's a deliberate boundary worth being upfront about. A tool built for tracking individual work orders, assigning technicians, and closing out jobs is solving a different problem than a tool built for answering "how many people do I need, and by when." MaintenanceCalculator.com is built for the second kind of question — the planning layer — not for dispatching technicians or managing parts inventory. If your backlog problem is really a work-order-routing problem, you need execution software. If it's a crew-sizing and scheduling-visibility problem, the calculation above is the whole answer, and it doesn't require replacing anything you already use to track individual jobs.

Turning the Formula Into a Weekly Habit

A backlog calculation run once, in a crisis, tells you where you stand today. Run weekly, it tells you whether the gap is closing or widening before it becomes a 187-ticket surprise.

The inputs to track every week are the same four numbers from the formula: backlog hours, crew size, scheduled hours per technician, and incoming demand hours. Most shops already have the first and last buried in a spreadsheet or CMMS report — the work is pulling them into one place, consistently, on the same day each week. [The Monday-morning workflow guide covers how to build that weekly check into a routine that doesn't eat half your morning.] Pairing the backlog check with a [visual status view across your fleet] and your [annual PM calendar] gives you both the current number and the context for why it's moving.

If you'd rather not rebuild the spreadsheet from scratch, the [Maintenance Backlog Capacity Calculator] does this math for you — enter backlog hours, crew size, and incoming demand, and it returns weeks-to-clear and the crew size needed for any target window, as a downloadable template you can reuse every week. If the crew-sizing question extends beyond backlog recovery into your steady-state staffing level, the [Maintenance Staffing Level Calculator] covers that version of the formula.

Either way, the point is the same one from the top of this article: a backlog that won't shrink is an hours problem, not a willpower problem, and it's one you can put an exact number on before your next planning meeting.