New client onboarding checklist: what to send after “yes”

Onboarding · 6 min read

The moment a client says yes is when many small businesses go quiet. A clear, friendly sequence of messages and forms keeps the momentum going and saves both sides a lot of back-and-forth. Here is what to send, in order.

Why does client onboarding matter?

Onboarding is the stretch between “yes” and the real work starting. It is where the client forms their first impression of working with you, and where small gaps, such as missing files, unclear expectations or an unknown decision maker, turn into delays later. A consistent process reduces those gaps and lets you start with everything you need.

The seven things to send or do

1. A welcome email. Thank the client, confirm what was agreed and explain what happens first.
2. An intake questionnaire. Collect the details you need before work begins: client and organisation information and a project overview.
3. Communication and accessibility preferences. Ask how they prefer to be contacted, when they are available and whether any adjustments would help.
4. A scope and expectations confirmation. Record what is included, what is not, how revisions work, who approves what and the key timing.
5. An asset request checklist. List the files, content, logos and access you need, with a due date and a secure place to send them.
6. A kick-off meeting. Use a short agenda covering the purpose, who is attending and what each person needs to prepare.
7. A timeline and next steps. Show the stages, who does what and by when, with client actions listed separately from yours.

What should a welcome email say?

• Thank them and confirm what they have agreed to.
• Say what happens first, and when.
• List what you need from them and by when.
• Explain how and when you will keep in touch.
• Give your contact details for questions.

Keep it short and warm. The detail can sit in the forms that follow.

Do not ask for passwords by ordinary email

When you collect files and access, use a secure upload location or a password manager’s sharing feature, and only request what the project actually needs. Passwords sent through ordinary email can be read by anyone who gets into either mailbox. Giving clients a safe way to share access also shows them you take their information seriously.

Plan for changes from day one

Projects shift. The easiest time to explain how changes are handled is at the start. If a request goes beyond what was agreed, record what is being asked and why, explain the effect on cost and timing, and get written approval before starting the extra work. Saying this up front makes it feel routine rather than awkward when it happens.

Keep a simple record

Save each completed form with the project file. If anyone later asks what was agreed, who approves what or how the client prefers to communicate, the answer is already written down.

---

The reading list

Latest articles