WEB DEVELOPMENT STATEMENT OF WORK ================================= Disclaimer — not legal advice. This template is provided free of charge, as is and with no warranty of any kind, and using it creates no attorney-client relationship. It is jurisdiction-neutral: you are responsible for adapting it, for your own legal and tax compliance, and for having a qualified professional in your jurisdiction review it before you rely on it. Full terms: https://trycolo.co/terms-of-use SOW reference: [SOW-NUMBER] Date: [DATE] Governing agreement: [ ] Web design / development contract dated [DATE] [ ] Master Services Agreement dated [DATE] This Statement of Work ("SOW") describes the website build to be delivered by [DEVELOPER BUSINESS NAME] ("Developer") for [CLIENT LEGAL NAME] ("Client"). The legal terms (liability, IP, confidentiality, termination) are set out in the governing agreement named above. 1. Project overview ------------------- Field | Detail ------------------------------- | ------------------------------------------------------------------------------------- Client contact (decision-maker) | [NAME], [TITLE], [EMAIL] Developer contact | [NAME], [EMAIL] Site purpose | [e.g. lead generation for a B2B services firm / product catalog / event registration] Primary domain | [DOMAIN] Existing site to replace | [ ] None [ ] Yes: [URL] Target launch window | [DATE] to [DATE] Fee basis | [ ] Fixed fee [ ] Time and materials with estimate of [N] hours 2. Page and template inventory ------------------------------ Every page or template in scope is listed below. Pages not listed are out of scope and are handled under section 10. # | Template / page | Unique layout? | Dynamic content | Notes - | ------------------------- | ---------------------------- | ------------------------------- | ----------------------- 1 | Home | Yes | [e.g. latest 3 posts] | [NOTES] 2 | About | Yes | None | [NOTES] 3 | Service detail (template) | Template, used for [N] pages | None | [NOTES] 4 | Blog index | Yes | Paginated posts, [N] per page | [NOTES] 5 | Blog post (template) | Template | Author, category, related posts | [NOTES] 6 | Contact | Yes | Form: see section 4 | [NOTES] 7 | 404 and legal pages | Shared template | None | Privacy, terms, cookies 8 | [PAGE] | [YES / TEMPLATE] | [DETAIL] | [NOTES] Total unique layouts: [N]. Total pages at launch: [N]. 3. Technical stack and accounts ------------------------------- Item | Choice | Account owner | Developer access -------------------------- | ------------------------------------------------ | ------------- | ------------------- CMS / framework | [e.g. WordPress, Webflow, static site generator] | [CLIENT] | Admin until [DATE] Hosting | [PROVIDER AND PLAN] | [CLIENT] | [LEVEL] Domain registrar and DNS | [PROVIDER] | [CLIENT] | DNS edit for launch Transactional email | [PROVIDER] | [CLIENT] | [LEVEL] Analytics | [TOOL] | [CLIENT] | [LEVEL] Other third-party services | [LIST] | [CLIENT] | [LEVEL] All accounts are opened in the Client's name. Subscription and license costs for these services are paid by the Client unless listed in section 9. 4. Functionality ---------------- - Forms: [FORM NAME] sends to [EMAIL / CRM / TOOL]; fields: [LIST]; spam protection: [METHOD]. - Search: [ ] Not included [ ] Site search across [CONTENT TYPES]. - E-commerce: [ ] Not included [ ] Up to [N] products, [N] variants each, payment via [PROVIDER]. - Multilingual: [ ] English only [ ] [LANGUAGES], with [MANUAL / PLUGIN] translation workflow. - Accessibility target: [WCAG 2.2 AA / OTHER]. Audit included: [ ] Yes [ ] No. - Performance target: [e.g. Largest Contentful Paint under 2.5 seconds on a mid-range mobile on 4G for the home page]. 5. Browser and device support ----------------------------- The site is built and tested against the following. Anything not listed is supported on a best-effort basis only. Platform | Versions | Widths tested -------------------------------------- | ------------------------- | ------------------------ Desktop: Chrome, Edge, Firefox, Safari | Latest [2] versions | [1280px, 1440px, 1920px] iOS Safari | Latest [2] major versions | [375px, 430px] Android Chrome | Latest [2] major versions | [360px, 412px] Tablet | [iPadOS Safari latest] | [768px, 1024px] 6. Content and assets --------------------- Asset | Supplied by | Format | Due date ------------------------------------ | -------------------- | ----------------------------------- | ------------------ Page copy for all pages in section 2 | [CLIENT / DEVELOPER] | [Doc per page, final and approved] | [DATE] Photography and illustrations | [CLIENT / DEVELOPER] | [Full resolution, licensed for web] | [DATE] Logo and brand guidelines | Client | [SVG + PDF guidelines] | [DATE] Blog migration | [DEVELOPER] | [N] posts from [SOURCE] | Migrated by [DATE] Redirect map | [WHO] | Spreadsheet of old URL to new URL | [DATE] If content arrives after its due date, the launch window moves by the same number of business days. 7. Environments and launch plan ------------------------------- 7.1 Development: built on the Developer's local or private environment. 7.2 Staging: a password-protected staging URL at [STAGING URL] is shared from [DATE] for review. 7.3 Production launch: scheduled for a [WEEKDAY] between [TIME] and [TIME] [TIMEZONE], not the day before a weekend or public holiday. 7.4 Launch steps owned by Developer: deploy to production, configure SSL, set redirects, submit sitemap, smoke-test all forms. 7.5 Launch steps owned by Client: approve go-live in writing, update DNS records at the registrar (or grant access), notify internal teams. 7.6 Rollback: the previous site remains available at [LOCATION] for [N] days after launch. 8. Acceptance testing and post-launch fixes ------------------------------------------- 8.1 Developer marks staging "ready for acceptance" and shares the test checklist. 8.2 Client reports defects in one consolidated list within [7] business days, each referencing a page in section 2 or a row in section 5. 8.3 A defect is behavior that does not match this SOW. A change of content, layout or preference is a change request under section 10. 8.4 Developer fixes reported defects within [5] business days and resubmits. If no defects are reported within the window, the site is accepted. 8.5 Post-launch fix window: [30] days from launch. Defects against this SOW are fixed at no charge. New features, content edits and third-party plugin failures caused by updates after launch are not covered and fall under a separate maintenance agreement. 9. Fees and payment milestones ------------------------------ # | Milestone | Trigger | Amount | Due - | ---------------- | ------------------------------ | -------------------------- | ---------- 1 | Kick-off | SOW signed | [CURRENCY] [AMOUNT] ([X]%) | On receipt 2 | Design approved | Client approves page designs | [CURRENCY] [AMOUNT] | Net [N] 3 | Staging accepted | Section 8.4 acceptance | [CURRENCY] [AMOUNT] | Net [N] 4 | Launch | Site live on production domain | [CURRENCY] [AMOUNT] | Net [N] | Total | | [CURRENCY] [TOTAL] | Third-party costs paid by Developer on the Client's behalf: [LIST OR "none"], re-charged at cost. Late payment terms: as set out in the governing agreement. 10. Change requests ------------------- 10.1 Any page, feature, integration or browser not listed above requires a written change request. 10.2 Developer responds within [3] business days with the added cost and the effect on the launch window. 10.3 Work on a change starts only after the Client approves the change request in writing. # | Date | Change | Fee impact | Launch impact | Approved by - | ------ | ------------- | ------------------- | ------------- | ----------- 1 | [DATE] | [DESCRIPTION] | [CURRENCY] [AMOUNT] | [+N days] | [NAME] 11. Acceptance of this SOW -------------------------- Developer | Client ------------------------------- | ------------------------------- Signature: ____________________ | Signature: ____________________ Name: [NAME] | Name: [NAME] Date: [DATE] | Date: [DATE] ------------------------------------------------------------ How to use this template 1. Fill in section 2 first and price from it. Every unique layout and every dynamic feature should be a row. 2. Agree the support table in section 5 on the kickoff call, before design starts. 3. Put the content due dates in section 6 into the project plan and remind the client a week before each one. 4. Keep the post-launch fix window short and specific, then offer a maintenance SOW for everything after it. 5. Log every change in section 10 the day it is agreed. Template provided by Colo (trycolo.co). Not legal advice — review with a qualified professional in your jurisdiction.