A maintenance backlog needs more than one number

Practical analysis | Logic Foundry | October 11, 2026. The workflow below is a proposal for review, illustrated with fictional examples. It is not a report of a completed trial or measured customer results.

1. What does the total leave out?

Imagine two fictional properties with the same number of open maintenance requests. At one, most requests are ready for assignment. At the other, several are waiting for access, a specialist inspection or a decision about replacement. Treating the totals as equivalent would leave out information needed to choose the next action.

The operational question is not simply which building has more open work. It is what kind of intervention would move each unresolved issue forward. A manager may need to assign a technician, arrange access, clarify the scope or make a decision. Those actions should be distinguishable in the review.

2. Separate priority from readiness

Priority describes why an issue deserves attention. Readiness describes whether the next action can actually proceed. A high-priority issue can still be blocked, while a low-priority task can be ready to start. Combining those ideas in one status risks making either the importance or the obstacle disappear.

Our proposed review uses the organisation's existing priority definitions, with a separate description of the next action and what is preventing it. It does not prescribe a universal scoring system. Local responsibilities, asset context and existing escalation procedures remain authoritative, especially for issues that could affect safety or essential service.

For a fictional example, a recurring water leak may require an investigation whose access arrangements are not yet agreed. The useful record is not merely awaiting access. It identifies the investigation, the person arranging access, the unresolved condition and the next review point. It also keeps the original issue visible while the coordination work proceeds.

3. Give waiting a specific meaning

Consider a small set of explanations that a reviewer can act on: scope unclear, access not arranged, material unavailable, specialist input needed, or decision awaiting an accountable owner. These are suggested starting points, not a complete taxonomy. Keep a free-text explanation where the category cannot capture the situation.

Distinguish a forecast from a commitment. An expected delivery date is different from confirmed material availability. A request sent to a contractor is different from an accepted appointment. If the evidence supports only an expectation, the record should preserve that uncertainty rather than present the task as ready.

A dependency also needs an owner who can act on it. Assigning a technician to work that cannot proceed may not resolve a purchasing or access problem. The review should identify who owns the obstacle as well as who would perform the eventual work. Where nobody has accepted responsibility, make that gap explicit.

4. Preserve the age of the issue

A proposed portfolio view would keep the original report date alongside the date of the latest meaningful progress. Changing a status or adding a routine note would not, by itself, be evidence that the underlying condition improved. Define what counts as progress before using the measure to compare buildings.

Related requests need care too. Several reports might describe one unresolved condition, but similar wording does not prove they are duplicates. Before linking or consolidating them, confirm the property, location, equipment and reported symptoms. Preserve the individual reports where they contain distinct evidence or occupant impacts.

The goal is to make unresolved work more understandable, not to make a dashboard look smaller. Closing a record for administrative tidiness should not imply that the reported condition was corrected. Any review method should preserve the distinction between a record change and evidence of an operational outcome.

5. Review decisions, not just rankings

At a recurring portfolio review, choose a manageable group of unresolved issues and ask three questions: what is the next action, what prevents it, and who can remove that obstacle? Record a next review point appropriate to the issue. Urgent matters should continue through established escalation routes rather than wait for this meeting.

A comparison between buildings could then show different kinds of demand on the organisation. One site may need clearer task scope, another help coordinating access, and another a replacement decision. The proposed view would support those discussions without pretending that a single backlog score captures all local context.

Be cautious about incentives. If teams are judged only on a shrinking count, the review can reward administrative changes rather than useful work. If every issue receives the highest priority, priority stops helping the team distinguish cases. Discuss how the information will be used before adding more fields or targets.

6. A small review exercise

Readers could try the proposal on a small, non-sensitive sample of existing open records. First, ask a reviewer to identify the next action and obstacle using the current information. Mark answers that require a phone call or an unsupported assumption. Do not change live priorities, authorisations or operating procedures for this exercise.

Next, add a short explanation of readiness and dependency to the sample, using verified information from the responsible team. Ask a second reviewer to make the same assessment. Record disagreements and missing context, including cases where adding a category made the issue harder to understand.

The hypothesis is that separating priority, readiness and dependency could help managers choose a more appropriate intervention. A tabletop exercise can test whether the records communicate those distinctions. It cannot establish faster completion, reduced costs or improved reliability. It may instead reveal that the team needs better scope definition or clearer decision authority.

Two discussion prompts can keep the exercise grounded: Which waiting category in your portfolio conceals the most different problems? Which unresolved decision repeatedly returns to review without an accountable next action? The answers may point toward a change in coordination rather than a new metric.

CORE-FM currently supports properties, assets, work orders, preventive maintenance and sensor monitoring. Logic Foundry's confirmed research includes AI-assisted work orders and future reporting and decision tools. The review structure described here is a proposal for discussion, not a claim that a backlog classification or automated prioritisation feature has been shipped or validated.