Skip to content

Web design contract checklist

By The Onbo team · Updated

Short answer

A web design contract should cover scope and pages, what's excluded, who supplies content and what happens if it's late, revision rounds, payment milestones, timeline, hosting and domain responsibilities, launch and acceptance, ownership of the finished site, ongoing support, and how changes and cancellations work. Have a lawyer review your template for your jurisdiction.

A general freelance contract covers payment and scope, but websites raise questions other projects don’t: who writes the content, who owns the domain, what happens when copy arrives six weeks late, and when exactly the site counts as “finished”. This checklist lists the clauses a web design contract usually needs, so you can check your own template or brief a lawyer efficiently.

How to use this checklist

Go through your current contract and tick each clause it covers clearly. For anything missing or vague, note what you want it to say in plain language, then have a lawyer turn those notes into wording that works where you do business. This checklist is a practical guide, not legal advice.

Scope and deliverables

  • Pages included, ideally referencing an approved sitemap
  • Features and integrations included
  • Number of design concepts and templates
  • What’s explicitly excluded (copywriting, photography, ongoing SEO, extra pages)
  • Browsers and devices the site will be tested on

Content

  • Who supplies copy, images and other content
  • Due dates for content, ideally per page
  • What happens if content is late: timeline moves, placeholders, or extra fees
  • Optional copywriting or content services and their price
  • Confirmation the client has rights to content they supply

Revisions, timeline and payment

Clause What it should settle
Revisions Rounds included per stage, what a round is, the cost of more
Timeline Key dates, and that they depend on client inputs and approvals
Payments Deposit, milestone payments (for example design approval, launch), due dates
Late payment What happens if a payment is late, including pausing work

Our guide to web design deposits covers common payment structures.

Hosting, domain and access

  • Who owns and pays for the domain
  • Who chooses, owns and pays for hosting
  • How access is shared: invites and delegated roles, not passwords
  • Who handles DNS changes at launch

See how to get website access from clients for the access approach.

Launch, ownership and support

  • What counts as acceptance or sign-off before launch
  • When ownership of the site transfers, usually on final payment
  • Source files and design files: included or not
  • Third-party themes, plugins, fonts and images, and who holds their licences
  • Your right to show the work in your portfolio, if wanted
  • Support or warranty period after launch, and what it covers
  • Ongoing maintenance as a separate agreement, if offered

Changes and ending the project

  • How change requests are quoted and accepted
  • How either side can pause or end the project
  • What’s owed for work done if it ends early
  • How the deposit is treated on cancellation

For example, a freelance web designer might find her contract says nothing about late content. She adds a clause that the timeline moves by however long content is late, with an optional copywriting add-on at a stated price. Two projects later, when a client’s copy arrives a month late, the conversation takes one message, because the client accepted that rule at the start.

How often should you update your contract?

Review your template whenever a project exposes a gap, and at least once a year. Common triggers are a dispute you could have avoided with a clearer clause, a new service you’ve started offering, or a change in how you handle hosting or support. Keep a short list of these as they happen, then take them to your lawyer together rather than one at a time. Version your template too, so you always know which terms a given client accepted.

Write the plain-language version first, then ask for legal wording. Clients read plain language, and your lawyer will spend less time guessing what you meant.

Where does the contract fit in onboarding?

The contract should be accepted before any work starts, with the deposit straight after; see client agreements before a project starts. For the rest of the website start, use the website client onboarding checklist.

Where Onbo fits

Onbo makes your web design contract the first step of every onboarding. The client reads your agreement, types their name and accepts, and Onbo records the acceptance with a fingerprint of the exact text and a PDF for both sides. The deposit invoice follows through your own payment link, then your website questionnaire and file uploads. Whether click-to-accept suits your contracts depends on your jurisdiction, so check with a lawyer. Try it free for 30 days; see pricing.

Questions

What should a web design contract include?

Scope and pages, exclusions, content responsibilities and late content, revisions, payment milestones, timeline, hosting and domain responsibilities, launch and acceptance, ownership, support, change requests and cancellation.

Who should own the website after launch?

That's for you and the client to agree, and the contract should state it clearly, including when ownership transfers and what happens to source files and third-party licences.

Do I need a lawyer for a web design contract?

It's wise to have a lawyer review your template once for your jurisdiction. After that you can reuse it, changing only project details.

Start your next client relationship with everything in place.

Collect the first steps in one link. Try Onbo free for 30 days, no card required.

Start free