The questions that prevent the most rework aren't the ones covering audience and goals, most designers already ask those. They're the ones covering who actually signs off, what exact formats and dimensions the files need to land in, and what happens if two stakeholders disagree. Miss one of the first kind and you redo some copy. Miss one of the second kind and you redo the whole deliverable. Asking the right questions in the right order, before the file is even open, is what separates a smooth project from a week-three scramble.
Why Order Matters More Than the List
Most published question lists for design clients are organized by topic, business goals, then audience, then brand, then scope. That grouping is fine for reference, but it hides something more useful: some skipped questions cost you an afternoon, and others cost you the entire deliverable. A missed export-format question means a re-export. A missed decision-maker question can mean the whole thing gets rejected by someone who was never in the loop and disagrees with everyone who was. Ordering by cost of the miss, not by category, is what actually protects a project.
The Questions, Grouped by What They Protect Against
| Question | What it protects against | Cost if skipped |
|---|---|---|
| Who has final sign-off, by name? | Total rework from an uninvolved decision-maker rejecting approved work | The whole deliverable, redone |
| What happens if two people on the client side disagree? | Total rework from conflicting direction | Weeks lost building around the wrong stakeholder's input |
| What exact file formats and dimensions does this need? | A wasted deliverable in the wrong format | A re-export at minimum, a redesign at worst |
| Where will this actually be used, print, web, or both? | Design built for the wrong medium (color mode, resolution) | Reprint costs or a visibly wrong result |
| What's explicitly out of scope? | A mid-project scope fight | Unpaid extra work or an awkward renegotiation |
| How many revision rounds are included? | The same scope fight, from a different angle | Free rounds that quietly become unlimited |
| What's the real deadline, and is it tied to anything external? | A stalled project with no urgency signal | A project that drifts for months with no clear end |
| Is there an existing brand guideline? | Work rejected late for conflicting with something that already existed | A redo after the client says "that's not our blue" |
Every row has a specific downstream failure attached to it, which is the point: knowing what a skipped question actually costs makes it much harder to skip. The first two rows are worth asking even when a project feels too small or informal to need them, since sign-off confusion is exactly as damaging on a small logo job as on a large one.
When the Client Says "I Don't Know, You're the Expert"
This answer shows up most often on the sign-off and decision-maker questions, and it's tempting to just proceed. The better move is to make the choice narrower rather than asking again: show two concrete, contrasting real examples and ask which one is closer to what they picture, or name two people and ask directly which one has final say if they disagree. A specific either-or question gets an answer where an open one gets a shrug. This technique carries over directly into building the written brief itself, covered in what to include in a design brief.
Where to Keep the Answers
Once asked, these answers need somewhere more durable than memory or a scattered chat thread, since they're what you'll refer back to the next time a scope question comes up. A single running document per project, even a plain text note, that records who answered what and when is enough. The point isn't the tool, it's having one place to check instead of scrolling back through weeks of messages when a disagreement surfaces later.
What to Do With Contradictory Answers From Different Stakeholders
When you're getting answers from more than one person on the client side and they don't match, the fix isn't to average their answers or guess which one is right. It's to surface the contradiction back to them directly and ask them to resolve it between themselves before you proceed. This is uncomfortable to raise but far cheaper than building around an assumption and finding out later which stakeholder actually had authority.
How Many Questions Is Too Many
A design intake can turn into an interrogation if every question above gets asked as its own separate message. In practice, most of these fit naturally into one structured conversation, ideally live, covering all eight in fifteen or twenty minutes rather than a long written questionnaire that a client has to sit down and fill out on their own time. A questionnaire that takes effort to complete gets rushed or partially skipped; a short live conversation gets real answers because you can follow up immediately when something's unclear.
Do Repeat Clients Still Need the Full List
For a client you've already worked with, several of these questions genuinely don't need re-asking, brand guidelines and general sign-off structure are usually stable from project to project. What still needs asking every time, regardless of history: scope for this specific project, the deliverable formats needed this time, and the deadline. Assuming a repeat client's answers from last time still hold on the current project is a common source of the exact rework these questions exist to prevent. History with a client shortens the conversation. It doesn't replace it.
Turning the Answers Into the Written Brief
These questions aren't an end in themselves, they're the raw material for the written brief you send back to the client for confirmation. The full six-section structure that these answers feed into, and how to handle a brief the client never planned to write, is in what to include in a design brief. Asked live, in a structured 30-minute conversation rather than a scattered email chain, these same questions form the backbone of the kickoff call, and this whole intake stage is one part of the six-stage process covered in the design project, start to sign-off.
FAQ
What's the most important question to ask a design client?
Who has final sign-off, by name. A missing or wrong answer to this question causes the most expensive kind of rework: work that gets rejected by someone who was never consulted.
Should I ask about formats before starting design work?
Yes. Exact file formats and dimensions are cheap to confirm up front and expensive to fix after the fact, since a wrong assumption here usually means a full re-export or, worse, a redesign for a different medium.
What if the client says "you're the expert, decide for me"?
Narrow the question instead of repeating it. Offer two concrete, contrasting options and ask which is closer. A specific choice gets answered far more often than an open-ended one.
What do I do if two stakeholders give conflicting answers?
Surface the contradiction back to them and ask them to resolve it before you proceed. Guessing which stakeholder has real authority is a more expensive mistake than asking the awkward question up front.