Most onboarding questionnaires ask about taste. Taste is the easiest thing to discover and the least likely to cause a problem, because it surfaces naturally the moment you show anything.
The questions worth asking are the ones that surface constraints — the things that will not come up on their own until they cost you a fortnight.
The short answer
Stop asking about taste. Taste surfaces on its own the moment you show anything; constraints do not surface until they have cost you a fortnight. The questions that earn their place are the ones that expose them: who actually signs off, and whether anyone else holds a veto — an invisible second decision-maker is the commonest cause of late reversals; what the budget band is and what it includes, since half of budget disputes are really definition disputes about fees, procurement and building work; and what is driving the timeline, because “before Christmas” is a wish and “before the wedding in March” is a constraint with a mechanism behind it. The answers then go straight into the welcome pack.
The four that matter most
Who signs off? Not who is emailing you — who has final say, and whether anyone else has a veto. A project with an invisible second decision-maker is the most common cause of late reversals, and it is entirely preventable by asking on day one.
What is the budget range, and what does it include? People resist the question, so make it easy: offer bands rather than a blank field, and state plainly what a band typically covers. Also ask whether it includes fees, procurement and building work — half of budget disputes are actually definition disputes.
What is driving the timeline? "Before Christmas" is a wish. "Before my daughter's wedding in March" is a constraint with a mechanism behind it. Knowing which you are dealing with changes how you sequence everything.
What has already been tried? A room that has been decorated twice already tells you something about the decision-making you are about to enter.
Function before taste
Ask how the rooms are actually used, not how they are meant to be used. Where do people eat on a Tuesday? Who works from home and where? Does anyone play an instrument, keep an aquarium, need a room dark at 3pm?
These answers change plans in ways moodboards never do. A dining room nobody has eaten in for four years is a different brief from a dining room used nightly, and the client will rarely volunteer the difference.
Then ask about dislikes. People describe what they want in borrowed language and what they hate with total precision. "I can't stand grey" is worth ten Pinterest boards.
The questions that predict trouble
Not to disqualify anyone — to price and scope correctly.
"Have you worked with a designer before, and how did it go?" The answer to the second half is the informative one.
"How do you prefer to make decisions — quickly, or with time to consider?" A deliberating client is not a problem unless your timeline assumed a decisive one.
"How would you like to hear from us, and how often?" Most friction attributed to design is actually communication mismatch.
"Is there anything about this project that worries you?" The most useful question on the form. People answer it honestly, and it tells you exactly where reassurance needs to go.
The questionnaire, in twelve questions
Adapt the wording; keep the order, because it moves from easy to awkward and the awkward ones are answered more honestly once somebody is already typing.
- Which rooms are in scope, and which are explicitly not?
- Who has final say, and does anyone else have a veto?
- What is the budget range for this work — and does it include fees, procurement and building work?
- What is driving the timeline, and what happens if it slips?
- Who else is already appointed — architect, contractor, engineer?
- What is the property: age, tenure, any listing, consents or freeholder permissions?
- How will the rooms actually be used, on an ordinary weekday?
- Who lives here — children, animals, anyone with access needs?
- What must stay? Inherited pieces, an existing sofa, something sentimental.
- What has gone wrong on a previous project, or with a previous designer?
- How do you prefer to receive information — email, calls, a shared folder?
- Is there anything you would consider a disaster in this project?
Question ten and question twelve earn the whole document. The first surfaces the fear driving their behaviour, and the second names the outcome you must not accidentally deliver — both usually answered in one sentence that saves a month.
Keep it short
Twenty questions completed beats sixty abandoned. If a question would not change what you do, cut it.
Send it after they have said yes, not during the pitch. A questionnaire in the sales conversation reads as an obstacle; the same questionnaire after commitment reads as thoroughness.
And read the answers back to them in the first session — literally, out loud. It confirms you understood, it catches the things they wrote quickly and meant carefully, and it starts the project with the client feeling heard rather than processed.
What to do with the answers
They should end up in the brief, not in a folder. The budget band sets the specification level. The decision-maker answer sets who gets copied on approvals. The timeline driver sets the sequence. The worry answer sets what you address unprompted in the first presentation.
A questionnaire that does not change the project is admin. One that shapes the brief is the cheapest risk reduction available to you.
