Web Design Questionnaire for Clients: 45 Questions and a Free Template
By GiveFeedback.ioUpdated 10 min read
A web design questionnaire for clients is the list of questions a client answers before you design anything, so the facts that shape the project are on paper in week one. Without it, they tend to surface later: the domain login nobody can find, the director who has never seen the designs, the copy that has been "almost ready" for a month. The free Word template below has 45 questions in ten sections, with hints for the client, room for the answers and a page for your team on what to do once it comes back.
What is a web design questionnaire?
A web design questionnaire is a structured set of questions that a client fills in at the start of a website project, covering their business, goals, audience, existing website and accounts, the pages and features they need, content, design preferences, budget, timeline and who makes the decisions. It is the first document of the project, and the brief, the sitemap and the plan all build on it.
It does three jobs. It saves meeting time, because the client gathers facts such as logins, brand files and analytics access at their own pace instead of during a call. It makes the client think before they talk, so the kickoff call starts from their answers rather than from zero. And it leaves a written record: when a request turns up in month three, you can check whether it was ever mentioned.
Agencies also call it a client intake form, a discovery questionnaire or a website brief questionnaire. The name doesn't matter; what it asks does.
Where does the questionnaire fit in the web design client onboarding process?
The web design client onboarding process is everything between the client saying yes and the work starting: the contract and deposit, the questionnaire, a kickoff call, collecting access and assets, an agreed brief, and setting up how you will communicate and review the work. The questionnaire sits in the middle, after the contract and before the kickoff call.
- Contract and deposit. Nobody should spend an afternoon on a questionnaire for a project that isn't confirmed.
- A welcome email with the questionnaire and a return date a few days before the kickoff call.
- Read the answers and mark the ones that are unclear or missing.
- Kickoff call: go through the marked answers, not the whole questionnaire again.
- Collect access and assets: domain, hosting, analytics, brand files, existing content.
- Write the brief and ask the client to confirm it.
- Set up the review process: one channel for feedback, the staging site, the number of review rounds.
- Put the dates in the plan: content deadline, review rounds and approvals.
The questionnaire is easy to confuse with the conversations around it. This is what each step is for:
| Step | When | What it's for | What comes out of it |
|---|---|---|---|
| Discovery call | Before the proposal | Fit, goals, rough scope and budget | A go or no-go, and the basis for a quote |
| Short pre-proposal questions | Before the proposal (optional) | The scope details you need to price | An accurate proposal |
| Full web design questionnaire | After the contract, before kickoff | Every fact the project depends on | Written answers and a list of gaps |
| Kickoff call | After the answers are back | Closing the gaps, meeting the people who decide | The brief, with owners and dates |
What questions should a web design questionnaire include?
Ten sections cover a typical website project: the business, goals, audience, current website and accounts, pages and features, content, design and brand, budget and timeline, decisions and reviews, and life after launch. The template has every question. The reasons are below, because knowing why a question is there tells you whether to keep it for a particular client.
1. The business
Ask what they do in one or two sentences, why customers choose them, which businesses they compete with online and three words that should describe the brand. If the client can't say what they do in two sentences, writing the home page headline will be hard too, and it's better to find that out now than in the second design round.
2. Goals
- Why do you want a new website now?
- What is the one thing you most want a visitor to do?
- How will you know the new website is working?
- What do you like and dislike about your current website?
The second question matters most. A site whose main goal is phone calls is designed differently from one meant to sell online or take bookings, and the answer decides what goes at the top of every key page. The third gives you a way to show, after launch, that the project worked.
3. Audience
Who the ideal customers are, what they need to find quickly, the questions they ask before buying, the devices they use and the languages the site needs. The questions customers ask before buying are a ready source of page content and FAQs. The device question tells you where to test first; ask the client to look at their analytics rather than guess.
4. Current website and accounts
Clients find this section dull, and skipping it is how a finished site ends up waiting on a password.
- Domain: who owns it and where it is registered. You need access, or the person who has it, to point it at the new site.
- Hosting: where the current site lives and who has the login.
- Email on the domain: if the client's email runs on the same domain, changing DNS records at launch can break it. Find out who manages it before you touch anything.
- Analytics and Search Console: who has access, so the history isn't lost when the new site goes live.
- Pages to keep: content that must survive, including pages that bring in visitors from Google, which will need redirects if their addresses change.
5. Pages and features
A rough page list, the features (contact form, booking, shop, blog, newsletter, member area, search, several languages), connections to other tools such as a CRM or a booking system, accessibility or legal requirements, and who will update the site after launch.
Feature questions are where scope gets set. Anything that isn't mentioned here or in the proposal is new work later, and having the answers in writing keeps that conversation short. If the client has a legal duty to meet accessibility standards, it changes the design and the testing, so it belongs at the start; the W3C's WCAG overview explains the guidelines most of those duties point to.
6. Content
Who writes the text, whether photos and videos exist, when the final content will arrive, who checks prices and legal texts, and who provides the privacy policy and cookie notice. Late content often delays a launch, and a content date agreed now is much easier to hold than one set when the site is already built and waiting.
7. Design and brand
Brand files, two or three websites they like in any industry with what they like about each, sites they dislike, and anything the design must include or avoid. "What they like about each" is the important part. A list of links tells you little; "I like how this one shows prices up front" tells you what to design.
8. Budget and timeline
A budget range, the launch date and what's behind it, and whether there is money for hosting and maintenance after launch. A launch date tied to an event or a campaign is fixed; one that's only a wish can move. Knowing which is which changes how you plan the review rounds.
9. Decisions, reviews and feedback
Who the day-to-day contact is, who has the final say on design and content, who else reviews, how they want to send feedback, which devices and browsers they'll use, and when they're unavailable.
This section protects the timeline. An approval from someone without the authority to give it can be overruled weeks later, and a reviewer who appears only in the last round reopens decisions that were already closed. Naming the approver now is what makes each stage approval stick, and the reviewers' devices tell you what to test before they look.
10. After launch
Who will maintain the site, whether the client needs training, and who should receive the logins and documentation at handover. These answers shape the build: an editor who updates the site every week needs a simpler admin than one who never will.
Which questions save the most time later?
The questions about decisions and logistics save more time than the ones about taste: who has the final say, who provides the content and by when, who holds the domain and hosting logins, what the one main action on the site is, and how feedback will be sent. Design preferences can be discussed at any stage; a missing approver or an unknown password stops the project.
| Question | What happens when nobody asks it |
|---|---|
| Who has the final say? | Someone senior sees the site for the first time in the last round and reopens approved decisions |
| Who writes the content, and by when? | The finished design waits for text, and the launch date moves |
| Who owns the domain and hosting? | Launch day is spent looking for a password or a former supplier |
| What is the one main action? | Every page tries to do everything, and nobody can say whether the site works |
| How will feedback be sent? | Comments arrive by email, chat and phone, and some of them get lost |
If a client will only answer a handful of questions, make it these five.
How do you get clients to fill in the questionnaire?
Send it when the client is most motivated, right after signing, with a return date and one line on why it matters. Delete the questions that don't apply, fill in what you already know from the sales call, and tell the client that "not sure" is a fine answer. Then read it before the kickoff call, so the call is about the gaps.
- Delete before you send. A brochure site doesn't need the questions about member areas and integrations.
- Pre-fill what you know. Answers from the sales call can go in already, for the client to correct.
- Say why. "These answers become the plan for your site" gets better answers than a bare attachment.
- Let several people answer. The marketing lead knows the audience and someone else knows where the domain is registered; ask for one combined copy back.
- Set the kickoff call after the return date, so there is time to read the answers.
The format matters less than getting one complete copy back:
| Format | Good for | Watch out for |
|---|---|---|
| Word document | Attaching to the welcome email; several people adding answers offline | Copies multiplying by email: ask for one file back |
| Online form | Tidy answers you can compare across clients | Hard to split sections between colleagues; long forms are tiring on a phone |
| Shared document (Google Docs) | Answering together, comments on unclear answers | Edits after the kickoff call: save a copy once it's agreed |
The Word template opens in Google Docs as well: upload it to Google Drive and open it with Docs.
What do you do with the answers?
Turn them into a short brief that you write and the client confirms: the goals and the main action, the audience, the page and feature list, the content plan with owners and dates, the access you still need, who approves what, and how reviews will run. Sending it back with "this is what we understood" catches misunderstandings while they are still cheap to fix.
Keep the questionnaire with the project files. When a request turns up that isn't in the answers, the brief or the proposal, it is new scope, and a change request form lets you handle it without an argument about what was agreed.
How do you set up the review process at kickoff?
Use the answers to section 9 to agree, at kickoff, where feedback goes, who sends it, how many review rounds there are and how long each one lasts. One channel for feedback, named reviewers and review dates in the plan keep the rounds from turning into an email thread that never ends.
GiveFeedback.io is built for this part of the project. You add one script to the staging site and a "Give Feedback" button appears. Reviewers click it, mark up a screenshot of the page with arrows, boxes, text or numbered markers, and send it, without creating an account. It works on computers, phones and tablets, so the client can report from the devices they listed in the questionnaire, and every report arrives with the page URL, browser, operating system and screen resolution attached.
Feedback types (Bug, Proposal, Recommendation and Feature by default, which you can rename in your profile, to Content for example) keep bugs apart from new requests. You can invite the client by email to a read-only view of the project's feedback, so they can see what has been resolved, and each report can be created automatically in Jira, Trello, ClickUp, Asana, Notion, Slack and other tools. The use cases page shows how agencies, web designers and project managers set it up, and the Free plan covers 5 projects and 50 feedback reports (pricing).
Send the questionnaire, read it before the call and confirm the brief in writing. The same answers come back at the end of the project, because the access list, the maintenance plan and the people who should receive the logins are your website handover checklist in draft. A project that starts with complete answers has fewer surprises at the end.
Frequently asked questions
When should you send a web design questionnaire?
Send a short version before the proposal, with the questions on goals, scope, budget and timeline, so the quote is based on facts. Send the full questionnaire once the contract is signed and before the kickoff call. At that point the client is committed and motivated, and you have time to read the answers and prepare follow-up questions.
How long should a client questionnaire for web design be?
As long as the project needs and no longer. A five-page site for a local business doesn't need the questions about integrations or member areas, so delete them before sending. Group the questions in sections and let the client answer "not sure": a shorter questionnaire that comes back complete is worth more than a long one that never comes back.
Should the questionnaire be a Word document or an online form?
Either works. A Word document is easy to attach, can be filled in offline and lets several people at the client add their part before one person sends it back. An online form gives you tidy, comparable answers but is harder to split between colleagues. The Word template here also opens in Google Docs if the client works there.
What if the client can't answer some of the questions?
That is useful information in itself. Unanswered questions about content, access or decisions are the risks of the project, so list them, go through them in the kickoff call and give each one an owner and a date. Don't fill the gaps with your own assumptions unless you write them down and the client confirms them.
What is the difference between a web design questionnaire and a creative brief?
The questionnaire holds the client's raw answers, in their own words. The brief is your summary of those answers after the kickoff call: goals, audience, scope, content plan, constraints and who decides, written by you and confirmed by the client. The questionnaire is the input; the brief, or a fuller requirements document, is what the team works from.
Keep reading
Guides
Bug Triage Process: Steps, Meeting Agenda and Free Checklist
A bug triage process for web teams: the steps, who attends the bug triage meeting, a 30-minute agenda, a triage matrix and a free Word checklist.
- 9 min read
Guides
Website Change Request Form: Free Template, Change Log and Process
A free website change request form (Word) and change log (Excel), how to tell a change from a bug, and a process to quote, approve and ship updates.
- 9 min read
Guides
Jira Bug Report Template: Free CSV Import and Field Guide
A Jira bug report template you can import: a free CSV with four example bugs, a field guide, a description to paste and how to write a bug report in Jira.
- 9 min read
Collect visual feedback on your next website
Visual website feedback for agencies, freelancers and their clients.
Free plan - No credit card - Set up in minutes
