Skip to content

Scope of work template

A scope of work is not a list of what you will do. It is a list of what you will do, what you will not do, and how both sides know when it is finished. The exclusions section is the one that saves the project.

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

Out of scope is the most valuable section

Everyone writes the deliverables list. Almost nobody writes the exclusions, which is why scope creep feels like a disagreement rather than a change. Write down the five things a reasonable client might assume are included and are not — copywriting, photography, hosting, training, ongoing maintenance — and name them. It is not defensive; it is the fastest way to find out what the client actually expected before you have quoted the wrong number.

Acceptance criteria turn opinions into tests

“Client is happy with the design” is not acceptance. “Client confirms in writing within 5 business days that the delivered files match the approved direction and specification” is. Give a review window and say what happens when it lapses: deemed accepted after [5] business days of silence. Without that, a project can stay 95% finished forever while an approver is on leave.

Revisions need a definition and a number

Two rounds is a reasonable default for most creative work. Define a round as one consolidated set of feedback from the client, collected from every reviewer, delivered by an agreed date. Then say what a third round costs. The point is not to be rigid — it is that everyone knows the meter exists, so extra work becomes a decision instead of an assumption.

List the client's dependencies as firmly as your own

Most late projects are late because the freelancer was waiting: for brand assets, for CMS access, for one person to reply. Put those dependencies in the scope with owners and dates, and say that the timeline moves day-for-day when they slip. It reads as professional planning rather than blame-shifting, and it makes the eventual conversation short.

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.

Scope of work template

SCOPE OF WORK

Project: [Project name]
Client: [Client legal entity name]
Supplier: [Your name or studio name]
Prepared: [2026-01-02]  ·  Version: [1.0]
Valid for acceptance until: [2026-01-16]

1. OBJECTIVE
[Client] needs [one or two sentences describing the business outcome in
the client's own words — e.g. "a marketing site that explains the new
product line and lets the sales team publish case studies without a
developer"]. This scope covers the work required to deliver that, at the
fee and on the timeline set out below.

2. DELIVERABLES
2.1 [Deliverable one — e.g. Information architecture: a sitemap covering
    up to 14 pages, plus page-level content outlines for the 6 core
    pages. Delivered as a shared document.]
2.2 [Deliverable two — e.g. Visual design: desktop and mobile designs
    for 6 unique page templates, delivered as a Figma file with a
    component library and a one-page style summary.]
2.3 [Deliverable three — e.g. Build: the 6 templates implemented,
    responsive at 3 breakpoints, tested on the browsers listed in 6.2,
    deployed to staging and then to production.]
2.4 [Deliverable four — e.g. Handover: a 60-minute recorded walkthrough
    and a 4-page written guide for the client's editors.]

3. NOT INCLUDED IN THIS SCOPE
The following are deliberately excluded. Any of them can be added by
change order (section 8) at the rates in section 7.
3.1 [Copywriting. Final copy is supplied by [Client] by [date].]
3.2 [Photography, illustration, and video production.]
3.3 [Content entry beyond the [6] example pages built during the project.]
3.4 [Hosting, domains, third-party subscriptions, and their renewals.]
3.5 [Ongoing maintenance, updates, and support after the warranty period
    in section 9.]
3.6 [Integrations with [systems not named in 2.x], migrations of legacy
    data, and accessibility remediation of content supplied by [Client].]
3.7 [Search rankings, traffic, conversion, or any other outcome that
    depends on factors outside the delivered work.]

4. REVISIONS
4.1 [Two] rounds of revisions are included for each deliverable in
    section 2.
4.2 A round means one consolidated set of written feedback from
    [Client], gathering the comments of every reviewer, returned within
    [5] business days of delivery.
4.3 Feedback that arrives after a round has been actioned, or that
    reverses a decision already approved, begins the next round.
4.4 Additional rounds are billed at $[350.00] each, quoted and approved
    in writing before the work starts.
4.5 A change of direction — new objective, new audience, a materially
    different concept after approval — is not a revision. It is a change
    order under section 8.

5. ACCEPTANCE
5.1 Each deliverable is submitted for review with a written note of what
    is being submitted and against which criteria.
5.2 A deliverable is accepted when [Client] confirms in writing that it
    matches this scope, or when [5] business days pass without written
    notice of a specific, scope-based defect.
5.3 Rejection must identify the specific requirement in section 2 that
    has not been met. Preference-based comments are handled as revisions
    under section 4.
5.4 Acceptance of a deliverable releases the corresponding payment in
    section 7 and closes that deliverable to further no-charge changes.

6. ASSUMPTIONS AND CLIENT RESPONSIBILITIES
6.1 [Client] names one approver, [name], who consolidates feedback and
    can sign off on behalf of the business.
6.2 [Supported browsers and devices: the current and previous major
    versions of Chrome, Safari, Firefox, and Edge, on desktop and iOS
    and Android phones.]
6.3 [Client] provides by [date]: brand assets and fonts (with licences),
    final copy, access to [systems], and any required approvals.
6.4 If a [Client] dependency is late, the schedule in section 9 moves by
    at least the length of the delay. Where a delay exceeds [10]
    business days, re-booking time may attract the rates in section 7.
6.5 Work is performed remotely during [Mon–Fri, 9:00–17:00, timezone].

7. FEES AND PAYMENT SCHEDULE
7.1 Total fee: $[15,000.00], fixed for the scope described above.
7.2 Schedule:
    · $[5,000.00] deposit, due before work starts. Non-refundable.
    · $[5,000.00] on acceptance of [deliverable 2.2].
    · $[5,000.00] on acceptance of [deliverable 2.4].
7.3 Hourly rate for approved additional work: $[125.00].
7.4 Payment terms: Net [14] from invoice date. Overdue amounts accrue
    interest at [1.5]% per month or the maximum permitted by law in
    [jurisdiction], whichever is lower.
7.5 Expenses over $[100.00] are approved in writing in advance and
    billed at cost with receipts.

8. CHANGES TO THIS SCOPE
8.1 Either party can propose a change at any time.
8.2 [Supplier] responds with a written change order stating what changes,
    the effect on the fee, and the effect on the dates.
8.3 No work on a change begins until the change order is approved in
    writing by [Client]'s named approver.
8.4 Nothing in this section obliges either party to accept a change.

9. TIMELINE
    Kick-off                    [2026-01-12]
    [Deliverable 2.1] delivered [2026-01-23]
    [Deliverable 2.2] delivered [2026-02-13]
    [Deliverable 2.3] delivered [2026-03-06]
    Launch and handover         [2026-03-13]
    Warranty period ends        [2026-04-12] — [30] days after launch,
    covering defects where the delivered work does not do what this
    scope says it does.

10. INTELLECTUAL PROPERTY
Ownership of the final delivered work passes to [Client] on payment in
full. Concepts not selected, and [Supplier]'s pre-existing tools,
templates, and know-how, remain [Supplier]'s property. Third-party
assets stay under their own licences.

11. ACCEPTANCE OF THIS SCOPE
Signing below approves the deliverables, exclusions, fee, and schedule
above, and authorises work to begin.

[Client]                          [Supplier]
Name: ______________________      Name: ______________________
Title: _____________________      Title: _____________________
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