Almost every difficult project is a project where expectations were never stated. Not broken — never stated. The client assumed something reasonable, you assumed something different and equally reasonable, and neither of you found out until it mattered.
The welcome pack exists to close that gap in the one window where the client is most willing to read: the week after they commit.
What it is for
A proposal persuades. A welcome pack orients. By the time it lands, the decision is made and the client's question has changed from "should I hire this person?" to "what happens now?"
Answer that question thoroughly and you remove most of the anxiety that otherwise arrives as check-in emails.
What to include
A warm opening. Two or three sentences, human, not corporate. This is the first thing they read as a client rather than a prospect.
The phases, with what happens in each. They saw this in the proposal; repeat it. Nobody remembers a document they read once while deciding.
What you need from them, and when. The single most valuable section. Access for measuring, decisions by certain dates, approvals within a stated window. Make the dependencies visible before they become delays.
How decisions get made. Who approves, in what form, and what happens when an approval is late. Say plainly that changes after sign-off carry cost and time — it is far easier to say now than in month three.
How to reach you. Preferred channel, working hours, expected response time. If you are in a different timezone from your client, say so explicitly — it converts "why hasn't he replied" into "he's asleep."
Payment schedule. Restated, with dates and what triggers each stage.
What comes next. One concrete action with a date on it.
What to leave out
Your full terms and conditions. Those belong in the agreement. Burying them here makes the pack feel defensive and stops it being read.
Portfolio work. They already hired you. Selling after the sale reads as insecurity.
Anything you will not enforce. A stated policy you routinely ignore trains the client that stated policies are decorative — and the one you actually need enforced later has already lost its authority.
The section most people skip
What happens when things go wrong. A short, unembarrassed paragraph: items get discontinued, lead times slip, site conditions surprise everyone. Here is how we will tell you, and how quickly.
Writing this down before anything goes wrong does two things. It makes the first problem feel like a known category rather than a crisis. And it quietly demonstrates that you have run enough projects to know problems are normal — which is more reassuring than claiming they will not happen.
Format and timing
Send it within a day or two of the deposit clearing, while commitment is at its peak. A PDF is fine. It should be readable in ten minutes and skimmable in two.
Then reference it. If a client asks something the pack answers, answer them and mention which page it is on — not to score a point, but because it teaches them the document is useful, and they will start checking it first.
A welcome pack nobody opens twice is a brochure. One that becomes the reference for how the project runs pays for itself in the emails you stop having to write.
