Keep critical work moving through growth, leave, and transition.

Small nonprofits often rely on a few experienced people to keep work moving. That can work well for a time. Problems start when the organisation grows, someone is away or a new colleague must learn a setup that was never made clear.

Operational continuity means important work can keep going through staff changes, leave, growth and leadership handovers. The work stays clear, owned and reliable. You do not need to document everything or remove human judgement.

Strong continuity work focuses on a few critical workflows. It makes ownership and access clear. It also gives backup colleagues enough practice to handle real exceptions. The test is whether the work can continue safely—not whether the organisation has produced a large manual.

Recognise continuity risk early

• How to spot key-person dependency before it causes problems — find where knowledge, judgement, access and coordination live with one person.
• Signs your organisation has outgrown the way work gets done — distinguish a busy period from a setup that no longer fits.
• Is the process clear enough for someone new? — test whether the work can be understood without relying on verbal rescue.
• Get staff buy-in for new nonprofit software — treat adoption as an operating transition, not only a training task.

Documentation is useful—and may not be enough

Use When Documentation Is Not Enough to Reduce Key-Person Risk to find the kind of dependency involved and choose the right response:

• Knowledge: record the minimum steps, definitions, contacts and locations.
• Judgement: make decision criteria explicit and practise exceptions.
• Access: create governed backup permissions and ownership.
• Coordination: redesign handoffs, status and exception routes.
• Capacity: plan realistic coverage and priorities.
• Relationships: create shared contact and deliberate transition.

Test continuity through real work

A document alone does not make a process easy to hand over. Choose one critical workflow. Ask the backup person to complete a real or realistic cycle while the usual owner watches but does not rescue them.

1. Confirm the trigger, result and current owner.
2. List decisions, exceptions, systems and relationships.
3. Set up appropriate access.
4. Use the existing guide or create the minimum missing instructions.
5. Run the work.
6. Record every hidden explanation, file, judgement or handoff.
7. Improve the workflow as well as the documentation.

When growth or transition increases the pressure

A new leader, planned departure, extended leave, rapid growth or system change can reveal weakness that routine work has hidden. Do not respond by trying to document the whole organisation at once.

First, make work with important deadlines or risks safe. Then map the most important workflows, name who owns each decision and put the changes in order. Use What to Fix First when several issues are connected.

Choose a sensible next step

Use the diagnostic when the risk may come from process, reporting, setup or growth. Contact Simple and Engaging directly when a handover is already happening. Direct help may also fit when the risk crosses several teams or systems, or the discussion needs an independent guide.