A resignation and forty client files
Your most experienced bookkeeper hands in notice. Four weeks later they are gone, and with them the reasons behind how forty clients are handled. Why one client's director's loan is split across two accounts. Which payments to a certain supplier are really rent. That the owner of the joinery firm never answers email but always answers a text on Friday afternoon.
The person picking up the files spends their first months rediscovering all of it, often by making the mistake first. Clients notice. Some say so.
Why client knowledge never gets written down
Writing notes is extra work at the end of a job, and in a busy month it is the first thing skipped. When notes do exist they are spread around: a comment in the ledger, a note in the practice tool, an email thread, a sticky note on a monitor. Nobody wants to write a handover document in their last weeks, and a document written then is a summary of what they happen to remember.
The knowledge that matters most is also the hardest to see. It is the exceptions, not the routine, and people doing a job every month stop noticing the exceptions because to them they are routine.
The cost of knowledge walking out
Clients get asked questions they answered years ago. Mistakes happen on files that were fine for years. Holiday cover is stressful for the same reason, and sickness even more so. And the firm stays dependent on individuals, which makes both growth and sale harder, because the value of the business is partly in people's heads.
| Knowledge that gets lost | Where it could be captured |
|---|---|
| Coding rules for unusual suppliers | From the ledger's own history of how they were coded |
| Who at the client answers what | From email and portal contact history |
| When records usually arrive | From dates documents came in |
| Special arrangements and exceptions | Short notes prompted at month end |
| Past problems and how they were fixed | From review comments and query history |
How we build client notes that stay current
- We set up a single client profile page linked to your practice tool, with fixed sections: contacts and how they like to be reached, records and when they arrive, coding rules, exceptions and history.
- Parts of it fill themselves. We read the ledger through the Xero or QuickBooks API to list how recurring suppliers are coded, which accounts exist and which bank rules are in use.
- A language model reads the month's emails and query answers for that client and drafts candidate notes, such as 'client confirmed Unit 4 payments are rent'. The bookkeeper accepts, edits or rejects each one.
- At month-end sign-off, the bookkeeper is shown two or three short prompts, for example 'anything unusual this month?', rather than a blank page.
- Notes are dated and attributed, so a later reader can see how old a rule is and who set it.
- When a client moves to a new bookkeeper, the profile becomes the handover pack, and the new person confirms they have read it.
The notes live in your systems, not ours. Where your practice tool has good notes and custom fields, we write into it rather than adding another place to look.
Handovers that take an afternoon
A new starter, a holiday cover or a partner stepping in can open a client and understand it. Clients stop being asked the same thing twice. Resignations are still a loss, but not a crisis, because most of what the person knew about each client was written down while they did the work, not in a rush at the end.
Does your firm depend on memory?
- Holiday cover means phoning the bookkeeper on holiday.
- A leaver's clients took months to settle with a new person.
- Coding rules for a client exist only in how one person does it.
- Notes are spread across emails, ledger comments and sticky notes.
- Clients have complained about being asked things they already told you.