How to write a freelance design contract that protects both sides
A section-by-section guide to a plain-language design contract: scope, revisions, timeline, payment, ownership and ending a project early.

Most freelance design disputes don't start with bad clients. They start with a vague agreement: an email that says "a new website, around four weeks, $6,000," and nothing about what happens when the copy arrives late, the client wants a third concept, or the invoice sits unpaid for two months. By the time the problem shows up, there is nothing written down to point to.
A good contract fixes that before the project starts. It isn't there to protect you from the client. It's there to make sure you and the client picture the same project, the same timeline and the same money. Below is how to write one that does that job, section by section, in plain language a client will actually read.
Start with plain language, not legal theatre
A contract full of "heretofore" and "notwithstanding" doesn't make you look more professional. It makes the client skim, and a skimmed contract is one nobody remembers when it matters. Write the way you'd explain the project on a call.
- Use short sentences and headings for each section.
- Name things consistently: if you call it "the website" on page one, don't switch to "the deliverable" on page three.
- Put the parts clients care about most (scope, price, timeline) on the first page.
- Keep it to two to four pages for a typical project. Longer is fine for bigger work, but every clause should earn its place.
One caveat up front: this is practical guidance from a designer's point of view, not legal advice. Contract rules differ by country, so have a local lawyer review your template once. After that, you reuse it for years.
Define the scope so tightly it's boring
Scope is where most arguments live, so it deserves the most detail. List exactly what you will deliver, and just as important, what you won't.
For a Framer website project, a scope section might say: "Design and build of a 5-page marketing site (Home, About, Services, Pricing, Contact) in Framer, responsive for desktop, tablet and mobile, with one CMS collection for blog posts. Includes two rounds of revisions per page."
Then add a "Not included" list:
- Copywriting and translation
- Stock photo or font licence fees
- Logo or brand identity work
- Ongoing maintenance after launch
- Custom code components beyond what's listed
The "not included" list is what turns "can you just add a quick shop page?" into a calm conversation about a change request instead of an awkward one about goodwill.
Write down how revisions and changes work
Revisions are not the same as changes. A revision is adjusting what was agreed: tightening spacing, swapping an image, changing a colour. A change is adding something new or reversing an approved direction. Your contract should say both how many revision rounds are included and what happens after that.
- State the number of revision rounds per phase (for example, two for design, one for build).
- Define what a round is: one consolidated list of feedback from the client, sent at once.
- Say how extra rounds or new requests are priced: an hourly rate or a quoted fee, approved in writing before work starts.
- Note that new requests may move the timeline.
This one clause removes most scope creep, because both sides know the process before anyone is frustrated.
Tie the timeline to the client's responsibilities too
Designers often promise a launch date without writing down what they need to hit it. Then the content arrives three weeks late and the date still feels like your promise. Make the timeline a two-way agreement.
- List the milestones and their target dates.
- List what the client must provide and by when: copy, images, logins, feedback.
- Give feedback windows a length, for example five working days per review.
- Say plainly that delays on the client's side shift the schedule by at least the same amount.
It's also worth adding a pause clause: if the client goes silent for, say, 30 days, the project is paused, and restarting depends on your availability. That protects your calendar without punishing anyone.
Make payment terms specific and unmissable
Payment terms should answer every question before it's asked: how much, when, how, and what happens if it's late.
- Deposit: a non-refundable deposit before work starts. 30–50% is common for small projects.
- Milestones: the remaining amount split across clear points, such as design approval and launch.
- Due dates: "due within 14 days of invoice" is better than "on completion".
- Late payment: what you'll do, such as pausing work or adding a late fee where your local law allows it.
- Handover: final files, transfer of the Framer project or site ownership happen after final payment.
That last point matters most. As long as you hold the final handover, you have a calm, legitimate reason for the client to settle the last invoice.
Be clear about who owns what
Clients usually assume they own everything once they pay. Mostly they should, but spell it out so there are no surprises.
A fair approach: the client owns the final approved design and site once paid in full. You keep ownership of rejected concepts, your working files and process, and any reusable components or templates you built before the project. You also keep the right to show the work in your portfolio, unless the client asks for confidentiality, in which case you can agree a delay or a private case study.
Also note who pays for third-party assets. Fonts, stock photos and plugins come with their own licences, and the client should buy them in their own name so they stay valid after you leave.
Plan for the project ending early
No one starts a project expecting to cancel it, which is exactly why this clause gets forgotten. A short termination section keeps an ending civil.
Either side can end the agreement with written notice. The client pays for all work completed up to that date, and the deposit is non-refundable. Files for paid work are handed over once that payment is settled.
Add a line on how disputes are handled first, such as talking it through, then mediation, and which country's law applies. You hope never to use it, but having it written down tends to keep disagreements small.
Get it signed the easy way
The best contract does nothing if it sits unsigned in someone's inbox. Send it as part of your proposal flow, so accepting the quote and signing the agreement happen in one step. Tools like an e-signature service or the contract feature in most client portals work fine. Don't start design work, not even a moodboard, until the contract is signed and the deposit has arrived.
Keep your template in one place, and after every project ask yourself what you wish had been written down. Add that clause. After a handful of projects, your contract will reflect how you actually work.
Conclusion
A freelance design contract is less about law and more about shared expectations. Define the scope and what's excluded, explain how revisions and changes are handled, make the timeline depend on both sides, spell out payment and ownership, and plan for an early ending. Write it in plain language, have it reviewed once, and send it before any work starts. Your clients will trust you more, and you'll spend your time designing instead of arguing.


