There are two documents in a freelance engagement and they do different jobs. The client contract governs the relationship — who owns the work, who is liable for what, how either side gets out. The scope of work governs the job — what you're delivering, what you're not, by when, for how much.
Plenty of freelancers combine them into one document. For projects under a few thousand, that's perfectly sensible. What matters is that the eight things below appear somewhere, in writing, before you start work.
The Eight Clauses That Do the Protecting
1. Deliverables — what is included
Specific and countable. "5 Instagram posts, each with one caption and two image variants" — not "social media content." If a deliverable can't be counted, it can't be finished, and a project that can't be finished is a project you're still working on in month four.
Prevents: endless projects with no definition of done2. Exclusions — what is not included
The single most valuable clause in the document, and the one almost everyone leaves out. If you're a web designer: "Does not include copywriting, stock image licensing, SEO setup, hosting, or ongoing maintenance." Every line here is a conversation you don't have to have later.
Prevents: "I assumed that was part of it"3. Revision rounds — a number, and a definition
State how many rounds are included, and define what a round is: one consolidated set of feedback submitted at one time. Without that definition, five separate emails over three days count as one round in the client's mind and five in yours.
Prevents: unlimited revisions by accident4. Client responsibilities and deadlines
What they must give you, and by when. Content, logins, brand assets, feedback within a stated number of business days. Add the consequence: delays on their side move the delivery date, they don't compress your working time.
Prevents: being blamed for a delay you didn't cause5. Payment terms and schedule
Total fee, deposit required before work begins, when the balance falls due, and what happens if it's late. A deposit isn't rudeness — it's the thing that separates a client from an enquiry.
Prevents: working for weeks before discovering they can't pay6. Scope change procedure
One sentence, and it does enormous work: "Scope changes will be quoted separately in writing before any additional work begins." This turns every awkward "can you also..." into an administrative step rather than a confrontation.
Prevents: absorbing extra work to avoid an awkward conversation7. Intellectual property and portfolio rights
State when ownership transfers — usually on final payment, not on delivery — and reserve your right to show the work in your portfolio. If a client needs that restricted, that's a conversation worth having upfront, not after you've published a case study.
Prevents: disputes over ownership and portfolio use8. Termination
How either side ends the engagement, how much notice, and what gets paid for work already completed. Nobody enjoys writing this clause. Everybody who has needed it has been glad it was there.
Prevents: an ugly, undefined endingThe clause most people skip: exclusions. Deliverables tell a client what they're getting. Exclusions tell them what they're not — and without that second list, anything not explicitly ruled out is arguably included. It's the difference between a document that describes the work and a document that defends it.
Where a Template Stops Being Enough
Worth saying plainly, because a lot of contract content online won't: a template you downloaded is not legal advice, and nobody reviewed it for your situation.
What a good template gives you is structure and language for the ordinary situations — the ninety-odd percent of freelance projects where the real risk isn't litigation, it's ambiguity. It sets expectations, creates a paper trail, and gives you something to point at when a request drifts outside the agreement.
What it doesn't do is survive a genuinely contested dispute in a jurisdiction whose rules it wasn't written for. Contract law varies significantly between countries and, in the US, between states. Terms that are standard in one place can be unenforceable in another.
So the honest rule of thumb:
- Routine project work — a well-structured template you understand and use consistently beats an expensive contract you never send
- High-value work, long retainers, anything involving significant IP or regulated industries — get a qualified solicitor or attorney to review your agreement
- Any project where you find yourself thinking "I hope this doesn't go wrong" — that instinct is usually correct, and it's worth the legal fee
Getting It Signed Without Making It Weird
The most common reason freelancers don't send a contract isn't that they don't have one. It's that sending it feels confrontational.
It isn't, and the framing matters. Don't present it as protection — present it as clarity:
"Before we start, I'll send over a short scope document covering deliverables, timeline and what's included. It just makes sure we're both working from the same picture. Have a read and let me know if anything looks off."
Nobody objects to that. What clients object to is a surprise — being told in week six that something they assumed was included is going to cost extra. The document prevents the surprise, which means it protects the relationship at least as much as it protects you.
And there's a signalling effect worth taking seriously. A freelancer who sends a clear scope document in the first week reads as someone who has done this before. Clients treat that person differently — and price objections tend to soften when the process looks professional.
A Practical Sequence
- Enquiry arrives — send a short intake form before booking any call
- Discovery call, capped at 30 minutes
- Send the scope of work with deliverables, exclusions, revision limit and price
- Get written acceptance — an email saying "approved" is a paper trail, it doesn't have to be a wet signature
- Invoice and collect the deposit
- Then start work
Steps 3 to 5 are where most of the year's problems get prevented. They take about twenty minutes.
Related Reading
- How to Write a Freelance Scope of Work Template That Protects You
- How to Write a Freelance Revision Policy
- Freelance Payment Terms: Getting Paid on Time
- 15 Client Red Flags Every Freelancer Must Know
A note on what we sell: the Client Scope & Protection Playbook is a 42-page operations toolkit — a fill-in-the-blank scope of work template with an exclusions clause, 13 copy-ready scripts, and checklists for each stage. It is not legal drafting and it hasn't been reviewed by a lawyer. For high-value contracts, get proper legal advice.