The checklist comes out of the engagement type
Not one list for everybody. What gets asked for follows from what the client actually signed up to, which is what stops the over-asking that makes onboarding feel bureaucratic.
Client intake
The fourth email asking for the same document
New client onboarding is the worst possible place for your process to look improvised, and it is where it most often does.
What actually happens
Nobody decided to let this happen.
A new client says yes. Then comes the checklist that lives in somebody's head, the welcome pack assembled by copying last time's, and the slow email tennis to collect documents that the client keeps meaning to send.
It is the first real experience the client has of how you operate, and it is usually the least designed part of the whole engagement. It also delays the point where billable work can start, which makes it expensive twice over.
Work out your own number
What is this costing you?
This one is worth measuring in days as well as hours.
-
1
Days from signed engagement to everything-in-hand. Average, across your last ten clients.
-
2
Hours of your team's time spent chasing during those days.
-
3
How many of those hours belong to someone who bills by the hour.
Compressing that window is worth more than the admin hours it saves, because it moves the start of billable work forward on every engagement.
The honest version
Buy a tool, or build it?
Buy the tool if
- Your practice-management or portal product has onboarding workflows and you are not using them yet.
- Every engagement needs broadly the same documents.
- You are comfortable with clients using a vendor's portal branded as a vendor's portal.
- Nothing needs to reach systems outside that product.
Build it if
- What is needed varies by engagement type, and a fixed checklist either over-asks or under-asks.
- The collected documents have to land somewhere specific — a matter file, a compliance record, a folder structure that already has rules.
- You need the audit trail as much as the collection: who provided what, when, and what was still outstanding.
- Client experience during onboarding is part of how you differentiate, and a generic portal undercuts that.
Most practice-management products handle a decent share of this and a lot of firms have simply not switched it on. Look there first. Build when the requirement genuinely varies per engagement, or when where the documents end up matters as much as getting them.
If it is the second one
What a build actually has to do
The chase is polite, scheduled, and stops
Escalating on a cadence you set, ending the moment the document arrives. Nobody should ever be asked twice for something they already sent — that is the failure that makes a firm look disorganised.
It files, and it leaves a trail
Documents land where your rules say they land, and there is a record of what arrived when and what was outstanding. In a regulated practice the trail is often the point.
When to leave this alone
Do not build this yet if…
If you take on a handful of new clients a year, this is a checklist problem, not a systems problem. Write the checklist down properly and see whether that fixes it before spending anything.
The part most people worry about
Nothing gets authority by accident.
Every workflow I build has a setting for how much it is allowed to do on its own, and you pick it per workflow rather than once for the whole business.
It drafts, you send
The system does the assembling and the remembering. A person reads it and presses the button. Where most work should start, and where a lot of it should stay.
It runs, you get told
It acts on the rules you agreed and reports what it did. Suitable once a workflow has proven itself and the cost of a wrong move is small.
It runs, you can stop it
Fully hands-off with a switch you own and a record of every action. Appropriate for high-volume, low-judgement work, and not much else.
Straight answers
Questions this one always raises
We handle confidential client information. What does the system touch?
Settled in writing before anything is built, workflow by workflow: which systems are read, which vendors are involved, what is retained and for how long, and what is explicitly excluded. No one-word promise that everything is safe — a specific list, and anything you are not comfortable with stays out of scope.
Can clients avoid another login?
Usually yes, and it is normally the right call. Every account you ask a new client to create is friction at the exact moment you want none. Collection can happen through channels they already use, with the filing and the audit trail happening on your side where it belongs.
Where this comes up
Most common in these areas
Not a rule, just where I see it most. I work across south and east King County.
Start at the bottom of the staircase
Sixty seconds, and you will know whether this is worth another minute.
No account, no calendar, no waiting for a reply. Run the Fit Check and you get the read on your own screen. If it says the work is worth mapping, the next step is a free 20-minute call. If it says leave it alone, you have lost a minute and I have lost a customer I should not have had.
Or just write to me: bryan@perseidechocreations.com · or call 425-243-3473