Queue aging worksheet

Find old work before it loses an owner or breaks a promise.

Use this weekly worksheet for tickets, invoices, records, and requests that are old, blocked, unowned, reopened, or close to a promised date. It makes the next action and escalation time visible without inventing a universal SLA.

Copy the worksheet Check reviewer capacity

Set age bands and escalation triggers from your own service rules, coverage hours, risk policy, and agreements. The examples below are fictional and are not SLA, legal, finance, security, or compliance advice.

Review focusOld + blocked

Also pull unowned, reopened, and promise-risk items.

Best usedWeekly

Review sooner when the team's written risk rule requires it.

Required resultNamed next step

Each item leaves with an owner, action, and time.

Fictional examples

The age matters less than what is stuck and who can move it.

Replace these examples with current records and your team's written age bands. Scroll sideways to see every field.

Three fictional rows. They do not set a standard response time, age band, or escalation deadline.
Item	Type	Opened	Age band	Last action	Promise	Blocker	Owner	Reviewer	Risk	Next action	Escalate by
Support ticket CS-1842	Delivery status request	Monday, 9:10 a.m.	Use the support team's current aging band	Assistant asked the carrier for a scan on Monday	Customer update due Tuesday at noon	No carrier scan or approved delay message	Support queue lead	Buyer support manager	Customer promise may be missed	Check carrier record and prepare an approved status reply	Before the promised update time through the support escalation route
Invoice packet AP-307	Invoice match preparation	Thursday, 2:40 p.m.	Use the finance team's current aging band	Receipt requested from the department owner on Friday	No vendor promise recorded	Receipt and buyer approval are missing	Accounts payable support queue	Buyer finance owner	Money and vendor-record risk	Keep payment actions blocked and request the missing records	At the team's written cutoff or sooner if a due date is at risk
Onboarding task ON-092	New-customer setup request	Wednesday, 11:25 a.m.	Use the onboarding team's current aging band	Assistant added the signed order form on Wednesday	Kickoff details due Friday	Implementation owner is not assigned	Customer onboarding queue	Customer success manager	Kickoff promise and handoff ownership	Assign the qualified owner before sending kickoff details	By Thursday afternoon through the onboarding manager route

Blank worksheet

Give each old item a visible decision.

Copy the block into the team's review note. Use safe record references, not customer details, when the note may leave the source system.

WORK-QUEUE AGING REVIEW

Queue or work lane: [Name]
Coverage window: [Days, hours, and timezone]
Review date: [Date]
Queue owner: [Name and role]
Reviewer: [Name and role]
Age bands: [Use the team's written bands]
Escalation rule: [Use the team's written trigger and route]

ITEM OR RECORD ID: [ID or safe reference]
ITEM TYPE: [Ticket, invoice, request, record, or other lane]
OPENED: [Date and time]
AGE BAND: [Team-defined band]
LAST ACTION: [Action, date, and owner]
PROMISED DATE: [Date, or none]
BLOCKER: [Missing input, approval, access, owner, or other cause]
CURRENT OWNER: [Person or team]
REVIEWER: [Person who checks the next action]
RISK: [Customer, money, access, legal, payroll, safety, or routine]
NEXT ACTION: [Specific action]
ESCALATE BY: [Date, time, trigger, and route]
STATUS: [Work, wait with owner, escalate, close, or correct record]

Repeat the item block for each old, blocked, unowned, or promise-risk item.

The worksheet stays visible. It does not save queue or customer data.

Review questions

Do not let "waiting" hide the missing decision.

A useful blocker names what is missing, who can supply it, and when the item changes route.

Is the age based on a timestamp that both the manager and worker can inspect?
Does every waiting item name the input, approval, access, or person it is waiting for?
Is the current owner able to take the next action, or does the item need a different owner?
Has anyone promised a date or outcome to a customer, vendor, employee, or internal team?
Does the risk require a manager, finance owner, security owner, qualified reviewer, or emergency route?
Is repeated aging caused by demand, reviewer capacity, unclear scope, missing SOPs, or a broken handoff?

20-minute review

Review exceptions before averages.

A healthy average can hide one old customer promise, finance item, access request, or ownerless case.

Pull the current queue export or work list and the team's written age bands, promises, coverage hours, and escalation rules.
Filter for old, blocked, unowned, reopened, or promise-risk items. Do not rely on the queue average alone.
Check the last action, blocker, current owner, reviewer, next action, and escalation time for each item.
Move money, access, legal, payroll, safety, and customer-promise decisions to the named owner before routine work continues.
Record the decision, close false or duplicate items, and carry capacity or process gaps into the weekly or monthly review.

Next review

The queue review finds the item. These tools help fix the staffing, review, service-rule, or decision-rights problem behind it.