Client onboarding checklist for freelancers: the scope-proof version (from "yes" to kickoff)
Most client onboarding checklists cover the admin: send the contract, send the invoice, set up a shared folder, get logins. You can see this in widely shared templates such as Zapier's. Those steps matter. But they don't touch the thing that causes most trouble later, which is that you and the client have slightly different pictures of the project.
This checklist keeps the admin and adds five scope-locking steps:
- an intake brief
- a dependency check
- a one-page scope summary the client confirms
- a stated revision limit
- a change process explained up front
The full checklist is below, grouped into four phases. Copy it, print it, or paste it into your task manager.
Why onboarding is where scope creep starts
Scope creep usually shows up mid-project as "can you also just...". The cause tends to be earlier. A goal like "a fresh look" or "some blog content" means one thing to the client and another to you. Unclear goals are a well-known early warning sign of a hard project. Freelancers Union, for example, includes it in its list of signs of a difficult client.
So onboarding is your cheapest chance to fix the problem. A question asked before you quote costs nothing. The same question asked in week three costs time, money or goodwill.
The checklist: four phases
Phase 1: Before the yes (discovery and quote)
Phase 2: The day they say yes
Phase 3: Before kickoff
Phase 4: Kickoff and the days after
The sections below explain the scope-locking steps in more detail.
The intake brief: 12 questions
Send this as a document or form after the first conversation and before you quote. Group the questions so the client can see why you're asking.
Goals
- What should this project achieve? How will you know it worked?
- Who is it for? Describe the people who will use or read it.
- What made you start this project now?
Deliverables
- List what you expect to receive. Give numbers where you can (pages, articles, screens, versions).
- Are there examples you like or dislike? What about them?
- Is there anything you already know you'll want later, after this project?
Constraints
- What's the deadline, and is it fixed or flexible? What's driving it?
- What budget range are you working with?
- Are there brand guidelines, tools or platforms we have to use?
Who decides
- Who gives feedback during the project?
- Who gives final approval? Is anyone else involved who we haven't talked to yet?
- Are other people or vendors working on this (developers, printers, agencies)?
Questions 6 and 11 do a lot of quiet work. Question 6 surfaces "phase 2" wishes before they turn up as mid-project requests. Question 11 finds the approver nobody mentioned, such as a business partner or a boss, who might otherwise appear at the final review with new opinions.
The dependency check
A dependency is anything the project needs that you don't control. Before you quote, go through the brief and list them. Common categories:
- Content and assets: copy, photos, logos, product data. Who writes or supplies them, and by when?
- Access: logins to the website, hosting, social accounts or analytics.
- Approvals: who signs off, and how quickly they usually respond.
- Third parties: other vendors, platforms or printers whose timelines affect yours.
- Paid extras: fonts, stock images, plugins, hosting. Who pays for them?
- Checks the client owns: legal, compliance or accessibility reviews on their side. Don't take these on by default.
For each item, write down who owns it and when it's due. These become the "client responsibilities" in your scope summary. If you want help spotting dependencies in a vague brief, the AI hidden-dependency check walks through one prompt, with a worked example.
The scope summary (and your revision limit)
The scope summary is a one- or two-page, plain-language description of the project. The client confirms it in writing before work starts. Include:
- Goal: one or two sentences.
- Deliverables: each item with quantity, format and "done when". For example: "5 website pages (Home, About, Services, Contact, FAQ), built in [platform]. Done when live on the client's domain."
- Timeline: milestones and dates.
- Client responsibilities: from your dependency check, with due dates.
- Assumptions: "The client provides final copy for all pages."
- Not included: written in a friendly way. "Social media graphics and ongoing updates aren't part of this project. Happy to quote them separately."
- Revisions: how many rounds, what counts as a round, and how long the client has to give feedback.
- How changes work: one or two sentences.
How many revisions? There's no standard. Two or three rounds per deliverable is a common choice among freelancers, but it's a habit, not a rule. For more on limiting revisions, see this Upwork Community thread and Freelancers Union's advice on avoiding unpaid revisions. Pick a number that fits your work and pricing, and define "a round". A useful definition is "one consolidated list of feedback", so that ten separate emails don't count as ten rounds.
A scope summary is not a contract. It describes the work in plain language and sits alongside your contract. It doesn't replace one. Payment terms, ownership, liability and cancellation belong in a contract, ideally one reviewed by a qualified lawyer where you work. This article is not legal advice.
A short kickoff agenda (30 minutes)
| Time | Item |
|---|---|
| 0-5 min | Introductions; confirm who gives feedback and who approves |
| 5-12 min | Goal and deliverables: read through the scope summary together |
| 12-18 min | Client responsibilities and their due dates |
| 18-23 min | Timeline and milestones |
| 23-27 min | Revisions and how changes work |
| 27-30 min | Questions; next steps and the first deadline |
For the "how changes work" slot, one sentence is enough: "If something new comes up, I'll tell you whether it fits the current scope. If it doesn't, I'll send a short note with the cost and timing so you can decide." Saying this at kickoff makes later conversations much easier. The guide to "that's extra" emails shows what those notes look like.
The recap email
Send this within a day of kickoff. It turns the conversation into a written record. Example (adapt freely; not legal advice, adapt to your contract):
Subject: [Project name]: kickoff recap and next steps
Hi [Client name],
Thanks for today. A quick recap so we're working from the same page:
- We're building: [deliverables, in one line]. Full details are in the scope summary you confirmed on [date].
- I need from you: [item] by [date]; [item] by [date].
- Next milestone: [milestone] on [date].
- Feedback: [number] rounds per deliverable. Please send each round as one list, within [number] working days.
- Changes: if anything new comes up, I'll let you know whether it fits the current scope, and send cost and timing if it doesn't.
Anything I've missed? Just reply here.
[Your name]
Want this as ready-to-use documents?
The checklist above is free to use as it is. The Scope Guard & Client Onboarding Kit turns it into fill-in documents and an AI-assisted workflow:
- a client intake brief template
- a scope summary template
- a kickoff pack (welcome email, agenda, "what I need from you this week")
- an onboarding checklist as a CSV for Google Sheets or Notion
- ten email scripts
- ten context-rich AI prompts, including a hidden-dependency audit
- a fictional worked example from first email to change request
It isn't a contract and it isn't legal advice. It's the process that sits around your contract.
The kit isn't on sale yet. See what's in the kit
Sources
- Freelancers Union blog post on early warning signs of a bad freelance client (2022): https://blog.freelancersunion.org/2022/02/01/6-early-warning-signs-of-a-bad-freelance-client/
- Freelancers Union blog post on avoiding unpaid revisions (2014): https://blog.freelancersunion.org/2014/09/02/how-avoid-lots-unpaid-revisions/
- Upwork Community thread on handling unlimited revision requests: https://community.upwork.com/t5/Freelancers/What-are-some-best-practices-to-handle-unlimited-revision/m-p/593678
- Zapier, client onboarding checklist template (an example of a typical admin-focused checklist): https://zapier.com/blog/client-onboarding-checklist-template/