Org Key-Person Risk Index
72
▲ 6 pts vs last quarter
Criticality-weighted. Lower is safer. Target < 45.
4
Critical single points of failure
▲ 1 new this month
$6.4M
Total quantified exposure
▲ $0.9M
31%
Critical roles with a ready successor
▼ improving
Top exposures right now
⚡ Live alerts
▲
David Kim flight-risk rose to High while still sole owner of the deploy pipeline.
2 days ago · retention + remediation recommended
＋
New critical SPOF formed: Aisha Bello now solely owns SOC2 evidence.
1 week ago
↑
Reconciliation knowledge concentrated further into Maria Reyes (+8).
2 weeks ago
✓
ETL ownership de-risked — backup owner now active for Priya Nair.
3 weeks ago
Every person, scored on criticality × irreplaceability
Click a row for the full risk profile →
| Person | Team | Criticality | Irreplaceability | Flight risk | Successor | Risk ▼ |
|---|
Stress-test the org. Select who "leaves" and LinchpinIQ computes the blast radius — orphaned systems, stalled projects, dollar exposure, and whether anyone can backfill.
Who leaves?
Blast radius
Select one or more people, then run the simulation.
Work the plan. As you complete actions, watch the org risk index fall — that delta is your renewal case.
Projected impact
Risk index if plan completed
45
−27 points
Current index72
Actions complete2 / 7
Exposure retired$2.1M
Flight-risk × criticality = where your retention budget actually matters. These are the people who would hurt the most to lose and are most likely to walk. Spend here first.
Retention priority matrix
One click turns your live risk posture into a data-room-ready summary. Hand it to an acquirer, investor, or auditor on demand.
Key-Person Risk Posture
Northwind SaaS · Prepared by LinchpinIQ · Confidential
72
RISK INDEX / 100
Headcount in scope142
Critical single points of failure4
Critical roles with ready successor31%
Quantified exposure$6.4M
Remediation in progress−$2.1M projected
Highest-priority dependencies
Maria Reyes — Payments core & reconciliation94
David Kim — Deploy pipeline & prod access86
Aisha Bello — SOC2 / security evidence74
Methodology: capability-only analysis of contribution metadata across connected systems. No individual productivity, activity, or content monitoring. Read-only.