Client onboarding starts when someone agrees to work with you and ends when both sides understand what happens next. A polished welcome email helps, but the more useful outcome is a shared starting point. The client knows what to supply, you know what to deliver, and the first milestone has an owner and a date.
For a freelancer or small agency, a repeatable checklist can live in a document, spreadsheet, or workspace. Use the same sequence each time, then adjust the details for the engagement.
1. Capture the people and the decision
Record the customer's organization, main contact, preferred communication channel, and the person who can approve the work. The person attending meetings may need someone else's approval before a milestone can move forward.
- Confirm the main contact's name and working email address.
- Record the decision-maker and anyone who needs status updates.
- Write a one-sentence description of the problem the client wants solved.
- Note any access or communication needs raised by the client.
Keep observations factual and relevant. A note such as “needs the draft before the Tuesday leadership meeting” is more useful than a vague label such as “urgent client.”
2. Confirm the scope before scheduling delivery
Put the agreed deliverables, exclusions, revision process, responsibilities, and payment arrangements in the appropriate engagement documents. An onboarding checklist helps you track these decisions. It does not replace the agreement itself.
For a website project, “five-page site” leaves important questions open. Does the client supply the copy? Who selects the photographs? Is content migration included? Turn the answers into explicit decisions before setting the delivery schedule.
3. Ask for inputs in one place
Send one organized request with an owner and a due date for each input. Separate items that block the first milestone from items that can arrive later. This makes a short, incomplete response easier to act on.
- Needed to start — project goals, relevant existing materials, and the first approval contact.
- Needed before the first draft — approved copy, brand assets, or other project-specific inputs.
- Needed before delivery — final approvals, destination details, and the handoff contact.
Use the service's invitation or secure sharing mechanism for access. Store a link to the relevant system instead of copying passwords into project notes.
4. Run a short kickoff with a written outcome
A kickoff does not need an elaborate presentation. Use a simple agenda covering the desired outcome, first milestone, responsibilities, communication rhythm, and known constraints. End by reading back the next action for each side.
After the meeting, record decisions where the work happens. A meeting recording can support the record, but someone should be able to find the next deadline without watching the whole call.
Our first milestone is a draft outline on Thursday. I will prepare it. Please send the approved source materials by Tuesday. We will use the project thread for questions and review the outline together on Friday.
5. Send a welcome message that tells the client what to do
Adapt this message to the actual engagement.
“Thanks for choosing us for this project. Our first milestone is [deliverable] on [date]. Your next step is [input] by [date]. I will handle [action]. We will use [channel] for questions, and I will send the next update on [date]. Here is the project reference with the agreed scope and useful links.”
Avoid adding several unrelated requests to the welcome message. Make the first action easy to identify, then link to the complete checklist.
6. Keep onboarding connected to delivery
Once the first milestone is underway, close the onboarding checklist and keep unresolved inputs visible in the project. Give each outstanding item an owner. A task called “waiting on client” is less useful than “Maya to supply approved product descriptions by Tuesday.”
In the Execuown workspace preview, you can create a customer record, link a project to that customer, and add tasks and document links around the project. Start with the workflow you already need. Add detail when it helps the next person act.
For the next stage, use the project handoff checklist and a consistent client document structure.