How to Write a Freelance Contract That Actually Protects You

Most freelancers grab a contract template from Google, swap in their name, and hope for the best. That works until it doesn't — and when it doesn't, you lose money.

Here's how to write a contract that actually holds up when things go wrong.

Start with the relationship, not the template

Before writing anything, answer these questions about the specific engagement:

• What exactly are you delivering?
• What are you explicitly not delivering?
• When does the client need to provide materials or feedback?
• What happens if they disappear for three weeks mid-project?
• Who owns the work — before and after payment?

Your contract should answer every one of these. If it doesn't, it's decoration.

The clauses that matter most

Payment structure

Never start work without a deposit. 50% upfront for small projects, milestone-based for larger ones. The contract should spell out:

• Total project fee
• Deposit amount and when it's due
• Milestone payments tied to deliverables
• Final payment due on delivery (not “on approval” — that's a trap)
• Late payment penalties

Scope boundaries

Scope creep is the freelancer killer. Your contract needs a change request process: any work outside the original scope requires a written amendment with its own timeline and cost.

Phrase it positively: “Additional work is welcome and will be quoted separately.” Clients understand this — it's how every other industry works.

Client obligations

Your client has responsibilities too. Content, assets, feedback, approvals — put deadlines on all of them. Add a clause that pauses the project timeline if client materials are late.

This is the clause most templates miss, and it's the one you'll use most often.

The “what if” clauses

These handle the scenarios nobody wants to think about:

• Termination: Either party can end the contract with 14 days notice. Work completed is paid for. Deposit is non-refundable.
• Dispute resolution: Try mediation before litigation. It's cheaper, faster, and less adversarial.
• Force majeure: If something genuinely beyond your control prevents delivery, neither party is liable.

Clauses that don't matter (as much as you think)

• Non-compete clauses — Rarely enforceable for freelancers in the UK. Don't let clients restrict your ability to work in your own industry.
• Warranty periods — Unless you're building software with SLAs, a 30-day bug-fix period is generous enough.
• Indemnity clauses — If a client wants you to indemnify them against third-party claims, that's what professional indemnity insurance is for. Don't accept unlimited indemnity.

Make it easy to use

The best contract is one you actually send. If generating a contract takes 45 minutes of copying, pasting, and formatting, you'll skip it for small projects — exactly when you need it most.