Coverage Scoring

The Coverage Problem

A role accumulates knowledge across many domains: vendor relationships, technical systems, internal processes, stakeholder relationships, regulatory context, financial oversight, and operational dependencies. The question for successor readiness is not just whether knowledge has been captured, but whether it has been captured comprehensively across all the domains that matter for the role.

Coverage Scoring addresses this directly. It calculates a domain-by-domain view of how well each area of the role's operational knowledge is documented, and surfaces gaps — the domains where knowledge capture is thin or absent — as priority targets for improvement before a transition occurs.

Domain Taxonomy

Coverage is calculated against a domain taxonomy that is either derived from the organisation's standard role framework or configured specifically for the role being assessed. Typical domains include:

• Decisions and governance
• Vendor and partner relationships
• Technology and systems
• Operational processes and workarounds
• Stakeholder and organisational relationships
• Financial and budget context
• Risk and compliance
• Team and people knowledge
• Strategic context and forward commitments

Each memory entry is classified by domain during the Classification Engine phase, which provides the raw input for coverage calculations.

How Coverage Is Calculated

Coverage for each domain is a function of three inputs: the number of memory entries classified to that domain, the average confidence score of those entries, and the recency of the most recent entry in the domain. A domain with many entries, high confidence, and recent activity scores well. A domain with few entries, low confidence, or stale content scores poorly.

Coverage is expressed as a percentage and presented alongside a gap analysis that identifies which specific topics within each domain are absent or insufficiently documented. The gap analysis is generated by comparing the accumulated entries against a template of what a well-documented role typically contains for each domain.

Using Coverage to Drive Capture

Coverage gaps feed directly into the capture and validation workflow. When a domain is identified as undercovered, the system generates targeted prompts for the role holder: specific questions about vendor relationships not yet documented, systems not yet captured, or processes not yet described. This transforms coverage scoring from a passive measurement into an active driver of knowledge capture — particularly valuable in the months before a planned role transition.

Coverage in the Successor Readiness Score

Coverage scoring is one of the primary inputs to the Successor Readiness Score. A role cannot be considered transition-ready if significant knowledge domains are undocumented, regardless of how good the captured entries are in the domains that are covered. Coverage gives the readiness score its breadth dimension — the depth dimension is provided by confidence scoring.