XimiTech
What should a website design contract include? A checklist before signing
Website design contract checklist: scope, schedule and acceptance, payment, source code and domain ownership, handover, warranty and handling changes to scope.
Many website disputes arise from what was never written down rather than technical issues. Here are ten groups of terms that help protect both the business and the website provider.
A website often takes weeks or months to complete and stays with a business for years. During that time, both parties exchange many requests: add a page, change a colour, adjust a feature. If the contract only says complete website design with a price, every small change can become a dispute. A clear contract helps both parties share the same understanding of the work and the asset to be handed over.
10 groups of terms to include in a website design contract
| Terms | Specify clearly | Why it matters |
|---|---|---|
| 1. Scope of work | Page list, features, revision rounds and who prepares the content | A basis for acceptance and all later changes |
| 2. Timeline | Design approval, development completion, testing and launch milestones; responsibility for delays | Avoid projects that drag on indefinitely |
| 3. Payment | Instalment counts and amounts linked to milestones, and payment methods | Payment tied to results, fair to both sides |
| 4. Acceptance | Acceptance criteria, response times and handling of issues found during acceptance | Define when the project is complete |
| 5. Ownership | Who owns source code, design, domains, hosting, data and administrator accounts, and from when | Determines whether the business truly owns the website |
| 6. Handover | Handover asset list: source code, accounts, usage documentation and server information | Enough to operate independently or change providers when needed |
| 7. Warranty | Duration, scope, response times and warranty exclusions | Avoid disputes over faults after handover |
| 8. Scope changes | How changes are proposed, assessed, quoted and approved, and their impact on timing | Control additional costs |
| 9. Information security | Responsibility for keeping data, accounts and business information confidential | Protect business and customer data |
| 10. Termination and disputes | Termination terms, payment for completed work, unfinished work handover and dispute resolution | A clear exit if the partnership falls short |
Scope of work: the most important clause
Many disagreements arise from different understandings of scope. A business assumes ecommerce includes online payments and shipping integration; the provider understands only a cart and basic ordering. Avoid this with a detailed appendix covering:
- A sitemap and brief description of each page.
- Feature list, including what is not included.
- Number of in-scope design and development revision rounds.
- Who prepares content and images; if the provider writes content, which pages it covers.
- Third-party integrations such as payments, shipping and CRM, with required account conditions.
Ownership and handover: make them clear
A website is a business asset only when its core components belong to the business. The contract should specify:
- The domain is registered to the business, which retains its management account.
- Hosting or servers owned by the business, or covered by a commitment to transfer ownership on request.
- Complete source code handover, usually after contractual payment is finished.
- Customer, order and content data belongs to the business and can be exported when needed.
- The business holds the highest-level admin account, together with usage documentation.
- Third-party licensing: valid licenses for themes, plugins, fonts and images, specifying who pays renewals.
Warranty and scope changes
Warranty terms should answer three questions: how long coverage lasts, what it includes and how to report faults. A warranty stating only a period without scope is of little use in a dispute. Clearly distinguish three requests: provider-caused faults, changes within the accepted scope and new out-of-scope requirements.
For scope changes, a reasonable process is: the business submits a written request, the provider assesses cost and timing, both parties confirm, then work proceeds. This protects the business from unexpected charges and the provider from unrecognized extra work.
Contract warning signs
- No scope appendix, only a generic description of custom website design.
- No mention of source code, domains or administrator accounts.
- Requiring nearly full payment before any product is available for review.
- Warranty with no defined scope, or a mandatory annual fee called maintenance without clear tasks.
- Guaranteeing specific Google rankings, such as reaching number 1 quickly.
- No termination or handover terms when collaboration ends.
Review together before signing
Reviewing the contract together with your web agency, clause by clause, often reveals differences in understanding before they become problems. A responsible provider will be willing to explain and clarify unclear points. See XimiTech’s process from requirements to handover, warranty and handover policy, or 9 criteria for choosing a reliable website agency.
A good contract is like an asset's documentation: it defines what it includes, who owns it and how it is maintained. To see a quote with clear scope, ownership and warranty terms, contact XimiTech.
Frequently asked questions
Do you need a contract for website development?
Yes. A contract, or at least a quote and scope appendix confirmed by both parties, helps avoid misunderstandings about work, costs, timing, ownership and warranty.
How many payment instalments are appropriate?
Payments are usually divided by milestones: a starting deposit, another payment on design approval or completed development, and the balance on acceptance. Each instalment should correspond to a specific result.
When is source code handed over?
Usually after payment is completed under the contract. Specify timing, handover method and the list of items to be delivered.
How are mid-project requirement changes handled?
Changes within the agreed scope follow the contract's revision rounds. New requests outside scope should be assessed and quoted for cost and timing, with agreement from both sides before work.
Is there a standard website design contract?
No template fits every project. Use the article's checklist to check essential contract categories and seek legal review when necessary.