Client Onboarding Form Template
Kickoff logistics without the email chain — contacts, access checklist, signed docs, and working agreements, with a CC field that appears only when needed.
Contract signed — now the practical part. Five minutes here replaces two weeks of "just following up on access" emails.
The two weeks after a contract signs are where client relationships quietly sour: not from bad work — no work has happened yet — but from seventeen small emails about access, contacts, and call times. This onboarding form compresses those seventeen emails into one structured pass, and its ending makes the operative promise explicit: from here, chasing is our job, not yours.
Contacts with a conditional twist. Point-of-contact and coordination email are the required spine. The phone field is framed "urgent items only" — a boundary-setting label that clients notice and appreciate. Then the branch: asked whether anyone else should be copied, a yes reveals a long-answer field for teammate names, roles, and emails; a no keeps the form two fields shorter. That show rule, visible in the Logic panel, is a small courtesy with a real effect — solo founders are not confronted with team fields that make the process feel built for someone bigger.
The access checklist is the schedule. Brand files, website admin, analytics, ad accounts, content docs — the multi-select asks which of these the client can grant this week, and the phrasing carries the deadline inside it. What gets checked becomes the kickoff agenda's first section; what stays unchecked becomes your polite chase list with dates attached. Agencies that run this discipline start billable work about a week earlier per engagement.
Documents and rhythm. The upload field accepts the signed agreement or key reference documents — PDF, up to three files — so the engagement's paper lives with the engagement's data. The working-agreements question collects the human constraints that never make it into contracts: response-time expectations, no-meeting Wednesdays, a CEO who reads everything. Knowing the sacred rules before violating them is the cheapest goodwill you will ever buy. The kickoff window select includes an async option because forcing calls on async-native clients starts the relationship with a small defeat.
Not here. Billing details and invoicing setup — finance flows through your invoicing tool with its own security posture. Scope restatements — the contract owns scope; repeating it invites drift. Satisfaction baselines — asking day-zero clients to rate anything is noise.
Who uses this. Marketing agencies, dev studios, bookkeepers, and consultancies — anyone whose delivery depends on client-side access. Fractional operators clone it per client and archive the response as the engagement's birth certificate.
Adapt it. Rewrite the access list to your stack. Wire the webhook to your project tool so onboarding answers create the project skeleton automatically. Turn on email notifications, and let partial responses tell you when a client stalled on page two — that is your cue to offer help with the access list, which is usually where they got stuck.
Frequently asked questions
Why does the teammates field appear only sometimes?
A Logic rule reveals it when "yes — add teammates" is chosen, keeping the form shorter for solo clients. Edit or remove the rule in the Logic panel.
What documents can clients upload here?
The block accepts PDFs, up to three files, sized to 10MB each — enough for the countersigned agreement and a couple of reference docs.
Can onboarding answers create the project in our PM tool?
Yes — point the webhook at your tool or automation platform; each completed form posts as signed JSON with all answers and file references.
How do I know if a client stalls halfway?
Check partial responses in the dashboard — you see which page they reached, which tells you exactly what to help with.