A Client Onboarding Checklist for Freelancers and Small Agencies

The first week of a project sets the tone for everything after it. When onboarding is rushed, the cracks show up later as missing files, surprise stakeholders, unclear feedback and arguments about what was included. When onboarding is calm and complete, the client knows what happens next and you can get on with the work.

This checklist is written for freelancers and small agencies. It is organized in the order things usually happen, with templates you can adapt. Skip what does not apply, but do not skip a step just because it feels awkward to ask.

Why onboarding deserves a checklist

Onboarding is repetitive, and repetitive work is where steps get forgotten. You might remember the contract every time but forget to ask who has final sign-off, or collect the logo files but not the brand fonts. A written checklist turns "I think we covered that" into "we covered that."

A checklist also makes you look organized to the client. A new client is often a little anxious at the start: they have just committed budget and do not yet know how you work. A clear, structured onboarding answers their questions before they ask them.

Stage 1: Paperwork before any work starts

Do not start production until these are done. Starting early "as a favor" is how unpaid work and unclear scope begin.

A signed agreement

Your agreement should cover, at minimum:

• Scope and deliverables. What you will produce, in what formats, and what is explicitly not included.
• Revision rounds. How many rounds are included at each stage and how extra rounds are handled.
• Timeline. Key dates, including the dates the client must give feedback by.
• Fees and payment terms. Amounts, currency, deposit, due dates and late-payment terms.
• Ownership and usage rights. When and how rights to the final work transfer, and what you may show in your portfolio.
• Ending the engagement. What happens if either side needs to stop early.

Some places require written contracts for freelance work. New York City's Freelance Isn't Free Act, for example, requires contracts worth $800 or more (including smaller jobs with the same client that add up to that amount within 120 days) to be in writing and to state the work, the pay and the payment date (NYC DCWP). Rules differ by location, so check what applies where you and your client are based, and consider having a lawyer review your template once.

For tips on keeping the scope intact once work begins, see our guide to managing scope creep.

Billing details and paperwork

• Confirm who receives invoices, the billing address and any purchase-order number the client needs on invoices.
• In the US, clients commonly request a Form W-9 from contractors so they have the taxpayer identification number they need for information returns (IRS). Have yours ready.
• Agree how you will confirm any change to bank or payment details. The FBI's guidance on business email compromise recommends verifying account-change requests through a second channel rather than trusting an email alone (FBI IC3). A simple rule for both sides ("we confirm payment-detail changes by phone") protects you and your client.

Stage 2: People and communication

Name the decision-maker

Ask directly: "Who gives final approval on deliverables?" You want one name. Other people can and should give input, but one person decides. If the client cannot name one, that is useful information: build extra review time into the schedule.

Also record:

• the day-to-day contact (often different from the decision-maker),
• anyone who must be consulted before approval (legal, a founder, a brand team),
• anyone who should simply be kept informed.

Agree how you will communicate

Settle these in writing during the first week:

• Where project communication happens. One place for files, updates and decisions; quick questions can still happen by message.
• Response times. For example: "We reply within one business day; we ask for feedback within three business days of a review request."
• Update rhythm. A short written update every week works well for most projects. A short Friday note covering progress, next steps and anything you need is enough.
• Meeting rhythm. A kickoff, then check-ins only at review points unless something needs discussion.

Stage 3: Collect what you need from the client

Most project delays in the first month come from waiting on the client for inputs. Make the list explicit, give each item an owner and a date, and ask for everything at once rather than in a slow trickle.

A typical collection list:

• Logo files in vector format (SVG, Adobe Illustrator or EPS) plus PNG
• Brand guidelines, fonts and color values
• Existing copy, or the name of the person who will write it
• Photography and video they own the rights to use
• Examples they like (and dislike), with a sentence on why
• Access to relevant systems: website CMS, hosting, domain, analytics, social accounts
• Any legal or compliance requirements (disclaimers, accessibility standards, approval chains)

On access and passwords: ask for your own user account on each system where possible, rather than a shared login. If a password must be shared, avoid email and chat. A password manager with a sharing feature is a better route; NIST's digital identity guidelines require services to allow password managers precisely because they make stronger passwords more practical (NIST SP 800-63B). Note every access you receive so you can hand it back cleanly at the end.

Our guide to organizing client assets covers how to store these once they arrive.

Stage 4: The kickoff meeting

Keep the kickoff to 45–60 minutes and send the agenda in advance.

Kickoff agenda template

1. Introductions (5 min). Who is who, and each person's role in the project.
2. Goals (10 min). What does success look like in three months? How will the client judge it?
3. Audience and constraints (10 min). Who the work is for, what must be avoided, and any fixed dates.
4. Scope walk-through (10 min). Read out the deliverables and what is not included. Invite questions now.
5. Process (10 min). How reviews, feedback and approvals work, including the number of revision rounds and the decision-maker.
6. Inputs and dates (5 min). Walk through the collection list and agree due dates.
7. Next steps (5 min). What happens this week, and when the client will next hear from you.

Write up the decisions the same day and share them. A short summary that the client confirms is worth more than a perfect memory of the call.

Stage 5: The welcome email

Send this after the kickoff. It becomes the reference the client returns to.

Subject: Welcome aboard: how the website redesign will run

Hi Priya,

Thanks for a great kickoff. Here is a summary of how we'll work together:

• Your project page: all files, updates and approval requests will be in one place. You'll get an email when something needs you.
• Who decides: you give final approval; Marcus and Lena will add input on content.
• Timeline: first design review on May 6, second review on May 20, launch target June 10.
• Feedback: please send consolidated feedback within three business days of each review. Two revision rounds are included per stage.
• What we need from you by April 29: logo files, brand fonts, current site login (via the password manager invite), and the product photography.
• Updates: a short written update every Friday.

If anything here doesn't match your understanding, reply and we'll fix it before work starts.

That final line matters. It invites corrections while they are still cheap.

Stage 6: The first two weeks

Onboarding is not finished when the welcome email goes out. In the first two weeks:

• Chase missing inputs early and politely. "Just checking on the logo files; we need them by Thursday to keep the May 6 review."
• Send the first update on schedule, even if progress is modest. Consistency builds trust faster than volume.
• Deliver one small, early piece of work (a moodboard, a sitemap, an outline) to confirm direction before the big effort.
• Ask one check-in question: "Is there anything about how we're working that you'd like to change?"

The complete checklist

Copy this into your own template and adapt it.

Before work starts

• Agreement signed (scope, exclusions, revision rounds, timeline, fees, ownership, ending terms)
• Deposit invoice sent and billing contact confirmed
• Tax paperwork provided if requested
• Payment-detail change rule agreed

People and communication

• Decision-maker named
• Day-to-day contact, consulted and informed people listed
• Communication place, response times and update rhythm agreed

Inputs

• Collection list sent with owners and due dates
• Access requested as individual accounts where possible
• Received access logged for later handback

Kickoff and welcome

• Agenda sent in advance
• Kickoff held and decisions written up
• Welcome email sent and confirmed by the client

First two weeks

• Missing inputs chased
• First weekly update sent
• Early direction check delivered

Making the checklist repeatable

The value of a checklist grows each time you reuse it. After every project, spend ten minutes asking what went wrong in the first month and add a line to prevent it next time.

Tools help with repetition. Clientwharf, for example, lets you send clients a requests checklist in their private portal, where they can reply, attach files and mark items done, so the collection list does not live in a thread. A shared document works too. The habit matters more than the tool: ask for everything clearly, once, with dates, and write down what you agreed.