A backlog is the defined population of unfinished eligible work at a stated snapshot time. Specify included statuses, the unit of work and the age clock. Separate blocked, actionable and completed-but-unclosed cases, then show counts and age bands without silently resetting long waits.
Define what remains unfinished
An open status can contain new requests, work in progress, blocked tasks and completed cases awaiting administrative closure. Decide which of these represents unfinished demand for the intended report. A delivery backlog and a system-cleanup queue are useful but distinct populations. Write the status inclusion list and the business interpretation of each status so a software label does not substitute for an operational definition.
Choose the unit of work. A customer request can contain several tasks, and a task can be reopened. Counting every task as a request inflates demand, while counting only parent requests can hide their varying workload. Keep count-based backlog separate from an estimated-effort backlog when both are needed. An estimate requires a known unit and an explicit treatment of work that has not yet been sized.
Specify the snapshot and age clock
A backlog is a stock at a moment, not the number created during a period. Record the snapshot timestamp and time zone. Define age from request receipt, eligibility confirmation or another event. If the clock pauses while awaiting a customer, preserve both calendar age and active-clock age where the decision requires them. Resetting age on every assignment or status update can make a long-waiting case appear new.
Use age bands with explicit boundaries, such as less than seven days, seven to under thirty days, and thirty days or more. Identify missing start dates instead of placing those records in the youngest band. Retain blocked reason and duration separately so managers can see whether a large backlog is actionable or depends on outside information. A small count can still carry substantial effort or urgency.
Reconcile stocks and flows
For a stable definition, opening backlog plus new eligible entries minus completed or otherwise valid exits should reconcile to closing backlog, allowing explicitly identified reopenings and scope changes. A discrepancy can reveal status timing, duplicate records or a changed extract. Do not force the bridge by relabelling unexplained disappearances as completions. Preserve cases that leave scope for another reason under a separate exit category.
The government framework provides quality background for defining and checking the population. The worked queue below is fictional. Pair total backlog with ageing, status and relevant priority information, then document who can change inclusion rules. A falling count can reflect faster delivery, a scope restriction or mass administrative closure; the bridge is what allows a reader to distinguish those possibilities.
Where snapshots are retained, keep their original status values and definition version. Reconstructing last month from today's records can lose cases that were deleted or reclassified, producing an apparently improving history that was never observed.
Fictional support queue: open does not mean unfinished
A fictional scenario to explain the method, not a customer result or a market benchmark.
A fictional service desk has 120 records marked open at Monday noon. Twenty are resolved but awaiting administrative closure, thirty are blocked awaiting customer information, and seventy remain actionable or in progress. Its delivery backlog includes the blocked thirty and actionable seventy, so the defined backlog is 100 cases rather than 120.
Of those 100, fifty-eight are under seven calendar days old, twenty-five are seven to under thirty days, and fifteen are thirty days or older. The blocked category is shown across those bands rather than hidden from the headline. Two cases have missing receipt dates and remain in a separate unknown-age group within the 100 total.
The following snapshot uses the same rule and a reconciled entry-exit bridge. These fictional counts illustrate definition and age handling. They do not establish expected effort, customer urgency or whether the blocked work should be escalated without further evidence.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Define unfinished work and status eligibility.
- Choose request, task or effort units.
- Specify snapshot time and age boundaries.
- Reconcile entries, exits and scope changes.
Common questions.
Should blocked work disappear from backlog?
Only if that is the explicit metric. Often it remains unfinished demand and should be separated by blocking reason.
Can the creation count be used as backlog?
No. Creation is a flow during a period; backlog is unfinished eligible work at a snapshot.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse Accuralytix.
Found an error or a missing qualification? Send an editorial correction.
Check my data readiness.
Use a practical tool to turn this idea into a clearer starting point.
Check my data readiness