How to Write a Web Design Contract: 12 Clauses That Protect Freelancers From Scope Creep

Most freelance web design projects do not go wrong because the designer is bad at design. They go wrong because of three sentences that were never written down: who pays when, how many revisions are included, and who owns the files before the final invoice is paid.

This guide is a clause-by-clause breakdown of a web design contract for freelancers. For every clause you get the risk it prevents and a plain-English wording example you can adapt. No legalese theatre, no 40-page template nobody reads. Just the sections that actually stop unpaid invoices and endless revision rounds.

Note: this article is practical guidance, not legal advice. Have a lawyer in your jurisdiction review your final template once, then reuse it for years.

The contract gaps that cause the most trouble

Before the clauses, here is where freelance web projects actually break. If your current agreement is missing a row in this table, that is your first thing to fix.

Missing clause What happens in real life Cost to you
No revision cap “Just one more small tweak” repeated 14 times Hourly rate drops by 40 to 60 percent
No deposit Client disappears after discovery and wireframes 2 to 3 weeks unpaid
No client-delay clause Content never arrives, project stalls for 5 months Final payment frozen, calendar blocked
No IP transfer trigger Client uses the site while the last invoice is open Zero leverage to get paid
No kill fee Project cancelled at 80 percent completion Weeks of work billed at deposit value only
No late payment terms Invoice paid at day 90 “when the accounting cycle allows” Cash flow gap, no legal pressure
signing contract laptop

The 12 clauses your freelance web design contract needs

1. Parties, project overview and definitions

Boring but load-bearing. If the contract names a brand name instead of a legal entity, you may be chasing a company that does not exist on paper. Always use the registered legal name, the registration number if there is one, and the billing address.

The project overview is also where you define vocabulary that gets abused later: “page”, “template”, “revision”, “deliverable”. A client who thinks a 12-section landing page is “one page” is not lying, they just never agreed to your definition. zeenesia.com goes into the numbers.

Plain-English wording example:

This Agreement is made between [Your legal name or company], registration number [X], of [address] (“the Designer”) and [Client legal name], registration number [X], of [address] (“the Client”).

“Page” means one unique page layout. Repeated use of an existing layout with different text and images counts as a Template Instance, not a new Page. “Revision” means one consolidated round of written feedback delivered by the Client in a single document or email.

2. Scope of work: what is included and what is explicitly not

This is the single most important clause for preventing scope creep. The trick that most templates miss is the exclusion list. Listing what you will do is only half the job. Listing what you will not do removes the assumption gap.

Your scope should quantify everything that can be counted: number of unique page designs, number of breakpoints, number of languages, number of forms, number of third-party integrations.

Plain-English wording example:

Included: design and build of 7 unique page layouts, responsive at 3 breakpoints (mobile, tablet, desktop), 1 contact form with email notification, basic on-page SEO fields, 1 blog template, deployment to the Client hosting, 1 handover session of up to 60 minutes.

Not included unless agreed in writing as a Change Request: copywriting, translation, additional languages, logo or brand identity creation, photography, custom illustration, e-commerce functionality, payment gateway setup, CRM or ERP integration, email marketing setup, data migration from an existing site, accessibility audit, ongoing maintenance, hosting fees and third-party licences.

3. Change requests and the out-of-scope rate

Scope creep rarely arrives as a big request. It arrives as a chain of small ones. A change request clause gives you a polite, pre-agreed script: “Happy to do that, it falls outside the scope so here is a change order for your approval.”

Set an hourly or per-task rate in the contract itself. Negotiating a rate in the middle of a project, when the client is emotionally attached to the new idea and you are tired, always ends badly.

Plain-English wording example:

Any work requested that is not listed in the Scope of Work will be quoted as a Change Request. The Designer will issue a short written estimate stating the additional cost and the impact on the delivery date. Work on a Change Request begins only after written approval by the Client. Out-of-scope work is billed at [currency] [X] per hour, with a minimum billable unit of 30 minutes. Approved Change Requests are invoiced with the next scheduled payment.

4. Revision limits and the feedback window

A revision clause has three moving parts, and most freelancers only write the first one.

  1. How many rounds are included per phase (not for the whole project).
  2. What a round is: one consolidated set of feedback, not 9 separate emails over 3 days.
  3. How long the client has to send it, and what happens if they do not.

The third part is the one that saves projects. Without a deadline on feedback, your project can stay open forever while your final invoice sits unissued.

Plain-English wording example:

Each phase includes 2 rounds of revisions. A round means one consolidated set of written feedback from the Client, submitted within 5 business days of delivery. Feedback received after a round has been actioned counts as a new round. Additional rounds are billed at the out-of-scope rate stated in Clause 3.

Revisions mean refinements within the approved direction. A request to change the approved concept, layout direction or site structure is a Change Request, not a revision.

If no feedback is received within 10 business days, the phase is deemed approved and the project moves to the next phase.

5. Payment schedule and deposit

Never finance your client. The payment schedule should keep the money ahead of or level with the work delivered, never behind it. A useful rule: at no point in the project should the value of unpaid work exceed the value of your next milestone payment.

Here are three structures that work well for freelance web projects:

Project size Structure Why it works
Small (under 3 weeks) 50 percent deposit, 50 percent before launch Simple, minimal invoicing admin
Medium (1 to 2 months) 40 / 30 / 30 at kickoff, design approval, pre-launch Cash arrives at each risk point
Large or long-running Deposit plus fixed monthly billing on set dates Predictable, survives timeline slippage

Plain-English wording example:

Total project fee: [currency] [X], excluding taxes.

Payment schedule: 40 percent due on signature, before any work begins. 30 percent due on approval of the design phase. 30 percent due before the site is deployed to the live environment or handed over. Web Design Contract Template: 10 Must-Have Sections covers this in more depth.

All invoices are payable within 14 days. Work on the next phase starts only once the previous invoice is settled. Bank fees and currency conversion charges are the responsibility of the Client.

6. Late payment terms, interest and suspension rights

Late payment clauses are not about collecting interest. They are about giving yourself a professional, non-emotional reason to follow up and, if needed, to stop working. Also check your local rules: many jurisdictions give B2B suppliers a statutory right to interest and a fixed recovery charge, even without a contract clause. Writing it in makes it visible and much harder to argue with.

Plain-English wording example:

Invoices unpaid after the due date accrue interest at [X] percent per month, or the maximum rate permitted by law, calculated daily from the due date. A fixed administrative recovery charge of [currency] [X] applies to each overdue invoice.

If an invoice is more than 10 days overdue, the Designer may suspend all work and withhold deliverables, access credentials and file transfers until payment is received in full. Suspension pushes the delivery schedule by at least the number of days of delay. The Client remains liable for any reasonable costs of recovery, including collection agency and legal fees.

7. Client responsibilities and content deadlines

Roughly half of all “late” web projects are late because of the client, not the designer. Content, logins, brand assets, feedback and approvals all sit on their side. If the contract does not assign those duties with dates, every delay becomes your fault by default.

Plain-English wording example:

The Client is responsible for providing, by the dates agreed in the project schedule: all text content, images, logo files in vector format, brand guidelines, product data, legal pages, and access to hosting, domain registrar, analytics and any third-party accounts required. This reference is the one worth keeping handy.

The Client confirms it owns or holds valid licences for all materials supplied to the Designer, and indemnifies the Designer against any claim arising from those materials.

Delays caused by late delivery of materials, late feedback or late approvals move the delivery date by at least the length of the delay and do not entitle the Client to a discount or refund.

8. Project stalling, reactivation and archiving

This is the clause almost no free template includes, and it is the one that rescues your cash flow. When a client goes quiet at 75 percent completion, you need a mechanism that converts silence into either payment or closure.

Plain-English wording example:

If the Client is unresponsive or the project is inactive for more than 20 business days for reasons not attributable to the Designer, the project is considered stalled. All work completed to date becomes immediately invoiceable. There’s a solid take on this from a studio that gets this right.

After 45 business days of inactivity the project is archived and this Agreement ends. Restarting an archived project requires a new agreement, current rates, and a reactivation fee of [currency] [X] to cover rescheduling and re-familiarisation.

9. Ownership of files and intellectual property transfer

This clause is your leverage. Ownership must transfer on receipt of final payment, not on delivery. Also be explicit about what transfers and what does not. Your reusable component library, internal boilerplate, base theme or custom framework should stay yours, licensed to the client rather than sold.

Decide too whether source files (layered design files, Figma working files, uncompressed assets) are part of the deal. Many freelancers deliver the final build as standard and sell source files as a separate licence.

Plain-English wording example:

All intellectual property in the deliverables remains the property of the Designer until the final invoice has been paid in full and cleared. On full payment, the Designer assigns to the Client all rights in the final approved deliverables created specifically for this project.

The Designer retains ownership of all pre-existing materials, reusable code, components, frameworks, templates and internal tools used in the project, and grants the Client a perpetual, non-exclusive, non-transferable licence to use them as part of the delivered website.

Rejected concepts, unused design directions and working source files remain the property of the Designer. Working source files may be purchased separately for [currency] [X].

Use of the deliverables before full payment is not authorised and constitutes a breach of this Agreement.

10. Third-party assets, licences and recurring costs

Fonts, stock photos, premium plugins, page builders, hosting, CDN, email services. If the contract is silent, the client assumes it is all baked into your fee, and you end up paying for their licences out of your margin. Worse, font licensing disputes can land on the designer who installed the font.

Plain-English wording example:

Third-party costs including fonts, stock imagery, plugins, themes, API services, hosting, domain names and SSL certificates are not included in the project fee and are paid directly by the Client, in the Client name, unless agreed otherwise in writing.

Licences for third-party assets are issued to the Client, who is responsible for maintaining them. The Designer is not liable for the discontinuation, price change or failure of any third-party service.

11. Termination and kill fee

A kill fee is not a penalty, it is compensation for the calendar space you reserved and the work already invested. Make the formula mechanical so there is nothing to argue about: all work completed to date, plus a percentage of the remaining fee, plus the deposit stays non-refundable.

Plain-English wording example:

Either party may terminate this Agreement with 10 business days written notice.

If the Client terminates, the deposit is non-refundable, all work completed up to the termination date is invoiced in full at the agreed rates, and a kill fee of 30 percent of the remaining unbilled project fee becomes due. All amounts are payable within 14 days of termination.

The Designer may terminate immediately if an invoice remains unpaid for more than 30 days, if the Client requests unlawful work, or if communication becomes abusive. In that case, all work completed to date is invoiced in full.

On termination, no intellectual property transfers to the Client unless all outstanding amounts have been paid.

12. Acceptance, launch, warranty and support window

Without an acceptance clause, a project never officially ends, and “can you just fix this” emails arrive two years later for free. Define what acceptance is, how long your bug warranty lasts, and what counts as a bug versus a new request.

Plain-English wording example:

The Client has 7 business days after delivery to test the site and report defects in writing. If no defects are reported in that period, the deliverables are deemed accepted.

The Designer will correct, free of charge, any reproducible defect in the delivered work reported within 30 days of acceptance. A defect means the delivered work does not function as specified in the Scope of Work on current versions of major browsers. New features, content changes, design changes, and issues caused by Client edits, third-party updates, plugins or hosting changes are not defects and are billed at the out-of-scope rate.

Ongoing maintenance, updates and support are not included and are available under a separate agreement.

signing contract laptop

Five short clauses to add at the end

These do not need a page each, but a missing line here can cost you real money.

  • Portfolio rights: “The Designer may display the work in a portfolio, case study and social media, including after launch, unless the Client requests confidentiality in writing before project start.”
  • Confidentiality: both sides keep business information private, which also reassures corporate clients.
  • Limitation of liability: “The Designer total liability under this Agreement is limited to the total fees paid by the Client. Neither party is liable for indirect or consequential losses, including lost profits or lost data.”
  • Independent contractor status: you are not an employee, you control your methods and hours, and you handle your own taxes and insurance.
  • Governing law and dispute resolution: name the country and city, and consider requiring a good-faith discussion or mediation before any court action.
signing contract laptop

How to get it signed without killing the deal

A strong contract only works if the client actually signs it. A few things that keep the process smooth:

  1. Send it with the proposal, not after the yes. Contract terms feel normal when they arrive with pricing, and feel like a trap when they arrive three days later.
  2. Keep it to 4 to 6 pages. Nobody reads 22 pages, and unread terms are weak terms.
  3. Put the scope and payment schedule in a one-page annex. That is the part the client actually reads, and it is the part you will change for every project.
  4. Use electronic signature. Signed in 2 minutes on a phone beats printed, scanned and forgotten.
  5. Explain the clauses that protect them too. Delivery dates, defect warranty, confidentiality and IP transfer all read as professionalism, not defensiveness.
  6. Never start work on a verbal yes. No signature and no deposit means no files.
signing contract laptop

Quick pre-signature checklist

Check Yes or no
Client legal entity name and address are correct  
Scope lists exact quantities and an exclusion list  
Revision rounds and feedback deadline are defined  
Out-of-scope hourly rate is written in  
Deposit is non-refundable and due before kickoff  
Late payment interest and suspension right included  
IP transfers only on final cleared payment  
Stalled project and reactivation fee covered  
Kill fee formula is stated as a percentage  
Warranty window and defect definition included  
Portfolio rights granted  
Governing law and liability cap set  
signing contract laptop

FAQ: web design contracts for freelancers

Do I really need a contract for small projects?

Yes, and arguably more so. Small projects attract casual clients, casual expectations and casual payment habits. For a one-page site you can use a two-page version of the same document: scope, price, payment schedule, revisions, IP transfer on payment, termination. The size of the contract should follow the size of the risk, not the size of the invoice.

Is an emailed agreement legally binding?

In most jurisdictions a written agreement accepted by email, with clear terms and clear acceptance, can be binding. The practical issue is not validity, it is proof and clarity. A signed PDF or e-signature with a version number and date is far easier to rely on if things go wrong.

How much deposit should I ask for?

Between 30 and 50 percent is standard for freelance web design. Below 25 percent you are financing the discovery phase yourself. For new clients, long projects or clients in a different country, lean toward 50 percent and milestone billing.

What is a fair number of revision rounds?

Two rounds per phase is the sweet spot for most projects. One round feels harsh and generates conflict, three or more invites indecision. The number matters less than the definition: a round must be one consolidated set of written feedback with a deadline attached.

What is a kill fee and how much should it be?

A kill fee is a payment due when the client cancels a project you had scheduled and started. Typical structure is: non-refundable deposit, plus 100 percent of completed work, plus 25 to 50 percent of the remaining unbilled fee. It compensates you for blocked calendar time and the work you turned down.

Should the client get the source files?

Only if you say so in the contract. Many freelancers hand over the final built site and keep working design files, or sell them as a separate add-on. Whatever you choose, write it down, because “I assumed I would get the Figma file” is one of the most common end-of-project arguments.

Can I use a free contract template I found online?

As a starting skeleton, yes. The problem with most free templates is that they cover scope, payment and IP but skip the clauses that actually protect your time: feedback deadlines, stalled project handling, out-of-scope rates, suspension rights and kill fees. Take a free template, then add the clauses in this article, then have it reviewed once locally.

What should I do when a client ignores the contract?

Quote it calmly and early. A short message referencing the clause number, the agreed term and the next step works better than a long emotional email. The whole point of writing the clause is that you never have to invent the rule in the middle of the conflict.

Final thought

A good web design contract for freelancers is not armour against bad clients. It is a shared script that keeps good clients good. The projects that stay profitable are the ones where both sides knew, on day one, what a revision is, when money moves, who owns what, and what happens if someone walks away.

Write it once. Refine it after every difficult project. Then let it do the uncomfortable talking for you.

Leave a Comment