Skip to content

Web design scope of work

Website design scopes go wrong when “a website” means five templates to you and forty pages to the client. This one counts unique templates, names the breakpoints, and separates design from build in writing.

Free to copy and use. Nothing to download, no email required. Replace anything in [SQUARE BRACKETS] with your own details.

Count templates, never pages

A 60-page site might be six templates. A 6-page site might be six templates. Price the unique layouts, then say how many pages each template is expected to serve and what a new template costs. This is the single most useful sentence in a web design scope: it makes the estimate defensible and it makes “can we add a careers page” a two-minute answer instead of a renegotiation.

Say who is building it, before you design

If you are designing and someone else is building, the scope should name the developer, say what handover format they are getting, and state that you are not responsible for build fidelity. If nobody is named yet, say the design assumes a standard component-based build and that platform-specific constraints discovered later may require design changes, which are a change order. Designing in a vacuum and finding out in week eight that it is going into a rigid theme is a common and avoidable loss.

Design systems are scope, not a bonus

Components, states, tokens, and documentation take real time and are what makes the site maintainable. If they are included, list them as a deliverable with a component count. If they are not, exclude them explicitly — otherwise a client who has read one article about design systems will expect one.

The scope of work template

Copy the whole thing, or select the parts you need. The numbers and dates are examples — change them to yours before sending anything.

Web design scope of work

SCOPE OF WORK — WEBSITE DESIGN

Project: [Website design — [Client] marketing site]
Client: [Client legal entity name]
Designer: [Your name or studio name]
Prepared: [2026-01-02]  ·  Version: [1.0]
Valid for acceptance until: [2026-01-16]

1. OBJECTIVE
[Client] needs [e.g. "a marketing site that positions the new product
line clearly to procurement buyers and makes it obvious how to book a
demo"]. This scope covers design only, through to developer handover.

2. DELIVERABLES
2.1 Discovery
    · [1] kick-off workshop, [90] minutes, with [Client]'s named
      stakeholders.
    · Review of [existing analytics, current site, brand guidelines,
      and up to 5 competitor sites].
    · A [2-page] direction summary: audience, key messages, tone, and
      the design principles this project will be judged against.

2.2 Information architecture
    · Sitemap covering up to [14] pages.
    · Content outlines for the [6] core pages, showing section order and
      the purpose of each section.
    · [1] round of revisions on the IA before design begins.

2.3 Visual design
    · [6] unique page templates: [home, product, pricing, case study,
      about, contact].
    · Each template designed at [3] breakpoints: [desktop 1440px,
      tablet 768px, mobile 375px].
    · [2] design directions presented at the first template, [1] chosen
      and applied to the rest.

2.4 Design system
    · [24] components with their states (default, hover, focus,
      active, disabled, error where relevant).
    · Tokens for colour, type scale, spacing, radius, and shadow.
    · Accessibility notes: colour contrast checked to [WCAG 2.2 AA],
      focus states designed, and heading hierarchy specified per
      template.

2.5 Handover
    · A [Figma] file organised in pages, with components published to a
      shared library.
    · A [4-page] specification covering spacing rules, responsive
      behaviour, image treatments, and empty/error states.
    · [1] 60-minute walkthrough with [developer name / Client's build
      partner], recorded.

3. NOT INCLUDED IN THIS SCOPE
3.1 Front-end or back-end development, CMS configuration, QA, and
    deployment. This is a design engagement.
3.2 Copywriting. [Client] supplies final copy by [date]; design uses
    real copy where available and clearly marked placeholder text
    otherwise.
3.3 Photography, illustration, iconography beyond [an existing icon
    set], and video production.
3.4 Logo design, brand identity work, and changes to the existing brand.
3.5 Additional page templates beyond the [6] in 2.3. Extra templates are
    $[900.00] each by change order.
3.6 Email templates, ad creative, social assets, and print collateral.
3.7 SEO strategy, keyword research, and any commitment about rankings,
    traffic, or conversion rate.
3.8 Accessibility audit or remediation of the built site. Design is
    delivered to meet [WCAG 2.2 AA] for the states shown; whether the
    built site conforms depends on the build.

4. REVISIONS
4.1 [Two] rounds included per deliverable in section 2.
4.2 A round is one consolidated set of written feedback from [Client]'s
    named approver, gathering all reviewers, returned within [5]
    business days.
4.3 Additional rounds: $[450.00] each, approved in writing first.
4.4 Choosing a different design direction after 2.3 has been approved is
    a change order, not a revision.

5. ACCEPTANCE
5.1 A deliverable is accepted when [Client] confirms in writing, or
    after [5] business days without a written, scope-based objection.
5.2 Acceptance of the design direction at template [1] fixes the visual
    language for the remaining templates.
5.3 Rejection must point to a requirement in section 2 that has not been
    met.

6. ASSUMPTIONS
6.1 Named approver: [name], [title]. One voice, consolidating feedback.
6.2 Build partner: [developer or agency name, or "not yet appointed"].
    The design assumes a standard component-based build. If platform or
    theme constraints emerge after appointment and require rework, that
    is a change order.
6.3 [Client] supplies brand assets, licensed fonts, and image library by
    [date]. Fonts must be licensed for web use in [Client]'s name.
6.4 Delays in [Client] dependencies move the dates in section 8
    day-for-day.

7. FEES AND PAYMENT SCHEDULE
7.1 Total: $[12,000.00], fixed for the scope above.
7.2 · $[4,000.00] deposit, before work starts, non-refundable.
    · $[4,000.00] on acceptance of 2.3.
    · $[4,000.00] on acceptance of 2.5.
7.3 Hourly rate for approved extra work: $[125.00].
7.4 Net [14] from invoice date. Overdue amounts accrue interest at
    [1.5]% per month or the legal maximum in [jurisdiction] if lower.

8. TIMELINE
    Kick-off workshop           [2026-01-12]
    IA delivered                [2026-01-20]
    First template + directions [2026-02-03]
    All templates delivered     [2026-02-24]
    Design system + handover    [2026-03-06]

9. INTELLECTUAL PROPERTY
Copyright in the final approved designs passes to [Client] on payment in
full. Unselected directions, working files created along the way, and
[Designer]'s components, templates, and methods remain [Designer]'s
property. Fonts and stock assets remain under their own licences, held
in [Client]'s name.
[Designer] may show this work publicly after [Client]'s launch date.

10. ACCEPTANCE OF THIS SCOPE

[Client]                          [Designer]
Name: ______________________      Name: ______________________
Signature: _________________      Signature: _________________
Date: ______________________      Date: ______________________

This is a practical starting point rather than legal advice. Terms like late fees and payment periods are regulated differently depending on where you and your client are, so check anything you plan to enforce.

Turn it into a scope your client approves in PaloWorks

Enter the deliverables, revision rounds, timeline, and price on the project's scope. Your client approves it on a link, every round of feedback is logged against the rounds you agreed, and work past them becomes a change order. It does not import this page's text: copy the parts you want into the scope.

Free for one client and three active projects. Pro is $19/mo for unlimited clients and projects.

Use this with