A Simple Client Onboarding Checklist
What to confirm, collect and set up before a new client's work actually starts, so nothing falls through in the first two weeks.
What to confirm, collect, set up and agree before a new client's first deliverable is due.
What does onboarding actually cover for a solo consultant?
Onboarding is the short period between a signed agreement and the first real piece of work. It covers four things: confirming what was agreed, collecting what you need to start, setting up access and tools, and agreeing how communication will work. Skipping this step does not save time. It moves the confusion from before the project to during it, which is more expensive for both sides.
A good onboarding checklist is short enough to finish in one sitting and specific enough that nothing is left to memory. It is not a second sales pitch and not a legal document. It is the bridge between the scope you agreed and the work you are about to do.
What should you confirm before anything else?
Confirm that both sides are working from the same written record of what was agreed: scope, price, timeline and who does what. Under general contract principles summarised by the Legal Information Institute, an enforceable agreement needs mutual assent through offer and acceptance, which is easiest to demonstrate when both parties can point to the same document (LII). If you have not already written that document, our guide on writing a clear scope of work covers the format.
If anything changed between the sales conversation and the signed agreement, say so explicitly now. "Just to confirm, we agreed on X, starting Y, for Z" takes one email and removes most onboarding disputes before they start.
What should you collect from the client before you begin?
Make a short, named list rather than a vague request for "everything you need." Typical items for a consulting engagement:
- Billing details: legal name, billing address, invoice contact, purchase order number if one is required.
- Access: logins, shared drive permissions, or an introduction to whoever controls them.
- Reference material: past reports, brand guidelines, existing data, or anything the client already has that would save you from rebuilding it.
- A single point of contact, even if several people will be involved in the work.
Ask for these once, in one message, with a deadline. Chasing scattered requests across several emails is one of the quietest causes of a slow start.
How should you handle personal or sensitive information you collect?
Only ask for personal data you actually need, and be clear about why you are collecting it. The UK Information Commissioner's Office sets out data protection principles that include being transparent about data use and collecting no more than necessary for the purpose (ico.org.uk). For a small consultancy, this usually means: do not request access to systems or files you will not use, tell the client how long you will keep what they send you, and delete project files on a set schedule after the engagement ends rather than leaving them indefinitely. If your work touches health, finance or other regulated data, check current official guidance for your sector before you design your intake form.
How do you set up tools and access without losing a week?
List every tool or system the client needs to grant you access to, and request it in the same message as your document collection. Where possible, ask for a time-boxed or role-limited permission rather than full access, which is easier for the client to approve quickly and easier for you to hand back cleanly at the end.
| Step | What to confirm | If missing |
|---|---|---|
| Agreement | Scope, price, timeline match the signed document | Resend a one-paragraph confirmation |
| Billing | Correct legal name, address, PO number | Ask before the first invoice, not after |
| Access | Logins, folders, named contact for IT questions | Request with a deadline |
| Communication | Who updates whom, how often, in what format | Agree a simple weekly format |
| Data handling | What you collect, why, how long you keep it | Write one line and share it with the client |
How should you set expectations for communication from day one?
Agree, in writing, how often you will update the client and in what format, before the first week of work begins. Putting expectations in writing early reduces disputes later; Acas, whose guidance covers employment rather than client work, makes a similar case for clear written terms (acas.org.uk). Our format for status updates clients actually read works well as the default if the client has no existing preference.
Also agree what happens if either side is unavailable. A one-line fallback, such as "message my shared inbox if I am out," prevents a short absence from becoming a client-facing problem.
What mistakes should you avoid during onboarding?
Do not start billable work before the access and documents you actually need have arrived; estimate a buffer day instead of promising a start date you cannot control. Do not accept verbal changes to scope during onboarding without writing them down, even small ones, because small unwritten changes are where managing changes mid project usually begins. Do not collect more personal or company data than the engagement requires, and do not let onboarding drag past two weeks for a short project; if it is taking longer than the work itself, something in the checklist needs to be shorter, not longer.
How do you turn this into a repeatable routine?
Write your checklist once, in a template you reuse for every new client, and update it only when a real project teaches you something new is missing. Keep it to one page. The goal is not to impress a new client with process. It is to make sure that by the time you send your first status update, there are no open questions left over from before the work began.
