Recurrence Rate & MTBI by Project(3.4.5)

A single incident is a problem to be solved. A recurring incident is a systemic failure that has not been addressed at its root cause. This visual shows you the recurrence rate per project — the proportion of issues that were resolved and then came back — alongside the mean time between recurrences, so you can see both the frequency and the pace of repeat failures.

A falling recurrence rate is the clearest data-side evidence that root-cause work is holding, which is typically what a NIS2 reviewer wants to see. This visual is the starting point for that evidence.

What you can conclude

• A high recurrence rate with a short mean time between incidents indicates an unresolved systemic problem — quick fixes are being applied without addressing the underlying cause.
• A low recurrence rate with a long mean time between incidents suggests the issue is isolated and the team is handling it effectively.
• Comparing recurrence rates across projects reveals whether chronic failures are concentrated in specific areas or distributed across the portfolio.

How this chart works

Bar chart showing recurrence rate and mean time between incidents per project. Use the project filter to focus on specific teams. The date filter selects which projects are listed, keeping those with incident activity in the period; the recurrence rate and the mean time between incidents are computed over each project's whole incident history, which is what makes a mean time between incidents meaningful at all.