The contract is signed, the deposit has landed, and most freelancers exhale and go quiet for a week while they "get started on the work." That week is an expensive silence. It is when the client forms their opinion of how you run projects: whether you are organized, whether you communicate, whether they made the right choice. Spend it well and they recommend you for years; spend it badly and they spend the next three months wishing they had hired someone else. This guide covers the five days between "deposit landed" and "first deliverable shipped": welcome packets, intake forms, kickoff calls, communication cadence, client portals, and the checklists that make it repeatable.
TL;DR
- Client onboarding starts the moment the deposit lands and ends when the first deliverable ships. It takes about five days: welcome packet, intake form, kickoff call, written cadence.
- The same checklist runs every engagement, same order, every time. Skipping steps because "this client is different" is how projects implode in month two.
- Use three communication channels at most: the portal for documents, chat for messaging, email for formal notices. Six channels is six places for things to get lost.
What onboarding is, and why most freelancers skip it
Onboarding is the handoff between selling the work and delivering it. The proposal sold the work. The contract made the work enforceable. The deposit funded the start. Onboarding turns those three events into a live project where both sides know what is happening, when, and through which channel. The freelancer who treats onboarding as an afterthought has built a practice that depends on every client being patient enough to figure things out for themselves. Most are not.
The common mistake is to treat the five-day window between "deposit landed" and "first deliverable ready" as private time. From the freelancer's side it looks like the start of the work — gathering materials, setting up files, opening Figma or VS Code. From the client's side it looks like silence. The fix is to make that window deliberately public: a welcome packet within an hour of the deposit landing, a kickoff call within five working days, a portal with everything the client needs in one place, and a written cadence so the client knows when to expect updates.
The freelancers who run good onboarding are not always the ones with the best craft. They are the ones who follow the same five steps for every new client. In COLO, the client management record holds the client's details, and the client portal gives the client one login to their projects, files, invoices, proposals and contracts, with per-project control over what they see. The steps themselves are yours to run; the client onboarding checklist keeps them in order.
For practices serving high-touch clients — coaches, consultants, therapists and similar — onboarding is also where the relationship trust gets built. The impression the client forms in week one carries through the whole engagement. Get it right and the client starts recommending you; get it wrong and you spend the rest of the project answering "have we heard from them?" emails.
What goes in a client welcome packet?
A client welcome packet carries seven things: a short personal welcome note, the signed contract and deposit receipt, the kickoff-call agenda and time slots, the communication cadence and channels, the client portal URL and login, the project timeline with milestone dates, and one named point of contact.
The welcome packet is the document the client opens within an hour of paying the deposit. Its job is to confirm that the project is real, that the next steps are clear, and that the freelancer they hired is organized enough to run it. Done well, it ends the deposit-anxiety window before it starts. Done badly, it is the moment the client starts to worry.
The packet needs seven things. A short personal welcome note (one paragraph, name-checked, not boilerplate). The signed contract and the deposit receipt (no rummaging through emails to find them later). The kickoff-call agenda and proposed time slots. The communication cadence and channels (when you reply, where, what counts as urgent). The client portal URL and login instructions. The project timeline with milestone dates, even if approximate. A single named point of contact for the engagement.
What does not go in the welcome packet: the entire contents of your brand book, a 12-page methodology document, three case studies, your personal life story. Keep it short. The client should be able to skim it in under three minutes and know exactly what happens next. The free client onboarding checklist template is the operational skeleton for both the packet and the broader onboarding workflow; print it, customize it, and run it the same way every engagement.
How you deliver the packet matters too. A 9MB PDF attachment is friction; a portal login where the client finds the packet next to their signed contract and deposit invoice is easier. In COLO's client portal, upload the packet and the intake form as project files, and the client sees them alongside the proposal, contract and invoices for that project. For freelancers running onboarding through HoneyBook or Dubsado, having the proposal, contract, deposit and welcome packet in one place is usually the biggest time saving in onboarding.
The packet goes out within one hour of the deposit landing, not "by end of week" or "first thing Monday". The deposit is the client's emotional commitment; the welcome packet is the freelancer's response. The gap between the two is the gap where doubt creeps in.
Intake forms: what to ask, what not to ask
The intake form is the structured questionnaire that captures everything you need to start the work. Brand assets, technical access, brief details, success criteria, key stakeholders, decision-makers, budget context, deadline drivers. Filled in before the kickoff call, it cuts the call from two hours to one and prevents the third-week "we forgot to mention" surprise that quietly doubles the workload.
A clean intake form has three sections:
- The brief: what the client is trying to achieve, the audience, the success criteria and the constraints.
- The materials: brand assets, existing content, access to relevant systems (analytics, CMS, design files) and reference examples.
- The logistics: primary contact, billing contact, stakeholders who need to approve, hard deadlines, and anything in the next quarter that affects the project.
What does not go on the intake form: thirty open-ended questions that nobody will fill in, "what is your favorite color" personality-survey items, anything the client does not actually know yet. The rule is that every question on the form has to be necessary to start the work; questions that "might be useful later" belong in a different document. Most freelancers' intake forms are twice as long as they need to be, which is why most clients fill in half of them.
For practices where the intake is heavy, such as brand design engagements, technical audits and strategy work, split the form into two phases: a short pre-kickoff intake (the essentials, fillable in ten minutes) and a longer post-kickoff deep-dive that the client fills in after the call when the project context is clear. That is the difference between a freelancer who runs a two-hour kickoff call because the client showed up unprepared and a freelancer who runs a one-hour kickoff call because the client filled in the right form.
The intake form also captures what the proposal did not. If the proposal was a one-page offer, the intake fills in the operational detail. Ask the client to upload the completed form and their assets to the project in the client portal, so both sides can find them for the life of the engagement.
The kickoff call: agenda, pace and what to decide
The kickoff call is the moment the project becomes real for both sides. The agenda is what separates a productive 60-minute kickoff from a meandering 90-minute one. Send the agenda 48 hours in advance, stick to it during the call, and write the summary within 24 hours afterward.
A clean kickoff agenda has six items:
- Introductions and roles: who is on the call, who is doing what, who makes decisions.
- Project goals and success criteria: confirmed from the proposal and the intake form, not re-debated from scratch.
- Scope walkthrough: what is in, what is out, where the boundaries are.
- Timeline and milestones: dates, dependencies, what could shift.
- Communication cadence: when, where, how and who.
- Next steps: first deliverable date, first checkpoint, first invoice timing.
What the kickoff call is not: a re-litigation of the proposal, a sales pitch for additional services, an open-ended creative discussion. The proposal sold the work; the contract scoped it. The kickoff is operational. Surprises at the kickoff stage usually mean the proposal or the intake form was incomplete. The fix is upstream, not in the kickoff itself.
Run the call on a tool the client is comfortable with. Most freelance kickoffs run on Zoom or Google Meet; either is fine. Upload the recording or your notes to the project's files so the client can revisit the discussion later, and post the summary in the project's chat conversation, which the client can read in the portal.
For coaches and consultants where the kickoff is also the first delivery moment (an intake call that produces a written report), the structure is the same but the timing compresses: the kickoff call is the first milestone. The intake form, the agenda and the summary are still non-negotiable.
The written summary within 24 hours is the part most freelancers skip, and it is the most valuable thing the kickoff produces. Five bullet points: what we agreed on goals, what we agreed on scope, what we agreed on timeline, what we agreed on communication, what the next step is. Posted in the client portal, referenced in every future check-in. Six months later, when a stakeholder you have never met joins the project and asks "what was the original scope?", the summary is the answer.
Communication cadence: when, where, how
Reactive communication is one of the biggest sources of freelance burnout. Email at 8am, Slack at 11am, WhatsApp at 3pm, text at 7pm, follow-up email at 10pm. The freelancer who runs every project on six channels with no defined cadence has built a practice that runs them instead of the other way around. The fix is to publish the cadence in the welcome packet on day one and stick to it.
A healthy freelance cadence has three rules. First, channel discipline: one channel for project documents (the portal), one for day-to-day messaging (chat), and email only for formal notices. Three channels at most. Second, response windows: chat answered in batches twice a day, email within one business day, urgent items escalated through a defined path. Third, no out-of-hours expectation: unless a premium retainer says otherwise in writing, evenings and weekends are off-limits, and you say so upfront.
This works because it closes an information gap. The client does not know that you have seven other projects, three pending proposals and plans for the evening; they assume you are waiting for their message. The cadence makes your availability explicit. "I check messages at 11 and 4" lands as professional; not checking and responding at midnight reads as reliable to the client and is unsustainable for you.
In COLO, chat gives every project its own real-time conversation that includes the client, plus direct and group chats for your team, so client messages stay next to the work. The client portal holds the documents: briefs, deliverables, proposals, contracts and invoices in one place. For freelancers running several clients at once, such as marketing agencies in their early stages or fractional consultants with four engagements, the cadence is what keeps the workload manageable. For more on choosing channels, read where client communication should live.
For practices that run communication informally through email and WhatsApp, moving to a defined channel structure can save several hours of admin a week. The clients who push back on the structure are usually the clients whose engagements were unprofitable anyway.
Client portals: what lives there and why it matters
The client portal is the one place the client opens to find everything about the project: signed contract, deposit invoice, kickoff summary, intake responses, schedule, latest deliverables, invoices, payment history and change orders. It is one login, limited to their own projects.
The portal does three jobs the email-and-Dropbox-link approach cannot. It ends the "where is the latest brief?" email, because the latest brief lives in the portal. It creates a record: approvals, signatures and deliverables are kept in one place, which helps if the engagement is ever disputed. And it gives every client the same experience: the freelancer with three portals for three clients looks more organized than the one with six email threads.
COLO's client portal covers the lifecycle from proposal to final invoice. The client sees only their own projects, never your other work, and you control per project which tasks and files they can see. Clients can accept proposals, sign contracts, pay invoices by card or PayPal, upload files and chat with you, and the portal carries your logo and brand colors. That suits marketing agencies and design studios that work with several people inside one client.
The portal also becomes your own record. Six months after a project ends, when you need to remember what was agreed in week three, the answer is in the project, not scattered across email threads and Drive folders.
For practices running onboarding through HoneyBook and Dubsado, the portal is where consolidation shows: instead of three tools the client logs into, there is one. See pricing for which plans include the client portal.
Common onboarding mistakes and how to avoid them
Five mistakes show up in freelance onboarding repeatedly. Knowing them in advance is faster than learning them the expensive way.
First, no welcome packet. The deposit lands, the freelancer says "great, I will be in touch soon" and goes quiet for a week. By day three, the client is already wondering if they made the right choice. Fix: packet within one hour, full stop.
Second, no kickoff call. "We had a discovery call already, we know what we are doing." The discovery call sold the work; the kickoff call turns it into a plan. Different goals, both required.
Third, no intake form. The freelancer starts work based on the verbal brief from the discovery call, misses three critical details, surfaces them in week three when the work is already half-done. The intake form catches those details before they become rework.
Fourth, no written communication cadence. The client emails at 10pm, the freelancer feels obliged to respond, and the client's habits set the cadence. By month two, the freelancer is burned out. The cadence in the welcome packet prevents this from day one.
Fifth, no portal. Everything runs through email, the engagement ends with seven email threads, three Drive folders and a shared Notion page nobody updated. Six months later when a question comes up, nobody can find the answer.
The fixes are operational, not heroic: the same five steps, in the same order, every engagement. The client onboarding checklist template gives you the steps; COLO gives you one place to run them. A freelancer who runs the checklist as a habit ends up with onboarding that no longer depends on memory. For a shorter walkthrough, read the client onboarding process for freelancers.
How COLO helps with this
Onboarding is the stage where the proposal, the contract, the deposit, the portal and the project have to connect. COLO keeps them in one workspace: the client accepts the proposal and signs the contract in the portal, pays the deposit invoice online, and finds the welcome packet, intake form and project files in the same place.
The client portal holds the files, deliverables, proposals, contracts and invoices for each project. Client management keeps each client's details and history in one record, and project management tracks tasks, statuses and members. An accepted proposal converts into an invoice without rekeying. Project chat keeps client conversations in the channel you named in the welcome packet.
For practices running onboarding across HoneyBook, Dubsado and email, consolidating into one workspace removes the handoffs that lose clients in the first week. For coaches and consultants, where onboarding is also a high-touch relationship moment, running the same five steps every time is what keeps the practice manageable as the client list grows.
The client onboarding checklist template is the free starting point, and COLO's Solo plan is free forever (see pricing for what each plan includes). The goal is the same whatever tools you use: make the five days between deposit and first deliverable the moment the client decides to recommend you.
FAQ
Q: What is freelance client onboarding and when does it start?
Onboarding is the five-day window between the signed contract and the first deliverable, where you set the rules of the engagement and the client forms their opinion of how you run projects. It starts the moment the deposit lands and ends when the first work product is in their hands.
Q: What should be in a freelance welcome packet?
A welcome note, the signed contract and deposit receipt, the kickoff-call agenda, the communication cadence (when and where), the client portal URL, the project timeline with milestone dates, and a single named point of contact. One PDF or one portal page, never six emails.
Q: How long should the kickoff call be?
45 to 60 minutes. Longer is a sign the agenda is unclear; shorter is a sign you have not covered the brief, the rules of engagement, or the milestone schedule properly. Send the agenda 48 hours in advance and stick to it.
Q: What is an intake form and why do I need one?
An intake form is the structured questionnaire that captures everything you need to start the work — brand assets, technical access, brief details, success criteria. Filled in before the kickoff call, it cuts the call from two hours to one and prevents the third-week "we forgot to mention" surprise.
Q: What is a healthy communication cadence with a freelance client?
One scheduled weekly update (15 minutes, async or live), asynchronous messaging in one channel during business hours, no expectation of evening or weekend response unless escalated. The cadence is written into the welcome packet so the client knows the rules from day one.
Q: Should I use email, Slack or a client portal for client communication?
A client portal for project artifacts (briefs, deliverables, invoices, decisions), a single chat channel for day-to-day messaging, email only for formal notices. Three channels max. Six channels is how things fall through the cracks.
Q: What is a kickoff checklist and what should be on it?
A repeatable list of every onboarding action — welcome email, intake form, kickoff call scheduled, portal access provisioned, asset access shared, milestone schedule confirmed, first deliverable date booked. Same items, same order, every engagement.
Q: How do I set client expectations without sounding rigid?
Frame the rules as how you protect their project, not how you protect your time. "I respond to messages between 9 and 5 so I can be focused when I am on your work" lands differently than "I do not work evenings." Same boundary, different message.
Q: What are the most common onboarding mistakes?
Five recurring ones: no welcome packet, no kickoff call, no portal, no written communication cadence, no intake form. Skipping any one of them creates a friction point that shows up in week three. Skipping all five is how projects implode in month two.
Q: How do I onboard a client I have already started work for without one?
Run the full onboarding mid-project as a "project reset." Send the welcome packet retroactively, book a 60-minute reset call, set up the portal, confirm the milestone schedule. The client may find it odd at first; by week two they will be grateful for the structure.
Related guides
Onboarding is the handoff stage; the full freelance lifecycle structure lives in the freelance business management guide. For the proposal stage that precedes onboarding, see the freelance pricing guide. For the contract that has to be signed before onboarding starts, see the freelance contracts guide. For invoicing the deposit that triggers the welcome packet, see getting paid as a freelancer. For the financial reporting side of multi-client onboarding, see the freelance taxes and finance guide. For scaling onboarding beyond a one-person practice, see the solo to small agency scaling guide.