Overview
Backlog Management is the controlled process used to turn identified maintenance needs into a visible, validated, prioritized, planned, risk-informed, and executable body of work.
A healthy backlog is not simply a list of open work orders. It is a managed inventory of valid work with clear ownership, reliable asset references, appropriate priority, known readiness, credible labor estimates, visible constraints, and a defined disposition path.
The goal is not to make the backlog as small as possible. The goal is to maintain enough high-quality, ready work to support stable execution while preventing hidden risk, obsolete work, duplicate records, material constraints, and unowned demand from accumulating.
What It Is
Backlog Management governs work after a maintenance need has been identified but before it has been finally completed, cancelled, transferred, or otherwise disposed.
A maintenance backlog may include work awaiting:
- validation;
- planning;
- materials;
- access;
- scheduling;
- execution;
- technical completion;
- administrative closure.
The organization must define its backlog boundary before reporting backlog KPIs.
What backlog is not
| Term | Why it is different |
|---|---|
| Open work order | Not every open order is valid executable backlog |
| Overdue work | Describes a date condition, not the backlog itself |
| Work request | A request may be rejected before it becomes backlog |
| Scheduled work | Committed work should normally be reported separately from ready backlog |
| Project work | Major project scope should transfer to project governance |
| Completed but unclosed work | This is a closeout queue, not executable backlog |
| Deferred work | Valid backlog that requires explicit risk acceptance and review |
Why It Matters
Backlog Management connects work identification to execution.
A controlled backlog supports:
- stable weekly scheduling;
- better planning;
- risk visibility;
- craft-capacity forecasting;
- material coordination;
- shutdown scope development;
- compliance tracking;
- maintenance cost control;
- operations alignment;
- leadership decision-making.
Poor backlog control creates predictable problems: planners work on low-value jobs, schedulers cannot find ready work, aging work disappears into the system, urgent jobs are mixed with routine work, and leadership sees counts instead of risk.
When to Use It
Backlog Management applies to accepted maintenance demand such as:
- corrective maintenance;
- PM follow-up work;
- predictive and condition-monitoring findings;
- inspection findings;
- calibration and test follow-up;
- compliance work;
- approved improvements;
- shutdown work;
- contractor maintenance;
- facility, fleet, utility, and infrastructure maintenance.
It should not be used as a holding area for invalid requests, duplicate work, completed work, major capital projects, or ideas that have not been approved as maintenance work.
Core Principles
- Every backlog item must represent valid work.
- Every accepted item needs an accountable owner.
- Work must mature through controlled readiness stages.
- Age does not determine priority by itself.
- Priority must reflect consequence, probability, urgency, criticality, and failure progression.
- Backlog must be compared with realistic usable labor capacity.
- Duplicate, obsolete, invalid, and completed records must be removed from active backlog.
- Hidden work must be surfaced and evaluated.
- Deferred work requires documented risk acceptance and review.
- Ready work must be clearly distinguishable from merely planned or open work.
- CMMS status design should support the process, not replace ownership.
Process or Lifecycle
- Identify Need leads to Screen and Validate.
- Screen and Validate leads to Classify and Prioritize.
- Classify and Prioritize leads to Plan Work.
- Plan Work leads to Resolve Materials and Constraints.
- Resolve Materials and Constraints leads to Ready Backlog.
- Ready Backlog leads to Schedule.
- Schedule leads to Execute.
- Execute leads to Technical Closeout.
- Technical Closeout leads to Final Closure.
- Final Closure leads to History and Reliability Feedback.
The backlog should also support alternate disposition paths such as cancellation, deferral, project transfer, and shutdown transfer.
Roles and Responsibilities
| Role | Primary responsibility |
|---|---|
| Requester | Describe the observed need |
| Supervisor | Validate need, assign ownership, support priority |
| Planner | Define executable scope, labor, materials, tools, and job requirements |
| Scheduler | Select ready work against realistic capacity |
| Operations | Confirm access, downtime, cleaning, isolation, and production windows |
| Storeroom / Procurement | Resolve material availability and lead-time constraints |
| Reliability | Review repeat, high-risk, and failure-driven work patterns |
| Maintenance Manager | Own backlog governance and risk escalation |
| EHS / Quality | Review work with safety, environmental, quality, food-safety, or compliance implications |
| CMMS Administrator | Maintain controlled fields, statuses, reports, and data quality |
Required Inputs
A controlled backlog depends on:
- valid asset or functional-location references;
- clear problem statements;
- work type;
- requester;
- assigned owner;
- priority;
- required dates where applicable;
- labor estimates;
- planning status;
- material status;
- safety and permit requirements;
- operations constraints;
- compliance dates;
- shutdown dependencies;
- approval status.
Required Outputs
The process should produce:
- validated backlog;
- planning backlog;
- ready backlog;
- shutdown backlog;
- compliance backlog;
- deferred backlog;
- constraint reports;
- backlog aging views;
- craft-capacity views;
- risk-based review lists;
- cancellation and transfer records;
- closeout queues.
Step-by-Step Implementation
1. Define the backlog boundary
Decide which lifecycle states count as backlog and which are reported separately.
For example, distinguish:
- newly submitted requests;
- validated work;
- planning backlog;
- planned-not-ready work;
- ready backlog;
- scheduled work;
- in-progress work;
- completed-but-unclosed work.
2. Define entry criteria
Work should enter controlled backlog only after:
- the need is traceable;
- the asset or location is identified;
- enough information exists for screening;
- the work is within scope;
- duplicate search is complete;
- the need is validated;
- ownership is assigned;
- work type and initial priority are assigned.
3. Segment the backlog
Useful segmentation includes:
- site;
- area;
- asset;
- criticality;
- craft;
- planner group;
- work type;
- priority;
- readiness;
- material status;
- age;
- shutdown requirement;
- compliance requirement;
- owner.
Segment only when the view answers a management question.
4. Establish readiness criteria
A work order is ready to schedule when preventable constraints are resolved.
Typical readiness criteria include:
- approved scope;
- job steps completed;
- labor estimate available;
- required materials available or confirmed;
- safety controls identified;
- specialty tools available;
- contractor requirements resolved;
- operations access confirmed;
- drawings and technical information available;
- required approvals complete.
5. Establish review cadence
Use regular backlog reviews for:
- new-work screening;
- high-risk work;
- planning constraints;
- material constraints;
- aging work;
- shutdown scope;
- deferred work;
- completed-but-unclosed work.
6. Control exit paths
Valid backlog exit reasons include:
- completed;
- closed;
- cancelled;
- rejected;
- duplicate;
- obsolete;
- no longer required;
- transferred to project;
- transferred to shutdown;
- deferred with approval;
- transferred to another responsible group.
Decision Rules
New work triage
- New Work leads to Valid asset and problem?.
- Valid asset and problem?, when No, leads to Return or Reject.
- Valid asset and problem?, when Yes, leads to Duplicate or already resolved?.
- Duplicate or already resolved?, when Yes, leads to Link and Cancel Duplicate.
- Duplicate or already resolved?, when No, leads to Immediate unacceptable risk?.
- Immediate unacceptable risk?, when Yes, leads to Emergency Response.
- Immediate unacceptable risk?, when No, leads to Evaluate Consequence and Probability.
- Evaluate Consequence and Probability leads to Mandatory due date?.
- Mandatory due date?, when Yes, leads to Compliance Backlog.
- Mandatory due date?, when No, leads to Shutdown or project dependency?.
- Shutdown or project dependency?, when Shutdown, leads to Shutdown Backlog.
- Shutdown or project dependency?, when Project, leads to Project Transfer.
- Shutdown or project dependency?, when Routine, leads to Priority and Planning.
Readiness decision
Do not move work to ready status unless scope, labor, materials, safety, access, and required approvals are sufficiently resolved for commitment.
CMMS Considerations
The CMMS should support:
- distinct request and work-order states;
- duplicate detection;
- controlled work types;
- priority fields;
- asset criticality context;
- labor estimates;
- planning status;
- material status;
- shutdown flags;
- compliance dates;
- deferral controls;
- cancellation reasons;
- owner assignments;
- readiness status;
- aging reports;
- audit history.
Avoid using one generic "open" status for all work.
SAP PM Considerations
The authoritative MKS supports backlog governance through SAP PM concepts such as maintenance notifications, maintenance orders, planner groups, work centers, statuses, priorities, maintenance activity types, materials, and scheduling fields.
Exact SAP configuration is organization-specific. The backlog process should be defined first, then mapped to available SAP objects and statuses.
Metrics and KPIs
Backlog Weeks
Definition: Estimated backlog labor demand expressed relative to usable weekly labor capacity.
Formula:
Backlog Weeks = Backlog Labor Hours ÷ Usable Weekly Maintenance Labor Capacity
Units: Weeks
Interpretation: Indicates the relationship between work demand and available capacity.
Limitations: Results can be distorted by poor estimates, unestimated work, mixed crafts, nominal rather than usable capacity, or contractor hours that are not actually executable.
Ready Backlog Weeks
Formula:
Ready Backlog Weeks = Ready Backlog Labor Hours ÷ Usable Weekly Scheduling Capacity
Units: Weeks
Interpretation: Shows the amount of schedule-ready work available to support future schedules.
Limitations: Only useful when "ready" is governed consistently.
Aging
Definition: Elapsed time from a defined lifecycle event.
Common aging clocks include:
- request age;
- validation age;
- planning age;
- ready age;
- closeout age.
Units: Days
Interpretation: Helps identify stalled flow.
Limitations: Old work is not automatically high priority.
Material-Constrained Backlog
Definition: Valid work unable to progress because required materials are not available or confirmed.
Units: Count, labor hours, or percentage of backlog
Interpretation: Helps identify procurement and materials bottlenecks.
Limitations: Requires current material-status data.
Common Failure Modes
- Treating all open work orders as backlog.
- Using work-order count instead of labor demand.
- Leaving duplicates and obsolete work open.
- Allowing work to age without an owner.
- Mixing scheduled work with ready backlog.
- Treating age as priority.
- Using nominal labor capacity instead of usable capacity.
- Moving work to ready status while materials or access remain unresolved.
- Deferring work without risk acceptance.
- Closing or cancelling work simply to improve the metric.
- Allowing "unknown" labor estimates to appear as zero.
- Hiding shutdown or project work inside routine backlog.
Best Practices
- Define backlog states in plain language.
- Separate total backlog from ready backlog.
- Manage backlog by labor hours and craft, not only record count.
- Review high-risk and compliance work separately.
- Maintain explicit cancellation and deferral reasons.
- Track constraints by owner.
- Keep ready status difficult to earn and easy to understand.
- Use aging to identify flow problems, not to override risk.
- Review backlog quality before chasing backlog size.
- Protect sufficient ready work for scheduling.
Maturity Levels
| Level | Characteristics |
|---|---|
| 1 — Reactive | Open work accumulates with weak screening and little planning |
| 2 — Visible | Backlog is reported, but definitions and readiness are inconsistent |
| 3 — Controlled | Entry, exit, priority, planning, and readiness rules are defined |
| 4 — Integrated | Backlog is linked to craft capacity, materials, shutdowns, risk, and scheduling |
| 5 — Optimized | Backlog flow is measured, constraints are actively removed, and data supports strategic decisions |
Real-World Example
A food manufacturing plant has 2,400 estimated backlog labor hours. The maintenance organization has 1,000 nominal labor hours per week, but 360 hours are already committed to PM, compliance, leave, meetings, routine rounds, and emergency allowance.
Usable weekly capacity = 1,000 − 360 = 640 hours Backlog weeks = 2,400 ÷ 640 = 3.75 weeks
Reporting the backlog against the nominal 1,000 hours would produce 2.4 weeks and materially understate the actual demand-to-capacity ratio.
The same site also finds that much of its electrical work is waiting on parts while mechanical work is largely ready. A single site-wide backlog number would hide that imbalance. Craft-specific and constraint-specific views give leadership a more useful picture.
Audit Questions
- Is backlog defined consistently across the site?
- Are work requests screened before becoming controlled backlog?
- Are duplicates actively removed?
- Does every accepted item have an owner?
- Are labor estimates required before ready status?
- Is material status visible?
- Are safety and access constraints visible?
- Is deferred work reviewed with documented risk?
- Are routine, shutdown, project, and compliance backlogs separated?
- Is ready backlog clearly distinguished from planned backlog?
- Are completed-but-unclosed orders reported separately?
- Are backlog weeks calculated using usable capacity?
- Are craft-specific imbalances visible?
- Are priority changes traceable?
- Are cancellation reasons recorded?
- Is aging used to identify stalled flow rather than replace priority logic?
Related Reliability Method Topics
Confirmed related topics:
- Maintenance Planning
- Maintenance Scheduling
- Work Order Management
- Asset Criticality Analysis
Related Tools and Assets
Potential future assets:
- Backlog Health Assessment
- Backlog Triage Checklist
- Ready-to-Schedule Checklist
- Backlog Aging Dashboard
- Backlog Weeks Calculator
- Backlog Review Meeting Template
- Deferral Risk Form
- Constraint Tracking Board
These assets are not created by this document.
References
References are limited to the authoritative MKS and its confirmed related internal sources:
- RM-MKS-6007 — Backlog Management
- RM-MKS-6002 — Maintenance Planning
- RM-MKS-6003 — Maintenance Scheduling
- RM-MKS-9003 — Work Order Management
Public derivative source: Draft. Publication status: Not Authorized.