Freelance Client Onboarding Checklist

A step-by-step checklist covering everything from signed contract to first deliverable delivery for a smooth, professional client onboarding.

work, productivity

by Morris

Contract and Legal Setup

Lock down the legal foundation before any work begins.

  • Send contract with scope-of-work clause
  • Include a kill fee clause (25-50% of remaining balance)
  • Add IP assignment clause transferring ownership only upon full payment
  • Specify revision rounds (e.g., 2 rounds included, $X per additional round)
  • Confirm contract is signed by an authorized decision-maker, not just a coordinator
  • Set payment terms: 50% upfront, 50% on final delivery (or milestone-based)
  • Confirm late payment penalty clause (e.g., 1.5% per month on overdue balance)

Payment and Invoicing Infrastructure

Set up the payment pipeline before the project starts.

  • Collect upfront deposit payment before kickoff call
  • Send invoice via your platform of choice (Bonsai, Wave, QuickBooks) with due date set to Net 7 or Net 14
  • Confirm client's preferred payment method (ACH, wire, PayPal, Stripe link)
  • Add client to your bookkeeping system and create a dedicated project folder for receipts/invoices
  • Set an invoice reminder sequence: auto-reminder at 3 days before due, on due date, and 3 days overdue

Kickoff Call Preparation

Prepare thoroughly so the kickoff call is efficient and sets a professional tone.

  • Send a pre-kickoff questionnaire 48 hours before the call
  • Prepare a kickoff call agenda and share it with the client the day before
  • Identify one single point of contact on the client side to avoid conflicting feedback
  • Record the kickoff call (with consent) and share the recording link in the project channel afterward
  • Send a written summary of decisions and next actions within 24 hours of the kickoff call

Requirements Gathering

Extract everything needed to do the work without constant back-and-forth.

  • Get access to all existing assets: brand guide, previous work samples, source files, logins
  • Document the target audience with at least 3 specific attributes (age range, role, pain point)
  • Clarify the definition of done for each deliverable - what does "finished" look like?
  • Identify any technical constraints or mandatory tools the client requires you to use
  • Ask for 3 competitor examples the client likes and 3 they dislike - and why
  • Confirm all content and assets to be provided by the client, and set a deadline for receiving them

Shared Workspace and Tool Setup

Create a single source of truth for files, tasks, and communication.

  • Create a shared project folder (Google Drive or Notion) with a clear folder structure
  • Set up a shared task tracker (Notion, Linear, Trello) with milestones mapped to the contract
  • Create a dedicated Slack channel or email thread label for this project - no DMs for project matters
  • Share a "Working With Me" document covering your working hours, response time SLA, and how to give feedback
  • Confirm the client has access to all shared tools and can navigate them without help

Communication Ground Rules

Set expectations early to prevent scope creep through informal channels.

  • Define response time expectations in both directions (your SLA and theirs)
  • Establish that all feedback must be in writing and consolidated into a single document per revision round
  • Set boundaries on out-of-hours contact (phone calls, urgent Slack messages)
  • Agree on meeting cadence for the duration of the project (e.g., weekly 30-min check-in every Tuesday)
  • Clarify the change request process: any new request not in the SOW requires a written change order before work begins
  • Document preferred feedback format: timestamps on video, inline comments on docs, numbered lists

Milestone and Timeline Planning

Build a realistic timeline with buffer and client accountability built in.

  • Build the project timeline backward from the hard deadline, not forward from today
  • Identify 2-3 client-gated milestones that require their input before you can proceed
  • Add client deadlines to the shared project tracker with clear ownership labels
  • Schedule all milestone review dates in both calendars immediately after kickoff
  • Write a timeline delay policy: if client input is delayed by more than 3 business days, the final delivery date shifts by the same number of days
  • Set a personal internal deadline 3-5 days before the client-facing deadline for all first drafts

First Deliverable Preparation

Set up the first draft for a smooth review and approval process.

  • Do an internal quality check against the acceptance criteria before sending anything to the client
  • Write a delivery email that frames what the client is looking at and what kind of feedback you need
  • Include version numbering in every file name (v1, v1.1, v2) from the first delivery
  • Confirm delivery method matches what was agreed (shared folder link, email attachment, staging URL)
  • Set a calendar reminder to follow up if no feedback is received within 2 business days of the review deadline

Feedback and Revision Management

Handle revision rounds efficiently and professionally.

  • Number each piece of feedback you receive and confirm your interpretation before making changes
  • Track all revision requests in the project tracker and mark them complete as you address each one
  • Include a revision summary in each new version delivery (what changed and where)
  • Flag scope creep requests that appear in revision feedback before acting on them
  • Track which revision round you are on and notify the client when they are approaching the included limit

Final Delivery and Handoff

Close out the project cleanly and professionally.

  • Deliver all final files in the formats specified in the contract (source files + export formats)
  • Send a written project closeout summary covering what was delivered and what was excluded
  • Request written sign-off or approval from the client before sending the final invoice
  • Send final invoice immediately upon receiving written approval
  • Transfer or revoke tool access: remove client from your private workspaces, transfer shared workspace ownership if appropriate
  • Archive the project folder with a clear naming convention for future reference

Invoice and Payment Follow-Through

Ensure the final payment lands on time and without friction.

  • Confirm the invoice was received and the payment is in queue on the client's end
  • Send a polite but firm overdue notice on day 1 past the due date
  • Escalate to a phone call or direct contact with the finance department if payment is 7+ days overdue
  • Apply late payment fee as specified in the contract if payment exceeds 14 days overdue
  • Record the final payment in your bookkeeping system and mark the project as closed

Relationship Building for Repeat Work

Turn a one-time project into a long-term client relationship.

  • Send a short personal thank-you note (not a template) within 48 hours of final payment
  • Ask for a testimonial or LinkedIn recommendation within 1 week of project close
  • Add the client to a 90-day follow-up reminder to check in and surface new opportunities
  • Ask if there are referrals they can make to others who might need similar work
  • Document what went well and what to improve for the next client engagement in a personal project retrospective
Itemi