Check whether backlog is growing
A single ending-backlog estimate can make it easier to see if incoming work is outpacing resolution volume.
Work Tools
Estimate ending case backlog from starting backlog, new cases received, and resolved cases.
Why this page exists
Service workload gets easier to track when starting backlog, incoming work, and resolved volume are rolled into one ending-backlog estimate instead of being reviewed as separate counts. This calculator helps teams estimate case backlog from starting backlog, new cases received, and resolved cases.
Interactive tool
Enter your numbers and read the result first, then use the sections below to understand what affects the outcome.
Calculator
Estimate ending case backlog from starting backlog, new cases received, and resolved cases.
Result
Estimated ending backlog based on starting backlog plus new cases received minus resolved cases.
This is a simple workload estimate only. Real backlog movement can still depend on case aging rules, reopened work, and how the reporting window is defined.
Planning note
Last updated April 16, 2026. Use this tool to compare scenarios and plan ahead, then confirm important details with the lender, employer, insurer, contractor, or other qualified provider involved in the final decision.
How it works
Enter starting backlog, new cases received, and resolved cases.
The calculator adds new cases to the starting backlog and subtracts resolved cases.
It shows the estimated ending backlog along with the values used in the calculation.
Understanding your result
This is a simple workload-tracking measure. It helps show whether work is building up or being cleared down, but it does not explain case complexity, aging, or queue mix.
Browse more work toolsExamples
Example scenarios help turn a quick estimate into a more useful comparison or planning step.
A single ending-backlog estimate can make it easier to see if incoming work is outpacing resolution volume.
Using the same backlog math each period can show whether operations are stabilizing or falling behind.
Backlog often becomes more useful when reviewed beside closure-rate, throughput, and staffing metrics.
When to use it
Use this when you want a quick ending-backlog estimate for a service queue, support team, or operations period.
It is especially useful when you need to see whether intake and throughput are staying in balance.
Assumptions and limitations
The estimate assumes starting backlog, new cases, and resolved cases are all counted on the same reporting basis.
It does not show case age, priority mix, complexity, or whether some work items are much harder than others.
Common mistakes
Comparing backlog changes without checking whether case definitions stayed consistent can make the trend misleading.
Treating a stable backlog as healthy without checking aging or reopen behavior can hide quality issues.
Practical tips
Review ending backlog alongside closure rate and average resolution time so you can see both workload and pace.
Track the calculation over a few periods in a row if you want to spot whether backlog pressure is becoming structural.
Worked example
A worked example shows how the estimate behaves when the inputs resemble a real planning decision.
A team starts with 140 open cases, receives 95 new cases, and resolves 88.
1. Enter the starting backlog, new cases, and resolved cases.
2. Add new cases to the starting backlog.
3. Subtract resolved cases to estimate the ending backlog.
Takeaway: The result gives a simple workload snapshot that can show whether the team ended the period ahead or behind.
FAQ
The calculator adds new cases to the starting backlog and subtracts resolved cases to estimate the ending backlog.
The calculator still shows the simple math but treats the operational ending backlog as fully cleared rather than negative.
Because it gives a fast view of whether work is accumulating faster than the team is closing it.
Related tools
Backlog-days, closure-rate, and resolution-time tools help explain whether the ending-backlog number reflects a capacity issue, a speed issue, or both.
Resolved-ticket-cost and reopen-rate tools can add quality and cost context when backlog is part of a broader service review.
Estimate how many days of work a current backlog represents from backlog size and daily throughput.
Estimate average support cases per agent from total support cases and total agent count.
Estimate case closure rate from total opened or assigned cases and the number closed.
Estimate the average time it takes to fully resolve a case, ticket, or support request.
Estimate average support cost per resolved ticket from total support cost and resolved ticket count.