Information
Client intake
Capture what the client needs, who approves, and which materials are missing.
A new client said yes. Now make the next step obvious. Collect what you need, confirm the scope, prepare a thoughtful welcome, and begin the work with everyone aligned.
Forms and templates are separate starting points. The Business Kit organizes client records, Docs and Tasks without promising automatic onboarding emails or contract signing.
Example first-week workflow
Agreement confirmed
Scope and project owner named
Client welcome prepared
Contacts and first-week expectations
Intake reviewed
Assets and key goals checked
Kickoff prepared
Decision-maker and agenda confirmed
The next client action
Provide the approved logo files and confirm the final decision-maker before the kickoff.
Fictional example of an onboarding plan; not live client data or an automated checklist.
After the yes, before the work
Freelance client onboarding is the process of turning an accepted project into a ready-to-start engagement. It bridges your sales conversation and the actual delivery work, with enough structure to clarify expectations before anyone is surprised.
It covers the agreement, welcome, intake review, client details, project setup, kickoff, and next steps. That is broader than a contact form—and different from an ongoing client portal.
Read the detailed onboarding guideInformation
Capture what the client needs, who approves, and which materials are missing.
Readiness
Confirm the scope, create the project plan, set expectations, and prepare the kickoff.
During delivery
An optional Business feature for viewing a particular engagement, selected documents and review requests.
Relationship
Keep communicating progress, feedback, milestones and decisions after the project begins.
The end-to-end process
You do not need endless paperwork. You need each stage to produce an identifiable outcome so both sides know whether the project is ready to proceed.
Make the deliverables, schedule, revision limits, fees and decision-maker explicit before asking the client to begin work.
You should haveA written scope and starting conditions
RememberAn onboarding kit does not sign contracts or collect deposits on your behalf.
Introduce the project owner, communication channel and what happens in the first week. Request only the information needed to get started.
You should haveWelcome guide with one clear next action
RememberAvoid a long welcome packet that hides the one thing you need today.
Ask about the business, goals, audience, budget, deadlines, current assets and required access. Read the answers rather than assuming a form submission means intake is complete.
You should haveVerified client details and requirements
RememberDo not request passwords in a general-purpose form.
Record the primary contact, project name and start date. Prepare working documents and assign the actions that must happen before kickoff.
You should haveClient record, project plan and assigned tasks
RememberChanges to a Task do not automatically change every project document or record.
Confirm goals and constraints, surface missing information, assign who approves work, and recap the first milestone in writing.
You should haveDecisions, owners and next checkpoint
RememberUse the client's actual availability and agreed communication process.
Check that the brief, assets, approvals and team responsibilities are in place. Tell the client where updates and review requests will appear.
You should haveA ready-to-start engagement
RememberA client portal is an optional separate Business feature, not automatically created by onboarding.
A useful client onboarding questionnaire
Collect the information that changes how you deliver the work. These nine examples show the thinking behind a focused intake: the basics, the project goals and a clean handoff. You do not need to ask every question of every client.
Who are we working with?
What does success look like?
What do we need before kickoff?
Collect only what you need. Do not ask clients to paste passwords, API keys or confidential credentials into a generic questionnaire. Use an approved access invitation or other secure process for account access.
Worked scenario · branding project
A fictional independent designer has agreed to refresh a local company's brand identity. Rather than starting with logo sketches, the designer verifies the scope and gathers the right decisions first.
This is an example of good onboarding practice, not an automated ZuffSuite workflow or a real customer story.
Explore the welcome guide template| Checkpoint | Owner | Evidence it's ready |
|---|---|---|
| Agreement accepted | Designer + client | Approved scope, pricing and milestones |
| Welcome delivered | Designer | One contact, response cadence and asset list |
| Intake checked | Designer | Goals, audience and missing details resolved |
| Kickoff completed | Both | Approver and first design review date confirmed |
| Delivery begins | Designer | First brief and review owner documented |
ZuffSuite Business Kits
It begins with the actual client record, then brings relevant documents and Tasks into the same workflow. This is more useful than a folder of blank templates—and more honest than claiming everything runs on autopilot.
Smart Table
Store the client name, contact, project, owner, start date and current onboarding stage. Repeated kit installs reuse the shared Clients table.
Doc
Give the new client a first-week timeline, point of contact and practical expectations—not a second sales pitch.
Docs
Make deliverables, boundaries, review points and milestones explicit. They are distinct documents that you review and customize.
Doc
Prepare the decisions, participants, questions and follow-up actions needed for the first project meeting.
Tasks
Review intake, finalize the scope, send the welcome guide, schedule kickoff and confirm the start. Task updates are not automatic document edits.
The Welcome Guide and Kickoff Agenda can refresh selected client details from the Client record. However, the Kit does not automatically send welcome messages, accept contracts, collect deposits, create clients from form responses or update records when a Task is completed. Review and complete those steps deliberately.
Avoid the common bottlenecks
Problem 1
Better approach
Name an owner for reading intake answers, checking ambiguity and recording follow-up questions before the kickoff.
Problem 2
Better approach
Keep the deliverables, exclusions, revision process and approval owner in writing. Confirm changes separately instead of treating every request as included.
Problem 3
Better approach
Use one contact, one organized list of missing items, and one deadline for collecting the necessary material.
Problem 4
Better approach
Document each decision with an owner and due date. Send a short recap so the client knows what they owe and what you will do next.
Once the engagement is underway, a dedicated client-facing portal can make selected documents and review requests easier to follow. Explore the separate freelancer client portal page and its Business-plan access model.
Answers before the next project
It helps organize the period after a new client agrees to work with you and before delivery begins. A practical setup usually includes contact records, intake questions, scope documents, welcome material, kickoff preparation and assigned tasks.
Intake collects information about the client's needs, contacts and constraints. Onboarding is broader: it also confirms scope, communication, responsibilities, project setup and readiness to begin work.
Confirm the agreement, contact and approver, intake answers, required assets, payment or billing terms, project scope, first milestone, kickoff agenda and the next communication. Adapt the list to the service instead of sending every client the same questionnaire.
ZuffSuite has a public Client Intake form template you can preview. It collects contact details, service needs, budget and preferred start date. You can also browse the Client Onboarding Kit for a broader workspace setup.
No. The current Kit reserves a proposed intake-to-client rule but does not provision that automation as an active workflow. Use the intake tools and client records deliberately, and review what you enter.
No. Intake forms, scope documents and a kickoff can be organized separately from a portal. Creating and managing client portals is a distinct Business-plan feature for eligible workspace managers.
Some Kit documents use selected connected-field substitutions from the Clients record. Refresh those details when they change. It is not an unrestricted live two-way sync, and ordinary document edits do not update the Clients table.
It depends on project complexity, approvals and how quickly the client supplies the required information. A simple solo project might need a few focused steps; a multi-stakeholder engagement may require a structured first week or more. Readiness matters more than an arbitrary number of days.
No. Avoid collecting account passwords or other secrets in a general-purpose questionnaire. If access is needed, use the service's approved invitation or least-privilege access method and follow your security obligations.
Start the next client relationship with clarity
Organize client information, working documents and tasks in the Client Onboarding Kit—or begin with a simple client intake template.