Freelance client onboarding: the checklist between 'yes' and the first hour of work
Freelance client onboarding is the short sequence between a client saying yes and your first hour of work: the agreement signed, the deposit paid and cleared, access and assets collected, one kickoff conversation, and the communication rules written down. Five essentials, eight steps in total, roughly a day of admin spread over a few days — and they prevent nearly every 'the project went sideways' story, because almost all of those stories begin with something that was assumed here instead of settled. This checklist runs the sequence in the order it should happen: do not let step five start while step one is still a handshake.
The welcome pack: send it all in one message
Do not let these eight steps dribble out across a week of separate emails — the client experiences that as disorganisation, and answers accordingly. Bundle the opening moves into one welcome message sent the day the project is agreed: the agreement ready to sign, the deposit invoice attached, the link to the shared folder, the list of assets and logins you will need, and two or three times for the kickoff call. One message, everything in it, nothing to hunt for. It reads as competence — because it is — and it quietly sets the standard for how the whole project will be run: one place, in writing, no loose ends. The steps below are what that message sets in motion, and the order they should complete in.
The message itself, ready to copy — 110 words, subject line and brackets included. Adapt the brackets; keep the shape: what happens next, the one thing you need first, and nothing left for the client to hunt for.
1. Get the agreement signed before any work starts
Scope, price and terms, in one document both sides have signed: what you will deliver, what it costs and when it is paid, what happens if the project changes or dies, and who owns the work. It is the only version of the deal either of you can point to later — memory starts diverging within a week, and every later disagreement is cheaper with a signature under it. Our guide to freelance contract basics walks the clauses in plain English, and the free scope of work generator assembles the deliverables list that sits at its centre.
2. Send the deposit invoice — and let it clear
Send the deposit invoice the day the agreement is signed, in whatever structure you agreed — half up front, thirds, the first month — and treat the cleared payment, not the promise, as the starting gun. A deposit does two jobs at once: it funds the work, and it is the cheapest seriousness test a client will ever sit. Someone who signs happily and then stalls on a modest deposit has told you, early and cheaply, how the final invoice will go. The structures are compared in our guide to freelance deposits and upfront payments; build the invoice itself with the free invoice generator. To turn the split into a dated schedule — the deposit now, the rest against milestones — the deposit and milestone schedule calculator lays out each amount with its due date counted in working days.
3. Set up one place for everything — and name one decision-maker
Create one shared folder or project space the client can see — named for the client and the job, the same name the end-of-project handover will carry — and put everything there from day one: the agreement, the brief, files, feedback, deliveries. Work that lives across four email threads and two chat apps belongs to nobody. In the same message, settle the human version of the same problem: one named person who approves work and answers questions, agreed in writing. Projects rarely stall on the work itself — they stall in the gap between three people's inboxes, each assuming another is deciding.
Expect this to matter more, not less, with an agency or a larger company: more hands will touch the work, so the named approver and properly granted access are the only defences against feedback by committee — and their invoices usually route through a separate accounts contact or a purchase-order system, which is a reason to collect the billing details in step eight now, while everyone is still responsive, rather than a reason to relax either rule.
4. Collect the access and assets — safely
List everything you need before the first working day: logins, brand files, copy, images, existing accounts, the content only the client has. Ask for logins the safe way — shared through a password manager, or as temporary access you hand back at the end — never as passwords pasted into an email, where they sit in two inboxes forever. Keep a short 'still waiting on' list in the shared folder and update it as items land. Most first-week delays are simply missing inputs, and starting without them does not remove the delay — it moves it into the paid work, where it costs more. Ask for originals rather than screenshots and the current version rather than the one from two redesigns ago: rebuilding from a flattened image or last year's logo file is billable-looking work that produces nothing, and it is entirely preventable in this one step. When a wait like this outlasts the first week, it stops being onboarding and becomes a stall — what to do when a project stalls on the client covers the two-door conversation, the formal pause and the restart.
Two refinements make this step work in practice. First, ask to be added properly: most systems let the client invite you as a user, with a role they choose and can revoke — their password stays theirs, and your access can be switched off the day the project ends. Say that in the welcome pack, framed as what it is: a protection for the client, not a lecture. Where a tool genuinely has no roles to give, the client performs the login step themselves with you on a call or a screen share, and hands over the result rather than the keys. And if a password lands in your inbox anyway — once in a while, it will — do not use it: reply with the proper route, then delete the message. Declining a password politely is one of the fastest trust signals you will ever send a new client.
5. Hold one kickoff conversation
Thirty to forty-five minutes, after the paperwork and before the work. Cover four things: the goal in the client's own words — write it down as they said it, because it is what 'done' will be judged against; the timeline, with milestones rather than one distant deadline; what the finished thing looks like, concretely; and the review rhythm — how many rounds, and how quickly each side turns feedback around. A kickoff feels like a courtesy. It is actually the last moment when mismatched expectations are free to fix. Do not confuse it with the discovery call — that earlier conversation, covered in our discovery call script, is where the job was scoped and priced; the kickoff assumes that price already exists.
6. Write down the communication rules
One short message that settles: the channel decisions happen in (pick one — email or the project tool, not both plus texts), your working hours, how fast each side normally replies, and how changes get requested — in writing, and priced before they start, exactly as the agreement says. None of this feels necessary while everyone is friendly, which is precisely when it is easy to agree. Every 9pm 'quick call?' and every corridor variation of 'while you're at it…' traces back to rules nobody set at the start. The fuller version of this step — hours, response windows and channels written as one published paragraph, and how to hold it kindly when it wobbles — is our guide to freelance availability and boundaries.
7. Schedule the first milestone — and state the payment calendar
Put milestone one in both calendars with a real date — counted in working days, not calendar days, so weekends stop quietly eating the schedule (the working days calculator does that arithmetic for you). Then, in the same breath, state the money schedule out loud and in writing: which invoices go out at which milestones, for how much, and on what terms — due dates included. A payment calendar agreed while the project is still exciting is just a schedule; the same conversation held after an invoice has gone overdue is a negotiation. If the vocabulary of terms is new to you, freelance payment terms explained decodes Net 7, 14 and 30 before you have to use them. How the milestone slices themselves should be sized, triggered and signed off is covered in milestone payments explained.
8. Do your own internal setup — including the boring billing details
Create the project in your time tracker or project tool with the agreed rate and terms noted against it, so the first timesheet is not reconstructed from memory. Give the client a file of their own in your records while you are at it — agreement, welcome message, deposit receipt, kickoff notes — so that anything about this engagement can be found in one place in six months' time, by you, in under a minute. And collect the client's invoice details now, not at billing time: the exact legal name and address your invoices should carry, their accounts contact, and any purchase order or reference number they require. Your first real invoice should take two minutes to send; the classic fortnight lost at payment time is an invoice rejected because the billing entity was wrong. Our freelance invoice checklist lists every field that invoice will need.
The first week: one small promise kept, every surprise raised early
Onboarding ends; the first week decides whether the client relaxes. Deliver one small, visible thing early — a first draft, an audit summary, one fixed page — chosen because it is finishable, not because it is impressive: a small promise kept on time beats a large one still pending, and it proves the kickoff's words were operational rather than ceremonial. Start the check-in rhythm exactly as agreed in step six, even when the first update is only 'inputs received, work begun' — the cadence itself is the reassurance. And surface surprises now, while they are cheap: the missing file that changes the plan, the assumption in the signed scope that turned out to be wrong, the approval that takes a week instead of a day. A surprise raised in week one is a scheduling note; the same surprise discovered in week six is a conflict, usually about money. Your other clients do not pause while this one onboards, either — which is precisely why the sequence above runs as a checklist rather than an improvisation (see managing multiple clients at once for running several of these in parallel).
Red flags during onboarding — and the calm response
Deposit resistance. 'We always pay on completion' is a policy that transfers all the risk to you. Restate your terms once, offer a smaller first milestone instead of a waiver if the sum is the problem — and treat a flat refusal as information, not a negotiating position. If the refusal survives every honest structure you offer, act on the information: our guide to when to say no to a project covers the polite, final version of that conversation.
No single decision-maker. Feedback arrives from three people and contradicts itself. Ask, in writing, who signs off each deliverable. 'We'll all review it' is a scheduling risk: either name the approver, or price the extra rounds it will cause.
'Start now, paperwork later.' Urgency today has a way of becoming amnesia at signing time. Offer the fastest honest version — a one-page agreement signed today, work starting when the deposit clears. If later never comes, the correct amount of work has been done: none.
Questions
The checklist on one page — and kept as a template
The eight steps compress into a single page you can tick off per client:
- Welcome pack sent — agreement, deposit invoice, folder link, kickoff times
- Agreement signed
- Deposit paid and cleared
- One project folder created, named for the client and the job
- Access granted the safe way — invites and roles, never passwords
- Decision-maker named, in writing
- Kickoff held — the goal recorded in the client's words
- First milestone dated, counted in working days
- Communication rhythm agreed — channel, hours, response windows
- Project-end retrospective pencilled into the diary
Keep that page where your other reusable documents live — it is a template, not a memory test (our guide to building a freelance template library covers where it belongs and how it should be versioned). Client twelve should onboard exactly like client two — only faster, because the list exists, the welcome message is already written, and the only new work is the client's name in the brackets.
Related: onboarding is the bridge
Onboarding sits in the middle of the chain: the proposal won the yes, the agreement and deposit made it real, and this checklist turns it into a project that can actually start. Run it the same way every time, for every client, and the first hour of work stops being the moment you discover what was never agreed. The loop closes at the other end of the project: a job that finishes well is where your next testimonial comes from, and asking while the result is still fresh is a skill of its own — see our guide to getting testimonials and case studies. The same discipline runs in the other direction when someone starts work for you: our guide to briefing a subcontractor turns the agreement into the one-page document the work is actually done from. And this checklist has a mirror at the far end of the job: our guide to writing a project handover document closes a project with the same deliberateness — five blocks that hand over the files, the access and the know-how, so the ending is as clean as the start.