The first week with a new client sets the tone for the whole project, and most early problems come from missing steps, not from hard work. Access never arrives, the brief stays vague, payment details are never exchanged, and by week two everyone is frustrated. An onboarding checklist prevents that drift: it lists every step, who owns it, and when it is due, so the start of a project is a visible process instead of a hopeful exchange of messages.
Start with the steps every project needs, then add the ones this client needs. A welcome message and project brief, access to tools and accounts, brand files and past work, payment details and terms, a communication channel and response times, and a kickoff call date cover most projects. A web project adds hosting and domain access; a writing project adds style guides and past articles. The checklist should fit the project, not copy a generic template nobody follows.
Owners matter as much as steps, because a step with no owner is a step nobody does. Each step belongs to you, to the client, or to both of you together. Access to the client own systems belongs to the client; a project timeline belongs to you; a kickoff agenda belongs to both. When a client sees their own name next to two or three steps, they understand that onboarding is shared work, not something they wait for you to finish alone.
Due dates turn a list into a schedule. A step due "soon" will be done never, while a step due Tuesday has a fair chance. Set due dates that respect the client own workload: access requests on day one, the brief within three working days, and the kickoff call within the first week are realistic for most projects. If a due date slips, the checklist shows exactly which step slipped and who owns it, which makes the follow-up message factual instead of awkward.
Progress is the part clients value most, because it answers their unspoken question: is this project actually moving? A checklist that shows six of eight steps done tells a client more than a reassuring message. Share the list, update it as steps finish, and let the client tick their own steps where possible. A shared list builds trust faster than any welcome email, because trust comes from visible progress, not from promises.
This builder is a different job from a proposal tool, and the distinction is worth stating. A proposal tool writes proposal text: it sells the project, states the price, and wins the work. This builder runs the start of the project after it is won: it organises steps, owners, and due dates, and tracks what is done. Use the proposal tool to win the client, then use this checklist to start the work well. Confusing the two leaves you with fine words and a chaotic first week.
Keep the checklist short enough to finish. Eight to twelve steps is right for most projects; thirty steps will be ignored, however complete they look. If a project genuinely needs more steps, split it into phases: onboarding, delivery, and handover, each with its own short list. A checklist that gets finished beats a perfect checklist that gets abandoned, and the progress percentage only means something when the list is honest.
Use this builder for every new client, starting with the template steps above and adjusting them to the project. Copy or download the finished list, share it with the client, and update it until every step is ticked. A strong first week makes the rest of the project easier: expectations are set, access works, payment is arranged, and the real work starts on a foundation that both sides can see.