The client onboarding checklist that actually finishes
Most onboarding checklists are written for the firm, not the client. This is how to build one that gets completed — what to ask for, what order to ask in, and where onboarding usually breaks down.
Write the list for the client, not the file
Internal checklists are organised by where documents end up: compliance, billing, matter file. Clients do not think in those categories, and a list organised that way reads as bureaucracy.
Organise by what the client has to go and find. "Your last two bank statements" is one action. "Financial verification documentation" is a question they have to ask you about first.
Ask for the blocking items first
Some items block everything else — the signed engagement letter, identity verification, and whatever your compliance obligations require before work can start. Everything else can arrive later without holding up the engagement.
Putting the blocking items first also front-loads the friction. If a client is going to stall, you want to find out on day one rather than day nine, when you have already scheduled work against the file.
Keep the list short by making it conditional
A twelve-item list where four items say "if applicable" reads as a twelve-item list. Clients count what they see, and a long list gets postponed rather than started.
Use conditional logic so each client sees only their own items. A sole trader should never scroll past company constitution and director identification to find the two things they actually need to send.
Collect the signature in the same place
Splitting the engagement letter into a separate signing tool creates a second inbox, a second reminder schedule and a second status to track. It is the most common reason a client is "half onboarded" for a fortnight.
Collecting the signature alongside the uploads gives you one status per client instead of three: complete, or not yet.
Automate the chase, then get out of the way
Decide the reminder cadence once and let it run. Email for the first two nudges, SMS for the stragglers, and per-item tracking so nobody is chased for something they already sent.
The measure of a good onboarding process is how rarely a human has to intervene. If your team is manually checking who has replied, the checklist is doing half its job.
Reuse it, because onboarding repeats
The same client will owe you documents again — next quarter, next financial year, or at the next compliance refresh. Save the checklist as a template rather than rebuilding it, and set recurring runs for anything on a known schedule.
Templates also make onboarding independent of who runs it. A new team member issuing their first request should collect exactly what a partner would.
FAQ
- What should be on a client onboarding checklist?
- A signed engagement letter, identity and address verification, any compliance evidence your obligations require, the documents specific to the work, and billing or payment details. Ask for the items that block the engagement first.
- Why do clients not complete onboarding checklists?
- Usually because the list is long, written in the firm’s language rather than the client’s, and offers no visible progress. Shortening it with conditional items and showing what is left outstanding fixes most of the drop-off.
- Should the engagement letter be signed before collecting documents?
- It should be collected in the same flow rather than in a separate step. Splitting signing into another tool creates a second reminder schedule and is a common reason clients stay half onboarded for weeks.
- How often should you follow up during onboarding?
- A cadence of email at day two and day five, escalating to SMS around day seven, works for most firms. What matters more is that reminders track per item and stop the moment that item arrives.
- Can the same onboarding checklist be reused for existing clients?
- Yes, and it should be. The same client owes documents again at the next compliance refresh or financial year end, so save the checklist as a template and use recurring runs for anything on a known schedule.
Run this workflow on RequestLoops
Try RequestLoops free for 7 days. From $11/month per organisation.