Source evidence
Key-person interviews, management calls, SOPs, operating reviews, role documents, and internal reports enter the protocol.
Turn interviews, calls, SOPs, and operating evidence into a structured transition record covering decision logic, relationships, process ownership, single-point-of-failure risk, successor readiness, and institutional knowledge. The departing employee, executive, founder, or specialist becomes a source of validated operating context the organization can retain.
Key person exposure
LiveLow
Owner dependency
distributed shape
3
Key persons flagged
Audit coverage
Low
Dependency
3
Key persons
2
Critical proc
5
Risks
Operating flow
The protocol structures source evidence, applies its method, records management actions, and updates the resulting operating state.
Key-person interviews, management calls, SOPs, operating reviews, role documents, and internal reports enter the protocol.
Processes, decision logic, relationships, knowledge, risks, owners, exceptions, gaps, and dependencies become mapped.
MCOS identifies concentrated knowledge, single points of failure, missing backups, successor gaps, and unresolved transfer requirements.
Teams assign successors, validate process ownership, document exceptions, transfer relationships, add missing SOPs, and close knowledge gaps.
Actions update dependency maps, transition readiness, ownership matrices, knowledge-transfer plans, and evidence-backed exports.
Ask operational questions against the audit graph and inspect entity relationships, ownership, risks, and missing evidence. Answers read only from extracted facts, with a purposeful empty state when the data isn't there.
Workspace modules
Dashboards and exports matter. The deeper value is the structured evidence, operating state, decision logic, and management workflow that can be revisited and updated.
Executive view of business health, efficiency, risk, recovery potential, action plans, and source-linked evidence.
Maps business-critical knowledge, owner dependencies, decision paths, and the institutional memory trapped in people.
Prioritizes operational, dependency, process, and cost risks by impact, severity, and remediation readiness.
Turns founder/operator knowledge into reusable operating memory with context, citations, and ownership.
Connects operational gaps and owner dependency to exit readiness, risk adjustment, and value creation potential.
Ask operational questions against the graph and inspect entity relationships, ownership, risks, and missing evidence.
Management actions
Validations, owner assignments, risk decisions, and approved changes are operating events. They should update the underlying state rather than remain comments beside a static report.
Assign Owner to Risk
Recalculates state
Resolve Dependency
Recalculates state
Validate Process Ownership
Recalculates state
Add Missing SOP
Recalculates state
Mark Action Complete
Recalculates state
Operating view
Key Person Audit makes hidden dependency, undocumented decisions, cost leakage, and process risk visible, scored, and assignable.
Inside the dashboard
Every audit opens as a working owner-dependency picture. Each module isolates one source of key-person risk and what it costs.
How much of the business lives in the owner's head, and what it costs.
Severity-toned dependency score with weighted drivers
Single points of failure and the exposure if they leave.
Influence-by-risk quadrant with person detail
What owner-dependency does to enterprise value, and how much is recoverable.
Valuation bridge, discount-band modeler
Where the business is exposed, ranked by severity.
Severity-mix bars, ranked risk register
Undocumented know-how that walks out the door.
Severity-ranked vault, single-holder flags
Who owns which processes and which have no backup.
Ownership-concentration groups
Extract the knowledge and build the bench.
Bench-readiness board, extraction sessions
A prioritized plan to de-risk the dependency.
Numbered plan, risk-to-mitigation mapping
How the audit was produced.
Agent-pipeline flow, knowledge-graph composition
Generate from the audit
Reports export as a branded PDF or a copy-ready prompt; the copilot actions launch grounded, source-backed answers. Everything reads from extracted facts only.
If a key person left tomorrow, which processes, decisions, and relationships break, answered from the audit.
Model the valuation impact and find the value a remediation plan recovers.
A 30 / 60 / 90-day transition plan for a named person, as Markdown.
The SPOF roster and succession priorities, as a branded PDF or a prompt.
The discount band and modeled dollars, as a branded PDF or a prompt.
The prioritized, numbered de-risking plan with risk-to-mitigation mapping.
Undocumented know-how, grouped and risk-scored, exported to Markdown.
A grounded ten-slide owner-readiness deck prompt.
The audit graph exported as JSON for institutional memory.
Why the numbers hold up
The dependency score is backed by weighted components, each with its value and basis, and unmeasured pieces say so rather than hiding.
Per-person share-of-dependency and a named concentration shape come from extracted knowledge-holders, not inference.
Valuation shows a directional discount band; real dollars appear only from figures you supply, with transparent math.
Every section reads only from extracted facts and shows a purposeful empty state when the data is not there.
These mechanisms are engineered to enforce accuracy by construction, but the system is under continuous improvement, and defects are corrected as they surface.
Governed output layer
Key Person Audit produces an evidence-backed operating report, business health dashboard, owner dependency map, risk inventory, and action roadmap.
Output package