Insights · businessleadersaward.com
How to map a client onboarding workflow before you automate it
In short: To automate client onboarding, first map it: list every stage from signed agreement to first delivery, then record for each step the owner, inputs, outputs, decision points, time limits and exceptions. Automate the predictable parts such as requests, reminders and status updates, and keep acceptance decisions with named people.
Client onboarding is everything that happens between a client agreeing to work with you and the first piece of real work being delivered: collecting information and documents, completing checks, setting up accounts and introducing the team. Mapping it means writing down each step, who does it and what it depends on. That map is the foundation for automation, because software can only follow a process that has been made explicit.
Many organisations skip this and buy a tool first. The result is usually an automated version of an unclear process, with the same delays now hidden inside a system.
Why map before automating
- It reveals steps that exist only in one person's head
- It shows where clients wait for you, and where you wait for clients
- It separates decisions, which need people, from logistics, which software can handle
- It exposes duplicated requests, such as asking for the same document twice
- It gives you a baseline to measure whether automation actually helped
Step 1: define the start and end
Agree what triggers onboarding and what marks it complete. A trigger might be a signed engagement letter or a paid first invoice. The end might be the client's first meeting with their account manager, or the moment all required checks are signed off. Without clear boundaries, the map grows into a description of your whole business.
Step 2: list the stages
Group the work into four to eight stages. A typical sequence for a commercial service provider looks like this:
- Welcome and introduction of the responsible contact
- Information and document collection
- Verification and internal checks
- Acceptance decision
- Account and system setup, including portal access
- Kick-off meeting and handover to the delivery team
Step 3: document each step in detail
For every step inside each stage, capture the same fields. A shared spreadsheet is enough at this point.
| Field | Question to answer | Example |
|---|---|---|
| Owner | Who is responsible? | Onboarding coordinator |
| Input | What is needed to start? | Signed engagement letter |
| Action | What exactly happens? | Send document checklist to client |
| Output | What does done look like? | Checklist sent and logged |
| Time limit | How long should it take? | Within one business day |
| Decision | Is a judgment required? | No |
| Exceptions | What can go wrong? | Client contact has changed |
Interview the people who actually do the work, not only the managers who designed it. The informal workarounds they describe, such as a reminder kept in a personal calendar, are often where automation adds most value.
Step 4: mark decisions, waits and handoffs
Go through the map and label each step as one of three types:
- Logistics: sending requests, reminders, notifications and status updates. Strong candidates for automation.
- Waits: time spent waiting for the client or a colleague. Reminders and escalation rules shorten these.
- Decisions: accepting a client, judging whether a document is adequate, approving an exception. Keep these with named people, but let the system collect the information and record the outcome.
Handoffs between teams deserve special attention. Every time work passes from one person to another, there is a risk that each assumes the other has it. Automation can assign the next owner explicitly and notify them.
A worked example
Consider a hypothetical property management company onboarding a new commercial landlord client. Before mapping, the process ran through email: the account manager sent a list of required documents, chased by phone, forwarded files to the finance team, and set up the client in the accounting system once everything arrived. Clients regularly sent documents to the wrong person, and nobody could say at a glance which clients were still incomplete.
After mapping, the company found that most delay sat in two waits: clients sending documents and finance noticing they had arrived. The automated version sends a welcome email with a link to a client portal showing a document checklist, reminds the client after a set number of days, notifies finance when the checklist is complete, and creates a task for the account manager to make the acceptance decision. The decision itself stays manual, but it is now recorded with a date and a name.
Step 5: decide what to automate first
Start with the step that is frequent, rule-based and currently causes the most waiting. Document collection with reminders is a common first choice. Leave rare exceptions manual at first; automating every edge case makes the first version slow to build and hard to change.
Trade-offs
Mapping takes time from people who are already busy, and the map will be wrong in places until it is tested against real cases. An automated process is also more rigid than an experienced coordinator, so you need a clear route for exceptions. Finally, collecting identity or financial documents brings data protection obligations: collect only what you need, restrict access, and set retention periods.
Once onboarding includes internal sign-offs, the same thinking applies to approval workflows with an audit trail.
Questions and answers
What tool should we use to map the process?
A shared spreadsheet or a simple flowchart is enough. The value is in the conversations with the people doing the work and in recording owners, inputs, outputs and exceptions consistently, not in the software used to draw the map.
Can the acceptance decision be automated?
Parts of the preparation can be: collecting documents, running completeness checks and presenting a summary. The decision to accept a client should stay with a named person, recorded by the system with a timestamp.