The Freelance Client Onboarding Checklist Nobody Gives You

A project rarely goes wrong in month three. It goes wrong in week one, and month three is when you find out.

The client assumed two rounds of revisions meant two rounds per page. Nobody said who signs off. You never got access to the analytics account and lost eight days waiting. None of these are difficult problems. They are all problems of things that were never written down while everyone was still being friendly.

Here is the sequence. It takes about an hour of your time and saves weeks.

Before you sign: the questions that decide everything

Ask these on the call, before the proposal. The answers change your price and sometimes change your yes into a no.

1. What does success look like in plain numbers? "More leads" is not a brief. "Move from 12 enquiries a month to 30" is. If they cannot answer, the project will be judged on vibes, and vibes are unwinnable.
2. Who is the final approver? Get a name. Ask directly: "Who signs off the final version — you, or does it go to someone else?" The invisible stakeholder who appears in week six has ended more projects than any competitor.
3. What is the real deadline, and what happens if it slips? Sometimes there is a trade show. Sometimes the date is arbitrary. You price these very differently.
4. What have you tried before, and why did it not work? You learn the graveyard, and the graveyard tells you what they will reject.
5. What is the budget range? Ask plainly. If they will not answer, give a range yourself and watch the reaction.

The agreement: five clauses that matter

Everything else in a contract is boilerplate. These five decide whether you have a good year.

• Scope, described as deliverables. Not "a website" — "5 unique page designs, responsive at 3 breakpoints, delivered in Figma." A deliverable is countable. A description is not.
• Revisions, with a number and a definition. "Two rounds of revisions per deliverable. A round is one consolidated set of feedback from your team, delivered in one document." Without the definition, ten emails become ten rounds.
• Timeline with client dependencies. Your dates are conditional on their inputs. Write it: "Timeline assumes feedback within 3 working days. Delays shift delivery by the same number of days."
• Payment terms and what happens if payment is late. Including your right to pause work.
• Kill fee and ownership. If they cancel in week three, what is owed? Who owns the work before final payment? The answer should be: you do, until paid in full.

Send it with an e-signature link. Chasing a printed signature costs you three days for no reason.

The onboarding questionnaire

Send this the moment the deposit clears. One document, answered once, kills the drip-feed of clarifying emails that otherwise runs for a fortnight.

Include:

• Brand assets: logo files, fonts, colour codes, existing style guide
• Access: analytics, CMS, hosting, ad accounts, social logins — with who to ask if they do not have them
• Three examples of work they like, with one sentence on why for each
• Three examples they dislike, and why
• Their audience in one paragraph — who they are, what they want
• Non-negotiables: things that must appear, things that must never appear
• Preferred communication channel and their working hours
• Anything happening in the business over the next 8 weeks that could affect timing

That last one catches the reorganisation, the funding round and the two-week shutdown that would otherwise ambush your timeline.

The kickoff call, run to an agenda

Thirty minutes, and you drive it. Agenda:

1. Confirm the outcome in their words, and repeat it back
2. Walk through the deliverables list line by line — this is where mismatched assumptions surface
3. Agree the feedback process: who consolidates, in what format, by when
4. Agree the milestone dates, out loud, including their dates
5. Confirm the single communication channel
6. Say what you need from them in the next 48 hours

Then send a written summary within an hour. That summary is the most valuable document in the project, because it is where "we agreed X" comes from later.

The welcome guide

One page that answers the questions clients are slightly embarrassed to ask. Send it with the summary.

• How to send feedback (and the format that gets acted on fastest)
• Your response time — "I reply within one working day, and I do not work weekends"
• What happens if they want something outside scope: you will price it, they will approve it, then it happens
• The milestone schedule with dates
• Who to contact if you are unreachable
• How and when they will be invoiced

Clients relax when they know the rules. A relaxed client sends fewer 9pm messages.

Week one, day by day

• Day 1 — Deposit invoice sent. Questionnaire sent. Contract signed.
• Day 2 — Access requested, kickoff call booked, calendar blocks created for the work.
• Day 3 — Kickoff call. Written summary sent within the hour.
• Day 4 — Confirm all access works. Test every login yourself; do not assume.
• Day 5 — Send a short "here is where we are, here is what is next" note. Set the rhythm early.

That Friday note becomes your weekly update, and a weekly update is the single cheapest thing you can do to prevent a nervous client from micromanaging you.

Handling the scope change when it comes

It will come, and it is not a betrayal. Handle it as process, not conflict:

1. Acknowledge it warmly and immediately: "Good idea — let me price it."
2. Send a one-page scope-change request: what is being added, the cost, and the effect on the timeline.
3. Get written approval before any work happens.
4. Add it to the deliverables list so it is visible next time.

Doing this the first time a small request appears sets the pattern for the whole project. Absorbing "just one quick thing" once teaches the client that quick things are free, and by month two there will be nine of them.

The last five percent

Projects end badly far more often than they run badly. Close properly:

• Handover document: where the files live, how to edit them, what to do next
• A short recorded walkthrough — five minutes of screen recording prevents months of small questions
• Final invoice on the day you deliver, not two weeks later
• A testimonial request while they are still delighted, with a specific prompt: "What was the situation before we started, and what changed?"
• A calendar reminder to check in 60 days later

That last one is the highest-value fifteen minutes in freelancing. Most repeat work comes from a check-in nobody asked for.