What to Include in a Web Design Contract (and the 12 Exclusions That Stop Scope Creep)

A contract that only lists what you'll do is half a contract

Most freelance web design contracts are a list of deliverables and a price. That covers the happy path, which is not the path that costs you money.

The clauses that actually protect your margin are the unglamorous ones: what is explicitly excluded, when intellectual property transfers, how many revision rounds are included, and what happens when an invoice goes unpaid. None of them matter until they matter, and then they are the only thing that does.

This is what a web design contract should include, why each clause exists, and the twelve exclusions that stop scope creep before it starts.

Split the paperwork in two: agreement and statement of work

The single most useful structural decision is to stop writing one giant document.

Use a services agreement for the terms — payment, IP, liability, termination, confidentiality, governing law. Sign it once per client. Then use a separate statement of work for scope and price, one per project.

The reason is practical. You renegotiate scope constantly and terms almost never. Keeping them apart means the second project with a client is a one-page SOW rather than a fifteen-page re-read, and it means a scope argument never accidentally reopens your liability cap.

What the services agreement must cover

1. Fees and payment

State the amount, the tax position, and a due date measured in days from invoice. Fourteen days, not thirty — thirty drifts to forty-five.

Two clauses earn their place here. First, the right to pause work if an invoice passes a stated threshold. Second, that the deposit is non-refundable once discovery begins. Both exist so that chasing payment is a contractual right rather than a favour you're asking for.

2. Intellectual property — and when it transfers

This is the most useful clause in the entire document, and most freelance contracts get it wrong by transferring IP on delivery.

Assign IP on final payment, not on delivery. Until the last invoice clears, the work remains yours and the client has no licence to use it. This is why you never launch a site with an unpaid final invoice — once it's live and owned, your leverage is gone.

Also carve out your own pre-existing tools, libraries and know-how, granting the client a licence to use them as incorporated. Otherwise you have technically assigned away the component library you use on every project.

3. Client responsibilities and delay

Every web project depends on content the client owes you. Say so, and state the consequence: delays in providing content, feedback or approvals move the delivery dates by an equivalent period.

Agreed in writing at the start, this is a shared understanding. Raised for the first time in week five, it's an accusation.

4. Revisions

State the number of rounds, and define a round: one consolidated set of feedback, not eleven messages over four days. Without that definition, "two rounds" means nothing.

5. Warranty

A fixed period — thirty days is typical — during which anything that doesn't work as specified gets fixed free. Then say plainly what the warranty does not cover: new features, content changes, third-party breakage, and problems caused by changes someone else made after handover.

6. Limitation of liability

Cap your total liability at the fees paid, and exclude indirect and consequential loss. Be aware that liability caps are treated differently across jurisdictions — in some they must pass a reasonableness test, and a cap that is void can take the whole clause with it.

7. Termination

Notice period, payment for work completed to date, and the right to terminate immediately for long-unpaid invoices. State which clauses survive termination — IP, liability and confidentiality should.

What the statement of work must cover

The SOW carries the parts that change every project.

Deliverables with visible units

List deliverables, not activities. "Homepage" is a deliverable. "Design work" is not. Each line should be something the client can look at and agree is finished.

Show the hours or days behind each line. A single-number quote invites negotiation on the number; a quote with visible units invites negotiation on scope, which is the conversation you want to be having.

Assumptions

Every assumption is a repricing trigger if it turns out false. Write them as falsifiable statements — "client provides all written copy by 14 March", not "client is cooperative".

Payment schedule

Front-load it. A 40 / 30 / 30 split — signature, design approval, launch — is standard and defensible.

The deposit is not primarily about cash flow. It is a qualification filter. A client who won't pay 40% up front very often was never going to pay the final 30% either, and you find that out before you've spent anything but a proposal.

The 12 exclusions that stop scope creep

Here is the page that does the most work in the entire document, and the one most freelancers leave out.

An exclusions list is not defensive or unfriendly. It is what makes a fixed price defensible, and it is the reference point you need three weeks later when the requests start arriving. Aim for at least eight. These twelve cover most web projects:

1. Copywriting, unless a copy line appears in the quote
2. Photography, videography and stock licensing
3. Logo design or brand identity work
4. Content entry beyond the page count stated
5. Third-party subscription costs — hosting, domain, CMS, email, plugins
6. Ongoing maintenance, updates or backups after handover
7. SEO content strategy or link building beyond the launch setup line
8. Email inbox or deliverability configuration
9. Training beyond the sessions stated
10. More than N rounds of revision per deliverable
11. Legal copy — privacy policy, terms, cookie notices, accessibility statements
12. Migration of historic blog posts or user accounts

Numbers 1 and 2 are the expensive ones. Who writes the copy and where the photos come from routinely swing a web project by thirty to forty per cent. Ask both questions on the discovery call, before you price anything.

The change-order clause, and why phase matters

Scope creep isn't caused by clients asking for things. It's caused by nobody deciding, in writing, at the moment of the ask.

Your contract needs a change-order clause: anything outside the deliverables is quoted separately before work begins. Then add an absorption threshold — requests under, say, thirty minutes are absorbed as a courtesy, not as an entitlement.

The part almost nobody states is that the same request costs differently depending on when it lands:

Clients genuinely don't know this, and explaining it is the most persuasive part of the conversation. So is stating the timeline impact rather than only the cost — "this moves launch to the 14th" changes more minds than a price ever does.

Absorb small requests, but never silently

Absorbing the occasional small ask is good relationship management. Absorbing it invisibly is how a profitable project quietly becomes an unprofitable one.

Do the work, don't charge, and log it. Then surface the running total at the next natural checkpoint — not as a complaint, as information:

"Also, a few small extras since we started: [list], about 2.5 hours in total. No charge on those — just flagging so we both know where we are against the original scope."

That single habit keeps you generous while making the next request visible, and it builds the case for a change order long before you need to have an awkward conversation.

Get it reviewed once — and know where to point the hour

Nothing above is legal advice, and a template downloaded from the internet is not a contract your jurisdiction has blessed. Contract law differs materially by country and by state.

The good news is that the economics favour you: a solicitor reviewing a document that already exists costs a fraction of one drafting from scratch. One hour, once, covers every project afterwards.

Point that hour at the six clauses that vary most:

• IP assignment on final payment — assignment formalities differ, and some jurisdictions require specific wording
• Limitation of liability — caps are unenforceable in some places, or must pass a reasonableness test
• Late-payment interest — many countries set a statutory rate and cap what you can charge
• Termination and the right to pause work for non-payment
• Consumer versus business clients — selling to an individual can trigger protections that override several clauses
• Governing law — naming a jurisdiction the client has no connection to can make enforcement harder, not easier

The short version

A web design contract that protects you has four things most templates lack: IP transferring on final payment, a written exclusions list, a defined change-order process with an absorption threshold, and a front-loaded payment schedule with the right to pause work.

Add those four and most of the ways a client project loses money simply stop happening.

Frequently asked questions

What should be included in a web design contract?

Scope and explicit exclusions, fees and a payment schedule, when intellectual property transfers, revision limits with a definition of a round, a warranty period, a limitation of liability, termination terms and governing law. Keep scope and price in a separate statement of work so you can renegotiate them per project without reopening the terms.

Should a web designer transfer copyright on delivery or on payment?

On final payment. Transferring on delivery removes your only real leverage if the last invoice goes unpaid. Assign the rights in the final deliverables when payment clears in full, and separately grant a licence for any pre-existing tools or libraries you incorporated.

How many revision rounds should a web design contract include?

Two per deliverable is common, but the number matters less than the definition. Define a round as one consolidated set of feedback rather than individual messages, and say what further rounds are billed at. Without that definition, "two rounds" is unenforceable in practice.

What is a statement of work in web design?

A document listing the specific deliverables, units, assumptions, exclusions, timeline and payment schedule for one project. It sits alongside a services agreement, which carries the standing terms. The split lets you sign terms once per client and issue a fresh statement of work for each project.

How do you stop scope creep on client projects?

An exclusions list in the statement of work, and a change-request process that gives every out-of-scope ask a verdict within one exchange — included, warranty, absorbed or change order. Log absorbed work with a running total and surface it at checkpoints, because silent absorption is invisible until the month is gone.

Do I need a lawyer to review a web design contract template?

Yes, once. A template is a drafting starting point, not a contract validated for your jurisdiction. A one-hour review of an existing document costs far less than drafting from scratch, and it covers every project afterwards. Direct that hour at IP assignment, the liability cap, late-payment terms, termination, consumer-versus-business status and governing law.

Everything in this article, as editable files

The clauses, the twelve exclusions, the change-order multipliers and the payment schedule above all come from The Web Agency Toolkit — 39 editable files covering a client web project from first enquiry to final invoice.

It includes the services agreement, statement of work, mutual NDA, change order and care plan agreement as Word documents, twelve delivery SOPs, proposal templates and a pitch deck, and a pricing calculator that derives your day rate from target income and a realistic billable percentage.

Or if you'd rather hand the project over entirely, that's the day job.