When Documentation Is Not Enough to Reduce Key-Person Risk

When important work depends on one person, “document the process” is sensible advice. It is also incomplete.

Documentation makes steps, meanings and instructions easier to find. But it cannot share one person’s judgement with the team. It cannot name a backup owner, fix a weak handoff or simplify a process. It also cannot give someone practice with unusual cases.

You should still document the work. The bigger question is what else must change. The work needs to continue without one person acting as the organisation’s memory, translator and safety net.

What documentation can solve

• Make a recurring sequence visible.
• Record definitions, locations, contacts and deadlines.
• Explain the normal route through a task.
• Give a new or backup colleague a reliable starting point.
• Reduce repeated questions about routine steps.
• Preserve decisions that would otherwise disappear into memory.

For stable, repeatable work, that may be enough. A short checklist, decision record or annotated example can be more useful than a long process manual.

What documentation does not solve

• Unclear ownership: a document does not decide who acts, approves or follows up.
• Hidden judgement: experienced staff may make decisions using context they have never expressed.
• Fragile handoffs: instructions do not make status visible or confirm that the next person accepted the work.
• Excessive complexity: documenting every workaround can preserve a process that should be simplified.
• System access and configuration: a backup still needs appropriate permissions, credentials, reports and knowledge of the setup.
• Relationships: trust, informal contacts and stakeholder expectations cannot be transferred through a checklist alone.
• Practice: someone who has read the process may still be unable to handle a live deadline or exception.

Find the kind of dependency

Map one critical workflow before writing more

Start with work that matters most. Ask what would harm deadlines, finances, reports, services or trust if the usual person were away.

1. Name the trigger and expected result.
2. List the essential steps and decisions.
3. List systems, files, contacts and access.
4. Mark every point where the usual person uses judgement or remembers an exception.
5. Name the current owner and a credible backup for each stage.
6. Record how status is shown and how handoffs are accepted.
7. Test the workflow with the backup person while the usual owner is available.
8. Revise the work, not only the document, when the test exposes friction.

The test matters. A process that looks complete on paper may still depend on explanations, personal files, unrecorded decisions or access that no one else has.

Choose the right level of support

Documentation may be enough when

• The work is stable, narrow and low risk.
• Ownership and access are already shared.
• Exceptions are rare and easy to describe.
• A backup can complete the task after using the guide once.

Add cross-training when

• Judgement and context matter.
• The work has time-sensitive or high-stakes exceptions.
• A backup needs live practice, not only written instructions.
• The organisation needs more than one person able to review quality.

Redesign the workflow when

• The usual person is a permanent human shock absorber between unclear teams, systems or decisions.
• The process contains repeated chasing, translation, checking or cross-checking.
• No single document can explain the work because it changes according to who is involved.
• The backup test reveals that status, ownership or exceptions are not explicit.

Use guided handover or outside support when

• A departure, leave period or leadership transition is approaching.
• The dependency crosses several teams or systems.
• The current owner cannot guide the handover while carrying the work.
• Role boundaries or priorities need an independent discussion.
• Failure would seriously affect reporting, finance, service delivery or organisational confidence.

A focused 30-day continuity test

1. Week 1: choose one critical workflow and list the types of dependency.
2. Week 2: simplify the normal route, document the minimum and set up backup access.
3. Week 3: have the backup person complete a real or realistic cycle while the usual owner observes rather than rescues.
4. Week 4: fix the points that required hidden knowledge, clarify ownership and schedule the next test.

Do not judge success by whether you produced a document. Ask whether the work continued safely. Could the backup see the status and unusual cases? Did the usual owner avoid stepping in behind the scenes?

Related guides

• How to spot key-person dependency before it causes problems
• When reporting depends too much on one person
• How to tell if a process is clear enough for someone new
• Signs your organisation has outgrown the way work gets done

Browse the Operational Continuity hub for the full growth, handover and key-person pathway.

When the Nonprofit Operations Review is useful

The Nonprofit Operations Review is useful when one important workflow depends too heavily on one person and you need an independent view of what to make stable first.

The review looks at the workflow, handoffs, ownership, hidden knowledge and current workarounds. You receive an Operational Friction Map, clear priorities and a practical 90-day plan. It will also say honestly which changes your team can handle internally and where outside support may be useful.

If a departure or extended absence is imminent, several critical workflows are exposed, or deadlines are already at risk, you may need broader continuity support rather than a review of one workflow.