Contracts

What to put in a freelance contract

A checklist of the clauses that prevent most freelance arguments.

Contracts guide. 2 minute read. Updated 20 November 2026.

A hand signing a document on a desk
Photo by Scott Graham on Unsplash

A good freelance contract is short enough that your client reads it and clear enough that you never have to argue about what it meant. Most disputes come from the same few gaps: nobody wrote down the price, the number of revisions or who owns the finished work.

This guide shows how each gap gets closed, with an example you can picture.

Who and what

Name both parties and describe the work. Put a list of deliverables in the contract or an attached statement of work, with what is not included.

Money

Set the fee, deposit, payment dates, accepted methods and what happens to late invoices.

Time

Give start and delivery dates and say what happens if the client is late with content or feedback.

Revisions

Say how many rounds are included and what counts as new work.

Ownership

Say when rights in the work pass to the client and whether you may show it in your portfolio.

Confidentiality and liability

Promise to protect private information and limit what you are responsible for, within what the law allows.

Ending

Explain how either side can end the agreement and what is paid for work done.

Sign it

Agree before work starts. An electronic signature is fine in most places.

A worked example

Say you are building a five-page website for a bakery. The contract names the bakery and you, lists the five pages, sets a fixed fee you both agreed, asks for half up front and half at launch, includes two rounds of changes and says the bakery owns the site once the final payment clears. It also says what happens if the bakery takes three weeks to send photos. That is about a page and a half, and nothing in it is exotic.

Words that cause trouble

Phrases like unlimited revisions, as needed, ASAP and reasonable mean different things to different people. Replace them with numbers and dates. Two rounds. Feedback within five working days. Payment within fourteen days of the invoice.

Sending it without drama

Send the contract before you start, with a short note saying it keeps both of you safe and that you are happy to adjust anything that does not fit. Most clients sign without comment. If one pushes back on a clause, ask what worry sits behind it. That tells you what to fix.

Keeping a copy

Save the signed version somewhere you can find it in a year, with the date in the file name. Add changes as signed addenda instead of editing the original.

A quick checklist

  • Names, project and deliverables are specific.
  • Price, deposit and due dates are written as numbers.
  • Revision limits and feedback windows are set.
  • Ownership and portfolio rights are stated.
  • Both sides have signed and saved a copy.

Questions

How long should it be?
As short as covers the points above. One to three pages is common for small jobs.
Can I use the same contract for every client?
A general contract, yes, with a statement of work for each project.
Hand-painted illustration: a paper-document character at a round wooden door holding up a brass key.

Ready when you are.

Start with a free privacy policy. No card needed, and you can upgrade whenever you like.