Most freelance contract disputes don't trace back to a bad clause — they trace back to a clause that was never written down in the first place, because the relationship started on a verbal "sounds good" and a Slack thread instead of a document either side could point back to. This checklist isn't legal advice; it's the practical list of what tends to cause actual arguments later, worth deciding on paper before a project starts rather than negotiating mid-dispute when both sides already feel wronged.

The invoicing mistake covered in our international payment guide — a $1,200 payment delayed six weeks because "payment on invoice receipt" was written into the contract but the invoice itself never got sent — is exactly the kind of thing this checklist exists to prevent. The contract term was fine; the process around it wasn't.

1. What exactly is being delivered, and what isn't?

"A website" or "a logo" isn't a scope — a specific number of pages, a specific number of concepts, a specific list of what's included and what counts as a separate, billable request is. The single most common source of scope creep is a deliverable description vague enough that both sides can honestly disagree about what was promised. Write down the number, not just the noun.

2. How many rounds of revisions are included?

Unlimited revisions sounds generous until a client uses it as an open-ended design-by-committee process. A specific number (two or three is typical) with a clear price for anything beyond that number protects both the timeline and the relationship — it's much easier to say "that's revision round four, here's the rate for it" than to renegotiate scope after the fact.

3. When exactly does payment happen, relative to delivery?

"Net 30" and "50% upfront, 50% on delivery" are both fine — what matters is that the trigger is specific and both sides agree on it. Does the clock start on delivery, on approval, or on invoice receipt? Our pricing guide covers the rate-setting side of this; the contract's job is just to make the timing unambiguous once a number is agreed on.

4. What happens if a payment is late?

A late fee clause (a flat amount or a percentage per week) rarely gets used, but its presence changes behavior before it's ever invoked — clients who might otherwise let an invoice slide tend not to, once there's a specific, written cost attached to doing so. Pair this with actually tracking what's been sent and paid; our password manager guide and e-signature tools guide both cover the lighter infrastructure that makes a contract enforceable rather than aspirational.

5. Who owns the work, and when does ownership transfer?

Default copyright law in most places gives the creator ownership until it's explicitly transferred — meaning a client technically doesn't own a deliverable just because they paid for it, unless the contract says so. Specifying that ownership transfers on final payment (not on delivery) is a meaningful piece of leverage: it means unpaid work legally still belongs to the freelancer, not just informally.

6. What's the kill fee if the project ends early?

Projects get cancelled — a client's budget gets cut, priorities shift, a company gets acquired. A kill fee clause (a percentage of the total project value, or payment for hours already logged) means an early cancellation is a bad outcome instead of a total loss. Without one, work already completed before a cancellation has no clear payment mechanism at all.

7. Is there a confidentiality or non-disclosure clause, and does it run both directions?

Clients often bring their own NDA, which is usually written entirely to protect their side. Worth checking whether it also protects the freelancer's own methods, templates, and non-client-specific business information — a one-directional NDA is common enough that it's worth actually reading rather than signing on the assumption it's standard.

8. What jurisdiction and dispute process applies?

For international clients specifically, this matters more than it looks — a contract that's silent on jurisdiction can mean an expensive, unclear path to resolving a real dispute. Naming a specific jurisdiction (usually the freelancer's own) and a lower-cost first step (mediation or arbitration before either side considers court) keeps a worst-case scenario from becoming disproportionately expensive relative to the project itself.

A wedding photography client once pushed back hard on a kill-fee clause, treating it as adversarial before any conflict had even happened. What actually settled it wasn't a legal argument — it was framing the clause as protection for both sides equally: if the client's circumstances changed, they'd only owe for work completed, not the full project; if mine did, they'd get the same protection in reverse. Once it was framed as mutual rather than one-sided, it stopped being a sticking point. The clause itself never changed — only how it was explained.

The two clauses that matter most if you only have time for two

If a full contract review isn't happening before a rushed project start, payment timing (#3) and ownership transfer (#5) are the two clauses that cause the most expensive disputes when left unwritten. Everything else on this list prevents friction; these two prevent situations where real money or real work product is genuinely at stake.

Bottom line

None of these eight items require a lawyer to write into a standard agreement — most proposal and e-signature tools include templates that already cover the bulk of this. See our proposal software guide if a proposal-to-contract workflow isn't already part of how a project gets started. The actual habit that matters is running through this list before a project begins, when both sides are still agreeing on everything, rather than reaching for it for the first time in the middle of a disagreement.

Want this checklist (plus two more — a software buying checklist and a new-client vetting checklist) as a printable PDF you can check off instead of just read? Get the bundle for $3.