Ticket Backlog Rate
Definition
Ticket Backlog Rate
Ticket backlog rate compares the tickets still open at the end of a period against the tickets that arrived during it. It is a measure of whether a desk is keeping up, expressed as open tickets divided by tickets received.
A rate above 1.0 means the queue grew — and anything sustained above it is a staffing or process problem rather than a bad week.
The measure works because it is self correcting for demand. A rising open count during a demand spike may still be a healthy desk.
Age matters as much as volume. A backlog of two hundred tickets all opened yesterday is a very different situation from two hundred opened last month.
Read it weekly — monthly reporting hides the moment a desk tipped from coping to drowning.
Key takeaways
- Ticket backlog rate divides tickets still open by tickets received in the period.
- A rate above 1.0 means the queue is growing faster than it is being cleared.
- Ageing the backlog matters more than counting it.
- Weekly reporting catches the tipping point that monthly reporting hides.
How it works
Count tickets open at period end, count tickets received during the period, then divide. Pair the ratio with an age profile so you can see whether the backlog is fresh work in progress or old work nobody has touched.
Definitions need pinning down first. Decide whether pending customer response counts as open, because that single choice can move the rate by a third.
| Element | What it sets | Common practice |
|---|---|---|
| Open definition | What sits in the numerator | Excludes awaiting customer, reported separately |
| Period | Sensitivity of the series | Weekly for operations, monthly for reporting |
| Age bands | Where the risk sits | 0 to 2 days, 3 to 7, 8 to 30, over 30 |
| Healthy range | The action threshold | 0.8 to 1.0 sustained across weeks |
Public sector service work treats queue health as a trust issue. Digital.gov publishes practical guides for teams running government digital services, including how service performance should be measured and shown.
Accountability frameworks push the same way. The US customer experience programme holds designated High Impact Service Providers to specific published actions rather than to a single blended figure.
Backlog is also a forecasting signal. Three consecutive weeks above 1.0 usually predicts a service level breach before the service level report shows one.
Pair the rate with clearance capacity. Knowing a desk closes 400 tickets a week turns an abstract backlog of 900 into a concrete two week recovery plan somebody can actually staff.
Examples
Backlogs build for very different reasons, and the age profile usually names the cause faster than the headline number ever does. Four cases from support and technical desks show the patterns worth recognising.
A Cebu technical desk. Backlog rate sat at 1.12 for five weeks. The age profile showed 40% of open tickets older than thirty days, all waiting on a single third party integration.
A retail support team. A promotional launch pushed the rate to 1.8 for one week, then back to 0.9. That spike was demand, not capacity.
A financial services desk. Counting awaiting customer as open produced a rate of 1.3. Reporting the two categories separately showed a genuinely healthy 0.85.
An internal IT help desk. Backlog held near 1.0 while the oldest bracket kept growing — a queue that looked stable while quietly ageing.
Related terms
Backlog rate reads alongside the ticket objects it counts, the systems that hold them, and the routing that decides where work lands. The terms below cover each.
- Support Ticket: the unit of work being counted.
- Open Ticket: the state that fills the numerator.
- Ticketing System: the platform the data comes from.
- Help Desk Support: the function the measure describes.
- Queue Management: the routing layer that shapes how backlog builds.
- Escalation: the path that clears the oldest and hardest items.
- Workforce Management (WFM): the function that sizes the desk against demand.
FAQ
What is a healthy ticket backlog rate?
Between 0.8 and 1.0 sustained across several weeks. Short spikes above that are normal; sustained readings above 1.0 are not.
Should tickets awaiting customer reply count as open?
Report them separately. Blending them in overstates the backlog and hides the work the desk actually controls.
How does backlog rate differ from resolution rate?
Backlog rate measures whether the queue is growing. Resolution rate measures how much of the arriving work gets closed.
Why age the backlog?
Because old tickets carry most of the risk. Two hundred fresh tickets and two hundred month old ones need completely different responses.
How often should it be reviewed?
Weekly. Monthly review usually spots the problem a full reporting cycle after it started.
Does adding staff always fix a backlog?
No. When the age profile points at a blocked dependency, more people simply produce a larger queue.
Find support delivery partners in the Outsource Accelerator BPO hubs.
Independent
