A backlog of 20,000 findings takes 463 working days at these assumptions
Worked examples
Four backlogs run through the same formula. The inputs are illustrations to compare against your own queue, not measurements of any team or platform.
Scroll the table sideways for more columns
| Open findings | Minutes each | Analysts | Queue hours a week each | Removed before analysis | Analyst hours | Working days |
|---|---|---|---|---|---|---|
| 5,000 | 15 | 2 | 30 | 0% | 1,250 | 104 |
| 20,000 | 25 | 3 | 30 | 0% | 8,333 | 463 |
| 20,000 | 25 | 3 | 30 | 40% | 5,000 | 278 |
| 50,000 | 20 | 5 | 25 | 60% | 6,667 | 267 |
Removing findings before analysis moves the result more than any other input: at the default 20,000 findings, taking out 40 percent saves 3,333 analyst hours. A platform's stated reduction is a vendor claim until it is measured on your own findings; the guide to measuring a backlog shows how to count it.
Assumptions
- Hours = findings left times minutes per finding, divided by 60.
- Working days = hours divided by (analysts times weekly queue hours divided by 5).
- Findings left = findings times (1 minus the percent removed before analysis, divided by 100).
- The percent removed is an input you set from a vendor result you trust; the calculator does not assume one.
- No fix time is included: the figure is analysis time only.
Related pages
Sources
1 source, each with its read date
Last reviewed 10 Nov 2026.