Client Onboarding Questionnaire | 25 Questions That Matter
A client onboarding questionnaire should make decisions, not collect answers nobody reads twice. Its job is to settle six decisions before kickoff, so the call runs on answers rather than introductions. Below are 25 questions, grouped by the decision each one informs. Each carries what a useful answer looks like, plus the action to take when the answer exposes risk.
What a client onboarding questionnaire is actually for
A client onboarding questionnaire is a structured intake form sent to a new client right after contract signature. It collects the scope, success, stakeholder, workflow, asset and risk information your delivery team needs to run kickoff without guessing.
That is the whole purpose. It is not a record. It is not a polite formality between the contract and the first invoice.
The failure mode: fields nobody uses
Look at the Jotform client onboarding questionnaire template currently ranking on page one. It carries more than 70 fields, and several of them ask for height, weight and current medications. The template was built for a fitness coach. Agencies still copy it, cut a few rows, then send it to B2B clients.
What follows is predictable. Your client spends 20 minutes on it. Someone files the response in a folder. Nobody opens it again, so the kickoff call reruns half the same questions live.
The rule: one question, one decision
A question earns its place only if the answer changes something you do. A new scope line. A different timeline. An extra approver. A risk task nobody had planned.
If no decision moves, delete the question. Apply that rule honestly and a typical client onboarding questionnaire loses half its length.
What survives sorts into six decisions: scope, success, stakeholders, workflow, assets and risk. The 25 questions below sit under the decision they feed.
When to send it
Send it within 24 hours of contract signature, before you schedule the kickoff call. That order matters. A client onboarding questionnaire that lands after the kickoff invitation reads as homework, and homework slides.
Sent first, it does something better. The answers become the kickoff agenda, so you spend the call on the two or three things the form could not settle. That is also the point where it plugs into your client onboarding checklist, as the gate between signature and kickoff.
The 25 questions, grouped by the decision they inform
Copy the bold lines. Together they are the client onboarding questionnaire, in order, ready to paste into a form. The line underneath each one is for you, not for the client.
Decision 1: What are we actually delivering? (5 scope questions)
These five write your statement of work. Get them wrong and you renegotiate scope in week 8, from a weaker position.
1. What outcome are you hiring us for, in your own words? Good answers name a business result, not a deliverable. The sentence becomes the outcome line of the SOW, in their language.
2. What does the finished deliverable need to contain to be accepted internally? Good answers list contents and format. Vague answers here become revision rounds later, so push for specifics.
3. What is explicitly out of scope or off-limits? Good answers name things. If the client says "nothing", you write the out-of-scope list yourself and get it confirmed.
4. What deadline is this tied to, and what happens on your side if it slips? A date with a consequence attached is real. A date without one is a preference, so plan accordingly.
5. Has anyone attempted this before, internally or with another vendor, and what happened? This is the cheapest risk detector on the form. A prior failed attempt predicts your scope fight, because whatever stalled it is usually still there.
Decision 2: How will we both know it worked? (4 success questions)
These four become the success section of your mutual success plan. Skip them and "success" gets decided at renewal, by someone who was not on the kickoff call.
6. What metric should we measure success with? Good answers name one metric, not four. Push back on lists, because a project with four success metrics has none.
7. What number is that metric at today? The baseline question. Without it you cannot prove improvement later, so treat a blank here as a task, not as a shrug.
8. What would make this a clear win in 90 days? Good answers are concrete enough that a stranger could check them. This is the strongest question on OnRamp’s list too, but they ask it without asking for the baseline first.
9. Who reports that result upward, and to whom? The person who reports it defines what counts. If you have never spoken to them, request an intro before kickoff.
Decision 3: Who approves, who blocks? (4 stakeholder questions)
The output here is a stakeholder map attached to the kickoff agenda. Four names, four roles, no ambiguity.
10. Who is our day-to-day contact, and who is the decision-maker if that is someone else? Often it is someone else. Then your day-to-day contact needs a route to that person, so agree it now.
11. Who must approve the final deliverable? Good answers give names and an order. Two approvers without a sequence means a two-week delay waiting to happen.
12. Who could veto or pause this project, even if they never attend a call? This question catches the week-8 surprise: legal, security, a regional lead, a founder with opinions about brand. Ask for the name while everyone is still friendly.
13. Who else will use or be affected by the deliverable? Good answers reveal a second audience you had not priced. Better to find them in the form than in the first review.
Decision 4: How do we work together? (4 workflow questions)
These four become the working agreement in your kickoff document. They take two minutes to answer and remove most of the friction people blame on personality.
14. What is your preferred channel for day-to-day work: email, Slack, or a shared portal? Pick one and say so in writing. Two channels means every message lives in the one nobody checked.
15. What response time should we both commit to? Insist on a number, in both directions. "Quickly" is not a commitment, so convert it before kickoff.
16. What meeting cadence works, and which recurring slot suits you? Book the series at kickoff rather than one meeting at a time. Otherwise the cadence quietly becomes monthly.
17. How do you want bad news delivered? It sounds soft, yet it sets your escalation norm. Some clients want a call the moment a date wobbles. Others want it batched into the weekly status.
Decision 5: What do we need in hand before work starts? (4 asset questions)
Missing assets delay more projects than difficult work does. So this is the part of the client onboarding questionnaire that pays for itself fastest. Make the asset list a commitment with an owner, not a wish.
18. Which brand assets and guidelines apply, and can you send the files? Files, not links to a drive that expired last year. Check that you can open every one before kickoff.
19. Which systems will we need access to, and who administers each one? "IT" is not an answer. You need a named admin per system, since access provisioning is usually the long pole.
20. What existing material should we reuse, and what must we not contradict? This protects you from the reviewer who appears in week 6 holding a document you never saw.
21. Who provides anything missing, and by what date? This one turns a shopping list into a commitment. Competitors list the assets and stop there, so their forms produce a list nobody owns.
Decision 6: What could sink this project? (4 risk questions)
Clients answer these honestly more often than you expect, mostly because nobody usually asks.
22. What worries you most about this project? Good answers hand you the real risk register. Whatever they name first is what they will judge you on.
23. What has frustrated you about working with vendors before? OnRamp asks a version of this and they are right to. It tells you which behavior to over-perform from week one.
24. Are any internal changes coming up that overlap with this timeline? A reorg, a product launch, a code freeze, an audit. Any of them can freeze your project, so rebuild the schedule around them now.
25. How did you hear about us, and why did you choose us over the alternative? Honest double duty: it is marketing attribution, and it also tells you what they expect you to be good at.
The answer-to-action table
A client onboarding questionnaire earns its keep here, not at the moment the client hits submit. This table maps each red-flag answer to the action you take before kickoff, so the form stops being a filing exercise.
| Q | Red-flag answer | Do this before kickoff |
|---|---|---|
| 1 | Names a deliverable, not a result | Ask what changes for their business once it exists. Rewrite the SOW outcome line. |
| 3 | "Nothing is off-limits" | Draft the out-of-scope list yourself, then get it confirmed in writing. |
| 4 | A date with no consequence attached | Treat it as soft. Do not build the critical path around it. |
| 5 | "We tried last year and it stalled" | Ask what stalled it. Add that cause to the risk list before you price anything. |
| 7 | Blank, or "we don’t measure that yet" | Add a measurement task to week 1. No baseline, no proof at renewal. |
| 9 | A reporter you have never spoken to | Request an intro. That person owns the definition of success. |
| 11 | Two approvers, no order | Agree the approval sequence and the review window at kickoff. |
| 12 | "Nobody", or left blank | Ask again, by name. An unknown veto holder is the most expensive blank on the form. |
| 15 | Response time given as "quickly" | Convert it to a number in both directions. Write it into the working agreement. |
| 19 | Access owned by "IT" | Get a named admin per system, plus a date for each request. |
| 21 | Assets promised with no owner or date | Assign both. An unassigned asset list is a delay you will absorb silently. |
| 24 | A reorg, launch or freeze inside your window | Move the schedule now. Week 6 is too late to renegotiate a date. |
The two rows that matter most
Row 7 protects your renewal conversation. A success metric without a baseline is theater, because nobody can compare the result to anything.
Row 12 protects the project itself. Every service business has a story about the stakeholder who surfaced in week 8 and rewrote the brief. That person was on the org chart all along.
How to build and send your client onboarding questionnaire
Format: 25 questions, six sections, few required fields
Cap your client onboarding questionnaire at 25 questions. Group them under the six decision headers above, because a form with visible sections reads shorter than the same questions in one column.
Mark a field required only when a blank genuinely blocks kickoff. Questions 12, 19 and 21 usually qualify, while the rest can arrive incomplete without stopping anything.
Use conditional branches for anything that applies to some clients only. OnRamp recommends progressive disclosure for exactly this, and the pattern works. Enterprise clients see the security and procurement questions. A four-week SMB engagement never does.
Tooling: any form builder will do
Typeform, Google Forms, Jotform, a Notion form, whatever your client portal already offers. The thinking is the product here, not the software. No client onboarding questionnaire gets better because the form builder costs more. So pick the tool your clients open without creating an account, then stop optimizing that decision.
Send it, chase it once, then offer to fill it live
Send within 24 hours of signature. Give a due date, not "whenever you get a chance". Then send exactly one reminder after three days, addressed to the person who signed rather than the whole thread.
If it is still open on day five, offer to fill it in together on a 20-minute call. You get better answers than the form would have produced, and the project stops waiting. No reliable public completion benchmark exists for B2B intake forms, so track your own: sent, started, completed before kickoff, and completed with help.
What Corso asks before a customer education project
Here are five questions from the client onboarding questionnaire above, adapted to a customer education engagement. The structure survives the translation, and the six decisions stay identical.
Who exactly will take this training, and what is their job title on the day they take it? (Decision 1: scope. Admins and end users need different content.)
Which product workflow costs your team the most support time right now? (Decision 1, and it usually reorders the whole content plan.)
What are the top three support-ticket themes from the last 90 days, and how many tickets did each generate? (Decision 2: the baseline. Without ticket volume today, nobody can prove the training worked. Our customer education KPIs guide covers the rest.)
What content already covers this workflow, where does it live, and who last updated it? (Decision 5: assets. Half the time something usable exists, so you rewrite instead of starting over.)
Who administers your LMS or help center, and can they grant edit access this week? (Decision 5 again, and the single most common cause of a slipped launch date.)
Notice that none of these ask what the training video should look like. Format is our decision. The client owns the outcome, the audience and the constraints.
FAQ
How many questions should a client onboarding questionnaire have?
For a B2B services engagement, 25 questions split into six sections is a practical starting point, not a universal benchmark. Shorter projects should ask less. Complex enterprise work may need conditional follow-ups. The real test is whether every question changes a decision and whether every required answer is used before kickoff.
When should you send a client onboarding questionnaire?
Within 24 hours of contract signature, and before you schedule kickoff. The answers should shape the kickoff agenda rather than repeat it. Give a due date, chase once after three days, then offer a 20-minute call to fill it in live.
What is the difference between a client onboarding questionnaire and a discovery call?
Sequence them instead of choosing. The questionnaire collects the facts: names, dates, systems, baselines, constraints. The call goes after depth: motivation, politics, the thing they did not want to type. Run the form first, so you never spend a paid hour asking who administers the CMS.
Should a client onboarding questionnaire sit in a client portal or go out as a form link?
Send a plain link unless the client already lives in your portal. Portals add a login, and a login is the most common point of abandonment on an intake form. Once they have a portal account anyway, move it there. Either way, copy the answers into whatever your team actually opens on a Monday.
Ask better questions, then remove the friction they expose
A client onboarding questionnaire tells you where clients get stuck. A Corso adoption pilot runs on the same thinking and then fixes it. We ask six decisions’ worth of questions, then rebuild the workflow your customers stall on as content they can use without you. It is the fastest route to higher product adoption that does not need a new feature.