Website Redesign Scope: What to Include

Defining the website redesign scope precisely is the most commercially significant task in any redesign project.

The most common source of budget overruns and client-agency disputes is not poor design or slow development, it is a scope document with gaps that both parties interpreted differently. That gap is entirely preventable.

Research shows that 70% of scope disputes in web development projects involve items that were never explicitly addressed as in-scope or out-of-scope.

The solution is not a longer scope document, it is a more precise one. Explicit inclusions and equally explicit exclusions, documented before the project begins, protect both parties from disputes that are expensive to resolve mid-project.

Key Takeaways

• Both inclusions and exclusions must be documented: Missing either creates assumptions that become disputes at the worst possible moment.
• Scope is more than a page count: Integration complexity, content workstream, custom functionality, and post-launch services are all scope dimensions that "20 pages" does not capture.
• Out-of-scope items carry commercial weight: Explicitly excluding maintenance, extra pages, and third-party tool costs prevents unexpected budget expectations post-launch.
• Client deliverables are scope items: Content delivery, asset provision, and feedback turnaround are client responsibilities that belong in scope, not left to assumption.
• Scope should be agreed, not imposed: A scope built collaboratively during discovery produces fewer surprises than one presented as final without the client's input.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

The Core Inclusions: What Scope Must Cover

Every professionally managed redesign scope includes the complete list of agency deliverables across all phases, not just the design and development work. Requirements behind scope decisions should be fully documented before any scope statement is written.

Discovery and Strategy Work

Project brief development, analytics audit, competitor review, stakeholder interviews, and audience research are time-intensive scope items that must be named explicitly.

• Project brief: The discovery brief documents business goals, audience requirements, competitive context, success criteria, and project scope. It takes time to produce, that time is in scope.
• Analytics audit: Review of GA4, Search Console, and any available CRM data to understand current performance and identify requirements. This is scoped work, not a quick glance.
• Stakeholder interviews: Structured sessions with sales, marketing, and leadership require facilitation, note-taking, and synthesis, all billed time.
• Deliverables list: At the end of discovery, specify what deliverables are produced: brief, sitemap, requirements document, personas, or technical specification, and name them in scope.

UX, Information Architecture, and Wireframes

Sitemap development, navigation architecture, and wireframes for each unique page template are distinct scope items with distinct production times.

• Sitemap: A full page hierarchy with navigation labels and URL structure. The time to produce this varies with the number of pages and the complexity of the navigation structure.
• Wireframe scope by template: Scope should specify the number of unique page templates to be wireframed, not the total page count. Twenty pages built from five templates requires significantly less wireframe work than twenty unique layouts.
• Wireframe revision rounds: Specify the number of included revision rounds, typically one to two, and what constitutes a revision versus a direction change.
• Mobile wireframes: Specify whether mobile wireframes are included in scope. Mobile UX decisions are not implied by desktop wireframes.

Visual Design by Template

High-fidelity desktop and mobile mockups for each agreed template type are the core visual design deliverable.

• Template count: The scope specifies the number of design templates produced, homepage, service page, case study, contact, not the total number of pages the templates will produce.
• Design system: Color palette, typography, spacing, and component library development is a distinct scope item. It is not assumed to be included unless stated.
• Desktop and mobile mockups: Specify whether desktop-only mockups or both desktop and mobile are included in scope. These are different amounts of work.
• Revision rounds: Specify the number of included design revision rounds per template, typically two. Unlimited revisions are not in scope and should never be implied.

Development, Content, and Technical Scope

Turning scope into the SOW happens when the scope document is converted into a detailed scope of work with specific deliverables and effort estimates.

Development Scope by Feature Type

Each development deliverable must be named individually to prevent the "I thought that was included" dispute.

• Page template development: Building each approved template to the design specification, named by template type, responsive across agreed breakpoints.
• CMS configuration: Custom content types, custom fields, editorial workflows, user roles, and media library setup. This is often several days of work not reflected in a page-count scope.
• Integrations: Each integration is named, CRM system name, email platform name, analytics platform, ad pixels, with the integration type specified. Unnamed integrations are not in scope.
• Redirect map implementation: Every URL change is documented and implemented as a 301 redirect. This is a scope item, not an assumed extra, and should be named explicitly.

Content Scope: Who Does What

Content scope ambiguity is the most common source of quote disputes and the most preventable.

• Agency-written content: If the agency is writing any copy, specify exactly what, which pages, word count, number of revisions, and language. Agency copywriting is priced separately from development.
• Client-supplied content: If content is client-supplied, specify the delivery format (Word documents, Google Docs), the delivery date, and what happens to the timeline if content is late.
• Content migration: Moving existing content from the old site to the new CMS is a scope item. The effort depends on volume, format, and the structural difference between old and new content models.
• SEO copywriting: Keyword-optimized copy that meets specific SEO requirements is a different scope item from general copywriting. If this is required, it must be named and scoped separately.

Platform and Hosting Scope

Platform selection, hosting setup, and domain management are each scope items that clients frequently assume are automatically included.

• Platform selection: Whether the platform is prescribed or recommended, the specific platform chosen is named in scope, because different platforms have different build costs.
• Hosting setup: Setting up the hosting environment, configuring server settings, and testing hosting performance is scoped work. Migrating from an existing host to a new one is also a scope item.
• SSL configuration: SSL certificate installation and HTTPS redirect configuration, often assumed to be automatic, but a scope item that requires time and testing.
• DNS management: DNS record updates at launch, including propagation monitoring and post-launch verification, are scope items that should be attributed to either the agency or the client.

Post-Launch Scope Items

Post-launch scope items are where the largest gap typically exists between what clients expect and what the agency's scope actually covers.

Redirect Map and SEO Continuity

Every URL that changes must have a documented 301 redirect, implemented before launch. Deliverables within scope for an SEO-conscious redesign should include the redirect map as a named item.

• Redirect map document: A spreadsheet mapping every changed URL from its old address to its new destination. This is produced in the SEO audit phase and implemented in the build phase.
• Redirect implementation: Loading the redirect map into the platform's redirect manager and verifying each redirect before launch. Named in scope, not assumed.
• Redirect testing: Post-implementation testing of every redirect using a bulk redirect checker. A redirect that returns a 302 instead of a 301, or lands on the wrong page, requires correction.
• Not in scope if not named: If redirect map implementation is not in scope, state it explicitly, so the client knows they need to arrange it independently.

Analytics Configuration and Verification

GA4 setup, conversion goal configuration, and Search Console property verification are post-launch scope items that are often assumed by clients but not included by agencies.

• GA4 installation: Installing the GA4 tag on every page via GTM or direct implementation. Specify whether this is agency-handled or client-handled.
• Conversion goal configuration: Setting up conversion events for form submissions, phone calls, and any e-commerce transactions in GA4. This is separate from installation, it is configuration work.
• Search Console verification: Verifying the new site property in GSC and submitting the sitemap. Takes minutes, but if not named in scope, may not happen on launch day.
• Tracking verification: Testing every conversion event end-to-end, from submission or click through to confirmed tracking in GA4, before the launch gate is signed.

Post-Launch Monitoring and Performance Review

30-day monitoring and a 90-day performance review are post-launch scope items in a complete engagement.

• 30-day monitoring: Active monitoring of Google Search Console, GA4 traffic patterns, and conversion rates for the first month after launch. Specify what the agency monitors and what they are looking for.
• Bug fix period: A defined post-launch bug fix window, typically 14 to 30 days, during which bugs identified after launch are fixed at no additional charge. Specify what constitutes a bug versus a change request.
• 90-day performance review: Formal comparison of post-launch performance against pre-launch baselines for traffic, conversion rate, and rankings. Named in scope with a specific deliverable, written report or review meeting.
• Not in scope if not named: If post-launch monitoring is not in scope, state this clearly. The client may need to arrange it separately or understand the implications of not having it.

Explicit Exclusions: What Must Be Stated as Out of Scope

How to scope a redesign properly requires as much attention to the exclusions as to the inclusions. Every item left ambiguous becomes a potential dispute.

Ongoing Maintenance and Support

Unless specifically scoped, ongoing maintenance after launch is not included in the redesign engagement.

• CMS updates: Platform and plugin updates after launch require a separate maintenance engagement. The redesign scope ends at launch plus the defined bug fix period.
• Content updates: Ongoing content changes, new page additions, and blog post publishing are not included in the redesign scope unless an ongoing retainer is explicitly agreed.
• Security monitoring: Active security monitoring, firewall management, and vulnerability patching are post-launch services, not redesign deliverables.
• Explicit statement: The exclusion should be worded clearly: "Ongoing website maintenance following the post-launch bug fix period is not included in this engagement."

Additional Pages Beyond the Agreed Count

Pages added after scope sign-off are out of scope and subject to a change order.

• Agreed page count: Specify the exact number of pages included in scope. Twenty-two pages is not twenty pages, even if the client considers the extras "small."
• Template additions: Adding a new page template after design sign-off requires design work, development work, and testing, all out of scope.
• Landing page additions: Marketing landing pages requested during the project are additional scope items, not inclusions within the agreed campaign pages.
• Explicit statement: "Any pages, templates, or content types not listed in this scope document require a written change order before work begins."

Third-Party Tool Licenses and Subscription Costs

The costs of any SaaS tools, plugins, or platform subscriptions required by the redesign are the client's responsibility unless explicitly included in scope.

• Platform subscription costs: Webflow, Shopify, or WordPress premium plugin subscription costs are client expenses, not agency scope items, even if the agency recommended the platform.
• CRM license costs: If the redesign integrates with a CRM, the CRM subscription cost is the client's responsibility regardless of whether the agency set it up.
• Hosting costs: Monthly or annual hosting fees are client expenses. The agency may provision the hosting as a scope item, but the ongoing cost is the client's.
• Explicit statement: "Third-party software licenses, SaaS subscription costs, and hosting fees are the client's responsibility and are not included in this engagement."

What Scope Means for the Estimate

How scope affects cost is a direct mathematical relationship. Every scope addition adds billable hours; every scope reduction removes them.

How Each Scope Addition Affects the Estimate

Each additional template, integration, content page, or custom feature adds a quantifiable number of hours to the project estimate.

• Template additions: Each new unique page template adds design time, development time, and QA time. These hours are not interchangeable across templates.
• Integration additions: Each additional third-party integration adds scoping, development, testing, and debugging time, typically five to fifteen hours per integration depending on API complexity.
• Custom functionality: Features not available as platform-native capabilities, custom calculators, interactive tools, complex filtering, add significantly more hours than standard implementations.
• Content additions: Each additional page of agency-written content adds copywriting, editing, and SEO optimization time that compounds across a large content scope.

The Trade-Off Between Scope and Budget

When budget is fixed, scope must be adjusted. The professional approach is to prioritize scope items by business impact.

• Priority classification: Scope items classified as must-have are non-negotiable. Should-have and nice-to-have items are the first to be deferred when budget constraints require reduction.
• Deferral to Phase Two: Items removed from Phase One scope should be formally documented as Phase Two scope, not abandoned. This preserves the budget planning for future investment.
• Trade-off transparency: When scope is reduced to fit budget, document exactly what has been removed and what the business implication of each removal is.
• Impact documentation: "Removing the blog template from Phase One scope means the content marketing program cannot launch until Phase Two is complete" is a trade-off that should be explicit, not discovered post-launch.

Using Scope to Build a Phased Budget Plan

A phased scope approach allows budget-constrained projects to launch with meaningful impact while planning future investment. Scope integration in project plan is the operational follow-through of the phased scope strategy.

• Phase One scope: Core site with highest-priority pages, essential integrations, and the primary conversion architecture. Enough to launch with commercial impact.
• Phase Two scope: Additional templates, secondary integrations, content marketing infrastructure, advanced features, and optimization work that builds on the Phase One foundation.
• Phase Three planning: Long-term roadmap items, personalization, advanced analytics, e-commerce expansion, that require Phase One and Two data before they can be scoped accurately.
• Budget planning: Phased scope gives the client a predictable investment roadmap, not a single large budget commitment with an unknown return.

Scope in the Project Plan

Scope integration in project plan is the point at which the scope document becomes the operational baseline for the entire project.

The Scope Baseline and Change Management

The agreed scope document is the project plan's scope baseline. Every change is measured against it.

• Baseline establishment: On the day scope is signed, the scope document is frozen as v1.0. All subsequent scope management references v1.0 as the baseline.
• Change order requirement: Any addition to v1.0 scope requires a written change order with an impact assessment before work begins. No verbal agreements modify the baseline.
• Version control: Each approved change order updates the scope to v1.1, v1.2, and so on, with a change log documenting what changed and when.
• Dispute reference: When a scope dispute arises, the v1.0 baseline, plus any signed change orders, is the definitive reference document. No other document takes precedence.

Scope Review at Phase Gates

At each phase gate, the scope is reviewed against the baseline.

• Deliverable check: Are the phase deliverables consistent with what is documented in the scope baseline? Additions or reductions must be formally noted.
• In-progress scope assessment: Are any tasks currently in progress that were not in the original scope baseline? These need change order assessment before they continue.
• Accumulated scope review: Small scope additions can accumulate invisibly across phases. A phase gate scope review makes accumulated additions visible before they become significant.
• Client sign-off record: Phase gate sign-off should include confirmation that the client has reviewed scope against the baseline, not just that they approve the phase output.

Closing the Scope at Project End

Project closure compares delivered scope against the scope baseline. The scope document makes this comparison possible.

• Scope delivery audit: List every item in the baseline scope and confirm it was delivered. Items not delivered are formal deficiencies that require resolution.
• Out-of-scope delivery check: List every change order and confirm that all approved additions were delivered. Items added via change order but not delivered are also deficiencies.
• Billing reconciliation: Items delivered outside of scope that were not covered by a change order are a billing dispute waiting to happen. Scope closure identifies and resolves these.
• Closure documentation: A project closure document that confirms all scope items were delivered, all change orders were actioned, and all outstanding issues were resolved closes the engagement cleanly.

Conclusion

A complete scope document covers inclusions, exclusions, client responsibilities, and post-launch services explicitly. Every item left ambiguous is a potential dispute. The inclusions list defines what the project delivers; the exclusions list defines what it does not.

Both are equally important, and the time investment in writing both sections precisely is a fraction of the cost of resolving a single scope dispute mid-project.

Review any current or recent scope document against the inclusions and exclusions in this article.

Mark every gap, those gaps are where the next scope dispute will originate, and they are fixable before they become expensive.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Defines Scope Explicitly, So There Are No Surprises

LOW/CODE Agency produces a detailed scope document on every project: documented inclusions, documented exclusions, client responsibilities listed, and a scope baseline that governs the entire engagement from kickoff to project close.

We operate as a strategic product team, not a dev shop. Our scoping process is built to give you a reliable estimate, a predictable budget, and a project that delivers what was agreed.

• Collaborative scope development: Scope built through discovery workshops, not estimated from a brief, so the scope reflects your actual requirements, not our assumptions.
• Explicit inclusions list: Every deliverable named individually, templates, integrations, content types, post-launch items, with no ambiguous line items.
• Explicit exclusions list: Ongoing maintenance, additional pages, third-party licenses, and out-of-scope services documented clearly before the contract is signed.
• Client responsibilities documented: Content delivery dates, review windows, asset provision, and approval responsibilities are in the scope document, not left to assumption.
• Change management process: Scope additions follow a written change order process with impact assessment and written approval before any work begins.
• Phase-gate scope reviews: At each project milestone, deliverables are checked against the scope baseline, so accumulated scope drift is identified and addressed promptly.
• Scope closure audit: Project close includes a formal comparison of delivered scope against the baseline, ensuring every item is accounted for.

LOW/CODE Agency has delivered 450+ digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku.

Our clearly scoped redesign projects give clients the commercial confidence to commit to a project without fearing what they will find in the invoice.

Start with a scoping call