Open the last intake form you sent.
Not the template. The actual submission.
When did the last field come back? If the honest answer is “after a week, two reminders, and a call to fill the gaps,” stop rewriting the questions.
You are asking too much, too early, of one person.
Most onboarding questionnaires ask for everything at once, to one contact, before the client’s team understands the work. The form sits. If you wait for “form complete” before anyone starts, the project sits too.
Picture this. You sent 34 fields on Friday. The marketing lead can answer six of them. IT has the access. Legal has the constraint. Finance has the date that cannot move. Your contact is now running an internal collection project they did not agree to, with no authority and no consequence they can take to a colleague. That is why it takes a week.
The fix is three waves, each tied to the work it unblocks.
What is a client onboarding questionnaire?
A client onboarding questionnaire is the structured set of questions you ask after signature so delivery can start. Discovery already happened in the sale. This is intake for the first work, not a satisfaction survey.
Every question should pass one test: name the work this answer unblocks. If nobody on your team can name that work in a sentence, drop the question.
Pull up your current form and try it. Write the unblocked work next to each field. Cut or move the blanks first.
Why does one long form stall the project?
Five things go wrong when the whole questionnaire goes out as a single request.
It ignores who can actually answer. One form usually spans a marketing lead, an IT admin, someone in finance, and a legal or security reviewer. You send it to one person. That person now has to chase their own colleagues on your behalf. This is the most common reason forms come back slowly. Rewriting the questions does not fix it.
It asks before context exists. In the first days after signature, the client’s wider team often has not been briefed. Your form is the first they hear of the project. A question that takes two minutes in week three takes a week in week one, because nobody knows why it matters.
Nothing visible happens when it is late. A form sitting at 60% has no consequence attached to it. The consequence arrives later, when a go-live date moves, and by then the cause is invisible.
You wait for the whole form before anyone starts. Then one unanswerable single sign-on question holds up four workstreams that do not need SSO.
It only ever grows. Every team adds its questions to the shared form. Nobody owns the total length, so the total length wins.
A shorter intro on the same 34-field form will not fix any of this.
How should you split the questionnaire into three waves?
Split by what each answer unblocks and when the client can realistically produce it.
| Wave | Sent when | Purpose | Typical length |
|---|---|---|---|
| 1. Start | With the handoff, several days before kickoff | Unblock the first piece of work | Short enough to finish in one sitting, around six questions |
| 2. Decide | Live, during the kickoff call | Settle decisions, not collect data | Six or seven questions, asked out loud |
| 3. Build | In batches during the build, per workstream | Collect the volume: content, data, users, edge cases | The longest, but never sent as one block |
The total number of questions may not drop much. What changes is when you ask each one and who has to answer it. That is what moves the calendar.
What belongs in wave 1?
Wave one exists to get the team started. Ask only for inputs whose absence would stop the first deliverable or force you to rebuild it later.
Six questions usually cover it.
- The first outcome, in their words. “When we deliver the first thing, what will you be looking at?” Their phrasing is more useful than yours. Any gap between the two is a scoping problem you want in week one, not week six.
- Their coordinator. One named person who can recruit colleagues internally and chase answers you cannot. A department name is not a coordinator.
- The approver for that first output. Not the committee. The person whose approval ends the discussion.
- Access to the one system the first piece of work needs. One. Not the full stack.
- Any hard constraint that could invalidate the approach. A legal review, a security questionnaire, a brand rule, a procurement step that has not started.
- Dates that cannot move. A launch, a board meeting, a company shutdown, the CFO’s holiday.
If a security or procurement review sits between signature and start, that review is your wave one. Nothing else on the first request can move until it clears. Treating it as item 19 of 34 hides the only thing on the critical path.
Send this with the sales-to-onboarding handoff, days before kickoff. Pre-fill what the AE already recorded. Ask the client to correct it, not to start from a blank page.
The agency client onboarding guide shows how to attach an owner, a due date and an acceptance test to each of these so “done” is not a matter of opinion.
Now imagine you send only those six on Monday. Kickoff is Thursday. Which of them can one named coordinator finish before the call? Most of them, if they do not also have to assemble a user list and a three-year content archive.
What belongs in wave 2?
The second wave is decisions.
Put a decision in a form field and you get one person’s guess. Nobody else heard it, so nobody else will stand by it three weeks later. Ask it on the call and the room hears the answer.
Ask these live:
- Who reviews the first deliverable before the approver sees it, and how long does that review usually take?
- Who consolidates feedback on your side, so we get one set of comments rather than four?
- What is our cadence, and which channel carries decisions?
- Who do we call on each side when something is stuck?
- What happens to the date if an input arrives a week late?
- What is most likely to delay this from your side?
That last question works where “anything else we should know?” fails. It asks for a prediction, so the client can answer without admitting a failure. What comes back is usually the most useful line in the intake.
I know what you are thinking. “We already have a kickoff agenda.” Good. These six are the decisions that agenda should close. Write every answer into the shared plan while the call is still running.
The kickoff call guide has the full agenda and the follow-up questions behind each of these.
What belongs in wave 3?
The bulk of most questionnaires is wave three: user lists, historical data, content, per-entity configuration, the edge cases.
This is the material that makes forms long. Almost none of it blocks the start.
Two rules make it come back faster.
Ask in the context of the work. A client who has seen the first draft, the first configured workflow or the first landing page answers detailed questions in a fraction of the time. The questions are no longer abstract. The same list in week one produces guesses you will redo.
Split it by workstream and attach each batch to the milestone it feeds. “We need these 40 user records before we can configure permissions on 3 September” gets answered. “Please complete the onboarding spreadsheet” does not.
A performance-marketing account might get brand assets for the first campaign in week two, then the secondary channel history when that channel is actually in scope. A SaaS implementation might get SSO metadata when SSO is the next workstream, not on the day of signature. A consulting engagement might get the second interview list after the first workshop has shown which roles actually matter.
A week-one form asks for details the client already expects to change after the first draft. Wait until the work is in front of them.
Which questions should you stop asking?
| Question type | What it costs you | Ask this instead |
|---|---|---|
| Anything already in the contract or CRM | Asking a client to retype what they gave your AE tells them your teams do not talk to each other | Pull it from the handoff and confirm it in one line |
| Anything published on their website | Research they can do for you is research you should have done | Look it up, then ask them to correct your reading |
| ”Tell us about your goals” | You get a shorter, worse version of an answer sales already recorded | Show what sales recorded and ask what has changed |
| Anything you will not act on for months | It lengthens the one wave that has to move fastest | Move it to wave three |
| ”Anything else we should know?” | Catch-alls get skipped, or produce something you cannot act on | ”What is most likely to delay this from your side?” |
If you are asking the client for information they already gave, the questionnaire is not the real problem. The sales-to-onboarding handoff is.
How do you write a question that actually gets answered?
Six rules, in rough order of how much time they save.
- Pre-fill your best guess and ask them to correct it. Correcting is faster than composing. A wrong guess still gets you a fast answer.
- Say what the answer unblocks, in the question itself. “We need this to confirm the baseline before Thursday’s recommendation” gets treated differently from the same question asked bare.
- Address a person, not a company. “The client” is not an owner and never has been.
- One decision per question. Two questions bundled into one field usually come back half answered.
- Define what done looks like. Access granted is not done. Access tested by the person who needs it is done.
- Offer options where you already know them. If there are four plausible answers, do not ask for an essay.
Compare these two versions of the same request.
Please provide details of your current analytics and tracking setup.
We can see GA4 on your site but no server-side tagging. Is that right? (yes / no / not sure). We need this confirmed by Thursday to validate the conversion baseline before the first recommendation. Owner: Priya.
The second takes one click from someone who knows, or one forwarded email from someone who does not. The first takes a meeting.
Try this on your own form tonight. Pick the three fields that come back blank most often. Rewrite each one with a pre-filled guess, an owner, and the milestone it unblocks. Send that version on the next account and see which fields still stall.
How do the waves change by business type?
The three-wave structure holds. What sits in each wave changes with the work.
| Business type | Wave 1 | Wave 2 (still live) | Mostly wave 3 |
|---|---|---|---|
| Agency or creative studio | Approved brief, platform or CMS access, the approver, brand constraints | Approval path, who consolidates comments, delay rule | Full asset libraries, secondary channels, the longer campaign calendar |
| B2B SaaS, sales-led | The first workflow to go live, the technical owner, one integration, security review status | Escalation, cadence, what happens if data is late | User lists and roles, data migration, edge-case configuration, remaining integrations |
| Consulting or professional services | The decision the work supports, the sponsor, the initial dataset, interview access | Who is in the review group, how findings get accepted | Wider stakeholder access, secondary datasets, extended research scope |
| Regulated or procurement-heavy | The compliance gate itself, who owns it, its real lead time | Who can grant exceptions, how a missed review date moves the start | Documentation volume, per-entity records, audit trails |
For a services business where the client relationship carries the project, our agency onboarding stack covers the tooling side of this in more depth.
Do not copy another team’s form because it looks thorough. Copy the wave that matches the first thing you actually have to produce.
Where should the questionnaire live?
Next to the plan. Not in a PDF. Not in an email thread. Not in a form that submits into a system the client cannot see.
Clients answer faster when they can see which milestone the answer unblocks. A PDF or a standalone form cannot show that.
Three things have to be true:
- Both sides can see the current status. No client should have to ask what is still outstanding, and no delivery lead should have to open four accounts to find out.
- Every open item has one named owner. Not a company, not a shared inbox.
- Reminders run automatically and name the consequence. “Analytics access is still open, it blocks the baseline due Thursday” works. “Just following up” does not.
For a client-facing intake that feeds directly into a shared plan, Valuecase is the strongest default we cover: forms, tasks, files and the plan live in one branded Space the client opens without a login, so the answers land where the work is. Internal production can stay in the project tool your team already uses.
If your onboarding is genuinely one short intake with one respondent, a form plus a shared checklist is enough. The threshold is coordination complexity, not company size. See onboarding workspaces vs. project tools for where that line sits.
The questionnaire is only one slice of the work. The customer onboarding checklist marks every item with an owner, including the ones a form will never collect.
How do you tell whether intake is the bottleneck?
Four measurements. You can produce all of them from your last ten clients this week.
| Measure | How to calculate it | What it tells you |
|---|---|---|
| Wave 1 turnaround | Days from request sent to the last wave-one answer verified | Whether the start itself is the delay |
| Field usage | Share of collected fields your team actually referenced in the first 30 days | How much of the form is dead weight |
| Re-ask rate | Questions your team asked again by email after the form came back | Whether the questions are answerable as written |
| Blank or “not sure” rate | Per question, across those ten clients | Which questions are aimed at the wrong person |
A high re-ask rate points at wording. A high blank rate on specific questions points at routing: the question is fine, it is just in front of someone who cannot answer it. If wave-one turnaround is long while field usage is low, you are waiting on information nobody needed.
Track wave-one turnaround next to the rest of your onboarding measurement. The onboarding metrics guide covers how it sits beside time-to-value. How to reduce time to value deals with the customer-side delay this questionnaire is trying to design out.
Open your current intake form. Write next to every question the work it unblocks. If you cannot fill one in, it is wave three at best. Move those off the first request before you rewrite a single sentence.