Skip to content

Maintenance Operations research

What a work order backlog count can and cannot prove

A research brief on work order backlog counts in property management, separating a queue that is long from a maintenance process that is failing.

| 3 sources sources

What a work order backlog count can and cannot prove
Table of contents

A property manager opens the maintenance report and sees 140 open work orders. The number is presented as evidence that the team is behind. Nobody asks how many are waiting on parts, how many are duplicates, or how many are older than the current month.

A work order backlog count is a useful capacity signal and a poor performance verdict. This brief sets out what the count can show, what it hides, and how to report it so it supports a decision about staffing, vendors, or the intake process.

Define what counts as open

The first decision is whether the count includes every ticket in every status or only the ones that need action. A ticket waiting on a resident to provide access is open, but it is not the team's delay.

Write the definition down: which statuses are counted, whether duplicates are merged, and whether preventive maintenance is included. A count without a definition is not comparable from month to month.

What the count can show

The count can show the size of the queue and its direction over time. A backlog that grows for three consecutive months is a capacity or intake signal worth reviewing.

It can show where the queue sits. A count by building or by trade often reveals that the total is concentrated in one property or one system, which is a different problem from a general overload.

It can support a staffing conversation when paired with the age of the tickets and the close rate. The count alone says how many are open; the other fields say whether the team is keeping up.

What the count cannot show

The count cannot show whether the open tickets are the right ones. A team can reduce the number by closing easy tickets and leaving the difficult ones, and the count will look better while the risk grows.

It cannot show whether a ticket was closed correctly. A closed work order with no repair note may be a completed job or a premature closure. The count does not distinguish.

It also cannot show resident satisfaction or compliance with habitability obligations. Those need the ticket detail and, in some cases, an inspection.

Methodology and limits

This brief reviews public guidance on internal control, housing inspection standards, and small-business operations, and maps it to a private work order system. The sources support documentation and review discipline; they do not establish a target backlog or a service level.

We tested the proposed fields against four common cases: a ticket waiting on parts, a duplicate ticket for the same issue, a ticket waiting on resident access, and a ticket closed without a repair note. Each produced a different interpretation of the same total.

Separate age and priority

Report the count by age band and by priority. A backlog of forty tickets, all under a week old, is a different situation from forty tickets with ten older than a month.

Priority matters because a small number of urgent tickets can carry more risk than a large number of routine ones. A count that treats them equally hides the exposure.

Record the waiting reason

Add a waiting reason to every open ticket: parts, access, vendor, approval, or scheduling. The reason turns the backlog into a map of where the process stops.

A cluster waiting on parts points to inventory or procurement. A cluster waiting on access points to resident communication. A cluster waiting on approval points to the delegation rules. Each has a different fix.

Report the oldest tickets

List the ten oldest open tickets with their age, building, and waiting reason. The tail is where the risk sits, and it is the part a total hides.

Review those tickets one by one in the weekly meeting. Close, escalate, or renegotiate each one. A backlog that is reviewed only as a number will keep its oldest items indefinitely.

Compare close rate to intake

A backlog grows when intake exceeds closures. Report both numbers so the trend is explainable, and separate new tickets from reopened ones.

A stable backlog with a high close rate may be healthy. A stable backlog with a low close rate may be a queue that is being abandoned in place. The two look identical in the total.

Intake quality

A backlog is only as good as the tickets in it. Check for duplicate tickets, missing units, and vague descriptions before using the count for a decision.

A short intake form with required fields reduces rework and makes the queue comparable. The time spent on intake is smaller than the time spent asking residents what the ticket meant.

A worked example

A portfolio reports 120 open tickets. Forty are waiting on parts, twenty on resident access, and ten are duplicates. The remaining fifty need scheduling.

The headline count suggests a staffing crisis. The waiting reasons suggest a procurement problem for one vendor and a communication problem in one building. The right response is different in each case, and the count alone would have hidden both.

What to do with the oldest tickets

Review the ten oldest tickets each week and record a decision for each: close, escalate, or schedule with a date. A decision record turns the tail into work rather than a permanent list.

If the same ticket stays in the oldest ten for three weeks, escalate it to the property manager. A queue that cannot move an item after three weeks needs a policy answer, not another reminder.

Seasonality and preventive maintenance

Include preventive work only if the client wants it in the same queue. Heating season and turnover season change the volume, and a raw comparison across months will attribute the seasonal effect to performance.

Record the season and the preventive schedule beside the report. That context makes a rise in the count explainable without excusing a genuine capacity problem.

Communicating the backlog

Share the count with the owner alongside the age and waiting reasons. A number without context invites a staffing request that may not be the right fix.

Offer one recommendation per report and state what it would change. A recommendation that is specific is easier to approve than a general call for more resources.

Data quality checks

Check for duplicate tickets, tickets with no unit, and tickets closed without a note. These defects distort both the count and the close rate.

Record the number of incomplete tickets beside the report. A high count is a finding about the intake process, and it should be fixed before the count is used for staffing decisions.

Limits and appropriate use

This brief is a method note, not an empirical study. It does not establish a target backlog or a standard close time. Results depend on the quality of the ticket data and the honesty of the status updates.

Small portfolios may not have enough tickets for a meaningful trend. In that case, read the counts directly and review the oldest items rather than relying on percentages.

Conclusion

A work order backlog count is a starting point. Used with age, priority, waiting reason, and close rate, it shows where the queue is stuck and what to fix. Used as a single number, it invites conclusions the data cannot support and rewards the wrong kind of closure.