Client Questionnaire for Agencies: Questions to Prevent Scope Creep
This page is the question-bank version. It gives you 20 concrete client questionnaire questions with usage notes. If you need a downloadable document format, use /templates/client-questionnaire-template.
What should a client questionnaire cover?
A complete client questionnaire covers 10 categories. Each one maps to a specific scope risk:
Goals: What does success look like? Without a measurable target, both parties will evaluate the project differently at the end.
Budget: What is the range? If the client will not answer, that is itself a risk flag.
Timeline: Are there external deadlines, such as product launches, events, or campaigns, that constrain the schedule?
Audience: Who is this for? The more specific the answer, the more useful it is for making creative and copy decisions.
Competitive context: Who are the competitors? How should this project differentiate from them?
Content and assets: Who delivers content? When? In what format? This is the most common timeline risk.
Stakeholders: Who reviews? Who approves? Who can stop a revision?
Technical constraints: What platforms, integrations, or systems must the project work with or around?
Approval process: How many rounds? Who approves? Is legal or compliance involved?
Success metrics: How will the client measure whether the project worked, six months after launch?
20 client questionnaire questions for agencies
1.
What does a successful project look like for you at the 90-day mark?
Forces a measurable outcome. 'We'll know it when we see it' is not an answer, follow up until you get a metric.
2.
What is your budget range for this project?
Non-negotiable for scoping. If the client refuses to answer, document that refusal and flag it as a risk.
3.
Are there external deadlines, such as product launches, events, or campaigns, that constrain the timeline?
Reveals hidden schedule drivers that will override your planned milestones if not surfaced now.
4.
Who is the primary point of contact day-to-day?
Identifies your working relationship early. Prevents confusion about who to contact for approvals vs. day-to-day questions.
5.
Who has final approval on deliverables?
The name that determines revision cycles. If this person is not the day-to-day contact, that is a variable you need to account for.
6.
Is legal or compliance involved in any stage of review?
Surfaces a common hidden timeline variable. One legal review can add two to four weeks to any milestone.
7.
Have you worked with an agency on this type of project before? What worked? What did not?
Tells you what to avoid and what the client values. Pay close attention to the 'what did not work' answer.
8.
How would your best customer describe your brand in one sentence?
Better than asking 'describe your brand' because it forces specificity by routing the question through the customer's perspective.
9.
Who do you consider your top three competitors?
Calibrates positioning and reference level. The team needs to know who they are designing against.
10.
What differentiates you from those competitors in a way your customers actually notice?
Surfaces real positioning, not marketing aspiration. The qualifier 'actually notice' prevents generic answers.
11.
Who provides copy, images, and other content assets?
Surfaces the most common timeline risk before it becomes a problem. Content delays are responsible for the majority of missed agency deadlines.
12.
When will content be ready for delivery to the agency?
Forces a commitment date. 'We'll have it ready when you need it' is not a content delivery date.
13.
Do you have existing brand guidelines, a design system, or a style guide?
Scopes design work before it begins. The answer also signals how mature the client's brand infrastructure is.
14.
What platforms, tools, or integrations must the project work with?
Reveals technical constraints that affect scope. List every integration, including third parties the client may have forgotten about.
15.
Do you have specific performance or accessibility requirements?
Surfaces edge cases that affect development scope. WCAG compliance and performance targets should be in the scope document, not discovered mid-build.
16.
What is your hosting environment, or are you open to recommendations?
Prevents assumptions about deployment. A client who says 'our IT team manages hosting' has just added a dependency you need to account for.
17.
How many rounds of revisions do you expect?
Sets a shared expectation before the first revision. Frame it as what is included in the scope, not what you are willing to do.
18.
Is there a preference for communication method, such as email, Slack, or video calls?
Sets process expectations early. Misaligned communication preferences cause friction that gets attributed to the project.
19.
What does failure look like for this project?
Reveals the client's risk perception and priority ranking. The answer tells you what to protect and what to watch.
20.
Is there anything we have not asked that we should know before committing to this project?
Catches the risk the questionnaire did not surface. Always include this, and take the answers seriously.
How to send and use your client questionnaire
Send the questionnaire before the kickoff call, not during it. The goal is for the client to have time to gather information they do not know off the top of their head: budget ranges, content delivery dates, stakeholder names, and legal requirements. If you ask these questions during a call, you get their best guess. If you ask in advance, you get their considered answer.
When responses come back, review them against a completeness standard before moving forward. Every question that is incomplete, vague, or unanswered is a risk flag. Resolve it before commitment by asking a follow-up question, not by absorbing the ambiguity.
In Clariva: once your client responds to a generated intake, their answers are scored automatically against coverage dimensions. Any gap that could create scope risk is flagged with the specific evidence and a suggested follow-up question. You see exactly what is missing and what to ask next.
Generate a tailored questionnaire from any brief with Clariva
The 20 questions above cover most project types. But a brand identity engagement needs different questions than a web development project or a content strategy. Generic questionnaires produce generic answers because clients answer at the level of specificity the question invites.
Clariva generates questionnaires from the brief context. Describe your project in one to three sentences, or paste an existing brief. Clariva produces a structured questionnaire with sections and questions adapted to what you have told it, and publishes it to a shareable link your client can fill out on any device.