Start with a welcome and a shared understanding
Once a client has agreed to work with you, an onboarding email helps turn that agreement into an organized project. It should make the client feel welcomed, but its main job is practical: confirm what you understand, explain what happens next, and identify anything you need from them. A client should be able to finish reading it and know whether they need to reply, send materials, or simply wait for your next update.
Open with a brief thank-you and name the project in plain language. Then summarize the intended outcome in one or two sentences. For example, you might say that you will design a small set of social templates that the client can adapt for future posts. This is not a replacement for a proposal or agreement. It is a quick check that you and the client are starting with the same picture of the work.
Confirm the scope and the first milestones
Include a compact recap of the deliverables, along with any important boundaries that could otherwise cause confusion. A designer might mention the number of concepts, the planned revision rounds, and the file types included at handoff. A writer might confirm the format, approximate length, and whether publishing is part of the work. Refer to the agreed scope rather than introducing new promises in a welcome email.
Next, outline the first few milestones: when you expect to begin, what the client will see first, and when you will need their input. If dates depend on receiving assets or approvals, say so clearly. You do not need to repeat a full project schedule; focus on the next decision or delivery. If a kickoff call is planned, include its purpose and tell the client what, if anything, they should prepare.
Ask for the materials you actually need
A broad request such as “send everything you have” can leave clients unsure where to start. Instead, list the specific inputs needed for the first phase. Depending on the project, these might include brand files, existing copy, product details, audience notes, examples of past work, access to a shared folder, or the names of people who will review drafts. Separate essential items from useful extras so the client can prioritize.
Make each request easy to act on. Say what format is helpful, where files should go, and when you need them to keep the project moving. If you use a questionnaire, explain why it matters and give the client a reasonable way to flag answers they do not yet have. Avoid requesting passwords in an ordinary email; where account access is necessary, agree on an appropriate access method instead.
The onboarding email is also a good place to ask one or two questions that will shape early work. Keep them focused. “Who makes the final approval?” is more useful at this stage than a long list of speculative preferences.
Set expectations for communication and feedback
Tell the client which channel you will use for routine updates and where you would like feedback collected. When comments arrive across email, chat, and shared files, decisions can be hard to track. Choosing a primary channel gives both sides a clearer record. You can also describe the rhythm of updates, such as a message at each milestone or a regular check-in during a longer project, without promising constant availability.
Explain how you will handle reviews. Let the client know whether you will send a draft with specific questions, how they can consolidate comments from multiple stakeholders, and what you will do after receiving feedback. If there is an agreed review window, restate it. This is a friendly way to show that timely, gathered feedback helps the project move forward without making the email sound like a list of rules.
Close with one clear next step
End by telling the client exactly what to do next. If you need files, give a short list and a place to send them. If the next action is a kickoff call, confirm how it will be arranged. If nothing is required yet, say when they can expect to hear from you. A simple closing such as “Once I have the logo files and approved copy, I’ll begin the first draft” is easier to act on than a vague offer to get started soon.
Before sending, read the email from the client’s perspective. Can they see what is agreed, what is coming, and what they owe you? Is any request buried in a long paragraph? Trim details that belong in the project plan and keep the tone human. A good onboarding email does not need to anticipate every question. It needs to give the project a calm, clear beginning.
