Restate what has been agreed

Summarise the approved scope, main contacts and immediate next steps using the current agreement as the reference. Identify the information or access needed from the client and explain why it is required. Avoid introducing major new expectations casually in an onboarding message. If something was missed during scoping, raise it clearly rather than treating it as an assumed obligation.

Make the first milestone visible

Explain what happens first, who owns it and what completion will look like. Provide one organised location for working resources where appropriate. Introduce the delivery team and show how questions or changes should be raised. A good onboarding experience reduces the need for the client to chase basic information and helps the team begin with a shared understanding of the work.

Imagine this

Hypothetical example

A hypothetical client moves from a sales conversation to an implementation team. The onboarding note confirms the agreed first phase, introduces the project owner and lists the three inputs needed to begin. It also explains where scope questions should go, preventing scattered requests across several channels.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.