Client Onboarding Checklist for Freelancers (Copy-Paste Template)
Client onboarding is everything between "yes, let's do it" and the first real milestone. It's where you confirm what was agreed, get access to what you need, agree how you'll work together and set the first date. When it's skipped or rushed, the same problems tend to show up later: missing logins, unclear approvers, feedback from three different people and a scope nobody wrote down.
You don't need a client portal or special software for this. A checklist, a welcome note and a shared folder cover it. Below is a copy-paste onboarding checklist for freelancers, adapted from the kickoff pack and Client Journey Checklist in our Client Ops Starter Kit.
The onboarding checklist at a glance
Before you say yes (intake)
- Goals, audience and what success looks like, in the client's words
- Deliverables they expect, and anything they assume is included
- Deadline, and what's driving it
- Budget range, and who approves spend
- Who gives feedback and who makes final decisions
Before kickoff
- Proposal accepted
- Scope of work accepted in writing (inclusions, exclusions, revision rounds, change-order rule)
- Payment terms confirmed; deposit invoiced if you take one
- One named decision-maker for approvals
At kickoff (welcome note)
- Goals restated as observable outcomes
- Access and assets checklist, with a due date
- Working rhythm: update day, review turnaround, response times, urgent channel, tools
- Risks and open questions, each with an owner
- Next actions for both sides, with dates
- First milestone: what, when and what you need to hit it
- Client replies to confirm
First week
- Access items received and tested
- Shared folder set up
- First weekly update sent on the agreed day
The rest of this guide explains each stage and gives you text to copy.
Stage 1: Intake questions to ask a new client
Whether you use a form, an email or a discovery call, these questions give you enough to price and scope the work:
- What are you trying to achieve with this project? What would make it a clear success?
- Who is it for (customers, users, internal team)?
- What do you picture being delivered? Is anything else assumed to be part of it?
- Is there a deadline? What happens if it moves?
- What budget range are you working with?
- Who will give feedback, and who has the final say?
- What already exists that I should see (brand files, current site, past work, examples you like)?
- What tools does your team use day to day?
Write the answers down in the client's own words. They become the "Understanding" section of your proposal and the goals in your kickoff note.
Stage 2: Before kickoff, get the basics in writing
Onboarding goes more smoothly when these are settled first:
- Scope of work accepted. It should list inclusions with acceptance criteria, exclusions, revision rounds (and what counts as one round), client responsibilities and a rule that out-of-scope requests need a written change order. If the scope starts in your proposal, our guide to how to write a freelance proposal shows how to list inclusions and exclusions up front. Our guide to handling scope creep with a change order covers that rule in detail.
- Payment terms confirmed. Due dates, deposit (if you take one), milestones and what happens if an invoice runs late.
- One decision-maker named. Feedback can come from several people. Approvals should come from one.
A common rule of thumb: don't start production work while the proposal is still open. Clarifying questions are fine. Deliverables wait for the yes.
Stage 3: The kickoff welcome note (copy-paste)
Send this on the day the scope is accepted, or the next business day. Paste it into an email, or into Notion, Google Docs or Word.
Subject: Kickoff: [Project Name]
Hi [Name],
Thanks for kicking off [Project Name]. This note confirms goals, access, how we'll work together and the first actions.
GOALS (success looks like)
1. [Goal 1, observable]
2. [Goal 2, observable]
Items not listed in the scope still need a change order before work starts.
ACCESS AND ASSETS: please share by [date]
[ ] Brand files / logos / fonts
[ ] Existing site / repo / hosting / CMS access
[ ] Analytics or ad accounts (if relevant)
[ ] Examples or inspiration links
[ ] Current copy / product info / pricing
[ ] Decision-maker availability for reviews
[ ] Tool invites (chat / docs / design files)
How to share: [shared folder link / password manager invite]
HOW WE'LL WORK
- Updates: [day and time, e.g. Fridays by 4pm]
- Review turnaround: [e.g. 2-3 business days for consolidated feedback]
- Routine response time: [e.g. 1 business day]
- Urgent: [e.g. subject line starts with URGENT]
- Decision-maker: [one named person]
NEXT ACTIONS
- Me: [action], by [date]
- You: [complete the access checklist], by [date]
FIRST MILESTONE
[Milestone name], target [date]. To hit it, I need [access / feedback / assets].
Please reply "Kickoff confirmed" or note any corrections.
[Your name]
Why each part is there:
- Goals as observable outcomes make reviews easier later. "Mobile-first homepage with a clear menu path" is easier to check than "a better website."
- An access checklist with a date turns "send me whatever you have" into a list with a deadline.
- Working rhythm sets expectations for response times and feedback before anyone is waiting on anyone.
- A confirmation reply gives you a written record that both sides agree on the starting point.
Stage 4: The first week
- Test access as soon as it arrives. A login that doesn't work is better found on day two than on the day you need it.
- Set up one shared folder with a simple structure, for example
01_Assets,02_Working,03_Deliverables. - Send the first weekly update on the agreed day, even if it's short: status, what's done, any decision needed (with a date) and whether the timeline still holds.
A short, predictable weekly update also gives you a clear record if dates move because access or feedback arrived late.
Your internal checklist (not sent to the client)
- Client and project added to your tracker
- Scope, proposal and kickoff note saved together
- Deposit received (if you take one) before production starts
- Review dates in your calendar
- Weekly update day blocked in your calendar
- Payment reminder schedule decided before the first invoice goes out (see how to follow up on an unpaid invoice)
FAQ
What's the difference between client onboarding and a kickoff? Onboarding is the whole stretch from yes to the first milestone: scope, payment terms, access and rhythm. The kickoff note or meeting is one step inside it, where you confirm goals, access and next actions.
Do I need a client portal? Not to start. A clear welcome note, a shared folder and a weekly update cover the essentials. If you later want a portal, the same checklist moves over.
Should I use an intake form or a call? Either works. A form is easy to reuse, and a call is better for complex projects. Use the same questions either way, and write down the answers.
Can I use this in Notion, Google Docs or Word? Yes. It's plain text, so it pastes into any of them.
Is this legal advice? No. These are business drafts to adapt and review. Have qualified counsel review any agreement you intend to rely on as binding.
Where this fits
The Client Ops Starter Kit's Client Journey Checklist maps each stage of a project (proposal, scope, kickoff, weekly updates, extra-work approval, invoice and follow-up) to the document to open. It comes with a full kickoff pack, the Offer Snapshot, a Scope & Extra-Work Agreement, AI prompts and five worked examples that follow one fictional project. The kit is plain Markdown files that paste into Notion, Google Docs or Word. You can read more on the home page, or start with the free sample.