03 Onboard Cornerstone guide
How to build a client onboarding process that makes delivery ready
Onboarding is not a welcome email. It is the stage that turns a signed agreement into an engagement your team can actually deliver: owned, informed, prepared and agreed.
- 01SIGNED
- 02WELCOME
- 03COLLECT
- 04PREPARE
- 05KICKOFF
- 06HANDOFF
A client saying yes does not mean the business is ready to deliver. Between the signature and the first piece of real work, a surprising amount must happen: the engagement needs an owner, the client needs to know what to expect, the inputs need to arrive and be usable, both sides need to be ready and the first milestone needs to be agreed.
When that happens informally, the symptoms are familiar. Delivery starts while information is still missing. The client asks what happens next. Kickoff becomes an information-gathering meeting instead of a decision-making one. The delivery team learns about a promise made in the sale only when the client mentions it.
This guide sets out six onboarding stages: signed, welcome, collect, prepare, kickoff and handoff. Each has an owner, an output and a check, so that onboarding ends with a delivery-ready engagement rather than a hopeful start.
Accept the signed engagement with an owner
Onboarding begins when the commercial side hands over the signed engagement. The first act is acceptance: a named onboarding owner confirms they have the signed scope, contacts, promises and risks, and that anything missing is listed.
AvariHQ recommendation
Do not start welcome messages until an owner has accepted the engagement. A welcome sent by nobody in particular is how clients receive three different 'next steps' from three people.
Welcome the client before asking for effort
The welcome has one job: help the client understand what happens next, who their contact is and what will be asked of them. Ask for effort only after you have explained why it matters.
Service blueprinting, a technique from service research, maps the customer's own actions alongside the provider's visible and behind-the-scenes work. It treats what the client must do as part of the service to be designed, not assumed. That is the basis of a good welcome.1
- Who their main contact is, and how to reach them
- What happens in the next two to four weeks
- What the client will be asked to provide, and by when
- How decisions and approvals will be made
- How and when they will hear about progress
Collect inputs once, and check they are usable
Most onboarding delays come from inputs: access, files, brand assets, data, contacts or decisions that arrive late, incomplete or in a form delivery cannot use. Ask once, in one structured request, and review each input on arrival.
| Input | Needed for | Due | Status |
|---|---|---|---|
| Current client list (CSV) | Setup, week 1 | Day 5 | Received, usable |
| Brand guidelines | Template design | Day 5 | Received, out of date: requested update |
| Approver name and backup | Review rounds | Day 3 | Outstanding |
AvariHQ recommendation
Mark each input Received, Usable or Needs follow-up. 'Received' is not the same as 'usable', and the difference is where onboarding time disappears.
Prepare by checking readiness on both sides
Before kickoff, run a short readiness check. On your side: the team is assigned, the scope is understood and the plan for the first milestone is drafted. On the client's side: the inputs are usable, the approver is named and the people needed for kickoff are available.
If something important is missing, move the kickoff rather than holding a meeting that cannot reach decisions. A short, honest delay at this point is far cheaper than a confused start.
Agree the operating baseline at kickoff
A good kickoff is a decision meeting. It confirms the outcomes, the roles and decision rights, the communication rhythm, the first milestone and its acceptance criteria. Everything else can be shared in advance.
The kickoff that became discovery, a hypothetical scenario
A bookkeeping practice holds a 90-minute kickoff with a new client. Forty minutes go on finding logins and asking which accounts are in scope. No first deadline is agreed.
The practice moves those questions into a pre-kickoff input request and a readiness check. The next kickoff takes 45 minutes and ends with three recorded decisions: the approver, the reporting rhythm and the first month-end close date.
Hand off a delivery-ready engagement
Onboarding ends when the delivery team accepts the engagement, with the agreed scope, inputs, decisions, contacts and first milestone. The receiver should be able to say Accepted, or list what is missing, before delivery begins.
Healthcare safety guidance recommends standardized hand-off tools and a chance for the receiver to ask questions. AvariHQ applies the same principle to the onboarding-to-delivery handoff by analogy.2
For a deeper look at the gap after the sale, read Why client onboarding breaks down after the sale. Delivery continues in How to control project delivery, scope changes and client approvals.
Put it into practice
Name the onboarding owner
Accept the signed engagement and list anything missing from the sale.
Send one welcome
Explain what happens next, the contact, the client's role and the rhythm of updates.
Request inputs once
One structured request; review each input as Received, Usable or Needs follow-up.
Check readiness
Both sides ready before kickoff; move the date if not.
Run a decision kickoff
Confirm outcomes, roles, rhythm, first milestone and acceptance criteria.
Hand off to delivery
The delivery owner accepts the engagement or lists what is missing.
The takeaway
Onboarding is complete when delivery can begin without chasing the client for information. Design it as a stage with owners and checks, not as a welcome sequence.
The free New Client Onboarding Checklist covers all six stages with the checks to complete before each step.
Sources & further reading
Numbered notes in the text refer to these sources. Findings keep their original populations, dates and limits. Operating advice marked as an AvariHQ recommendation is our own guidance, not a research finding, and the scenarios in this guide are hypothetical.
Bitner, M. J., Ostrom, A. L. and Morgan, F. N., "Service Blueprinting: A Practical Technique for Service Innovation", California Management Review 50(3) (2008).
Peer-reviewed research. A design technique illustrated with case examples; it describes a method rather than measuring outcomes.
The Joint Commission, Sentinel Event Alert 58: Inadequate hand-off communication (12 September 2017).
Cross-domain standard. Healthcare and patient safety. Used only as an analogy for business handoffs.
Free tool Word
New Client Onboarding Checklist
From the signed agreement to the start of delivery, for every new client.
The complete method
03 / SYSTEMONBOARD
The Client Onboarding System
84-page System Guide, 6 tools and editable records. $149, USD, one-time purchase.
See what’s includedWhere to go from here
Measure it
The Client Operations Assessment
Score all seven stages and find where to start. About ten minutes; nothing is stored.
Take the assessmentRun it in software
AvariHQ Client portals and forms
Give clients one place for welcome information, input requests and progress.
Explore Client portals and formsGet help
Launch Assist
Get guided help setting up your onboarding in AvariHQ.
Explore ServicesKeep learning
The Client Operations Brief
One practical email every two weeks on running client operations.
About the Brief
Prefer to start with software? AvariHQ runs the whole client journey in one place.
Start your 30-day AvariHQ trial (opens in a new tab)30 days free. No credit card required.