HomeInsightsHow to find business process bottlenecksHow to measure queue age and find work that is stuckHow to prioritize an aging queue without neglecting urgent work

Capacity Expansion / Article

How to prioritize an aging queue without neglecting urgent work

By Mark Rawlins

An oldest-first rule can neglect urgent requests. An urgent-first rule can leave ordinary work waiting indefinitely. A useful queue rule makes both risks visible and gives someone authority to resolve conflicts.

01

Set priority from a known commitment

Choose one queue and list the commitments that apply to it: promised dates, customer impact, dependencies and any required response times. Define urgent work by a specific condition that a reviewer can check, such as a critical service interruption. An approaching deadline alone may require escalation rather than an automatic change of class.

Record each item's original arrival time, class, reason for priority and owner, plus the next action. Keep paused items visible and distinguish waiting for the team from waiting for someone else. A priority label with no explanation is difficult to challenge or review.

02

Give each class a review route

Agree who can classify or change priority, who covers that role when absent and when the queue is reviewed. Within each class, use age or due date as a starting order, then allow documented exceptions for dependencies or risk. Give routine work a regular review and an escalation point before a commitment is missed.

When urgent demand exceeds the time available, the reviewer must decide what can be delayed and tell affected owners. Reserving capacity for routine work is a planning choice, not a guarantee that an emergency can wait. Record the decision and revisit it as conditions change.

03

Work through a hypothetical day

A team has six hours for a queue. Two urgent items need an estimated hour each; three routine items need two hours each. The oldest routine item is close to its agreed delivery date. The team handles the urgent items and the oldest routine item first, using four hours, then starts the next routine item. It assigns an owner to notify anyone whose commitment is at risk.

If a third urgent item arrives, the reviewer checks its urgency and remaining capacity before changing the order. Estimates can be wrong, so the team updates the queue as work completes. The three routine items require six hours in total, but only four hours remain after the urgent items. The team should not promise all three will finish that day.

04

Check for unintended waiting

At each review, inspect the age and count of open items by class, overdue commitments, completed work and the number of priority changes. Look at individual old items as well as a typical age. A falling average can hide one request that has waited far longer than the rest.

If everything becomes urgent, sample the reasons and clarify the definition with the people assigning it. If routine work ages while urgent arrivals keep rising, compare demand with available capacity and renegotiate commitments.

05

Review reserved time

Review reserved urgent time against actual arrivals over several comparable periods. If a block regularly goes unused while routine work ages, agree a release time with the person responsible for urgent coverage. For example, an unused afternoon block might be reassigned after a morning review, with an escalation route if an urgent request arrives later. Record both unused capacity and urgent work that could not be accommodated before changing the rule.

Continue reading

Related guides and articles.

Put the work into practice

Find a useful next step.

Explore how Capacity Expansion approaches this work, or review the scope of a capacity audit.