Contracts & Legal

7 Freelance Contract Clauses That Actually Protect You

The freelance contract clauses that prevent scope creep, unpaid work and IP disputes — what each does, why clients accept them, and wording to start from.

Hirushan Rajapaksha8 min read
A contract document behind a protective shield with a checkmark
— Contents

Most freelance contracts are copied from a template, skimmed once, and never opened again — until the week a client decides that the "small tweak" you have been asked for eleven times was always part of the deal.

A contract is not primarily a litigation tool. Freelance disputes almost never reach a court; the numbers are too small and everyone involved knows it. What a contract actually does is settle arguments before they become arguments, by being a document both people agreed to when everyone was still friendly.

These are the seven clauses that do the most work. The sample wording below is a starting point to adapt, not legal advice — have a lawyer in your jurisdiction review anything you plan to use repeatedly.

1. Scope of work — write it so it can be counted

The single highest-value clause in the document, and the one most often written as a paragraph of vibes.

Vague scope is not a communication failure; it is a pricing failure with a delay on it. "Design a marketing website" can mean four pages or twenty-four, and both parties will remember the number that suits them.

Make every deliverable countable:

VagueCountable
"A marketing website""6 unique page designs at desktop and mobile breakpoints"
"Brand identity""1 primary logo, 2 lockup variants, colour palette, 2 typefaces, 12-page guideline PDF"
"Revisions until happy""3 rounds of revisions per deliverable; further rounds billed at $150/hr"
"Ongoing support""Up to 4 hours per month of maintenance; unused hours do not roll over"

Add an explicit out of scope list. It feels adversarial to write and prevents more disputes than anything else in the contract:

Not included: copywriting, photography, ongoing hosting or maintenance, third-party licence fees, migration of legacy content, and integration with systems not listed in Appendix A.

2. Change orders — the clause that makes scope enforceable

Defining scope achieves nothing without a mechanism for what happens when the client wants something outside it. Otherwise the answer defaults to "you do it for free, slightly resentfully".

Changes to scope. Any work requested that is not expressly described in the Scope of Work constitutes a change. The Contractor will provide a written estimate of the additional fee and any impact on the delivery schedule. Work on a change begins only after the Client approves the estimate in writing. Email approval satisfies this requirement.

The behavioural effect is the point. Once every extra request produces a short email with a number in it, roughly half of them are quietly withdrawn. Not because clients are being unreasonable, but because "can we also…" is a question people ask before they have weighed it against a cost.

3. Payment terms — including the right to stop

Cover four things: amount, schedule, what happens when payment is late, and the right to suspend.

Fees and payment. The Client shall pay a deposit of 40% of the total project fee before work commences. The remaining balance is invoiced per the milestone schedule in Appendix B and is due within 14 days of the invoice date. Overdue balances accrue interest at 1.5% per month. The Contractor may suspend all work on the project if any invoice remains unpaid more than 14 days past its due date, and delivery dates shall be extended by the duration of any such suspension.

That last sentence does more work than the interest rate. A stalled project with a launch date attached focuses attention in a way that a percentage never will. The schedule extension matters too — otherwise you pause for three weeks and are still contractually bound to the original deadline.

4. Intellectual property — transfer on final payment

The default position in the absence of a clause varies significantly between jurisdictions, and neither party should be relying on a default they have not checked. Under US law, for instance, a commissioned work only counts as "work made for hire" in nine narrow categories and only with a signed written agreement — otherwise the freelancer keeps the copyright by default, whatever the client assumed.

The arrangement that is fair to both sides and rarely contested:

Ownership. The Contractor retains all rights in the deliverables until the Client has paid all outstanding fees in full. Upon receipt of final payment, the Contractor assigns to the Client all rights in the final deliverables identified in the Scope of Work.

Contractor materials. Any tools, libraries, templates, source files or components developed by the Contractor prior to or independently of this project remain the Contractor's property. The Contractor grants the Client a perpetual, non-exclusive licence to use such materials solely as incorporated into the deliverables.

Portfolio rights. The Contractor may display the deliverables in its portfolio and marketing materials following public release, unless the Client requests otherwise in writing.

Three separate things, and they need to be separate. Payment-gated transfer gives you real leverage. The carve-out stops you accidentally signing away the component library you have spent four years building. And portfolio rights are trivially easy to secure up front, but nearly impossible to obtain retroactively from a client's legal team.

5. Kill fee — you are selling calendar, not just output

If a client cancels in week three of a six-week project, you have lost more than three weeks of work. You lost six weeks of calendar you reserved for them and turned other work away for.

Cancellation. The Client may terminate this agreement at any time with written notice. Upon termination, the Client shall pay for all work completed to the date of termination, plus 30% of the remaining unbilled project fee. Any deposit paid is non-refundable.

Twenty-five to fifty per cent of the remainder is the normal band. It is not a penalty — it reflects a real, quantifiable loss — and framing it that way in conversation is usually enough to get it accepted.

6. Limitation of liability — cap your exposure

Skipped by almost every freelancer, and the one that could genuinely end your business. Without a cap, your theoretical exposure from a bug or a missed deadline is unbounded.

Limitation of liability. The Contractor's total aggregate liability arising out of or relating to this agreement shall not exceed the total fees paid by the Client under this agreement. Neither party shall be liable for indirect, incidental, special or consequential damages, including lost profits, revenue or data.

Capping liability at fees paid is a standard, widely accepted commercial position. Larger clients will often have their own preferred wording; the negotiation is usually about the multiple, not the principle.

7. Client responsibilities — the deadline protection nobody writes

Half of all missed deadlines are caused by the client, and almost no freelance contract says so.

Client obligations. The Client shall provide all content, assets, credentials, approvals and feedback required for the Contractor to perform the work, within 5 business days of a written request. Delivery dates are contingent on timely receipt of these materials, and shall be extended by one business day for each business day of delay.

Deemed approval. Where the Client does not respond to a request for approval within 10 business days, the relevant deliverable shall be deemed approved and the project shall proceed to the next milestone.

The deemed-approval provision is the underrated one. It stops a project from being frozen indefinitely — unbillable, unfinished, still occupying your calendar — because one stakeholder went on leave.

What to do with this

  • Read your current template against these seven and note which are missing
  • Add the change-order and client-obligations clauses first — they prevent the most common problems
  • Get one lawyer review in your own jurisdiction, then reuse the reviewed version
  • Keep the signed agreement somewhere you can find it in under a minute
  • Reference the specific clause number on invoices and in follow-ups

None of this makes you difficult to work with. Clients who run projects professionally expect a contract that covers scope, change control and payment; its absence reads as inexperience rather than flexibility. The clients who object to a change-order clause are, reliably, the ones who were planning to test it.

Where to go next

Frequently asked questions

Do freelancers really need a written contract for small projects?

Yes, and small projects are where it matters most, because they are the ones people skip it on. A written agreement does not exist to win a lawsuit — most freelance disputes never get near a court. It exists so that when scope, payment timing or ownership becomes contested, there is a document both parties already agreed to that answers the question, rather than two competing memories of a call.

What is a kill fee and how much should it be?

A kill fee is a payment due if the client cancels the project after work has begun. Typical structures are 25–50% of the remaining project value, or all work completed to date plus a percentage of what remains. It compensates you for the calendar time you reserved and turned other work away for, which is the real loss when a project is cancelled in week three.

Who owns the work — me or the client?

It depends entirely on what the contract says, and defaults vary by jurisdiction. The cleanest arrangement for both sides is that you retain ownership until final payment clears, at which point the agreed deliverables transfer to the client. You should also carve out any pre-existing tools, templates or components you bring to the project, licensing those to the client rather than assigning them.

How do I stop scope creep contractually?

Define the deliverables in specific, countable terms, cap the number of revision rounds, and include a change-order clause stating that work outside the defined scope requires written approval and is billed separately. The clause does not stop clients from asking for more — it converts each request into a decision with a price attached, rather than an assumption that it is included.

Can I use a contract template I found online?

A good template is a reasonable starting point and far better than no agreement at all. Have a lawyer in your jurisdiction review it once before you use it repeatedly, since employment classification, IP defaults, late-payment rights and limitation of liability all vary by country, and a template written for one jurisdiction can be unenforceable in another.

Share this article

— Keep reading