Build a Client Onboarding Checklist From the Emails You Already Have

Build a client onboarding checklist by reviewing existing emails, recording confirmed details and turning unresolved gaps into questions. Give each requirement a status, a source reference and a next step. Review the result before contacting the client, booking a kickoff or making a new commitment.

Use the method below for one client and one project at a time. The goal is a reviewable readiness checklist—not a copy of every message or an assumption that an old instruction still applies.

What should a client onboarding checklist include?

Start with scope, contacts, required inputs, timing and unresolved decisions. Sage’s accounting-specific onboarding checklist includes scope, contact information, information gathering, access and kickoff arrangements; use those categories as a reference rather than adopting its accounting requirements wholesale. (Sage onboarding checklist (PDF))

For a small design project, use these prompts:

• Scope: What deliverables have both sides agreed to?
• Contacts: Who coordinates the project, and who approves the work?
• Inputs: Which files, brand materials or background information are needed?
• Timing: Which dates are agreed, proposed or unknown?
• Readiness: Which unresolved decisions prevent the next step?

Add a source reference beside each item. Record the actual message subject, sender and date so the reviewer can check your interpretation without searching the entire conversation again.

For this checklist, use three status labels:

• Confirmed: An explicit statement applies to this project.
• Missing: The reviewed material contains no answer.
• Uncertain: The wording is tentative, conflicting or needs reconfirmation.

Keep receipt separate from readiness. Record that a logo arrived, for example, without assuming it is the approved version for the project.

How do you build the checklist from existing emails?

Follow these six steps to create a draft the project owner can check.

1. Select the relevant conversation. Gather messages about the agreed project and their referenced attachments. Exclude unrelated correspondence.
2. Extract stated details. Record what the client supplied or confirmed. Keep suggestions separate from commitments.
3. Attach evidence references. Note where each detail appears. If an attachment is mentioned but unavailable, record that limitation.
4. Assign a status. Apply the definitions above to each requirement, not just to the project overall.
5. Prioritize unresolved items. Identify which gaps block the immediate next step and which can wait.
6. Review before drafting a request. Compare the checklist with the source messages and remove questions already answered clearly.

Use this fictional example as a starting format. It represents no real customer or product interface.

Requirement	Evidence reviewed	Status	Next step
Logo file	Attachment in the brand-materials message	Confirmed: receipt only	Verify that it is the approved version
Final approver	No approver named in reviewed messages	Missing	Ask who gives final design approval
First-draft timing	Preferred week mentioned without agreement	Uncertain	Agree timing after checking feasibility
Project scope	Scope-confirmation message specifies a brochure	Confirmed	Check for subsequent scope changes

Do not judge readiness by counting confirmed rows. Review the importance of each unresolved item. In this example, identify the approver before relying on a review plan.

What should you ask the client for next?

Prepare a request containing only the information needed for the next decision. Mailbird’s onboarding guidance recommends specific requests and a clear next step; treat that as editorial advice, not evidence of a guaranteed response or faster onboarding. (Mailbird client onboarding email guidance)

For the fictional project, adapt this draft:

Subject: Details to confirm for [project]

Hi [client name],

Thank you for sending the logo. Before we prepare the next step, please confirm:

• Is the supplied logo the approved version for this project?
• Who will give final approval on the designs?
• What timing would you like us to consider for the first draft?

We have the brochure scope recorded from our conversation. Please let us know if that has changed.

Once these details are confirmed, we can review readiness and agree the next step.

Thanks,
[name]

Replace every placeholder before approval. Add an agreed deadline only when the underlying conversation supports it; do not manufacture urgency to make the request sound more decisive.

How should you handle uncertain or sensitive details?

Resolve uncertainty explicitly rather than filling gaps with an assumption. Use the checklist’s evidence field to show what needs a decision.

What if two emails conflict?

Record both messages and mark the requirement uncertain. Ask the appropriate decision-maker which instruction applies, then record the clarification alongside the original references.

What if no deadline is agreed?

Write “not agreed” in the timing field. Ask for a preferred date and check feasibility before treating it as a commitment.

Where should access information go?

Keep the checklist limited to access status, such as “requested” or “pending.” Follow your organization’s approved secure process for credentials rather than copying them into this working document.

What needs approval before onboarding moves forward?

Review the checklist, outgoing request and any proposed kickoff booking separately. For this suggested workflow, preparation does not authorize external action.

Before approval, check the recipient, scope, attachments, open questions and wording that could create a new commitment. Assign delivery work separately once the relevant decisions are confirmed.

If using Donetra, keep the same preparation-first boundary when discussing this workflow with Max, your AI Chief of Staff.

Ask Max to help prepare your next client onboarding checklist. Review the details before approving anything to be sent or booked.