The bottleneck is almost never your team
Ask a service firm where onboarding time actually goes and the answer is rarely the work. It is the waiting: identification documents, signed terms, access credentials, brand assets, last year's figures, the technical specification. Each one was requested once, in an email, in a list, alongside four other things — and each one now sits in a thread nobody owns.
The client is not being difficult. They received one message containing six requests, of which they could action two, and there has been no reminder since because chasing a paying client for paperwork is the least comfortable job in the business.
One list, one status, visible to both sides
The fix is unglamorous: every required item as its own tracked line with its own state — requested, received, checked, still outstanding — visible to the client as well as your team. Most of the friction disappears the moment the client can see exactly what is still needed without having to reread an email thread, and your team can see the same thing without asking each other.
Where a client portal already exists, this belongs inside it rather than beside it.
Where the process actually breaks down
- Six documents requested in one email, of which two arrive and four are never mentioned again
- Files returned by reply, so the current version lives in an inbox rather than anywhere findable
- Nobody chasing, because chasing a client for paperwork feels rude and belongs to no one in particular
- No record of what was asked for, when, or what is still outstanding — so the next conversation starts by reconstructing it
- Work starting anyway on incomplete information, and being redone later
Chasing that is a process, not a favour
Reminders go out on an agreed schedule and name the specific items still outstanding, so the client always sees the short list rather than the original one. Because the cadence was agreed up front, nobody has to decide whether today is the day it becomes acceptable to ask again.
When everything is in, the person waiting to start the work is told — which is the step that most often gets missed even when the documents did arrive.
Handling sensitive documents responsibly
A lot of what gets collected is sensitive: identity documents, financial records, contracts. Collect only what is genuinely required, keep it somewhere with real access control rather than in an inbox, and be able to say who accessed what. Those are baseline engineering standards we build to; they are not a claim of certification on your behalf, and your own regulatory obligations remain yours.
What this does not do
It does not verify identity documents, check legal validity, or approve anything. It asks, tracks, reminds and records — the review and the judgment stay with your team. For what happens after everything is in, see onboarding automation; for tracking sign-off on what you send back out, see Client Approval Automation.
Questions
Isn't this what our onboarding email already does?+
An onboarding email makes the request once. This tracks each item separately until it arrives, reminds about only what is still missing, and tells the person waiting when the set is complete — which is where the email approach quietly fails.
Where do the documents actually end up?+
Wherever your team already works — an existing portal, document store or system of record. Creating a second place for files to live would recreate the problem it is meant to solve.
Does it check whether a document is valid?+
No. It confirms something was provided for a required item; whether it is correct, current and acceptable is a judgment your team makes.
Can clients see what is still outstanding?+
Yes, and that is most of the value. When the client can see the remaining list themselves, a large share of the chasing stops being necessary.