Client process

Freelance Client Onboarding Questionnaire

Gather goals, audience context, assets, stakeholders, access, timing, risks, and approval expectations before delivery begins.

Customize the template

Use it for the right moment.

Send this after the project is approved and before kickoff, then review the answers with the client.

Delete questions that do not affect the project you sold.
Explain why sensitive access is needed and use a secure sharing method.
Resolve conflicting answers during kickoff instead of making silent assumptions.

Customize your working copy.

Your edits stay in this browser tab and are not sent to SolveNook.

Editable template text

CLIENT ONBOARDING QUESTIONNAIRE

Project: [Project name]
Primary contact: [Name and role]
Preferred contact method: [Email, platform, or other]

BUSINESS CONTEXT

1. What does your business provide, and who is it for?
2. Why is this project important now?
3. What has already been tried?
4. Are there existing constraints, commitments, or previous decisions I should understand?

GOALS AND AUDIENCE

5. What should be different after this project is complete?
6. Who is the primary audience or user?
7. What action should that audience take?
8. What would make this project feel unsuccessful?

BRAND, CONTENT, AND ASSETS

9. Which brand guidelines, source files, examples, or existing content are available?
10. Who owns or is authorized to use the supplied materials?
11. Are there examples you like or dislike? What specifically creates that reaction?

ACCESS AND WORKFLOW

12. Which systems or accounts require access?
13. Who will provide access, and by what date?
14. Are there security, privacy, compliance, or confidentiality requirements?

STAKEHOLDERS AND APPROVAL

15. Who gives feedback?
16. Who gives final approval?
17. Should feedback be consolidated by one person?
18. What is the expected response time during reviews?

TIMING AND DELIVERY

19. Is there a fixed deadline? What creates it?
20. Are there dates when key people are unavailable?
21. How should final files, access, documentation, or training be handed over?

SUCCESS

22. How will we judge whether the project achieved its goal?
23. What information or result should be reviewed after launch?
24. Is there anything important that the current scope does not address?

Review before you send.

Check names, dates, currency, scope, payment instructions, attachments, and promises. Keep a copy of the final version and the client approval.