Web Design Agency Contract Checklist: 18 Clauses to Review Before You Sign
Direct answer: Before signing a web design agency contract, confirm the exact scope, who controls the business accounts, which rights and files transfer, how acceptance is tested, how changes are priced, and what happens at handover or early termination.
What should you check first in a web design agency contract?
A strong contract names the deliverables, responsibilities, approval process, payment schedule and acceptance tests instead of relying on broad phrases such as “complete website.”
The business should know who controls the domain, hosting, CMS, analytics and Search Console accounts—and exactly which files, licences and credentials are handed over.
SEO, accessibility, performance and security need testable deliverables. “SEO included” or “fast website” is not a measurable commitment.
The exit clause matters before trouble starts: document cancellation, refunds, work completed, data export, credential transfer and post-termination access.
This guide is a commercial checklist, not legal advice. Ask a qualified lawyer in your jurisdiction to review terms that affect liability, intellectual property, privacy or disputes.
A web design agency contract should turn a sales conversation into a delivery system. It should tell both sides what is being built, who supplies each input, how decisions are approved, what “finished” means and what happens if the project changes. When those details remain scattered across email, proposals and calls, even honest teams can remember the deal differently.
Use this checklist after comparing the proposal and before paying a non-refundable deposit. It is written for small-business owners, marketing teams and agency buyers—not lawyers. The goal is to reveal unclear commercial and technical assumptions early enough to fix them in writing.
Do not treat a long contract as a good contract by default. A useful agreement can be concise, but its important terms must be specific. Conversely, ten pages of legal language cannot rescue a scope that says only “design a modern, SEO-friendly website.”
How should you review a web design agency contract step by step?
Use this eight-step review before the deposit is paid. It turns a dense agreement into a practical project map and exposes the gaps that are expensive to discover after design or development begins.
Step 1: Have you collected every document that forms the deal?
Put the proposal, statement of work, timeline, quote, email commitments and contract in one folder. Confirm which document controls if two versions conflict.
Step 2: Have you marked every deliverable and exclusion?
Highlight pages, templates, integrations, content tasks, migrations, testing and training. Create a second list of work that is explicitly excluded.
Step 3: Have you assigned an owner to every input and account?
Name who supplies copy, images, legal text, product data, feedback and credentials. Record who owns the domain, hosting, CMS, analytics and Search Console accounts.
Step 4: Have you translated promises into acceptance tests?
Replace vague phrases with observable checks: forms deliver correctly, agreed breakpoints are tested, redirects return the right status and editors can complete routine updates.
Step 5: Have you mapped payments to milestones?
Connect deposits and stage payments to defined outputs or approvals. Identify recurring fees, third-party subscriptions, taxes and charges for work outside scope.
Step 6: Have you rehearsed a change request?
Ask what happens if you add a template, rewrite approved copy or connect another system. The contract should explain estimates, approval and timeline impact.
Step 7: Have you rehearsed launch and handover?
List the people, access, files, training, backup, DNS change, analytics checks and sign-off needed to move from staging to live operation.
Step 8: Have you rehearsed an early exit?
Check cancellation notice, payment for completed work, access to unfinished assets, data export, licence limits and credential transfer before a dispute exists.
Which 18 clauses should you review before signing?
Read these clauses together. Scope affects price; ownership affects handover; acceptance affects final payment; and maintenance affects what happens after launch. A strong contract joins those decisions instead of treating them as unrelated legal paragraphs.
1. Does the scope name the exact website deliverables?
The scope should describe the website as a set of deliverables, not as a mood. Record the page inventory, unique page templates, reusable sections, forms, ecommerce functions, integrations, migrations, content entry, redirects, analytics setup, training and launch support. If a proposal lists ten pages, clarify whether that means ten independently designed layouts or ten pages built from three templates.
Separate discovery, design, development and content work. “Custom design” may refer to a tailored visual system, a modified theme or a fully bespoke front end; those are different levels of effort. Ask the agency to identify what is custom, what is configured from the platform and what remains your responsibility.
Also list exclusions. Accessibility audits, copywriting, photography, paid plugins, email migration, ongoing SEO and post-launch changes often sit outside a standard build. Exclusions are not automatically bad; invisible exclusions are.
2. Who supplies copy, images, product data and approvals?
A timeline cannot work if the contract names deadlines for the agency but leaves client inputs open-ended. Assign responsibility for copy, brand assets, photographs, legal policies, product data, translations and access credentials. State the required format and the date each input is due.
Name one client decision-maker who consolidates feedback. Without that role, three stakeholders can send contradictory comments and still expect the original deadline. The agency should name its delivery lead too, so questions and approvals have a clear route.
The delay clause should be balanced. If late content pauses the schedule, explain how work restarts and whether a new launch date is mutually agreed. Avoid wording that lets either side impose unlimited delay without notice.
3. Are milestones tied to specific outcomes?
Milestones should describe what you will receive: approved sitemap, agreed wireframes, accepted visual direction, working staging site, completed content entry, launch-ready QA and final handover. A calendar date without an output is difficult to approve or challenge.
Distinguish a target date from a guaranteed date, especially when the project depends on client feedback, a third-party API or platform review. Record assumptions and decision windows. If a launch date is business-critical, ask what contingency exists and which late changes can be deferred.
For staged delivery, confirm whether approval of one phase authorises the next. That prevents a design direction from being reopened after development has begun unless the parties agree to a change request.
4. What exactly triggers each payment?
Connect payments to unambiguous events: contract signature, delivery of a named milestone, written approval or launch. Avoid a schedule that makes the full balance due before you can inspect the agreed work, but do not expect an agency to finance an entire project until the end.
The fee section should cover taxes, payment method, currency, late-payment consequences and expenses. List recurring platform, hosting, app, plugin, font, stock-media and domain costs separately from the agency fee. Record who purchases each subscription and whether it renews automatically.
If a deposit is non-refundable, clarify how it is treated if the project is cancelled before production starts. For hourly or retainer work, ask for the rate, billing unit, approval threshold and reporting method.
5. How many revision rounds are included?
“Unlimited revisions” sounds reassuring but rarely defines a stable process. A better clause names the review stages, number of feedback rounds, response window and people authorised to approve. It also separates corrections to agreed requirements from new preferences or added functionality.
Define what a revision round means. Is one round a consolidated document from the client, or every message sent during a week? State what happens when feedback arrives after approval or contradicts the brief.
The change-control process should require a short written description, estimated fee and timeline impact before extra work begins. A change can replace an existing deliverable, move to a later phase or expand the scope; the decision should be explicit.
6. What tests define an acceptable website?
Acceptance should be based on agreed checks, not whether the site feels perfect. List supported browsers and devices, representative screen sizes, form behaviour, payment flow, account creation, search, navigation, links, error states, content accuracy and editing permissions.
Separate defects from enhancements. A form that fails to send is a defect if the contract requires a working form. A request to add conditional routing after approval is an enhancement. Define how defects are reported, prioritised and retested, plus the length of any launch warranty.
Use Webcurry’s mobile QA checklist as a practical companion: it focuses on real launch checks rather than a vague promise that the site will be “responsive.”
7. Who is the registrant of the domain name?
The contract should say whose name and email appear on the domain registration and who controls the registrar account. ICANN describes the registrant as the person or entity holding the rights to the registered domain name. That is different from the developer who points DNS records or the host that serves the website.
For most business projects, the client should be able to access the registrar directly, maintain accurate contact details, renew the domain and transfer it when eligible. The agency can be granted technical access without becoming the only person who can recover the account.
Record renewal responsibility, two-factor authentication, DNS change approval and the recovery process. A domain that expires or remains trapped in a former supplier’s account can interrupt the website, email and marketing at the same time.
8. Who controls hosting, the CMS and connected accounts?
List every operational account: hosting, Wix or WordPress, Shopify, email delivery, forms, payments, CRM, analytics, tag manager, Search Console, maps, cookie consent and backups. For each one, record the account owner, administrator, billing owner and day-to-day user.
The safest structure usually gives the business durable ownership and grants the agency only the access it needs. Avoid shared passwords sent in chat. Use named users, roles and two-factor authentication where the platform supports them.
If the agency resells hosting or a platform plan, ask what happens when the relationship ends. Can the service be transferred? Does the price change? How much notice is required? What files and database exports will be supplied?
9. Which intellectual-property, portfolio and confidentiality rights apply?
Do not assume that paying an invoice automatically transfers every right in every asset. The agreement should distinguish client-supplied material, agency-created work, reusable agency tools, open-source components, third-party software, stock media, fonts and platform features.
State when ownership or the agreed licence transfers—often after full payment—and what the client may do with the work afterward. Ask whether editable design files, source files, custom code repositories and documentation are included. If they are excluded, make the limitation visible before signing.
This is one area where local law and precise wording matter. Use Webcurry’s website ownership guide to prepare questions, then ask a qualified lawyer to review terms that affect copyright, licensing or reuse.
Portfolio and credit clauses should respect confidentiality, launch timing and regulated information. Decide whether the agency may use screenshots, your logo, project outcomes or a public case study. If approval is required, name the process.
Also check whether a footer credit will appear on the live site. A discreet credit may be acceptable, optional or prohibited depending on the brand. It should not be added by surprise or made technically difficult to remove.
If the project includes confidential product plans, customer data or an unannounced launch, make those limits explicit. A separate non-disclosure agreement may be appropriate, but it should align with the main contract rather than contradict it.
10. Are third-party licences and renewal costs disclosed?
A modern website may depend on premium themes, apps, plugins, APIs, stock images, fonts or email services. The contract should name important dependencies, licence holder, first-year cost, renewal cost and consequence of cancellation.
Clarify whether an agency licence can legally remain on the client site after the engagement. Some licences cover only websites maintained by the agency; others can be transferred or replaced with a client licence. The answer affects both cost and future independence.
Ask how alternatives are approved when a service changes price or is discontinued. The agency cannot guarantee that every vendor will exist forever, but it can document dependencies and avoid silently locking critical functions to a private account.
11. Which accessibility standard will the website target?
“Accessible website” needs a defined target and testing method. The W3C recommends WCAG 2.2 for current accessibility work. A contract can name an intended conformance level, the pages and components tested, the tools used, manual checks, known exceptions and remediation responsibilities.
No automated scanner can prove complete conformance on its own. Include keyboard navigation, focus visibility, form labels, error handling, headings, alternative text, contrast and zoom or reflow checks where relevant. Decide who supplies accurate alt text and accessible documents.
Avoid guarantees that no legal complaint will ever occur. A useful clause defines the work performed, evidence delivered and process for correcting agreed defects. Legal obligations vary by jurisdiction and business type.
12. How will performance and Core Web Vitals be tested?
Replace “fast website” with a test plan. Name representative pages, mobile and desktop conditions, the point in the project when testing occurs, and which third-party scripts must remain enabled. A clean demo page is not a meaningful substitute for the final site with real media, consent tools, analytics and marketing tags.
Google’s Web Vitals guidance evaluates recommended targets at the 75th percentile of page loads, which is field data collected from actual visits. A pre-launch contract can still use lab tests for diagnosis, but it should not pretend a new site already has stable field data.
Record who optimises images, fonts, scripts, caching and app choices. If the client later adds a large video or heavy chat widget, the agency should not remain responsible for an unchanged score without a maintenance scope.
13. What SEO work is actually included?
“SEO included” is not a scope. Name the deliverables: crawlability review, page titles, meta descriptions, heading structure, image alt text, internal linking, structured data, XML sitemap checks, robots directives, canonicals, redirect mapping and Search Console verification.
If the project is a redesign or migration, require an old-to-new URL map and direct server-side permanent redirects where technically possible. Google’s site-move guidance recommends mapping old URLs to relevant new destinations and avoiding unnecessary redirect chains. The contract should also cover testing, updating internal links and monitoring after launch.
Separate technical launch work from ongoing keyword research, content production, link earning and reporting. No responsible agency can guarantee a particular ranking, traffic level or appearance in an AI answer.
14. Who owns Analytics, Tag Manager and Search Console access?
Measurement accounts should survive an agency change. Set up the business as the durable owner or administrator and add agency users with appropriate permissions. Google Search Console distinguishes owners, full users and restricted users; those roles do not provide the same control.
The contract should name the property, data stream, conversion events, consent requirements, filters, referral exclusions and handover documentation included. If an existing setup will be replaced, decide whether historical access remains available.
Require a launch verification: page views, form events, purchases or leads should be tested on the live domain. An analytics tag being present does not prove that meaningful events, consent behaviour or reporting are correct.
15. What security, backup and privacy work is included?
Security must be described as controls and responsibilities, not as a promise that the site can never be attacked. List platform updates, access roles, two-factor authentication, backup frequency, retention, restore tests, vulnerability handling and incident contacts.
The OWASP Web Security Testing Guide provides a broad framework for testing web applications, but the appropriate depth depends on the site. A brochure website and a custom application processing sensitive data do not need identical assessments. Ask the agency to state what it will and will not test.
Privacy work should identify who supplies policies, configures consent tools, maps forms and decides retention. A web designer should not invent legal policies for the business unless qualified and contracted to do so.
16. What maintenance and support happen after launch?
Define the handover from project to support. State whether the launch includes a defect warranty, how long it lasts, which issues qualify and how quickly they are acknowledged. A response time is not necessarily a resolution time.
For a maintenance plan, list updates, backups, monitoring, small content changes, performance reviews, security checks and reporting. Set monthly limits, unused-hour rules, emergency rates and exclusions. “Ongoing support” without a service description is too elastic.
If there is no retainer, ask how future work is requested and priced. Confirm whether another developer can maintain the site without voiding support for unrelated defects.
17. What happens if either side ends the project early?
The termination clause should explain notice, outstanding invoices, payment for completed work, refunds, access to work in progress and removal of confidential information. It should not wait until a dispute to decide whether the client can receive approved designs, content and exports.
Include a practical transition period where appropriate. The agency may need to transfer repositories, platform roles, DNS notes, licences and documentation. The client may need to pay undisputed amounts and remove agency access after confirming the handover.
Check whether termination for convenience differs from termination for breach. Legal consequences vary, so ask a lawyer to review liability, indemnity, dispute resolution, governing law and caps on damages.
18. What must be included in the final handover?
Create a handover schedule before launch. It can include registrar and hosting access, CMS administrator roles, code repository, design files, database export, media library, licences, renewal dates, analytics, Search Console, tag manager, DNS records, backup, documentation and training.
The business should test ordinary tasks: editing a page, adding a user, exporting form submissions, updating products, viewing analytics and restoring access. A password spreadsheet alone is not a handover if critical accounts remain owned by somebody else.
Use an acceptance record that lists open items, owners and due dates. Small non-blocking issues can be scheduled after launch, but unresolved payment, checkout, form, access or indexing failures should not disappear behind a celebratory “site is live” message.
Which contract red flags should make you pause?
The scope uses “complete website,” “SEO-ready” or “unlimited” without defining deliverables or limits.
The agency will register the domain in its own name and will not provide direct registrar access.
The full balance becomes due before you can inspect or test the agreed work.
Ownership, licences and source-file delivery are absent or deferred until after signing.
The contract promises guaranteed rankings, traffic, PageSpeed scores or legal compliance.
There is no change-control process, so additional requests can become surprise invoices or invisible delays.
The exit clause lets one side retain essential accounts, data or paid-for work without a clear handover path.
Third-party subscriptions and renewals are bundled into one fee with no dependency list.
Security and maintenance are described as permanent protection rather than specific controls and tasks.
The proposal, statement of work and contract conflict, but no clause says which document takes priority.
How should agency and client responsibilities be divided?
The exact division depends on the project, but every responsibility needs an owner. This practical starting point prevents “I thought you were doing that” conversations.
Workstream | Practical responsibility split |
Page inventory and user journeys | Agency proposes; client confirms business priorities |
Copy and legal policies | Client supplies or separately commissions; agency places and formats |
Design system and responsive layouts | Agency creates; client reviews through named decision-maker |
Domain and platform ownership | Client controls durable accounts; agency receives role-based access |
Technical SEO and redirect map | Agency delivers if included; client confirms priority URLs and history |
Accessibility content decisions | Shared: agency implements patterns; client supplies accurate content and documents |
Launch approval | Client signs acceptance checklist; agency records remaining issues |
Post-launch maintenance | Named in a separate support scope or clearly excluded |
What should you ask a web design agency before signing?
Which documents form the agreement, and which one controls if they conflict?
What exact pages, templates, integrations and content tasks are included?
Which deliverables and recurring costs are excluded?
Who owns the domain, hosting, CMS, analytics and Search Console accounts?
What rights, files, licences and credentials transfer after payment?
How are revisions, defects and new requests treated differently?
What acceptance tests must pass before the final payment or launch?
What technical SEO, redirect, accessibility, security and performance work is included?
What happens when either side delays an input or approval?
What do I receive if the project ends early?
What are the most common web design contract questions?
Is a web design proposal the same as a contract?
Not necessarily. A proposal usually describes the offered scope and price, while the contract sets the binding terms of the engagement. The documents can be incorporated together, but the agreement should state which version controls if they conflict. Ask a lawyer when the legal effect is unclear.
Who should own the domain name?
The contract should identify the registrant and account controller. ICANN describes the registrant as the person or entity holding rights to the registered domain. For most business websites, the business should have durable registrar access, accurate contact details and the ability to renew or transfer the domain, while the agency receives only the technical access it needs.
Should a web design contract include source files?
Only if the agreement says so. Specify whether editable design files, custom code repositories, exports, documentation and media originals are included, when they are delivered and which reusable or third-party components are excluded. Do not assume an invoice automatically transfers every file or right.
How many revisions should be included?
There is no universal number. The useful approach is to define review stages, feedback rounds, response windows and the decision-maker. Separate corrections to agreed requirements from new features or changes to an approved direction, then use written change control for extra work.
What does SEO included mean in a web design contract?
The phrase is too vague on its own. List the deliverables, such as crawlability checks, titles, descriptions, headings, internal links, canonicals, sitemap review, structured data, redirect mapping and Search Console setup. Keep ongoing content, link earning and reporting separate, and reject guaranteed-ranking promises.
Can a web design agency guarantee a PageSpeed score?
Be cautious. Scores depend on the tested page, device, network, content and third-party scripts. Define a test method, representative pages, required services and remediation responsibility. Lab tests can support launch QA, while stable Core Web Vitals field data requires real visits over time.
What should happen if the website project is delayed?
The agreement should assign inputs and approval deadlines to both sides, explain how delays affect milestones, and describe how a paused project restarts. For a fixed launch date, identify contingency work and late requests that can move to a later phase.
What is a website acceptance clause?
It defines how the client decides that contracted work is complete. Good acceptance criteria are observable: agreed forms work, representative devices are tested, required content is present, redirects are verified and known issues are recorded. It should also distinguish defects from new requests.
Should maintenance be included in the original build contract?
It can be, but it needs a defined scope. State whether updates, backups, monitoring, content changes, security checks and support are included, with limits and response times. If maintenance is separate, the build contract should still explain the launch warranty and handover.
What happens to unfinished work if the contract is cancelled?
The termination clause should address notice, payment for completed work, refunds, access to approved or in-progress assets, data export, licences and credential transfer. The exact legal result depends on the contract and local law, so obtain legal advice for disputed or high-value projects.
Should accessibility be written into the contract?
Yes when accessibility is part of the requirement. Name the intended standard or target, tested pages and components, manual and automated checks, known exceptions and remediation process. Avoid treating an automated scan as proof of complete conformance or promising that no complaint can ever occur.
Do I need a lawyer to review a web design agency contract?
A practical checklist can reveal unclear scope and technical assumptions, but it is not legal advice. A qualified lawyer is especially useful for intellectual property, privacy, liability, indemnity, termination, dispute resolution and governing-law clauses.
What should you do before you sign?
The best contract is not the one with the most legal pages. It is the one that makes delivery, decisions, ownership and exit boringly clear. Start with the scope, account control, acceptance tests and handover; those four areas expose most operational surprises.
If a clause is vague, ask for a concrete example: Which files? Which account owner? Which test? Which deadline? Which fee? If the answer changes the deal, add it to the agreement before you sign.
Once the contract is clear, keep the delivery trail equally clear. Use one brief, one decision-maker, written approvals and a launch checklist. That gives the client and the agency a fairer project—and gives the website a much better chance of launching without expensive cleanup.
Which authoritative sources support this checklist?
This guide combines practical project-planning experience with current public documentation. The sources below support the domain, migration, access, accessibility, performance and security sections; the commercial and legal wording should still be reviewed for your jurisdiction.
Who wrote this web design contract guide?
Written by Sameer Verma, a web designer and digital marketer at Webcurry. His work focuses on practical website planning, technical SEO, conversion-focused design and reliable handover workflows for small businesses. This guide reflects Webcurry’s project-planning approach and publicly documented standards; it does not provide legal advice.



Comments