Contracts
What to Put in a Freelance Contract So You Actually Get Paid (The Five Clauses That Matter)
A Freelancers Union survey of around 5,000 freelancers found just 28% used a written contract for a given gig. The survey is a decade old and predates the state laws that now require one, but nothing since suggests the habit fixed itself. Most disputes over scope or payment still happen with nothing in writing to point back to. A contract doesn't need to be long to close that gap. It needs the right five things in it.
Do you actually need a contract for this job?
Almost always, yes, and the exceptions are narrower than they feel. A written agreement matters most in the situations freelancers most often skip it: small fees, repeat clients, and referrals from friends, all of which feel too settled to formalise and are the hardest to resolve when they aren't. It's also increasingly a legal requirement on the client's side rather than a preference on yours: California's Freelance Worker Protection Act (SB 988) requires a written contract for freelance work over $250 from 1 January 2025, Illinois' Freelance Worker Protection Act at $500 from 1 July 2024 (aggregated across a 120-day period), and New York's Freelance Isn't Free Act at $800, statewide from 28 August 2024. For a genuinely small job with a known client, an email confirming deliverables, price, payment schedule, revision count, and deadline is a proportionate floor. It just won't cover IP assignment, confidentiality, or liability, which is why it's a floor rather than a substitute.
The five clauses that actually prevent payment disputes
A freelance contract needs, at minimum: a scope definition (what's included, ideally referencing a separate scope-of-work document rather than a paragraph buried in the contract), the payment amount and schedule (upfront deposit, milestones, or a flat fee on delivery), a late-payment or interest clause stating what happens if an invoice goes unpaid past its due date, a revision limit (how many rounds of feedback are included before extra work is billed separately), and a termination or kill-fee clause covering what happens if either side ends the project early. Contracts that skip the revision limit are the single most common source of scope creep freelancers report. Without a stated cap, "just one more round" has no natural stopping point.
| Clause | What it must say | What goes wrong without it |
|---|---|---|
| Scope | What is included, by reference to a separate scope of work | Every request becomes arguable; nothing is provably extra |
| Payment amount and schedule | Deposit, milestones or flat fee, with dates | You carry the whole project cost until the end |
| Late payment | The fee or interest, and when it starts | A reminder with nothing behind it; retroactive fees rarely stick |
| Revision limit | A number of rounds, and the rate beyond it | The single most common source of unpaid work |
| Termination / kill fee | Notice period and what is owed for partial work | A cancelled project can end with nothing owed to you |
The three clauses to add if the client is in Illinois, New York or California
Where a freelance protection statute applies, the contract has required content, and the obligation to produce it sits with the hiring party rather than with you. That is useful rather than burdensome: it means a contract you draft to the statutory shape is harder for a client to object to, because it is what the law asks them to provide anyway. Three items recur across all three states. The name and mailing address of both parties, which sounds trivial and is the field most often left as a brand name rather than the registered entity. An itemised list of the services with the value of each, not a lump-sum description: this is the requirement that quietly forces the scope conversation to happen before work starts. And the date compensation is due, or the mechanism for determining it. Illinois adds a constraint the other two do not: that date must fall no later than 30 days after delivery. Illinois also gives the freelancer two years to bring a civil claim, with remedies including double the underpayment, statutory damages and attorney's fees, which is the strongest enforcement of the three.
Scope of work belongs in its own section, not buried in the contract
Keep detailed scope, what's explicitly included and excluded, out of the main contract body and in its own document instead. A contract that tries to double as the scope document either stays too vague to be useful ("design and development services") or gets so long that nobody, including you, rereads it when a dispute comes up. A dedicated scope of work document listing inclusions and exclusions line by line is what actually gets checked against when a client asks "can you just also...", and it's easier to update per-project without renegotiating the whole contract.
When to get a lawyer instead of using a template
A template covers the common case: a single client, a defined project, standard payment terms. Get an actual lawyer involved for anything with real complexity or exposure: deals involving equity instead of cash payment, contracts governed by a country's law you don't operate in regularly, work that transfers significant intellectual property rights, or any engagement large enough that a dispute would meaningfully hurt your business. Templates are a starting point that gets most freelance work covered in writing instead of nothing; they're not a substitute for legal review on the deals where the stakes are actually high.
Frequently asked questions
- Do freelance contracts need a signature to be enforceable?
- In most jurisdictions, a written and clearly agreed contract, including an email exchange confirming terms, is enforceable without a physical wet signature. An e-signature still makes intent and agreement much clearer if a dispute ever comes up, so it's worth collecting even where it's not strictly required. This isn't legal advice; enforceability specifics vary by location.
- Should I write a new contract for every project, or use one master agreement?
- For repeat clients, a single master service agreement covering your general terms (payment, IP, liability) plus a lightweight scope-of-work or change-request document per project is more practical than a full new contract each time. It's faster to issue, and it keeps the parts that actually change project to project, scope and price, separate from the parts that don't.
Sources
- Freelancers Union - Why do only 28% of freelancers use a contract? (survey of ~5,000 freelancers)
- California Legislative Information - SB-988, Freelance Worker Protection Act
- Illinois Department of Labor - Freelance Worker Protection Act
- Epstein Becker Green - Freelance Isn't Free Act Takes Effect Throughout New York State
