Separate three kinds of instruction
Label every note:
- standard process: the firm's normal method;
- client exception: a durable variation required for this client; or
- temporary workaround: a response to a current tool, staffing, or data problem.
Without these labels, the next person may treat a workaround as policy or “correct” a necessary exception.
Build one exception card
For each exception, capture:
| Field | Question |
|---|---|
| Trigger | What observable condition tells the worker this applies? |
| Difference | Which normal step changes? |
| Reason | Why does the difference exist? |
| Evidence | What file, message, or record supports the decision? |
| Owner | Who can confirm or change it? |
| Failure | What goes wrong if it is missed? |
| Recovery | How is the mistake corrected? |
| Review date | When should the exception be challenged? |
Avoid embedding passwords, full bank details, or unnecessary personal information. Link to an approved credential or document system instead.
Observe a full work cycle
Interviewing alone tends to produce the remembered happy path. Shadow a real monthly or quarterly cycle with permission:
- the experienced bookkeeper narrates decisions while working;
- the successor marks every surprise, lookup, and client-specific choice;
- both compare the observed work with the standard procedure;
- they create exception cards only where behavior truly differs; and
- the successor performs the next cycle while the expert observes.
The final step exposes instructions that sounded clear but could not be used.
Include recovery and relationship handoffs
Some knowledge is not a bookkeeping rule. It is who responds to reminders, which person can approve a correction, how missing evidence is escalated, and when a client expects a call instead of email.
Record the channel and ownership without inventing personality profiles. Confirm with the client when the handoff changes contacts, permissions, or service behavior.
Keep the record alive
At the end of each cycle, ask:
- Did a new exception appear?
- Did an old workaround disappear?
- Did the evidence location change?
- Is the named decision owner still correct?
- Does this exception belong in the standard process now?
Assign a record owner and review date. A static departure document begins aging the day it is written.
Define a successful handoff
The handoff succeeds when the successor can complete a representative cycle, identify exceptions from observable triggers, obtain decisions from the right person, and recover one simulated mistake without relying on private memory. The artifact is the client-specific exception register—not a claim that every judgment can be reduced to a checklist.