Coverage Scoring
Coverage scoring identifies single points of failure in your team's knowledge distribution. It measures how well critical knowledge is spread across the team so that no single departure creates a crisis.
Team Coverage
The team-level coverage is displayed in the Team Dashboard as a percentage with three topic categories:
- Captured Topics — knowledge areas where at least two people have documented expertise
- At-Risk Topics — areas where knowledge exists but is concentrated in one person
- Critical Topics — areas where no one has recorded sessions or documentation
The overall coverage percentage represents the ratio of well-covered topics to total identified topics.
Per-Member Coverage
Each team member has an individual coverage score shown in the Knowledge Coverage Bar on the Team Dashboard. This shows:
- Member name and email
- Personal coverage score (percentage)
- Number of knowledge sessions recorded
Bus Factor Score
The Handoff Report includes a Bus Factor Score (0–100) for each employee, measuring how much risk their departure would create:
| Score | Label | Meaning |
|---|---|---|
| ≥ 70 | Healthy | Knowledge is well-distributed; departure is manageable |
| 40–69 | At Risk | Some knowledge gaps; transfer needed before departure |
| < 40 | Critical | Significant single-point-of-failure risk |
The score is color-coded: green (healthy), yellow (at risk), red (critical).
Critical Gaps
When a Handoff Report identifies critical gaps, each gap includes:
- Topic — the knowledge area at risk
- Severity — critical, high, or medium
- Reason — why this gap exists (e.g., "only person with production access knowledge")
- Recommendation — suggested action to close the gap (e.g., "schedule knowledge transfer session with backup engineer")
Safe Topics
Topics with adequate coverage are listed as Safe Topics, each showing the topic name and its coverage level (e.g., "Well covered", "Documented").
Action Plan
Every Handoff Report concludes with a numbered action plan — specific steps to transfer knowledge before a departure or role change.
Data Sources
Coverage data comes from goSvc.getTeamCoverage() which analyzes:
- Knowledge sessions recorded per topic per person
- Documents authored and their subject matter
- Manual topic assignments in knowledge profiles
- Cross-referencing who knows what across the team