Onboarding & Knowledge Transfer
When Knowledge Lives With One Person
Capture one critical task—and check whether someone else can use the guidance.
Published · Updated · 2 min read
If a key employee were unavailable next week, what would become confusing first?
The answer may be a grant report, board packet, donor workflow, or recurring program task. Someone knows the steps, file locations, history, and exceptions, but the rest of the team relies on asking them.
Start there. You do not need to document everything to address one important coverage gap.
Choose a task with a real consequence
Prioritize work that is time-sensitive, difficult to reconstruct, or essential to an organizational commitment.
Ask the person who knows it best:
- What would a backup be most likely to miss?
- Which decision requires context?
- What looks routine but needs approval?
- Where does the current information live?
Reserve time for this work. Do not make knowledge transfer an invisible addition to an already full workload.
Create a short continuity note
Capture:
| Element | What the backup needs |
|---|---|
| Trigger | When the task starts or becomes due |
| Owner and backup | Who normally handles it and who covers |
| Inputs | Required information and approved file locations |
| Steps | The sequence needed to complete the task |
| Decisions | Routine boundaries and exceptions |
| Completion | How to check that the work is done |
| Help | Who can resolve a problem |
Link to approved systems and access procedures. Do not place passwords or confidential records in a general instruction document.
Test the note with a backup
In a hypothetical nonprofit, a program manager documents a recurring report. A colleague walks through the instructions using approved practice material.
The colleague finds the template but cannot tell which reporting period to select or who authorizes submission.
Those gaps are useful findings. Update the note, confirm the approval boundary, and test again.
The goal is not a finished document. It is an arrangement someone else can use within their role and authority.
Keep the knowledge current
Name the owner of the guidance and record when it was last checked. Update it when the work changes.
If the task is part of a new employee’s role, include it in onboarding and supported practice.
Start with one critical task and one backup.
Oh, BTW—if you're curious about the costs behind everyday operational friction, I made an operations and funds check. Take the Operations & Funds Check