Client onboarding

Client onboarding form: questions + free template

A client onboarding form gathers the information your team needs after a client agrees to proceed, so the project can start without repeated emails and missing files.

What should the form include?

• Primary contact details
• Business or organisation name
• Website or existing materials
• Main goals and desired outcome
• Target audience or customer
• Key deadline or launch date
• Useful files or brand assets
• Anything the team should know before kickoff

When should you send a client onboarding form?

Send it after the client has agreed to work with you but before the kickoff meeting or delivery work begins. That timing keeps sales qualification separate from project setup and gives your team enough context to prepare properly.

If the client has not yet committed, use a lead or consultation form instead. Onboarding questions tend to be more detailed and are easier to answer once the relationship has actually started.

Separate information your team needs now from information it can collect later

The best onboarding form is not the longest one. Ask for the details that affect kickoff: who owns the project, what outcome matters, what assets already exist, what the deadline is and where communication should happen.

Deeper discovery questions can wait until the team has reviewed the account. This reduces abandonment and means later questions can be based on real context rather than a generic questionnaire.

Use conditional questions for different client types

A freelancer, agency and consultancy rarely onboard every client in exactly the same way. Conditional logic lets the form stay short while still collecting relevant details.

For example, a website project can reveal questions about hosting and existing analytics, while a branding project can reveal questions about current assets and brand guidelines. Clients only see the questions that apply to them.

Collect files with a clear purpose

File uploads are useful when the team knows what it needs: a logo pack, current brief, analytics export, content inventory or another specific asset. Avoid a vague “upload everything” field that encourages large, unstructured submissions.

If some clients do not need to provide files, make that step optional or conditional rather than forcing everyone through it.

Design the form around kickoff readiness

A useful test is simple: after reading the submission, can the person running the kickoff meeting understand the client's goal, stakeholders, deadline, existing materials and major constraints? If not, the form is probably missing an operational question.

Conversely, if the form asks questions nobody refers to during kickoff or delivery, remove them. Onboarding should make the next step easier, not create an archive of unused answers.

Create a clean handoff from sales to delivery

Where possible, avoid making the client repeat information already collected during sales. Carry forward basic contact and project details, then use the onboarding form for the new information the delivery team needs.

This is especially important for agencies and consultancies where the person who closed the work may not be the person who runs the project.

Do not turn it into a ten-page brief

A long questionnaire can create friction before the project has even started. Collect the facts needed for kickoff first, then ask deeper strategic questions during the project when context is clearer.

A shorter, well-structured form that your team actually uses is more valuable than a comprehensive document that clients postpone or abandon.

Use the free Formni template

Open the ready-made template, change the questions and wording to match your workflow, add conditional logic where needed, then publish and share your own version.