- A spreadsheet checklist is a description of the process, not the process itself — it can't enforce steps or track progress automatically
- When onboarding is spread across spreadsheet, email, Slack, and shared drive, status is always someone's memory
- The fix is tying onboarding tasks to the client record so completion is automatic and visible
- The result: faster onboarding, less chasing, and a clear record of what happened and when
Picture the onboarding process your business runs for a new client. There's probably a checklist somewhere — Google Sheet, Notion template, a Word document that gets copied for each new client. It was accurate when it was written. It's probably slightly out of date now, because the process evolved and the document didn't.
Someone sends the checklist to the client coordinator. They send the intake form by email. The client returns it by email. Someone saves it to the shared drive, then messages Slack to say it's arrived. The account manager checks it off in their copy of the spreadsheet. Then chases the client for the document they forgot to attach. Then updates the CRM note to say onboarding is at "stage 2." Then asks if the compliance check has been run yet.
This is not a process failure. It's what happens when you use documentation tools to manage an operational process. The checklist describes what should happen. It cannot make it happen.
Related HubSecure buying path
Secure Client Portal guidesecure client portalRooms moduleGoogle Workspace comparisonsecure client portal guideGuide Librarybook a workflow demo
Related secure document collection resources
Continue with secure document collection, document collection checklist, secure client portal, Secure Vault module, security and trust center.
Related use case
This guide belongs to the Secure Document Collection Guides cluster. Continue with the product hub for secure document collection.
The symptoms of a broken onboarding workflow
"Has the client sent everything yet?"
Nobody knows without asking someone. Status lives in someone's inbox or in their mental model of the process — not in a system everyone can check.
Multiple chase emails for the same document
The client gets three separate requests for their ID because the team member who sent the first request is on holiday and two other people didn't know it had been sent.
Documents saved in the wrong place
The intake form arrives by email. One team member saves it to the drive. Another prints it. A third replies directly to the email. Now there are three different locations for the same document.
Onboarding takes longer than it should
The actual work of onboarding — verifying identity, running checks, collecting documents — doesn't take 3 weeks. The coordination overhead does.
"Where did we get to with Client X?"
The new team member covering for a colleague can't tell without asking around or reading through an entire email thread to reconstruct the current state.
Why another template won't fix this
The instinct when the checklist is causing problems is to improve the checklist. Make it more detailed. Add a progress column. Build a fancier Notion template. Add a Slack notification when something is checked off.
The problem is not the template. The problem is that the template is separate from the CRM, separate from email, separate from document storage, and separate from the compliance workflow. Every piece of information about the onboarding has to be manually recorded in the template — and the people doing the work don't always remember to do that.
The template can describe the process perfectly and still not know that the client sent their ID documents because that happened by email and nobody updated the sheet.
The structural issue: A checklist is read-only documentation of a process. An onboarding workflow is a live, active system that tracks state automatically as things happen. If your checklist can't update itself when a document arrives or a task is completed, it will always lag behind reality.
What a connected onboarding workflow looks like
The spreadsheet way
- Checklist in Google Sheets — manually updated
- Intake form sent by email — response in inbox
- Documents saved to shared drive — manually, inconsistently
- Status known only to the person managing the thread
- Compliance check run in separate tool — result noted manually in CRM
- Average time to complete: 2–4 weeks
The connected way
- Tasks created from CRM client record — auto-assigned, tracked
- Intake form sent from CRM — response goes to client record
- Documents go to Vault, attached to client record automatically
- Status visible to anyone with access — no asking around
- Compliance check triggered automatically — result on client record
- Average time to complete: 3–7 days
The specific workflow that makes the difference
The key change is not replacing the checklist with a better checklist. It's making the tasks exist inside the system that manages the client — not in a separate document that someone has to keep updated manually.
When a new client is created in the CRM, a set of onboarding tasks is automatically created and assigned. "Send intake form" is assigned to the account manager. "Run identity verification" is assigned to the compliance officer. "Review signed agreement" is assigned to the responsible partner. Each task has a due date. Each task has a clear owner.
When the intake form comes back — because it was sent from within the CRM and responses return to the same record — the task updates automatically. The account manager doesn't need to remember to tick a box. The team can see the status at any point without asking anyone.
When the client uploads their documents via the client portal or the secure link, those documents go to Vault, attached to their record. The document request task closes. The compliance officer sees the documents are ready without a Slack message.
When the compliance check clears, the CRM record updates. Deal progression unblocks. The next stage of work begins — without anyone having to manually update a spreadsheet to say "onboarding complete."
What this means for the client experience
The client experience in a fragmented onboarding is: multiple emails from different people, some of them asking for the same thing, with inconsistent communication about what's needed and what's already done. The client doesn't know where the process stands any more than your team does.
In a connected onboarding, the client receives one clear request listing everything needed. They upload to one place. They sign in one place. They can see the status of their onboarding — what's done, what's pending — without emailing someone to ask. First impressions matter, and a client who is onboarded smoothly starts the relationship with more confidence in your organisation.
Can we customise the onboarding tasks for different client types?
Yes. You can create different task templates for different client types — for example, individual clients vs. corporate clients, or standard onboarding vs. enhanced due diligence. When a new client record is created, the correct template is applied based on client type.
What if part of our onboarding process is handled by a third party (e.g. an external ID verification provider)?
HubSecure integrates with external identity verification providers via API. The verification result comes back to the client record automatically. For providers without a direct integration, we support webhook callbacks that trigger task completion when the external step is done.
See client onboarding as a connected workflow
We'll walk through a complete onboarding — intake, document collection, identity check, signature, and CRM update — all from one client record.
Book a demoReviewed for regulated teams
Prepared by the HubSecure editorial team for operators, compliance leaders and IT reviewers evaluating secure client operations software.