Maintenance backlog: distinguish approved work from work ready to plan

Topics: maintenance backlog management; oil and gas maintenance records; work-order readiness; planning completeness.

The weekly meeting opens with 40 outstanding maintenance orders. Operations asks why planning is behind. The planner says several orders have no agreed scope, while others are waiting for materials or current document references. Everyone is discussing the same total, but not the same work.

Maintenance backlog triage should reveal the next decision each record needs. An approved request can be ready for planning while still missing information needed to finish the plan. A completed plan can still await separate authorisation for execution. Those distinctions make the queue useful.

Name the stages in terms people can verify

Begin with the local process, then map system statuses to it. A practical reporting model distinguishes a recorded request, approved scope, planning in progress, planning information complete, scheduled work and the site's separate execution authorisation. These are proposed reporting distinctions, not a replacement work-control procedure.

For each stage, specify the entry evidence. “Approved scope” needs a decision reference and owner. “Planning complete” needs the applicable inputs and dispositions defined by the planning process. A date field or a work-order number alone does not establish either state.

Equipment and maintenance data should use consistent definitions. ISO 14224 is relevant to that data discipline; its scope is broader than a backlog dashboard, and this article does not claim to implement the standard. ISO catalogue

Keep the priority assigned by the qualified maintenance and operations authorities. Administrative triage must not automatically defer a safety-related request because its attachment is missing. The missing evidence should become an escalated action under the approved process.

Forty orders can conceal several different queues

Illustrative example. A snapshot of 40 open orders is classified into mutually exclusive primary reporting states:

The total is still 40. There are 28 orders with approved scope and 15 with complete planning information. That is 15/28, or about 54%, of the approved-scope population. It is also 15/40, or 37.5%, of the entire open population. Either percentage can be useful if its denominator is named. Presenting one as the other changes the story.

These primary states simplify the report. An individual order may have several blockers. Keep those in a separate blocker table so an order with both material and document gaps is not counted twice in the headline total. When the primary blocker closes, the remaining one must stay visible.

The 15 complete records are not necessarily authorised for execution. Readiness for the next planning or scheduling decision must not be displayed as permission to perform the work.

Order count also says little about workload. In another illustrative comparison, ten orders estimated at two labour-hours each represent 20 hours, while two orders estimated at 40 hours each represent 80 hours. Show estimated effort by relevant craft alongside count once the plans support it, and leave unknown estimates visible. The scheduler still needs crew availability and dependencies; a high percentage of complete records is not a capacity plan.

Give ageing a starting event

“Open for 90 days” is useful context, but it does not tell the team where the delay occurred. Record request date, scope decision date, planning start and the opening and closing times of each blocker. Do not reset the original age when a record moves between teams.

Suppose one order waited 60 days for a scope decision and five days for a material confirmation. Calling it a 65-day planning delay directs attention to the wrong owner. The report should preserve the sequence so the team can address the real handover.

A blocker record needs the missing input, person or role responsible, requested date, expected response, latest evidence and escalation route. Avoid using “awaiting information” as a permanent category with no recipient. If the requested information is no longer required, the authorised owner should record why the criterion changed.

Give the weekly review a decision list

A useful review begins with changed or ageing blockers and the decisions needed to move them. The planner coordinates completeness. Materials confirms availability and reservations. Document owners confirm revisions. Qualified technical and operations authorities determine priorities and the applicable work permissions.

When the scope changes, revisit the planning inputs that depended on it. A previously complete material list may no longer support the revised job. Retain the old version and mark affected evidence for review rather than allowing the order to stay green because it passed yesterday.

For readers evaluating the work-permission boundary, OISD's catalogue identifies a separate Work Permit System standard. The full applicable process must be established by the site's qualified owners. OISD standards catalogue

Use the existing CMMS before adding another queue

First test whether the current system can represent approved scope, blocker type, owner, evidence and age. A lightweight reporting layer may be enough if the underlying records are reliable. A new application adds little when “complete” has three meanings across departments.

Integration helps where the material reservation or document revision is held elsewhere. Show the last successful refresh and source reference so the planner can tell whether a reservation is still current. Calculate ageing from recorded events, and retain the underlying blocker notes for the review meeting.

Close duplicate or cancelled requests through a recorded disposition, with a link to any surviving work order. Removing them from a report without explanation can make the backlog appear to improve while the original demand remains unresolved. Compare successive snapshots using additions, completions, cancellations and reopened work so the total change can be explained.

Measure the share of approved-scope orders with complete planning information, the age of unresolved blockers and repeated returns caused by missing inputs. Segment by relevant work type and priority without treating a fast closure rate as proof that important work was handled appropriately.

Summary and next actions

Backlog becomes manageable when the team can distinguish a request awaiting a decision from approved work awaiting information. Clear states and owners make the next action visible while preserving the authority of the maintenance and work-control process.

1. Classify one backlog snapshot into defined, non-overlapping primary states.
2. Add a separate record for every blocker, with its owner and opening date.
3. Compare completeness using explicit denominators and retain the original request age.
4. Carry the same evidence discipline into turnaround package readiness.