Web design client questionnaire with the questions that save time later
Most of the rework on a website project traces back to a question nobody asked at the start. This web design client questionnaire focuses on those questions: who approves, who gives feedback, who writes the content, when it has to be live and which pages it can't launch without. Each question says which later problem it heads off, and the whole questionnaire is at the end, ready to copy.
Ask the questions that are expensive to get wrong
A typical onboarding form asks about favourite colours, fonts and competitors. Those answers help, but they rarely cause trouble later. The questions that do are about people, content and dates: the director who sees the site for the first time a week before launch, the copy that was "nearly ready" for a month, the domain login that belongs to someone who left the company.
Each question below has a short note on the problem it heads off, so you can explain to the client why you're asking. That note is for you. The copyable version at the end has the questions only, written for the client to fill in.
1. Business and goals
- What does your business do, and who are your customers? Two or three sentences is plenty.Heads off: copy and design pitched at the wrong audience, found in the first review.
- What is the one thing you most want a visitor to do on the site?Heads off: a homepage with five competing buttons, and a late request to "make the enquiry form stand out more".
- How will you judge whether the new site is working, six months after launch?Heads off: a project judged only on taste, with no shared idea of what success looks like.
- What do you dislike about your current site, and what should stay the same?Heads off: redesigning away the part customers liked, or carrying an old problem into the new build.
- Name two or three websites you like, and say what you like about each one.Heads off: vague feedback like "make it pop" in round two, because you already know what they mean by good.
2. People and approvals
- Who has the final say on the website? Please give one name.Heads off: a late change of direction from a senior person who never saw the earlier rounds.
- Who else will give feedback, and which parts will each person look at?Heads off: a flood of comments from people reviewing everything, including parts outside their area.
- When two reviewers disagree, who settles it before the feedback reaches us?Heads off: two comments on the same heading asking for opposite changes, with you left to pick one.
- Does anyone outside the team need to see the site before launch, such as legal, a board, a franchise or a parent company?Heads off: a compliance review in the final week that rewrites pages already signed off.
- Who is the day-to-day contact, and who covers when the decision-maker is away?Heads off: a review round that stalls for two weeks because the approver is on holiday.
- How should we reach you, and how quickly can you usually reply?Heads off: long silences mid project, and the awkward chasing that follows. See what to do when a client goes quiet.
3. Content
- Which pages must the site have on launch day, and which could follow later?Heads off: pages added in the last week, and a launch held up by pages that could have waited.
- Who will write the text for each page, and when will it be ready?Heads off: a finished design waiting on copy nobody owned, or real text that doesn't fit the layout built for it.
- Do you have photos, a logo and brand files we can use, and do you hold the rights to them?Heads off: images swapped out at the end, and licence questions at handover.
- Is there content to move across from your current site, such as blog posts, products or case studies? Roughly how much?Heads off: days of migration work that nobody quoted for.
- Does the site need any legal or required text, such as a privacy policy, cookie notice, terms, or wording set by a regulator? Who provides it?Heads off: a launch delayed while someone finds a lawyer to write the privacy policy.
4. Technical and access
- Who owns the domain name, and who can log in to the account where it's registered?Heads off: launch day spent tracking down a login that belongs to a former employee or an old agency. The website handover checklist covers what the client should own at the end.
- Where is the current site hosted, and who has access to it?Heads off: a migration that can't start because nobody can reach the old site or its email settings.
- Which tools does the site need to connect to? For example booking, payments, a newsletter, a CRM or analytics.Heads off: an integration discovered in week six that changes the platform or the price.
- Who should receive messages from the site's forms?Heads off: enquiries going to an old inbox for a month after launch.
- After launch, who will update the site, and how comfortable are they with editing it?Heads off: a site built on a platform the client's team can't edit, and a stream of small change requests.
5. Timeline and budget
- Is there a date the site must be live by? What is it tied to, such as a launch, an event or a campaign?Heads off: treating a soft target as fixed, or missing a real deadline nobody mentioned.
- Are there dates when you or the approver won't be available?Heads off: review rounds landing in someone's holiday or busiest month.
- What budget have you set aside, and does it cover ongoing costs like hosting, licences and maintenance? If something has to give, is it the date, the scope or the budget?Heads off: a scope larger than the budget, and arguments later about which one bends.
6. Review and feedback
- How many rounds of changes do you expect, and what should each round focus on?Heads off: open-ended revisions. Our post on how many revision rounds to include has wording for the contract.
- How many working days can your reviewers have for each round?Heads off: feedback that trickles in over weeks, one email at a time.
- Are you happy to give all feedback as comments on the page itself, through one review link, rather than by email or screenshots?Heads off: feedback spread across email, chat, a call and a marked-up PDF, with some of it missed.
- What will count as sign-off on the final version, and who gives it?Heads off: "I thought we were still discussing it" a day after launch.
- Will your reviewers check the site on a phone as well as a computer?Heads off: phone layout problems found by customers after launch instead of reviewers before it.
The full questionnaire, ready to copy
The questions only, written for the client. Paste it into a doc, a form or an email, and swap the parts in curly brackets for your own details. There is also a short email to send with it.
Email to send with it
Once the client has agreed to go ahead.Go through the answers on the kickoff call
A questionnaire on its own tends to come back half finished, with "TBC" next to the hard questions. Send it a few days before the kickoff call and use the call to go through it together. Spend most of the time on the people and content groups, because those are the answers clients guess at most often.
- Push for one name. "The team will decide" is not an answer to question 6. Ask who decides when the team disagrees.
- Put a date on every content owner. "Marketing will write it" becomes "Priya sends the About and Services copy by the 4th".
- List the gaps. Anything still unknown goes in the kickoff notes as an open question with an owner and a date.
- Send the answers back. A short written summary of what was agreed is the thing you point to when the scope is questioned later.
Agree how feedback will work before the first review
The review and feedback questions are the easiest to skip at kickoff and the hardest to fix mid project. Once a client has started sending notes by email, moving them to another method feels like extra work. Agree it at the start, while everyone is keen.
With HTMLAnnotate that agreement is short. You send one review link for each round. Reviewers click anything on the page to leave a comment pinned to it, with no account, and desktop, tablet and phone comments are kept separate. When the final version is right, the approver presses Approve, which is recorded against that version, and you get an email straight away. New versions go on the same link, and earlier versions keep their comments.
For the wider process, our guides on setting up a client feedback process and getting client approval on a website pick up where this questionnaire leaves off.
Questions
When should I send a web design client questionnaire?
Send a short version before you write the proposal, so the quote covers the right pages, integrations and content work. Send the full version once the client has agreed to go ahead, and go through the answers together on the kickoff call.
How long should a client questionnaire be?
Long enough to cover approvals, content, access, timeline and feedback, and short enough to finish in about half an hour. The one on this page has 29 questions in six groups. Cut any that don't apply to the project before you send it.
Should I send it as a form or go through it on a call?
Both work best together. Send it in writing first so the client can check with colleagues and find logins, then use the kickoff call to go through the answers, fill gaps and settle anything vague. Write up what was agreed and send it back.
What if the client can't answer some questions?
Treat each gap as an open question with an owner and a date, and list them in the kickoff notes. An unanswered question about who approves or who writes the copy is a risk to the timeline, so say so plainly rather than letting it drift.
What is the most important question to ask a web design client?
Who has the final say on the website. Knowing the one person who can approve, and making sure they see every round, prevents the most expensive kind of rework: a late change of direction from someone who joined at the end.
Agree at kickoff how feedback will work: one review link, comments pinned to the page, and Approve when it's right. Reviewers never need an account.
Start a free review