35 items

Freelance Client Onboarding

Miss one step here and you risk unpaid invoices, endless revisions, and scope creep that turns a 2-week project into a 6-week marathon. This checklist locks in every legal, financial, and communication detail before a single deliverable is touched. For more background and examples, see the guidance below; for built-in tools and options, use the quick tools guide.

Author

Checklistify Editorial Team

Last Updated

Checklist Items

0 done•35 left•5 of 6 sections collapsed

Send a contract covering scope, payment, revisions, IP, and termination — and collect the signed copy

Your contract must cover at minimum: specific deliverables (not vague categories like 'website'), the payment schedule with exact amounts, the number of revision rounds included, when IP ownership transfers to the client, confidentiality obligations, and a termination clause with refund policy. Use DocuSign, PandaDoc, or HelloSign for legally binding e-signatures — a PDF returned by email is not enforceable in many jurisdictions. Keep the signed copy in the client's dedicated folder; you will reference it every time a scope question arises.

Invoice the deposit and do not begin any work until it has cleared your account

A deposit of 25–50% is standard for most freelance projects; for fixed-scope work over $5,000, 50% upfront is typical. For engagements shorter than a week, consider requiring 100% upfront. Do not begin any work — not even preliminary sketches or background research — until the deposit has cleared your account, not just been sent. Stripe and Wise typically settle within 1–2 business days; PayPal can hold funds up to 21 days for new senders. State the no-work-before-clearance rule explicitly in both your contract and on the invoice itself.

Confirm payment method, billing currency, invoice schedule, and any purchase order requirements

Establish whether remaining payments are milestone-based (paid when each phase is delivered) or time-based (paid on a recurring date). Milestone-based suits fixed-scope projects; time-based suits ongoing retainers. Confirm the exact platform — bank transfer, Stripe, PayPal, or Wise — and whether the client requires a purchase order number on invoices. Large companies often do, and a missing PO number can delay payment by 30 days or more. For international engagements, agree on the invoicing currency and who absorbs currency conversion fees.

Include a late-payment fee clause in the contract and confirm the client has read it

A late-payment fee of 1.5–2% per month on overdue balances is standard and legally enforceable in most countries. State this in the contract and repeat it in the footer of every invoice you send. Beyond the fee, define what happens when payment is overdue: most freelancers include a clause that pauses all project work until outstanding invoices are settled. Clients who object strenuously to a standard late-payment clause during onboarding are revealing how they handle financial obligations under pressure.

Send and collect a signed NDA before sharing any confidential information

Send the NDA before sharing any sensitive material — customer data, unreleased product plans, pricing strategy, or internal system access. Determine whether it should be one-way (protecting the client's information only) or mutual (protecting both parties). Mutual NDAs are appropriate when you will also be sharing proprietary processes or methodologies of your own. Store both signed copies: one in your client folder, one sent to the client for their records. NDAs cannot retroactively protect information you have already shared, so send it before any briefing begins.

Confirm when IP ownership transfers and whether you retain portfolio rights — in writing

IP ownership should transfer to the client only upon receipt of full final payment — not the deposit and not partial payment. State this explicitly so a client cannot claim ownership of work while still owing you money. Separately, clarify whether you retain the right to display the finished work in your portfolio and case studies. Clients in finance, healthcare, or stealth startups may require confidentiality about the work itself; if so, negotiate a written testimonial or an anonymized case study in exchange for accepting the portfolio restriction.

Add the client to your invoicing system with all billing details captured now

Capture the legal entity billing name (not just a first name), billing email address, payment terms (Net 7, Net 15, or Net 30), any applicable tax or VAT registration number, a purchase order number if required, and whether invoices should be CC'd to a separate accounts payable contact. Gathering these details during onboarding — not when the first invoice is due — prevents the delays caused by administrative back-and-forth at billing time, which can push payment out by weeks.

Send a client intake form at least 48 hours before the kickoff call

Your intake form should gather: a business overview and what makes the client unique, the target audience and their primary pain points, project goals with measurable success metrics, 2–3 competitor references and what the client admires or wants to differentiate from, existing brand assets, and absolute must-avoid elements (colors, phrasing, design approaches). Sending this 48 hours before kickoff gives you time to prepare informed, specific questions rather than collecting basic information live during the call. Typeform, Tally, and Google Forms all work well for this.

Collect all brand assets and document what does not yet exist

Request logo files in vector format (SVG or AI/EPS), brand color codes in hex and CMYK (not 'it's kind of a teal blue'), primary and secondary typefaces with licensing details, and any existing tone-of-voice guidelines. If the client has no formal brand guidelines, document their verbal descriptions during kickoff and send a written summary for their confirmation — this becomes your working brief and protects you if the client later says 'this doesn't feel right.' Store everything in a clearly labeled Brand Assets folder in the shared workspace.

Confirm exact deliverables in writing with format, quantity, and file specifications

Vague deliverable descriptions are the source of most scope disputes. Instead of 'website design,' write: '5 unique page layouts (Home, About, Services, Blog, Contact) designed in Figma, delivered as a shared Figma link plus static PNG exports at 1440px desktop and 375px mobile.' Instead of 'social media content,' write: '12 Instagram posts per month, static image format, 1080x1080px, editable Canva files included.' The more specific the deliverables list, the less room there is for a client to expect something that was never discussed.

#10

Confirm the project deadline and any hard internal milestones driving it

Ask directly: 'Is there an event, launch, or presentation behind this deadline?' Board meetings, product launches, trade shows, and investor demos create hard dates that cannot move. Knowing this upfront lets you build the timeline backward from real constraints rather than arbitrary dates. Also ask what the consequence would be if the deadline slips — some clients have genuine flexibility, while others face financial penalties or contractual obligations if the date is missed. That context shapes how aggressively you need to buffer and flag risk.

#11

Map every stakeholder who will review or approve deliverables, including any hidden approvers

Ask explicitly: 'Who will review the work? Who gives final approval? Are they the same person?' Problems arise when a junior manager hires you but a CEO or legal team must sign off — and you find out only at the revision stage, weeks into the project. For complex organizations, map the full approval chain: who reviews first, who approves final, and whether any departments (legal, compliance, IT, brand) have mandatory input. Getting this wrong means a deliverable your primary contact approved can be rejected by someone who was never in the loop.

#12

Confirm who has single-point decision authority for time-sensitive questions

Establish your designated contact for decisions that cannot wait for a committee. This protects you: if your primary contact approves work that is later overruled by their manager, you have documentation that you received sign-off from the person designated as the decision-maker. In larger organizations, the person managing the day-to-day relationship often does not control the budget or hold final creative approval. Identify which approval layer your deliverables must actually survive — and get that person's direct contact details during onboarding.

#13

State the revision policy in the contract and get the client's written acknowledgment

Define the exact number of revision rounds included per deliverable (e.g., two rounds) and what a round means: one consolidated batch of feedback is one round; multiple piecemeal rounds of notes are not. Specify your rate for additional revisions — typically $75–$150 per hour depending on discipline. Include this in the contract and reference it again in the kickoff summary email. Written acknowledgment — not a verbal yes — prevents a client later claiming they were unaware that revision limits existed.

#14

Create and organize the shared project workspace before kickoff

Build the shared folder (Google Drive, Dropbox, or Notion) before the kickoff call so the client sees a structured, professional environment on day one. A clear folder structure: /00-Contract-Legal, /01-Brief-Assets, /02-In-Progress, /03-Review, /04-Final-Approved. Use date-prefixed filenames in YYYYMMDD format so versions are automatically sorted chronologically. A disorganized workspace signals disorganized work — even when the actual output is excellent — because clients have no other reference point yet.

#15

Request account access at minimum permission level only, and log every credential granted

Request only the access level the project actually requires: editor access to a CMS (not admin), read-only for analytics (unless you need to configure goals), analyst access to ad accounts (not billing). Over-requesting permissions creates security concerns and can delay access being granted. Document each request in your project notes: tool name, URL, permission level, and date granted. At project close, use this log to confirm every access has been properly revoked — protecting both you and the client from lingering credentials.

#16

Test every login at least 24 hours before the kickoff call

Troubleshooting broken credentials during a live kickoff wastes time and creates a poor first impression. Test every login before the call: confirm you can navigate to the correct sections in a CMS, verify the analytics property shows expected data, and check that SSH keys or FTP credentials connect. If anything is broken, report it with specific error details — not 'it doesn't work,' but 'the WordPress login returns Error 403 Forbidden' — so the client can escalate the right fix before kickoff begins.

#17

Add the client to your project management tool with milestone visibility but no internal workflow access

Invite the client to a filtered view showing milestone dates, phase status, and upcoming deliverables — but not your internal task details, time estimates, or working notes. In Asana, use Guest access to a specific project. In Notion, share a filtered database view. In ClickUp, use View-only access at the project level. Clients who can see real-time progress send significantly fewer 'just checking in' messages, reducing communication overhead throughout the project for both parties.

#18

Agree on one primary communication channel and document it in writing

Communication scattered across email, Slack, WhatsApp, LinkedIn DMs, and text is the leading cause of missed messages in freelance projects. Choose one primary channel and document the agreement explicitly: 'Our primary channel is Slack. For urgent matters, email is acceptable. Please do not use WhatsApp or LinkedIn for project communication.' Whatever channel is agreed, write it down — verbal agreements about communication preferences are rarely remembered identically by both parties three weeks later.

#19

Store all shared credentials in a secure password manager — never send passwords in plain text

Use a credential-sharing tool like 1Password (supports guest sharing), Bitwarden (free tier available), or LastPass to share access securely without exposing the raw password. If a client must send credentials directly, ask them to use a self-destructing message service like Privnote rather than a standard email or Slack message. Log every credential you hold in your project notes so you can confirm revocation at project close — protecting both parties from lingering access after the engagement ends.

#20

State your working hours, time zone as a UTC offset, and response time commitment in your onboarding document

Be specific: 'I work Monday–Friday, 9am–6pm UTC+1, and respond to messages within one business day. For urgent matters, email reaches me faster than Slack.' Vague commitments like 'I'm usually pretty quick' create mismatched expectations and frustration when you take 18 hours to reply. Include this in your onboarding document and repeat it in the kickoff summary email. For international clients, always use UTC offsets rather than regional abbreviations — 'EST' is ambiguous across seasons; 'UTC-5' is not.

#21

Set a written feedback turnaround expectation for the client and include it in the contract

Agree that the client will respond to review requests within a defined window — 2–3 business days is reasonable for most projects. Include a consequence clause: if feedback is not received within the agreed window, the project timeline extends by an equivalent number of days and the delay is attributed to the client in writing. This protects you from being blamed for a missed deadline when the actual cause was a client who took 10 days to review a draft. Verbal agreements on turnaround are routinely forgotten; contract language is not.

#22

Walk the client through your process and set frame expectations for what type of feedback belongs at each stage

Explain the stages clearly: research and strategy, initial concepts, first review, refinement, final delivery. At each stage, tell the client what kind of input is appropriate: 'At the concept stage, feedback should focus on strategic direction — which approach fits the brand — not on execution details like exact font sizes or button color. That level of detail belongs in the refinement stage.' This prevents comments that arrive at the wrong time and require undoing work that was already in progress.

#23

Agree on a specific format and schedule for progress updates

Decide upfront whether updates will come as weekly email summaries, async Loom walkthroughs, live board updates in the PM tool, or brief check-in calls. Match the format to the client's communication preferences and the project's pace. A 2-week sprint benefits from brief daily check-ins; a 3-month project is better served by weekly written summaries. Whatever the format: maintain consistency. If you commit to weekly Friday emails, send them every Friday — even when the message is simply 'on track, next milestone by Wednesday.'

#24

Confirm the out-of-scope change request process in writing before work begins

Agree that any work outside the defined deliverables list will be flagged, quoted separately, and approved in writing before execution. The process does not need to be bureaucratic for small additions: a brief email describing the new work, a quoted cost, the client's written confirmation, and an updated invoice or contract addendum is sufficient. The essential outcome is a paper trail for every change so neither party can later dispute what was agreed. Verbal approvals for scope additions are the origin story of most freelance payment disputes.

#25

Schedule the kickoff with the time zone written out explicitly, duration specified, and required attendees named

Send the calendar invite with the time zone written as a specific location or UTC offset (not just 'PST'), the expected duration (45–90 minutes depending on scope), a working meeting link, and a list of required attendees with a note on any materials they should prepare. A clear invite prevents last-minute confusion and reduces the chance of key decision-makers skipping it. If a client reschedules the kickoff more than once before it happens, treat that as meaningful information about how the rest of the engagement will unfold.

#26

Prepare a written kickoff agenda and share it at least 24 hours before the call

A written agenda signals professional preparation and gives the client time to gather materials or think through their answers. Cover: project overview and goals confirmation, timeline walkthrough, any open questions from the intake form, communication norms and process explanation, and immediate next steps with named owners. Share it as a separate document — Google Doc or PDF — not as a block of text in the calendar invite body, so it remains easily referenceable after the call ends.

#27

Review the project brief live on the call and surface every ambiguity before the call ends

Do not assume the written brief captured everything accurately. Use the kickoff to ask questions that a form cannot resolve: 'When you said you want to reach millennials, do you mean early-career professionals or new parents — because those audiences require very different messaging?' These nuances rarely survive a written intake form but can change the entire direction of the work. Assign an owner and a due date to every unresolved item before the call closes — never let kickoff end with open questions that have no resolution path.

#28

Run a final pass through outstanding access, deliverables, and timeline items before closing the call

Spend the last 10 minutes of kickoff confirming what is still outstanding: missing account access, unclear deliverable specifications, unconfirmed milestones, unsigned documents. Be explicit about what is needed before work begins and who is responsible for providing it, with a specific deadline: 'Before I start on Monday, I need the CMS login and confirmation on the video background question. Can we confirm both by end of day Friday?' Specific requests with deadlines resolve far faster than general follow-up messages.

#29

Send a kickoff summary email within 24 hours covering all decisions, open items, and next steps

Send the summary the same day if possible, while the conversation is fresh for both parties. Include: confirmed scope and deliverables, agreed timeline and milestone dates, confirmed communication channel and update cadence, all outstanding items with a named owner and due date, and your first scheduled delivery date. This email becomes the definitive written record of what was agreed at project start. When scope disputes arise weeks later — and they will — this document closes the conversation.

#30

Build a project timeline in phases with an internal buffer that is not visible to the client

Break work into phases (Strategy, Design, Review, Revision, Final Delivery) with internal deadlines for each. Build a 15–20% buffer into your total timeline — not shown to the client — to absorb unexpected delays, sick days, or slow client approvals. Share only milestone dates in the PM tool (client review by X, final delivery by Y); keep your internal phase deadlines in your own task manager. A timeline with no buffer is a timeline that cannot survive any of the ordinary disruptions every project encounters.

#31

Log the project in your income tracker with all expected payment dates and amounts

Track: contract total, deposit amount and date received, each remaining invoice amount, expected payment dates, and actual dates received. Tools like HoneyBook, Bonsai, Wave, or a spreadsheet all work. The goal is to spot cash flow problems before they arrive — if three invoices from different clients fall in the same week, you can plan around it. Also track how long each client historically takes to pay; this data tells you which clients need earlier reminders and which reliably pay on schedule.

#32

Set invoice reminders with advance notice, due-date, and overdue follow-up steps

Schedule three reminders per invoice: one three days before the due date as a friendly advance notice, one on the due date itself, and one five to seven days after if the invoice is still unpaid. Most late payments are administrative oversights — a prompt, professional follow-up resolves the majority without friction. For invoices overdue beyond 14 days, escalate to a formal email explicitly referencing the late-payment clause from your contract. Invoicing tools like FreshBooks, Wave, and QuickBooks can automate reminder sequences, removing the awkwardness of manual follow-up.

#33

Block actual calendar time for a midpoint check and a pre-deadline review — not just reminder alerts

Block real calendar slots — not just notification alerts — at the project midpoint and one week before the final deadline. Use the midpoint to assess: Is the scope still as defined? Are there outstanding client inputs blocking progress? Are revision rounds being consumed ahead of schedule? Use the pre-deadline block to confirm: Is final delivery on track? Are all approvals secured? Are there outstanding invoices that should be settled before final delivery is handed over? Catching a problem at the midpoint gives you weeks to resolve it; finding it the week before delivery leaves almost nothing.

#34

Create a project decisions log and update it throughout the entire engagement

Maintain a running document — a simple Google Doc is sufficient — that logs every key decision made with its date, every change request received and whether it was approved or declined, verbal approvals noted from calls, and any scope additions along with the agreed additional fee. This document is both a legal protection in scope and payment disputes and a working memory tool that prevents re-litigating decisions already made. When a client says 'I don't remember agreeing to that,' you open the log.

#35

⚠️ Onboarding Behaviors That Predict a Difficult Engagement

These patterns, observed before any work begins, account for the majority of difficult freelance situations. Each one deserves a pause before you proceed.

They resist signing the contract before reading it. Objecting to the act of signing — not to specific clauses — signals an aversion to enforceable commitments.
They ask you to start small and sort the paperwork later. "Just do this one quick thing" is how paid work becomes unpaid work. Work begun before protection exists is debt you are taking on, not the client.
They have already parted ways with two or more freelancers on the same project. One departure can be circumstance. Two is a pattern. Ask why — the answer tells you more than any portfolio review could.
They cannot name who has final approval. Unclear decision authority means your work will be revised indefinitely by committee, with each reviewer operating from a different brief.
They want to remove the late-payment clause, the revision limit, and the termination clause. Negotiating specific terms is reasonable. Eliminating every protection clause is not negotiation — it is restructuring the agreement entirely in their favor.

📖 The Phantom Approver

A UX designer delivered a complete app redesign to her primary contact — the product manager — who approved it. The work then went to the CMO, who had entirely different expectations about brand direction and requested a near-complete redo. The PM had never mentioned the CMO's involvement. The designer had no contract language covering unanticipated approvers and redid the work unpaid to protect the relationship. Total uncompensated hours: 38. Asking "who else needs to sign off?" during onboarding would have surfaced this in thirty seconds.

🧮 The Cost of a Missing Sentence

A copywriter left IP ownership transfer terms out of her contract. The client assumed ownership transferred at deposit. The writer assumed it transferred at final payment. The client published the work before paying the final invoice of $1,800. Without a clear clause, there was nothing enforceable to point to. The dispute cost $400 in legal consultation and the $1,800 was never recovered — all avoidable with two sentences that take twenty minutes to add to a contract template, once.

🔧 When a Client Asks: "Do We Really Need a Contract?"

Most freelancers hear this eventually. It is rarely about the paperwork — it is almost always about the discomfort of formal commitment. A simple, non-defensive response that works:

"Absolutely — the contract protects both of us equally. It means I cannot change the scope or fees without your written approval, and you have clear recourse if I miss a milestone. It takes five minutes to sign and neither of us has to think about it again."

Frame it as mutual protection — because it genuinely is. If a client still refuses after this response, that refusal itself is the clearest possible signal about whether this engagement is a good idea.

🧮 The Hidden Math of "Just One Small Addition"

Scope additions that feel minor in isolation accumulate quickly. Consider a $3,000 fixed-scope project where out-of-scope requests are absorbed without billing:

Base contract value .............. $3,000

"Quick" homepage revision ........ 1.5 hrs × $95 = $142

"Just add" a pricing page ......... 2.0 hrs × $95 = $190

"One more" email template ......... 1.5 hrs × $95 = $142

"Small" copy tweaks (3 rounds) .... 2.5 hrs × $95 = $237

Uncompensated additions .......... $711 — 24% of contract value

Each addition felt too minor to formally raise. Together, they represent nearly a quarter of the project's value delivered for free. A change request process agreed during onboarding makes these conversations routine rather than charged — because the rule was established before there was any money at stake.

💡 Onboarding Is a Positioning Signal, Not Just Admin

A professional onboarding process communicates something no portfolio piece can: that you have done this before and you know what you are doing. Clients who have worked with disorganized freelancers — and most have — notice immediately when intake forms arrive on schedule, kickoff agendas come prepared, and shared workspaces are logically structured before the first call. This experience shapes both the rates they will accept next time and whether they refer you to others. The process is not bureaucracy. It is proof of competence, delivered before the first deliverable exists.

Master This Checklist Quickly

Every important button and option for this pre-made checklist, shown in a glance-friendly format.

Start Here

1
Click any item row to mark it complete.
2
Use the note row under each item for quick notes.
3
Use the tool row for undo, redo, reset, and check all.
4
Use Save Progress when you want to continue later.

Checklist Row Tools

UndoRedoResetCheck allCollapse/Expand sectionsShow/Hide detailsInline notes

Top Action Buttons

Open all sharing and export options in one menu.

Email DraftContinue on another devicePrint or Save as PDFPlain Text (.txt)Word (.docx)Excel (.xlsx)

Add & Ask

Open one menu for apps and AI guidance.

NotionTodoist CSVChatGPTClaude

Copy and customize

Create a new editable checklist pre-filled with your chosen content.

Save Progress

Adds this checklist to My Checklists and keeps your progress in this browser.

Most Natural Usage

Track over time

Check items -> Add notes where needed -> Save Progress

Send or export

Open Share -> Choose format -> Continue

Make your own version

Copy and customize -> Open create page -> Edit freely

Freelance Client Onboarding

Checklist Items

Legal & Financial: Complete Before Any Work Starts

Client Information & Project Brief

Access & Tools Setup

Communication & Expectations

Kickoff Call

Project Tracking Setup