Scope of Work Template for Web Design Projects

You need a scope of work for a web design project and you're starting from scratch. Every project feels slightly different, so you end up rewriting the scope section every time — or worse, copying from a previous project and forgetting to update the details. Both approaches waste time and introduce errors.

Here's a template specifically for web design projects. The structure stays the same every time. You only customize the deliverables, exclusions, and timeline to match the specific project.

The Template

Project Overview

"This project involves the design and development of [project type: marketing website / e-commerce store / web application / landing page] for [Client Name]. The primary goal is [specific outcome: increase lead generation / improve mobile conversion / launch new product line / replace outdated site]. The project will be delivered as [deliverable format: live website on client hosting / staging site for client review / design files in Figma]."

Customize the bracketed sections for each project. Keep it to 2-3 sentences maximum.

Deliverables

This is the section that matters most. Use the checklist below as a starting point and remove what doesn't apply.

Design deliverables:

• Homepage design (desktop and mobile responsive layouts)
• [X] interior page templates (list them: About, Services, Contact, etc.)
• Navigation design (header and footer)
• Mobile responsive layouts for all pages
• Style guide (colors, typography, button styles, spacing rules)

Development deliverables:

• Functional build of all designed pages on [platform: custom code / WordPress / Webflow / etc.]
• Contact form with email notification to [specified address]
• CMS integration for [specify which content types: blog posts / team bios / portfolio items]
• Basic SEO setup (meta titles, descriptions, XML sitemap, robots.txt)
• SSL certificate installation and HTTPS configuration
• Cross-browser testing (Chrome, Safari, Firefox, Edge — current versions)
• Mobile testing (iOS Safari, Android Chrome)

Delivery deliverables:

• Staging site for client review before launch
• Production deployment to client hosting
• 30-minute walkthrough session on CMS usage
• Source files delivered to client upon final payment

Adjust the list for each project. The key is specificity — "5 interior page templates" not "website pages." Every line should be something both you and the client can point to and say "yes, this is done" or "no, this isn't done yet."

Exclusions

Include all of these unless they're actually part of your scope:

• Content creation: copywriting, photography, video production, illustration
• Ongoing maintenance, updates, or hosting management after launch
• Search engine optimization beyond basic technical setup
• Email marketing integration or setup
• Social media integration beyond linked icons
• Third-party costs: hosting fees, domain registration, premium theme or plugin licenses, stock photography
• Custom animation or motion design
• Accessibility audit or WCAG compliance testing (specify if you are including this)
• Training beyond the included walkthrough session
• Browser support for legacy browsers (IE11, older mobile browsers)

The exclusions list is your insurance policy. Every item here is something a client has at some point assumed was included. Write it out now so you don't argue about it later.

Acceptance Criteria

"Design deliverables are approved upon written client confirmation or after [5] business days without feedback following delivery. Development deliverables are approved upon client review of the staging site confirming functionality matches the approved design. Final launch approval requires written client sign-off."

Revisions

"This project includes [2] rounds of design revisions and [1] round of development revisions. A revision round is defined as a single consolidated set of feedback delivered at one time. Additional revision rounds are available at [$X]/hour."

Defining what constitutes a "round" prevents the situation where the client sends feedback in five separate emails over two weeks and claims it's all one round.

Change Orders

"Work outside this scope is handled through change orders. Each change order includes a description, timeline impact, and cost estimate. Work begins only after written client approval of the change order."

Timeline

| Phase | Duration | Deliverable | Client Input Needed | |-------|----------|-------------|-------------------| | Discovery + Wireframes | Week 1 | Wireframe layouts | Content and brand assets | | Design | Week 2-3 | Design comps | Feedback within 5 business days | | Development | Week 4-6 | Staging site | Review and testing | | Revisions | Week 7 | Revised staging | Final feedback | | Launch | Week 8 | Live site | Hosting credentials and DNS access |

Customize the durations for your project. Always include the "Client Input Needed" column — it sets the expectation that timelines depend on both parties.

How to Use This Template

Copy the entire structure. For each new project, customize: the project overview, the deliverables list (add or remove items), the exclusion list (remove items you're actually including), the timeline durations, and the pricing that maps to each phase.

The sections you rarely need to change: acceptance criteria, revisions policy, and change order process. These are your standard operating procedures and they should be consistent across projects.

For how this scope of work fits into a complete proposal, see the full proposal structure guide. For strategies on holding scope boundaries once the project is underway, read How to Prevent Scope Creep as a Freelance Developer.

If you want to skip assembling all these sections manually, Scope In Seconds generates the full proposal — scope, timeline, pricing, terms, and approval path — from your project notes in seconds.

FAQ

Q: Should I use this template for web application projects too? A: The structure works for web apps, but you'll need to add deliverables specific to application development: user authentication, database design, API integrations, admin panels, etc. The exclusions list will also differ. Adjust the template to match your actual deliverables.

Q: What if the client wants to negotiate the scope after I send it? A: That's normal and expected. Negotiating scope is much healthier than negotiating price. If they want to add items, show them the cost impact. If they want to remove items to reduce the price, help them identify what's least critical to their core goal.

Q: How often should I update this template? A: Review it after every 3-5 projects. You'll notice patterns — deliverables you always add, exclusions clients always ask about, timeline estimates that were consistently off. Update the template to reflect what you've learned.