How to create a client onboarding form

A client onboarding form is the short set of questions you send a new client before (or right at) kickoff, so their answers — not a back-and-forth of emails — set the terms for the project. It's not a contract, and it's not the invoice. It's the document that stops "wait, I thought that was included" and "who's supposed to approve this?" from surfacing in week three, by getting the answers down on day one.

What to ask on a client onboarding form

Every onboarding form should cover the same handful of areas, whether you're a designer, developer, writer, or consultant. The specifics change by trade; the categories don't.

• Contact details. Who's the point of contact, their email, and — if it matters for your project — a phone number or a second contact for when the primary person is out.
• Project scope. A plain-language description of what's included, written the way you'd want the client to read it back to you. This is the line you'll point to later if scope starts creeping.
• Deliverables. The concrete things you're handing over — files, pages, a working build — not just the activity you're doing.
• Timeline and milestones. Key checkpoints with target dates. Most projects need somewhere around 3–6 milestones; fewer and you lose visibility into progress, more and you're managing a project plan instead of an onboarding form.
• Budget and deposit. What percentage is due upfront, if any, before work starts.
• Payment terms. How and when the remaining payments are due, and whether you're mentioning a late-fee policy upfront.
• Communication channel and response time. Where messages should go (email, a chat tool, a project-management app) and how quickly each side can expect to hear back.
• Access and assets. Anything the client needs to hand over before or during the project — logins, brand files, existing accounts, source material — that would block your work if it's missing.

Approvals and feedback rounds are worth writing down too, even though they're often the most skipped line on a form. If a deliverable needs sign-off from someone other than your main contact, or you only offer a fixed number of revision rounds, say so before the first draft goes out, not after the client is surprised by it. There's no separate field type for this on most generators — it lives wherever you list what you need from the client, or in the scope summary itself.

A sample field list you can copy

If you're building a form from scratch, this is a workable starting set:

1. Business name — yours, for the header of the document.
2. Client name — theirs, for the header and the greeting.
3. Project type — a short label for what kind of work this is.
4. Scope summary — one paragraph, client-facing language.
5. Milestones — a label and a due date for each checkpoint.
6. Communication channel — where messages go.
7. Response-time expectation — how fast either side replies.
8. Deposit percentage — what's due before you start.
9. Payment schedule — the rest of the payment plan.
10. Late-fee mention — whether you're flagging your late-payment terms upfront.
11. What we need from the client — a list: assets, access, approvals, anything that would block your work if missing.

Common mistakes freelancers make with onboarding forms

The most common failure isn't a missing field — it's timing and specificity.

• Sending it too late. If the form goes out after you've already started work, it's a retroactive record, not an onboarding tool. Send it as soon as the client has agreed to move forward, before any billable work begins.
• Writing scope for yourself, not the client. A scope summary full of internal shorthand doesn't set expectations with anyone who didn't write it. Use the language you'd want quoted back at you in a dispute.
• Leaving out what you need from them. Freelancers are usually careful to list what the client gets; they're less careful listing what they need back — logins, brand assets, approvals from a specific person. Every one of those is a potential delay you're not tracking.
• No milestones, or too many. A single "delivery date" gives you no early warning if something's off track. A milestone for every minor task turns the form into a project plan nobody reads.
• Treating it as a one-time document. Your defaults — communication channel, response time, standard payment terms — rarely change between clients. Save them once and reuse them, rather than retyping the same answers for every new project.

When to send the onboarding form

Send it after the client has said yes to working with you, but before any billable work starts — ideally in the same message as your welcome note, or immediately after the signed agreement or first invoice. Sending it earlier, before they've committed, asks for information they may not want to hand over yet. Sending it later means you're already working without written answers to the questions that most often cause disputes: what's in scope, who approves what, and what you're waiting on from them.

Build it instead of writing it from scratch

You don't need a document editor for this. TidyPapers' Client Onboarding Kit Generator turns the field list above into two documents from one form: an internal checklist for you, and a client-facing welcome brief for them, both in a single PDF. It covers business identity, project scope and milestones, communication defaults, payment terms including the deposit and late-fee mention, and a free-text list for what you need from the client — access, assets, approvals, anything that would otherwise slip through a chat thread. Your business details and default terms save to your browser automatically, so the next client's form takes less time to fill in. Your documents stay in your browser — there's no account, and nothing you type is uploaded. See the step-by-step guide for a full walkthrough of every field.

Frequently asked questions

Related: fill this out in a few minutes with the Client Onboarding Kit Generator, follow the step-by-step guide, or set your late-payment terms with the Late Payment Interest Calculator before you mention them on the form.

Also for a new client: price extra requests with the change order generator, take an upfront payment with the deposit invoice generator, or add a cancellation clause with the kill fee clause generator.