Continuity coverage
Where an answer is missing, where it exists but was never rehearsed, and why those are not the same gap.
Two different questions
Coverage answers two things that are often collapsed into one metric. First: are there business processes with no recovery strategy at all? Second: among those that have one, how many have a primary strategy nobody validated, or validated long ago?
Separating them matters because the work differs. An uncovered process requires deciding what to do. A stale strategy requires scheduling an exercise. A single "coverage" number would hide the second behind the first.
What counts as stale
A primary strategy never validated, or validated more than twelve months ago, enters the stale list. The assessment is about the primary — the one the organization intends to execute — not about the set of alternatives.
Strategies of the accept type are excluded: accepting is a recorded decision, not a procedure to rehearse. Chasing them would create a gap that is structurally impossible to close.
The ruler comes from the BIA
Not every uncovered process weighs the same. The criticality that orders the list comes from the BIA, along the process → product → impact assessment chain. A process sustaining a critical product with no strategy is a different conversation from a support process in the same state.
That also means the reading depends on the chain being mapped. A process with no associated product has no derived criticality, and coverage does not invent one.