For plant & operations managers

When the person whoknows how leaves, the know-how leaves too.

One machinist knows the fixture trick that keeps line 3 in tolerance. He’s 63, and there’s no SOP. When he retires you find out the way every plant does — a scrap spike and a six-month relearning curve. This radar scores every critical process on whether its know-how is actually captured, and forces SINGLE-POINT on the ones held by one head with nothing written down.

Get the Radar — $99one-time · instant download · yours to keep
Five deliverables · runnable
Loss-exposure radar engine
Python
Radar workbook (.xlsx)
.xlsx
Knowledge-capture interview guide
.docx
Capture-queue runbook
.docx
Seven-process worked sample
.csv
Works alongside
Key-Person Risk Audit · Manufacturing Ops Pack · Doc-Processing Diagnostic
01.The Problem

The retirement cliff is a documentation problem wearing a headcount problem’s clothes.

1 head

is all it takes. The critical procedure with no written SOP and one person who can run it is a single point of failure the org chart doesn’t show.

6 months

is a common relearning curve after an unplanned departure — rediscovered the expensive way, in scrap and downtime, because the know-how was never captured.

“we’ll write it up”

is where tribal knowledge goes to stay tribal. A draft nobody has run is a rumor, not an SOP — and this radar refuses to count it as one.

Every AI vendor is selling knowledge-management platforms and semantic search over documents you haven’t written yet. None of them tell you which undocumented process to capture first, before the person who holds it walks out the door. That is a triage problem, and it is exactly what this radar does.

02.See It Work

Grade a process. Watch the gate release when you train a backup.

Live radar · evaluated 2026-06-30

Criticality
Documentation depth
Qualified operators
1
Soonest departure (months)
SINGLE-POINT
43
capture score
Capture first · departure ≤ 12 mo

Fix: Write & validate the SOP (reach depth 3), or qualify a 2nd operator

Critical, held by one operator, no verified SOP — the single-point trap. Train a second operator or reach a validated depth-3 SOP and it releases.

Scores a process, never a person. Deterministic and offline — your inputs, no benchmark multiplier.

The worked process is critical, held by one operator, with only a draft SOP — SINGLE-POINT, and flagged capture-first because the operator leaves in eight months. Train a second operator, or take the SOP to a validated depth 3, and the same process releases. The gate never fires on a well-staffed process, so it never cries wolf.

03.The Engine

One command reads your process list and builds the capture queue.

$ python3 tk_radar.py sample_processes.csv --as-of 2026-06-30
====================================================================
TRIBAL-KNOWLEDGE LOSS EXPOSURE RADAR  -  RedHub AI  (TKR-099)
Evaluation date: 2026-06-30
====================================================================

Process: Line 3 fixture alignment
  Criticality / Depth / Operators : 3 / 2 / 1
  Soonest departure               : 8 mo
  Capture score                   : 43  <- single-point, departure <= 12 mo
  VERDICT                         : SINGLE-POINT
  Fix                             : Write & validate the SOP (reach depth 3), or qualify a 2nd operator

Process: Line 3 fixture alignment (2nd op trained)
  Criticality / Depth / Operators : 3 / 2 / 2
  Soonest departure               : 8 mo
  Capture score                   : 43
  VERDICT                         : THIN
  Fix                             : Deepen documentation toward a verified SOP

Process: Furnace ramp recipe
  Criticality / Depth / Operators : 3 / 3 / 2
  Soonest departure               : 24 mo
  Capture score                   : 100
  VERDICT                         : CAPTURED

Process: Weekly CMM calibration
  Criticality / Depth / Operators : 2 / 1 / 1
  Soonest departure               : 40 mo
  Capture score                   : 21  <- single-point
  VERDICT                         : SINGLE-POINT
  Fix                             : Write & validate the SOP (reach depth 3), or qualify a 2nd operator

Process: Palletizer jam clear
  Criticality / Depth / Operators : 1 / 0 / 3
  Soonest departure               : 36 mo
  Capture score                   : 0
  VERDICT                         : UNDOCUMENTED
  Fix                             : Document this process - it is undocumented

Process: Legacy PLC changeover
  Criticality / Depth / Operators : 2 / 0 / 1
  Soonest departure               : 5 mo
  Capture score                   : 0  <- single-point, departure <= 12 mo
  VERDICT                         : SINGLE-POINT
  Fix                             : Write & validate the SOP (reach depth 3), or qualify a 2nd operator

Process: Shipping label reprint
  Criticality / Depth / Operators : 1 / 2 / 4
  Soonest departure               : 60 mo
  Capture score                   : 67
  VERDICT                         : CAPTURED

--------------------------------------------------------------------
PLANT KNOWLEDGE VERDICT : EXPOSED
Capture first           : Legacy PLC changeover  (depth 0, 1 operator(s), departure 5 mo)
--------------------------------------------------------------------
Scores a process, never a person. Deterministic and offline - your
inputs, no benchmark multiplier. Not HR or legal advice and not
grounds for any employment decision.

Stdlib-only Python. Same process, one vs. two operators, prints SINGLE-POINT then THIN — the gate doing work the capture score alone can’t. A well-staffed but undocumented process reads UNDOCUMENTED, not a false alarm. The workbook reproduces these exact verdicts, and the demo above computes the identical numbers — verified byte-for-byte on the shipped sample.

04.The Standard

Three rules keep the radar honest.

Only a verified SOP counts

A document nobody else has run is a rumor. Capture is proven when someone other than the original holder executes the process from the document alone — depth 3, nothing less.

Single-point is an intersection

Critical, solo-held, and undocumented — all three at once. A well-staffed process is never a false single-point alarm. Either half clearing releases the gate.

Urgency orders, never softens

The departure horizon decides which single-point process to capture first. It sequences the queue; it never changes a verdict. The risk is structural, not calendar-driven.

05.What It Is — And Isn't

A capture-triage radar for processes, not a scorecard for people.

What it is
  • A deterministic, offline radar over the critical processes you already run.
  • A capture queue — which undocumented process to write and validate first.
  • The process-grain companion to the Key-Person Risk Audit’s person grain.
What it isn’t
  • It scores a process, never a person — no field for anyone’s performance.
  • Not a knowledge-management platform, wiki, or document search — it triages, you capture.
  • Not HR or legal advice and not grounds for any employment decision.
06.Who It's For

Anyone staring down a retirement cliff or a thin bench.

Built for
  • Plant and operations managers with aging, tenured crews
  • Continuous-improvement leads building an SOP capture program
  • Quality and EHS teams who need procedures documented and validated
  • Owners preparing a business for sale or succession
Not built for
  • Evaluating or ranking employees — it scores processes
  • Plants that want a wiki instead of a capture priority
  • Real-time monitoring — this grades a documentation posture
  • Replacing the actual SOP writing — it tells you what to write first
08.Common Questions

The honest answers.

They work at different grains and answer different questions. The Key-Person Risk Audit scores a person — how load-bearing one individual is across relationships, knowledge, authority, and output, to answer “could the business run if this person vanished.” This radar scores a process — whether the know-how to run one specific operation is written down in a form someone else could execute, to answer “if we lose the person who does this, does the procedure leave with them.” A person can be well-backed in the audit and still be the sole holder of an undocumented critical procedure here. The audit's fix is usually cross-train or insure a person; this radar's fix is write and validate the SOP. Run the audit for continuity and diligence; run the radar to build your capture queue.

Capture it before
it walks out the door.

One purchase, lifetime access, 12 months of updates. $99, once.

Sold by RedHub AI LLC · Secured by Stripe · redhub.ai