The short version: a good freelance contract template has seven working parts, scope, payment terms, revision limits, a kill fee, IP transfer timing, a late payment clause, and a way to end things cleanly, and you build it once in a plain document, not a fancy app, then adjust ten percent of it per client. The template’s job isn’t to make you look professional. It’s to stop the same three arguments happening over and over.
More on this here: What Does a Freelance Technical Writer Need to Get Started?.
Why you need one template, not a new contract every time
I spent about four years sending “bespoke” contracts to every new client, which really meant copying an old Word document and hoping I’d remembered to change the client’s name. In 2019 I sent a contract to a new client with the previous client’s payment terms still in it, 30 days instead of the 14 I wanted. She held me to the 30. That cost me nearly six weeks of cash flow on a £3,200 project.
A template fixes this because it’s built once, and then you only touch the two or three fields that change per client: the scope, the fee, and the dates. Everything else, your payment terms, your IP clause, your cancellation policy, stays fixed. Fixed terms are terms you remember and enforce, because you’ve read them fifty times, not once.
The seven clauses that get used
Most contract templates floating around online are eight pages long and written by a lawyer for a lawyer. You don’t need that. You need the parts that get referred to when something goes wrong, because that’s the only time anyone reads a contract. In eleven years of freelance and consulting work, these are the seven that have ever mattered.
1. Scope, written as a list, not a paragraph
“Marketing support” is not a scope. “Four blog posts of 1,200 words each, two LinkedIn carousels, one email newsletter, delivered by the 20th of each month” is a scope. Write it as bullet points inside the contract itself, not as a separate brief that lives in your inbox and gets forgotten. If it’s not in the contract, it didn’t happen.
2. Payment terms with an actual number
Not “payment due promptly.” Payment due within 14 days of invoice date, 50% upfront for anything over £1,000, remainder on delivery. I learned to insist on the 50% deposit after a £4,500 project where the client went quiet for three weeks post-delivery and I ended up settling for 70% of the fee just to close the file. If you’re setting this up, it’s worth reading how to set up electronic invoicing for a freelance business alongside your contract, because the invoice needs to match the contract’s terms exactly, or you’ve just created a second argument.
3. A revision limit
Two rounds of revisions included. Anything beyond that is billed at your day rate. Without this clause, “just a few tweaks” becomes an unpaid fourth draft, which becomes resentment, which becomes you quietly deciding never to work with this client again without ever telling them why.
4. A kill fee
If the client cancels the project after work has started, they pay a percentage of the total fee, commonly 25 to 50% depending on how far in you are. I use 30% if we’re under a week in, 60% if we’re past the halfway point. Without this clause, a cancelled project means you’ve done unpaid work and have no contractual ground to stand on.
5. IP transfer tied to payment, not delivery
This is the one people get wrong most often. Copyright and usage rights transfer on receipt of final payment, not on delivery of the work. If you hand over full rights the moment you send the file, you’ve lost your only use if the invoice goes unpaid. I once sent final files to a client before the last payment cleared, purely because I was excited about the launch. She used the content, then took four months to pay the final £800. There was nothing in my contract stopping her, because the rights had already transferred on delivery.
6. A late payment clause with teeth
UK law already gives you the right to charge statutory interest on late business-to-business payments, currently 8% above the Bank of England base rate, under the Late Payment of Commercial Debts Act. Put a version of this directly in your contract so the client has read it before, not discovered it during a dispute. It rarely gets used, but the two times I’ve invoked it, payment arrived within 48 hours.
7. A clean exit clause
Either party can end the agreement with 14 days’ written notice, client pays for work completed to that date. This sounds obvious but most freelance contracts never mention how to end things, which means every ending becomes a negotiation instead of a formality.
Step by step: building the template itself
Here’s exactly how I’d build one from nothing, in an afternoon:
- Step 1: Open a plain document (Google Docs is fine, you don’t need special software) and write the seven clauses above as fixed sections with placeholder brackets like [CLIENT NAME] and [PROJECT SCOPE].
- Step 2: Set your default payment terms and put them in the document as actual numbers, not “TBC.”
- Step 3: Write your kill fee and revision policy once, in plain English, and never negotiate the wording, only negotiate the percentage or number if a client pushes back.
- Step 4: Add a signature block with a date field, and a line confirming both parties have read and agreed to the terms, this matters more than people think if a dispute ever goes further than an angry email.
- Step 5: Save it as a locked master copy, then always work from a duplicate for each new client. Never edit the master.
- Step 6: Every six months, review the template against what went wrong with a client that period, and add or tighten a clause. Mine has changed four times in three years, each time because of a specific incident, never because I thought it looked incomplete.
If you’d rather not build one entirely from scratch, there’s a decent overview of how to use online contract templates to speed up client agreements, which covers the software side of this if you’d prefer something with e-signatures built in rather than a Word document and an emailed PDF.
The bit nobody wants to say out loud
Here’s the uncomfortable part. A contract does not protect you from a client who was never going to pay. It protects you in a dispute you’re willing to escalate, and most freelancers, myself included for most of my career, are not willing to escalate. Small claims court in England and Wales caps at £10,000 and costs a filing fee from £35 to £455 depending on the amount, plus your time, plus the relationship damage, plus the very real chance the client simply doesn’t respond and you’re left chasing a judgment that’s hard to enforce against a small company with no assets.
So the honest use of a contract isn’t “I will sue you if this goes wrong.” It’s clarity before the work starts, so the argument that would have happened at the end happens, if at all, in week one, when it’s cheap to walk away. The best contracts I’ve ever used have never been enforced in court. They’ve been referred to once, in an email, with the line “as per clause 4,” and that was usually enough to end the disagreement, because most clients who push back on a clear term aren’t trying to cheat you, they’ve just forgotten what was agreed and a written reminder does the job.
This is also why templates matter more than lawyers for most freelancers under, say, £80,000 a year in revenue. A £600 solicitor-drafted contract is not going to protect you any better than a clear, specific, consistently used template, because the value isn’t in the legal weight, it’s in the fact that you and the client both read and agreed to the same specific terms before any money changed hands.
Where the template fits with your other systems
A contract template works best when it’s part of a wider set of fixed systems, not a one-off document you dig out when someone asks. I keep mine in the same folder structure as my invoice template and project brief template, and I treat all three the same way I’d treat any productivity template for your business, something built once, tested against real use, and only changed when something in the real world proves it wrong.
If you’re just starting out and taking on early clients, for example if you’re one of the people looking at freelance writing jobs as a total beginner in the UK, don’t wait until you’ve been burned once to build this. Build the seven-clause version above before your second client, not your fifth. The version you write after a bad experience is always better than the one you write before, but you shouldn’t need the bad experience to justify sitting down for an afternoon.
Different industries need different weight in different places. A contractor building physical work needs far more detail on delays and material cost overruns than a copywriter ever will, which is why a construction contract template that covers delays and costs looks so different from a freelance writer’s one-pager. Match the template’s complexity to the actual risk in your work, not to how official you want it to look.
What to leave out
Don’t add a non-compete clause unless you operate in a niche where clients regularly poach your other clients, most freelancers never need one and it just makes you look territorial. Don’t add a confidentiality clause longer than a paragraph, most clients skim past dense legal blocks and it does nothing for you if it’s never read. And don’t add jurisdiction clauses copied from American templates specifying US state law if you’re a UK freelancer working with UK clients, I’ve seen this mistake more than once and it makes the whole document look like it was never read before being sent.
Frequently asked questions
Do I need a lawyer to write my first freelance contract template?
No. For most freelance work under roughly £80,000 a year in revenue, a clear template covering scope, payment terms, revisions, kill fee, IP transfer, late payment, and an exit clause does the practical job just as well as a solicitor-drafted one, because the value is in clarity both sides read and agreed to, not legal complexity.
Should IP rights transfer on delivery or on payment?
On payment, always. If you transfer copyright or usage rights the moment you deliver the work, you lose your only real use if the final invoice goes unpaid. Write the clause so full rights transfer on receipt of cleared payment, not on the date you hand over the files.
What’s a reasonable kill fee if a client cancels midway through a project?
Somewhere between 25% and 60% of the total fee depending on how much work is done. A common structure is 30% if cancelled in the first week, rising to 50 or 60% past the halfway point, so you’re not left doing unpaid work with no contractual claim on it.
How often should I update my contract template?
Review it roughly every six months, but only change a clause when something specific has gone wrong with a client, not because it feels incomplete. A template built from real incidents tends to hold up far better than one written from a checklist of things that might theoretically happen.
Primary sources
Related reading: Where to Find Free Contract Templates You Can Edit in Word and What Should You Know Before Signing a Long Term SEO Contract.
