Free · No signup

Client Onboarding Checklist

The gap between “you are hired” and “I can actually start” is where projects quietly lose their first week. This is the list that closes it — contract, deposit, contacts, access, assets, channel, dates — with discipline-specific extras at the end.

Who it is for. Freelancers starting a new client relationship who would rather not discover on day four that nobody has the CMS password.

Download this template

Free · No signup · No email · Version 1.0, updated September 2026

The files are generated when the site is built and served as ordinary static downloads. Nothing you type into them is ever sent anywhere — once the file is on your machine it has no connection to Freshlance at all.

What the file looks like

This preview is generated from the same definition the downloads are built from, so what you see here is what opens. Placeholders like {{CLIENT_NAME}} are shown exactly as they appear in the document.

Onboarding checklist — document preview2 pages

CLIENT ONBOARDING CHECKLIST

{{CLIENT_NAME}} · {{PROJECT_NAME}} · starting {{START_DATE}}

Client
{{CLIENT_NAME}}
Project
{{PROJECT_NAME}}
Start date
{{START_DATE}}
Primary contact
{{CLIENT_CONTACT}}
Approver
{{APPROVER_NAME}}

Work through this before delivery work starts. The first three sections block everything else: an unsigned agreement, an uncleared deposit and an unnamed approver are the three reasons a first week disappears.

1. Agreement
  • Proposal or estimate accepted in writing
  • Contract signed by both parties
  • Scope of work attached and agreed
  • Revision allowance confirmed
  • Start date and target completion date agreed
2. Payment
  • Deposit invoice sent
  • Deposit received and cleared
  • Billing entity and billing address confirmed
  • Billing contact and email for invoices confirmed
  • Client tax / VAT number obtained where required
  • Purchase order number obtained, if the client uses them
  • Payment terms and payment method confirmed
3. Contacts
  • Primary day-to-day contact confirmed
  • Named approver identified — the person who can sign things off
  • Other stakeholders identified, with what each one approves
  • Out-of-hours or emergency contact, if the work needs one
  • Time zones noted for everyone involved
4. Project information
  • Project goals confirmed in writing
  • Success criteria agreed
  • Known constraints and non-negotiables captured
  • Existing research, analytics or prior work received
  • Competitors or reference examples discussed
5. Access
  • Required accounts identified, with the permission level each one needs
  • Credentials received, or access granted to your own account
  • Access confirmed working — actually logged in, not just received
  • Shared drive or repository access granted
  • Staging or test environment available
  • Security requirements understood (MFA, VPN, device policy)
6. Assets
  • Brand guidelines received, or confirmed not to exist
  • Logo files received in usable formats
  • Fonts received, with licences that cover this use
  • Photography and imagery received
  • Existing copy or content received
  • Source files for anything being reworked received
7. Communication
  • Main channel agreed (email, Slack, Teams, portal)
  • Update frequency and format agreed
  • Feedback process agreed — consolidated, from the named approver
  • Feedback turnaround time agreed
  • Meeting cadence set, with invitations sent
  • Working hours and expected response times stated
8. Timeline
  • Milestones confirmed and dated
  • First deliverable date confirmed
  • Client-side deadlines and fixed dates captured
  • Known absences on both sides noted
  • Dependencies and who owns each one agreed
9. Technical setup
  • Tools and file formats agreed
  • File naming and version conventions agreed
  • Where deliverables will be handed over decided
  • Backup and source-file arrangement understood
  • Any required integrations or third-party services identified
10. Kickoff
  • Kickoff meeting booked, with the approver attending
  • Agenda sent in advance
  • Scope, milestones and responsibilities walked through
  • Questions and assumptions logged
  • Notes and agreed actions sent afterwards in writing
11. Internal setup (for you, not the client)
  • Project created in your own system, with the estimate attached
  • Time tracking set up against this project
  • Capacity checked — this project fits alongside your existing commitments
  • Recurring invoice or milestone invoice dates scheduled
  • Client folder created, with the contract and scope filed
  • Key dates in your calendar, including the client-side ones
12. Client confirmation
  • Scope and exclusions confirmed in writing
  • Approver and approval process confirmed in writing
  • Feedback turnaround confirmed in writing
  • Payment schedule confirmed in writing
  • What happens to out-of-scope requests explained and acknowledged

Freshlance Template · version 1.0 · freshlance.app/templates/freelance-client-onboarding-checklist

What is included

  • Twelve grouped sections

    From the signed agreement to the internal setup you do for yourself, in the order the items actually become urgent.

  • Standard Markdown task syntax

    The .md version uses `- [ ]` task lists, so it renders as real checkboxes in GitHub, GitLab, Obsidian and Notion imports.

  • A client-confirmation block

    The short list of things to get in writing, so “we agreed that on the call” has a record.

  • Discipline-specific extras

    Short additional lists for designers, developers, writers and consultants — as sections of one checklist, not four separate documents.

How to use it

Five steps, in the order that keeps the work out of trouble.

  1. 1

    Copy the file per client, or keep the Markdown version in the client’s folder and tick items as they land.

  2. 2

    Work top to bottom. The first three sections are the ones that block everything else.

  3. 3

    Do not start delivery work before the deposit clears and the agreement is signed. That is the whole point of putting them first.

  4. 4

    Delete the discipline sections you do not need, and add the items you find yourself chasing every time.

  5. 5

    Run the client-confirmation list at kickoff, while everyone is already on a call.

The worked example

The checklist ships filled in with nothing — it is a list to work through, and pre-ticked example boxes would be actively unhelpful.

The example content is filled in throughout the preview above, so you can see the shape of a finished document before you start on your own.

What to change

The parts that are deliberately yours to decide.

  • Your own recurring chase

    Everybody has one — a form, a VAT number, a particular approval. Add it to the list the second time you have to ask for it.

  • The access section

    The riskiest lines on the list. Make sure the items name a permission level, not just “access”.

  • Kickoff

    On a small project the kickoff is an email, not a meeting. Adjust rather than skipping — the list of things to agree is the same either way.

  • The internal section

    Nobody sees it but you. It is also the part that makes the project easy to run in month two.

About the formats

What differs between the files, and why you might pick one over another.

MD
Standard `- [ ]` task lists. Drop it into a repository, an Obsidian vault or a Notion import and the boxes are tickable immediately.
DOCX
Word, with real checkbox characters you can type an X over or replace with Word’s own checkbox control.
ODT
The same checklist for LibreOffice Writer.
PDF
For printing, or for running through on a kickoff call.

Questions

When should onboarding happen?
Between the signature and the first piece of delivery work. Doing it afterwards means doing the first week twice.
Is there a separate checklist for designers or developers?
Not as a separate download. The last section of this one carries the discipline-specific items, because the other ninety per cent of the list is identical and four near-identical files would help nobody.
Should the client see this?
The first eleven sections, yes — it makes you look organised and it tells them exactly what you need. The internal setup section is for you.
What if the client will not provide access?
Then the dates move, and you say so at the time rather than absorbing it. That is why access sits in the same list as the deposit.

Download it

Download this template

Free · No signup · No email · Version 1.0, updated September 2026

The files are generated when the site is built and served as ordinary static downloads. Nothing you type into them is ever sent anywhere — once the file is on your machine it has no connection to Freshlance at all.