How to write a freelance contract that actually protects you

Open the contract by stating who is contracting whom. Include your full legal name (or business entity if you have one), the client's full legal name and business entity, and the date of agreement. This sounds trivial until a dispute escalates and someone has to figure out which entity is on the hook. If you trade as a sole proprietor, your own name is your legal contracting party — there is no separate business to point at. If you have an LLC, contract under the LLC; otherwise the LLC's liability protection won't apply.

The most common cause of freelancer disputes is scope drift, and the most common reason scope drifts is that the original scope was vague. 'A redesigned website' is not a scope. 'A 6-page WordPress site (Home, About, Services, Pricing, Blog, Contact), built on the Astra theme, with up to two rounds of revisions per page' is. List concrete deliverables, file formats, page counts, word counts, episode counts — whatever unit of work makes sense for your craft. If a deliverable isn't on the list, it isn't included. Make that explicit with a line like: 'Any work outside this scope will be quoted separately.'

State the total fee, the deposit (if any), milestone payments (if any), and the final balance. Include the due dates relative to events ('50% on signing, 50% on delivery' or 'invoiced on the 1st of each month, net 14'). If you charge by the hour, state the rate, the rounding rule (per quarter-hour, per minute), and the cap or estimate. Never leave 'we'll figure it out' in a payment section. The payment clause is the one your client will read most carefully — if it has gaps, those are the gaps you'll be arguing about later.

Revisions are the second-most common dispute cause. Specify how many rounds are included, what counts as a round, and what happens beyond the limit. A clear pattern: 'Two rounds of revisions per deliverable are included. Revisions consolidate all feedback into a single set of changes per round. Additional revisions are billed at $X per hour with a one-hour minimum.' This isn't being rigid — it's giving the client a clear path to ask for more, and giving you a way to say yes without losing margin.

Every contract should specify what happens if the project ends early. The standard pattern: any deposit is non-refundable, work performed up to the termination date is invoiced at the agreed rate, and ownership transfers only upon full payment. A 'kill fee' (typically 25–50% of the remaining contract value) is appropriate for projects where you've reserved time you can't easily fill. The kill fee isn't a punishment — it's compensation for the calendar slot the client asked you to hold.

Default IP rules vary by country and project type — don't rely on assumption. State explicitly that ownership of the deliverables transfers to the client only upon final payment, and that until then, you retain ownership. If the work is for hire (e.g., copywriting in the US), call that out — work-for-hire copyright vests in the client by default. If you want to retain the right to use the work in your portfolio, write that in: 'The freelancer retains the non-exclusive right to display the deliverables in their portfolio and case studies.'

Three clauses every contract should include: (1) a confidentiality clause covering the client's non-public information, (2) a limitation of liability clause capping your exposure at the contract value, and (3) a governing law clause specifying which jurisdiction's laws apply if there's a dispute. These don't change how the engagement runs day-to-day — they change what happens in the worst case. Freelancers who skip these have nothing to fall back on when something goes very wrong.

An unsigned contract is paperwork. A signed one is a contract. Send the contract before kickoff, not after. E-signature is legally binding in nearly every jurisdiction (in the US, the E-SIGN Act of 2000 made electronic signatures equivalent to wet signatures), so there is no reason to wait on PDFs being printed and scanned. If a client pushes back on signing, that is a signal — not a delay. Find out why and resolve it before doing free work.