How Long Will the Post-Incident Review Backlog Take?

How to Use This Tool

Translate unresolved reviews into a capacity-backed completion horizon. Teams restore service and move on, allowing unfinished learning and corrective actions to age behind the next incident.

Why Postmortem Backlog needs more than a raw total

Total review effort divided by genuinely protected capacity reveals whether the organization has a recovery process or only an intention. For this page, the useful comparison is weeks to clear backlog, not whichever input happens to be largest. The Postmortem Backlog result answers the decision in the heading and should not be reused as a score for a different workflow.

The exact Postmortem Backlog formula

Clearance weeks equal pending incidents multiplied by hours per review, divided by protected weekly capacity. The visible fields are Incidents awaiting review, Average review effort and Protected review capacity. For Postmortem Backlog, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed weeks to clear backlog may be arithmetically valid but operationally meaningless.

Interpreting weeks to clear backlog

Prioritize severe and recurring incidents, schedule named owners and track corrective actions separately from completing the review document. The ten-percent comparison is deliberately narrow: it tests the influence of incidents awaiting review and is neither a forecast nor a confidence interval. Preserve the values used, their dates and the resulting decision so a later reviewer can reproduce why Postmortem Backlog supported the choice.

What this Postmortem Backlog model leaves out

This assumes similar review effort and no new incidents; it excludes remediation work, stakeholder scheduling and legally privileged processes. That is where Postmortem Backlog stops being trustworthy. If an excluded factor could reverse weeks to clear backlog, extend the model explicitly or use the authoritative account system instead of hiding the factor inside an unexplained adjustment.

Evidence and independent verification

The reference reviewed for Postmortem Backlog is Google SRE Book — Postmortem culture. Google SRE Book — Postmortem culture supports the named definition or rule but does not supply private values for weeks to clear backlog. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.

Private, reproducible calculation

Postmortem Backlog runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Postmortem Backlog inputs away from the site's calculation server, while leaving the user responsible for detecting stale data or a changed platform rule. When an assumption changes, reopen Google SRE Book — Postmortem culture and rerun the saved Postmortem Backlog scenario.