The Checklist You Rebuilt From Scratch — Twice a Week
Onboarding a client and onboarding a new hire feel like different jobs. They're the same job: repeatable steps, run on one system, with nothing left to memory.
Most practices treat client onboarding and staff onboarding as unrelated problems. One is handled by the partner who wins the work; the other by whoever has a spare hour and a half-remembered induction email. Yet if you watch what actually happens in the first week of each, they look uncannily alike: a sequence of steps that has to run in order, documents that have to be collected, access that has to be granted, and a handful of things that only ever go wrong when someone tries to hold the checklist in their head.
The reason both keep breaking is the same. Onboarding is a repeatable process being run as a one-off every time.
Two onboardings, one shape
When you bring on a new client, a predictable set of things has to happen. You verify who they are, run your AML/CTF checks, request the documents you need to start, set up the client record, send an engagement letter, get it signed, and put the recurring compliance work into your calendar so BAS, IAS, tax and ASIC dates don't slip. Miss a step and you feel it weeks later — an unsigned engagement letter, a job that stalls because you never asked for the trial balance, a lodgment obligation nobody scheduled.
When you bring on a new staff member, the shape is identical. You collect their details, set up their logins, give them access to the right clients and boards, walk them through how the practice actually runs, assign their first real piece of work, and check in before something goes sideways. Miss a step and you feel it later too — a junior locked out of the system they need on day three, or a return half-done because nobody explained where the handoff sits.
Same shape. Same failure mode. The only difference is who's on the receiving end.
Why memory is the wrong storage system
The classic onboarding runs on the person who's done it before. They know that this client type needs an extra verification step, that the engagement letter has to go out before any work starts, that the new hire needs read-only access first and write access once they've been shown the ropes. It works — right up until that person is on leave, or the pace picks up, or two clients and a new bookkeeper land in the same week.
Then the gaps appear. A document requested twice because two people didn't know the other had asked. An engagement letter that never got signed because it lived in someone's sent folder. A client added to Xero under a slightly different name, quietly starting a duplicate that surfaces months later. None of these are competence problems. They're design problems. The process was stored in a head, not in a system.
Build the sequence once, run it every time
The fix isn't a longer induction email. It's turning onboarding into a defined set of steps that the same practice management software can run for both clients and staff — so the sequence exists independently of who happens to be driving it that day.
For client onboarding, a workable sequence looks like this:
- Create the client record first. One record, spelt one way, that becomes the source of truth and syncs cleanly with Xero rather than fighting it.
- Run verification and AML alongside your PBC request — the documents overlap, so ask once, not twice.
- Send the engagement letter and get it e-signed before work begins. Scope and pricing agreed in writing, not assumed.
- Schedule the recurring obligations the moment the client is live, so BAS, IAS, tax and ASIC dates land on one calendar instead of a spreadsheet nobody opens.
- Assign the first real task — the thing that moves the engagement forward — rather than leaving the client wondering what happens next.
For staff onboarding, the same engine handles a parallel sequence:
- Set up the person and their access to the clients and boards they'll actually work on.
- Walk them through live work, not a slide deck — the boards, the recurring jobs, where handoffs sit.
- Assign a first work item with a clear owner and due date, so their first contribution is real and reviewable.
- Build in a check-in before anything can quietly go wrong.
Because Finye runs client records, work items, engagement letters, compliance deadlines and access from one place, both of these onboardings live on the same system. You define the steps once as a repeatable checklist, and every new client or new hire runs through the same sequence — no rebuilding it from memory, no forgotten step, and a trail you can actually audit afterwards.
What you get from doing it once
When onboarding is a defined process rather than an act of memory, three things change.
Nothing depends on the one person who knows. The partner who wins the work doesn't have to be the one who onboards it. A new team member can run the same sequence on their first week because the sequence is the system, not the person.
The gaps close before they cost you. The engagement letter can't be skipped if it's a step. The obligation can't go unscheduled if scheduling is part of going live. The duplicate client doesn't start if you create one clean record first.
New staff learn the practice by running it. When a new hire onboards their first client through your standard sequence, they're learning how the whole firm operates — how you handle client accounting, how work moves, where judgement is required. The onboarding process becomes the training.
Stop treating them as separate problems
The practices that scale smoothly aren't the ones with the best induction email or the most experienced onboarder. They're the ones who recognised that onboarding a client and onboarding a colleague are the same problem wearing two hats — a sequence of steps that should never live in someone's head.
Build the sequence once. Put it in the system every client and every staff member already runs on. Then the checklist you keep rebuilding from scratch, twice a week, becomes the one thing you never have to think about again.