A good maintenance backlog is not zero. It is controlled, prioritized, and executable. The useful question is not simply how many work orders are open, but how many crew weeks of valid work exist, how much is truly ready, what is blocking the rest, and whether the work is aging faster than the organization can control it.
Enough executable work to give the scheduler real choices without allowing ready work to age excessively.
A larger reservoir for planning and resource balancing, while still requiring control of aging and constraints.
Requests that have not been screened or approved should normally remain separate from the maintenance backlog. Once work has been validated and accepted, it enters a controlled inventory that planning, materials, operations, and maintenance must move toward execution.
All approved outstanding work. It may include jobs waiting for planning, materials, engineering, permits, outage access, contractor support, or scheduling.
Approved work that still requires planning activity before it can be considered executable. This is demand on the planning process, not yet demand the scheduler can safely commit.
Work that has passed the site's readiness gate and is waiting primarily for labor, timing, or equipment availability. This is the inventory the scheduler can actually use.
These categories are not interchangeable. If a dashboard reports only one backlog number, leaders cannot tell whether the real constraint is labor capacity, planning throughput, parts availability, operations access, or weak work-order governance.
A backlog number is only useful when you can see where work is accumulating. The same five-week total can represent a healthy planning system or hundreds of hours trapped behind unresolved constraints.
If someone gives me one plant-wide backlog number, my next question is always: what percentage of that work can a supervisor actually assign tomorrow without discovering a missing part, unclear scope, permit issue, access problem, or engineering question? Backlog only becomes useful when readiness is real.
Ten work orders could represent ten labor hours or a thousand. Work-order count can still be useful for aging and workflow analysis, but capacity decisions need estimated labor.
The phrase selected backlog matters. Calculate total backlog weeks and ready backlog weeks separately. If desired, calculate planning backlog the same way to understand planner workload.
A mechanical crew has 1,200 estimated hours of approved outstanding work. Realistically, 300 crew-hours per week are available for this class of work after fixed commitments.
Total backlog = 1,200 ÷ 300 = 4.0 crew weeks.
Only 360 of those hours have complete scope, material, information, and access requirements resolved.
Ready backlog = 360 ÷ 300 = 1.2 crew weeks.
The site does not have a four-week scheduling reservoir. It has 1.2 weeks of executable work and 840 hours trapped behind constraints.
A backlog calculation becomes misleading when the denominator assumes every paid hour is available for backlog execution.
Account for recurring PM work, required inspections, training, meetings, shift handoff, and other predictable commitments when they consume the same labor pool.
A four-week electrical backlog cannot be cleared by excess mechanical capacity unless the skills and work are actually interchangeable. Calculate by crew or craft where the constraint demands it.
The exact capacity method matters less than applying the same documented definition over time. Trend quality disappears when the denominator changes every week.
SMRP's maintenance and reliability metrics are intended to standardize definitions, formulas, qualifications, cautions, and benchmark values. Older SMRP material and practitioner discussions have commonly cited approximately 2 to 4 weeks for ready backlog and 4 to 6 weeks for broader planned or total backlog.
The terminology deserves attention. In a January 2026 SMRP member discussion, the SMRP Best Practices Chair explained that the 7th Edition definition of Planned Backlog intentionally combines work that has been planned but is not yet ready with work that is ready to perform. In other words, planned backlog can represent the broader planned-work horizon, while ready backlog remains the executable subset.
How much work has been prepared sufficiently that labor can execute it when equipment access and schedule timing allow?
How much identified work has passed through formal planning, including work still waiting on material, access, timing, tools, environmental conditions, or other readiness constraints?
Emergency and urgent classifications are rare enough to preserve their meaning. Risk and business consequence, not requester influence, determine priority.
Old work is reviewed instead of merely reported. The team decides whether to execute, re-scope, defer with a reason, or cancel it.
A job is not marked ready simply because a planner touched it. Scope, labor, materials, information, safety, tools, access, and coordination meet a defined readiness gate.
Waiting on parts, engineering, operations, permits, contractor support, shutdown access, or technical information are distinct states rather than one generic "open" bucket.
Enough jobs have realistic labor estimates for crew-week calculations and weekly scheduling to reflect actual capacity.
The team knows which jobs entered after the weekly schedule was set and why they displaced committed work.
Growing backlog triggers diagnosis of the constraint. Shrinking backlog triggers a different question: are we improving throughput, or simply failing to identify work?
Aggregate backlog weeks answer a capacity question. They do not tell you whether critical work is being displaced by easy work. Age and consequence need their own review.
| Backlog pattern | What it may mean | Management response |
|---|---|---|
| Young + high consequence | Important defect recently identified. | Validate priority, accelerate planning, and resolve constraints before age becomes risk. |
| Old + high consequence | Potential governance failure, access constraint, capacity problem, or accepted risk without visible ownership. | Escalate. Confirm current condition, interim controls, accountable owner, and execution path. |
| Old + low consequence | Work may be repeatedly displaced, poorly scoped, intentionally deferred, or no longer worth doing. | Revalidate, re-scope, formally defer, bundle, or cancel. |
| Young + low consequence | Normal future-work inventory. | Plan appropriately and allow priority to govern sequence. |
Do not let an average hide a tail of old high-risk work. Segment backlog by priority, asset criticality, age band, craft, work type, and constraint category.
The site has plenty of known work but too little executable inventory. Investigate planning throughput, material availability, access, approvals, engineering support, and readiness definitions before assuming the only answer is more technicians.
Work is being prepared, but execution capacity may not be consuming it fast enough. Review labor capacity, schedule loading, contractor strategy, production access, and whether priority or scope is allowing low-value work to crowd the queue.
This can be healthy in a genuinely low-demand environment, but it can also signal weak defect identification, poor operator reporting, reactive execution outside the CMMS, or an oversized labor model. Verify the demand system before celebrating.
Aggregate weeks can hide risk. Segment by priority, criticality, asset, work type, and age. A stable average is not healthy if high-consequence work is quietly aging behind low-risk jobs.
Validate asset, problem, requested outcome, duplicate status, ownership, and initial priority before accepting work into backlog.
Separate planning, waiting material, waiting access, engineering, ready, scheduled, deferred, and other meaningful states.
Challenge whether the condition still exists, whether the scope is still correct, and whether the work still deserves resources.
Planning should remove constraints deliberately rather than simply add notes to open work orders.
Commit work based on priority, real labor capacity, craft, asset access, and production constraints.
Use actual hours, missing parts, scope changes, findings, and technician feedback to improve future estimates and job plans.
Download the Backlog Triage Register Download the Job Readiness Checklist
You do not need a perfect CMMS cleanup to determine whether your backlog number can be trusted. Start with one crew and test the work behind the KPI.
Backlog is a queue of decisions, not a museum of old work orders. Every aging item should still have a reason to exist and a credible next action.
Unscreened requests, duplicates, completed-but-open jobs, projects, standing work, and obsolete records inflate the total.
The organization reports work-order count because planned labor is missing, then tries to make staffing decisions without a capacity denominator.
The CMMS field says ready, but materials, permits, access, drawings, isolation requirements, or basic scope are still unresolved.
The backlog becomes an archive of intentions. Aging grows while leaders assume every open job represents valid maintenance demand.
When everything is high priority, the scheduler loses a defensible basis for choosing between competing work.
Electrical, mechanical, controls, facilities, contractor, and shutdown work can have different bottlenecks. Aggregate backlog can average away the problem.
XRVE Reliability analyzes backlog age, status, priority, labor estimates, parts signals, work type, asset history, repeat failures, planning quality, break-in work, and data quality to show where work is accumulating and what is preventing execution.
See how ready backlog, job planning, parts readiness, labor estimates, weekly scheduling, and technician feedback fit together.
Use work orders, assets, PM history, backlog, failure data, labor, downtime, and technician notes to find the maintenance priorities that matter.
Usually no. Zero backlog can mean the site has no identified future work, work is not being documented, or jobs are being executed reactively before they can be planned. The goal is controlled inventory, not zero inventory.
Divide estimated labor hours in the backlog category you are measuring by the weekly labor capacity realistically available to that work. Calculate total and ready backlog separately.
Total backlog includes approved work that may still be waiting on planning or other constraints. Ready backlog is the subset prepared sufficiently for scheduling and execution.
No, not if the missing material prevents execution. Keep it visible in total backlog and identify the material constraint, but do not represent it as schedulable work.
It is useful for workflow, aging, and record-quality analysis, but it is weak for capacity planning because work orders vary dramatically in labor demand. Use estimated hours and crew weeks for capacity.
Backlog control should be part of the normal weekly planning and scheduling cadence, with additional review of aged, high-risk, deferred, and constraint-heavy work as needed.
XRVE Reliability uses external maintenance and reliability guidance as reference points, not as substitutes for site-specific engineering, safety, production, regulatory, and operating requirements.
Ask how much approved work exists, how much is ready, what is blocking the rest, which jobs are aging, and whether the backlog gives the scheduler enough real options to protect the week.
Start free Maintenance Health Check Explore maintenance planning