Skip to content
Automated Vulnerability Remediation

A backlog of 20,000 findings takes 463 working days at these assumptions

Working days for the team: 463

Analyst hours: 8,333

Year 1
Year 2
463 working days is 92.6 working weeks: one tick per week, one row per year, a taller tick every quarter.

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

Computed with the formula under Assumptions; working days are rounded.
Open findingsMinutes eachAnalystsQueue hours a week eachRemoved before analysisAnalyst hoursWorking days
5,000152300%1,250104
20,000253300%8,333463
20,0002533040%5,000278
50,0002052560%6,667267

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.

Sources

1 source, each with its read date
  1. CISA Known Exploited Vulnerabilities catalog (the source for the finding counts readers compare against), read 10 Nov 2026

Last reviewed 10 Nov 2026.