Client Onboarding Forms: Collecting Everything Once, Then Never Chasing

Short answer: an onboarding form should collect everything you would otherwise chase in the first two weeks — billing details, decision-makers, the brief, assets, access and dates — as a stepped form sent the day the client signs, with almost nothing marked required. As of August 2026 the technical part is trivial. The design decisions are what determine whether it gets completed.

The gap this closes

There is a predictable dead zone between "client says yes" and "work starts". It is filled with emails asking for a logo, a billing address, a login, the name of whoever actually signs things off.

That dead zone costs more than the time it consumes. It happens at the exact moment the client is most enthusiastic and most impressed by you, and it is spent demonstrating that you are disorganised. Then the enthusiasm decays, replies slow down, and the first task starts two weeks late through nobody's fault in particular.

An onboarding form closes it by asking once, in one place, while the excitement is still high.

What actually belongs on it

Six categories cover almost every service business:

Billing. Legal entity name, billing address, purchase-order requirements, the accounts email, VAT or tax number where relevant. This is the section people leave off and then chase for a month while an invoice sits unpaid because it was addressed to the wrong entity.

People. Who approves work, who to contact daily, who to escalate to. These are usually three different people and getting them wrong is the source of most first-month friction. Ask for names and roles rather than "main contact".

The brief in their words. One open box, prompted specifically: what does success look like in six months, and what has been tried already. The client's own phrasing is worth more than a tidied version, and it is frequently the most useful thing on the entire form.

Assets and files. Logos, brand guidelines, existing documents, references. Include a link field beside the upload field — for a large media library, a shared drive link beats fighting a size limit.

Access. Which systems you need, and who administers each. Note the shape carefully: you want to know who to ask, not the credentials themselves. Never collect passwords or API keys through a form — that data ends up in submission storage, notification emails and exports, which is the wrong place for all three.

Dates. Launch dates, blackout periods, holidays, the annual event everything is really pointing at. The constraint the client forgot to mention is the one that derails month two.

Structure it by who can answer

The instinct is to group by topic. Group by person instead.

Step	Section	Who answers	Blocking?
1	Company and contacts	The person you signed with	Yes
2	The brief	Same person	Yes
3	Brand assets and files	Marketing, sometimes	No
4	Dates and constraints	Same person	No
5	Billing details	Finance	Often a separate form
6	System access	IT or an agency they use	Often a separate form

Steps 5 and 6 are where onboarding stalls, every time. The person who signed the contract frequently does not know the VAT number and definitely does not have the admin login. If those fields are required in the middle of a single long form, the whole submission stops there and you receive nothing at all.

Split them into their own short forms that the client can forward. A separate three-field billing form sent to finance gets answered in a day; the same three fields buried in step five of a twenty-minute form get answered never.

For everything that can be answered in one sitting, a stepped form with an honest progress indicator is the right shape — the client sees the scope, and the length feels manageable. The branching mechanics are covered in smart multi-step forms that adapt to answers, and skipping whole sections based on an earlier answer matters here: a client with no existing brand should never see four questions about brand guidelines.

What does not belong on it

The contract. A form is not an e-signature tool. Anything that has to be legally executed belongs in a dedicated e-signature service, and trying to make a form stand in for one is where a sensible process starts creating risk.

Credentials. Bears repeating. Ask who administers the system; arrange access through that person's own invitation flow.

Everything you might eventually want. The pull toward a comprehensive form is strong and it is what produces the sixty-field questionnaire that gets abandoned in step two. Ask for what blocks the first two weeks of work. The rest comes up naturally in conversation, and you will have a relationship by then.

Anything you will not read. If nobody opens the "tell us about your competitors" answer, cut the question. Every field costs completion, and unused fields cost it for nothing.

Send it at the right moment

The same day they sign, not the following week. Enthusiasm is at its peak and never returns to that level.

Three things raise completion sharply:

A deadline tied to a real consequence. "We start on the 14th; we need this by the 10th to hit that." Not an arbitrary date — one that visibly connects to something the client wants.

A time estimate that is honest. "About fifteen minutes, and you can skip anything you need to look up." That last clause is what stops the form being abandoned at the one field they cannot answer from memory.

Almost nothing required. Mark only what genuinely blocks the first task. A form that will not submit until every field is complete gets abandoned at the field the client has to go and find. A partial submission gives you nine-tenths of what you need and a specific short list to follow up on — which is a far better position than an empty inbox. The same logic drives most of reducing form abandonment.

Turn the submission into the kickoff document

The onboarding form pays for itself twice if the submission becomes the record rather than the raw material for one.

The failure pattern is familiar: the client fills in the form, someone copies the answers into a project brief, someone else copies part of that into an invoice, and a third person copies the contact names into the project tool. Every copy is an opportunity for the brief to drift from what the client actually said.

Instead, generate the documents from the submission. On BotForms a submission can produce a branded PDF automatically — the brief, the contacts, the dates, in your template — which is the kickoff document rather than the source material for one. That mechanism is covered in generating a branded PDF from every submission; white-label PDFs sit on the Business plan and standard PDF generation is on every plan.

If you already run onboarding on a document your team trusts — a printed brief sheet or a PDF questionnaire — rebuilding it digitally is a better starting point than designing something new, because that document already encodes years of learning about what you need to ask. See converting a PDF to an online form.

The follow-up that is easy to forget

Two automatic messages, same as any other form.

To your team: a notification with enough detail to start. Naming the client and the project in it means whoever picks it up is not opening a dashboard to find out what arrived.

To the client: a confirmation of what was received and what happens next. This one carries more weight in onboarding than anywhere else, because it is your first operational act as their supplier. "Got everything — kickoff call is Thursday at 10, and we'll come back on the two items you skipped" sets a tone that a silent form does not.

The client's contact also belongs on your audience list at this point, with consent, so that the relationship survives the project ending. That mechanism is in turning form submissions into an email audience.

Multiple people, one project

Larger clients mean several people filling in several forms, and the coordination is the part that gets messy.

Two patterns work. Send each short form directly to the person who can answer it, and accept that they arrive separately — the project tool is where they get reassembled. Or, where a member of your own team is doing the collection in a meeting, give them a restricted collection link rather than an account, which is the pattern in field team form collection without account access.

What does not work is one heroic form that requires four people in a room.

The tooling question

Dedicated client-onboarding platforms exist and are typically priced per client or per seat, which becomes expensive for a small studio running a handful of onboardings a month.

For most agencies and freelancers the requirement is a stepped form with file uploads, conditional sections, a document out the other end, and no per-client fee. As of August 2026 BotForms is $29/month for Starter (1,000 submissions, unlimited forms, 100 AI-builder runs, PDF generation), $79 for Pro ($63 annually, $49 founder — 10,000 submissions, unlimited PDF tracking, five team collectors, API access), and $199 for Business ($159 annually — 50,000 submissions, unlimited collectors, white-label PDFs). Thirty-day trial on every plan, no free tier.

Unlimited forms on every plan is the part that matters for this use case, since a working onboarding process is usually four or five small forms rather than one large one. If you are comparing against a general-purpose builder you already use, a Jotform alternative worth the switch covers that ground, and the best intake form software for service businesses covers the adjacent case where onboarding and job intake are the same thing.

A working first version

Build it in an afternoon and improve it from real use:

1. List what you chased on your last three clients. That list is the form. Nothing hypothetical.
2. Split it by who can answer — the signer, finance, IT. Three forms, not one.
3. Generate the main one from a description of your service and client type, then cut anything that fails the "will we read this" test.
4. Mark only the blockers required.
5. Write the confirmation message with a real next step and a real date in it.
6. Send it the day the next client signs, and note which fields they skipped. Those are the ones to reword, drop, or move to a different form.

The measure of success is not a completed form. It is that nobody on your team sent a "just chasing that logo" email in the first fortnight.

Start a 30-day trial and build the first version, or read the feature list and published plans first.