Skip to content

KEY PERSON AUDIT / BUILT ON MCOS

Capture critical knowledge
before a key person leaves.

Turn interviews, SOPs and operating evidence into a reviewable transition record. See the people, processes and decision rules the business depends on—and what still needs to be captured, practiced or confirmed.

Pilot-stage protocol · Agent-assisted analysis · Human review

FROM ONE PERSON’S KNOW-HOWILLUSTRATIVE
DISPATCH / RECORDED EXCERPT
“The workaround isn’t
in the dispatch guide.”
Dana / fictional interview
KNOWLEDGE / COVERAGE / NEXT STEP

Capture the exception.
Check who can carry it.

A named observer is a starting point. Capability still needs review.

HANDOVER NOT ESTABLISHED
Fictional example. A record of knowledge is distinct from a completed transfer.

The person can leave. The next agent or reviewer still needs the operating context, the exceptions and the open questions.

Follow the knowledge

ONE EXCEPTION. A REVIEWABLE HANDOVER.

Capture what they know.
Inspect what can carry forward.

Follow a dispatch workaround from interview evidence to a proposed transfer and the record the business keeps.

NORTHLINE DISPATCH / FICTIONAL EXAMPLEInteractive example · No live analysis

01 / CAPTURE THE CONTEXT

The procedure is more than a job title.

The attached interview excerpt points to an exception the written guide may not cover. Keep the saved account and its qualifications with the knowledge note; the decision rule itself still needs to be captured.

Work
Rush shipment dispatchA carrier cut-off change triggers a workaround.
Knowledge
Dana’s exception handlingThe actual rule and its limits still need to be captured.
Coverage
Maya observed onceIndependent execution is not established.

“Only I know” is the speaker’s assertion. It is a reason to investigate coverage, not proof that no backup exists.

01 / 05Capture

Illustrative saved records, not a live KPA result. The example demonstrates review and retention; it does not establish a successful handover or measured business outcome.

THE KPA WORKSPACE

People. Processes. Exceptions.
A clearer place to review them.

Agent-assisted analysis organizes the audit. Focused views help people inspect the evidence and decide what needs attention.

01 / PEOPLE & DEPENDENCY

See who the work depends on.

Review the audit’s dependency assessment alongside the people and responsibilities recorded.

Explore the modules

Audit Overview

The recorded dependency picture, quality notices and documentation-progress context. Derived progress is distinct from a new model reassessment.

Key People

Recorded roles, process connections, knowledge and coverage questions. A job title does not establish sole dependency.

02 / PROCESSES & KNOW-HOW

Find the knowledge between the steps.

Inspect process ownership, documentation and the exceptions people carry in their heads.

Explore the modules

Process Map

Recorded processes, owners, criticality and documentation status, with attached evidence where supplied.

Tribal Knowledge

Knowledge notes, named holders, recorded excerpts and transfer assertions. Captured knowledge remains distinct from demonstrated capability.

03 / EXPOSURE & QUALIFICATIONS

Keep the open questions visible.

Review the risk narrative and the assumptions behind any financial framing.

Explore the modules

Risk Watch

Saved risk entries, recorded mitigation and supporting excerpts where available. A response written down is not evidence of risk reduction.

Valuation

Inspect the saved valuation context and assumptions. Recorded amounts and scenarios are not an independent valuation or promised financial outcome.

04 / HANDOVER & ACCOUNTABILITY

Prepare the transfer. Review the evidence.

Turn recorded gaps into questions and proposed next steps the business can review.

Explore the modules

Succession

Recorded readiness and backup fields, capture activity and a proposed transition sequence. Documentation receipts do not establish readiness.

Action Brief

Saved recommendations, separate risk responses and proposed planning questions. A generated plan still needs human review.

Decision Trail

Available run outcomes, stage issues and recorded review history. A completed report alone does not establish successful model processing.

Knowledge Graph access is enabled per engagement. Inspect recorded nodes and connections, then review their fields and qualifications. Connections are not independent proof of source support.

KNOWLEDGE THE BUSINESS CAN KEEP

The agent organizes the audit.
The business keeps the context.

When the person, agent or team changes, the next reviewer needs more than a finished recommendation. Keep the recorded basis and the questions still open.

  • Inspect saved people, processes and knowledge notes.
  • Keep recorded coverage separate from demonstrated readiness.
  • Export module reports and graph records within their stated scope.
Inspect the example files
THE RETAINED AUDITSCOPE MATTERS

The recorded knowledge

Notes, holders and excerpts where supplied.

01

The coverage questions

Processes, backup fields and readiness qualifications.

02

The proposed next steps

Recommendations and planning questions, separate from completed work.

03
What the record does—and does not—establish

Exports retain the saved fields within each report’s scope. Source excerpts are available where attached; a graph snapshot is not the full audit or source-companion package.

Documentation progress, model reassessment, transfer assertions and readiness are different records. None automatically proves reduced operational risk, financial improvement or complete successor coverage.

Human review and accountable decisions remain part of the handover. Retaining a record does not make arbitrary agents or models interchangeable.

START WITH ONE CRITICAL HANDOVER

Keep the knowledge.
Make the next step reviewable.

Bring one role, process or transition. We’ll identify the evidence to capture, the coverage questions and the checks a pilot would need.