Website client onboarding checklist
By The Onbo team · Updated
Short answer
Before building a website, collect an accepted agreement, a deposit, answers to a website questionnaire, brand files, a content plan with owners and dates, a signed-off sitemap and confirmed domain and hosting arrangements. Work through them in that order so design starts with everything in place.
Website projects stall in predictable places: the content isn’t ready, the sitemap changes after design, nobody knows who controls the domain. Most of these problems can be caught during onboarding. This checklist covers what a web designer needs from a client before design starts, in the order it’s usually collected.
How to use this checklist
Work through the phases in order. Each phase depends on the one before it: there’s no point collecting content before the scope is agreed, and no point designing before the sitemap is signed off. Copy the list into your own process, remove what doesn’t apply and add anything specific to your services.
Phase 1: Scope and agreement
- Proposal accepted, listing pages, features and revision rounds
- Agreement accepted, covering scope, timeline and payment terms
- Content ownership agreed: who writes copy and sources images
- What happens if content is late, written into the agreement
- Ongoing care or maintenance agreed separately, if offered
Phase 2: Payment
- Deposit invoice sent straight after the agreement is accepted
- Deposit paid before design time is booked
- Later payments scheduled, for example at design approval and launch
Phase 3: Website questionnaire
- Business goals and what the site should achieve
- Main audiences and what each needs to find
- Pages the client expects, and any must-have features
- Sites they like, and why
- Competitors and how they want to differ
- Tools the site must connect to, such as booking or email marketing
- Who approves design and content on the client’s side
Our web design client questionnaire has the full set of questions, grouped by section.
Phase 4: Brand files and content
- Logo in a vector format (SVG, AI or EPS)
- Brand guidelines, fonts and colour codes
- Photos the client owns or has licensed
- Existing copy worth keeping
- Content plan: every page with an owner and a due date
See how to request brand assets from clients for wording and formats.
Phase 5: Structure and technical setup
- Sitemap drafted from the questionnaire answers
- Sitemap signed off by the client’s approver
- Domain owner confirmed, and how DNS changes will be made
- Hosting plan agreed, and how you’ll be given access
- Email, analytics and other accounts that need connecting, listed
- Launch date and any fixed deadlines confirmed
Keep passwords out of questionnaires and email. Agree with the client how access will be shared, such as inviting you as a user on their hosting or domain account, and arrange it with them directly.
Phase 6: Kickoff
- Kickoff booked once phases 1 to 5 are complete
- Agenda built from the questionnaire and open questions
- Design direction and first milestone agreed
- Brief shared with everyone working on the project
For running the kickoff itself, from the agenda to what happens after the call, see the website project kickoff guide.
Why does sitemap sign-off matter so much?
The sitemap decides how many pages are designed, built and filled with content. When it changes after design starts, every later phase moves: new templates, new content to chase, new revisions. A signed-off sitemap during onboarding gives you a clear reference point. If the client wants a new page later, you can show what was agreed and discuss whether it changes scope, timeline or price.
For example, a two-person web studio might draft the sitemap from the questionnaire answers within a day of receiving them, send it for approval, and book the kickoff only once it’s signed off, so the call can focus on design direction instead of page lists.
How can you collect all this without endless emails?
Bundle the client’s tasks into one sequence. Many studios use workflow tools for this; Dubsado, for example, offers workflows to automate business processes, and Content Snare focuses on collecting client information. Whatever you use, the principle is the same: one place for the client’s steps, in a fixed order, with automatic reminders. Our new client onboarding checklist covers the general version for any service.
Where Onbo fits
Onbo covers phases 1 to 4 from one link. The client accepts your agreement, pays the deposit through your own payment link with later payments on the same invoice, answers your website questionnaire with autosave, and uploads logos, photos and content into your own Google Drive through file collection. Reminders follow up on anything unfinished, and the Markdown hand-off brief gives you the answers for sitemap planning. Try it free for 30 days; see pricing.
Questions
What do I need from a client before building a website?
An accepted agreement and deposit, answers about goals, audience and pages, the logo and brand guidelines, a content plan, a signed-off sitemap and clear domain and hosting arrangements.
What should a web design onboarding include?
The agreement, the deposit invoice, a website questionnaire, a file request for brand assets and content, sitemap sign-off and a kickoff call focused on design direction.
Should I collect hosting logins during onboarding?
Keep passwords out of onboarding forms. Agree with the client how access will be shared, such as inviting you as a user on their hosting account, and handle it directly with them.