Statement of Work Template for Website Builds (UK 2025)

When You Need This Contract

A website build SOW must translate design aspirations into precise technical specifications that both client and developer can agree on. It should cover the full project lifecycle from discovery and wireframing through design, development, content population, testing, and launch. Critical elements include CMS requirements, hosting specifications, browser and device compatibility, accessibility standards, SEO requirements, and comprehensive go-live criteria. Ambiguity in website SOWs is the primary cause of project disputes in digital agencies.

Key Clauses

• Page count and site structure with sitemap
• CMS selection and functionality requirements
• Browser and device compatibility matrix
• Accessibility standards compliance level (WCAG 2.1 AA minimum)
• Go-live checklist with comprehensive acceptance criteria

What to Watch Out For

• Not specifying the complete site structure upfront, leading to scope creep as additional pages are requested during development
• Failing to include accessibility requirements, which may create legal risk under the Equality Act 2010

Sample Clauses

• Sample site structure clause: 'The website shall comprise [X] page templates and approximately [Y] total pages as defined in the sitemap at Appendix A. Additional pages beyond the agreed sitemap require a change request. Template types include: Homepage, Standard Content, Blog Listing, Blog Post, Contact, and Landing Page.'
• Sample go-live clause: 'The website shall not go live until the following criteria are met: all pages are content-populated and proofread, all links are tested and functional, the contact form is tested with deliverability confirmed, Google Analytics and Search Console are configured, SSL certificate is installed and verified, mobile responsiveness is tested on agreed devices, and accessibility has been tested to WCAG 2.1 AA standard.'