Scope of work: [Project name]

How to use this template

Write this before the project starts and attach it to your contract or proposal: the scope says what you will deliver, the contract says what it costs and how it is paid.

Give each deliverable a format, a size and a date someone else could check. Under Out of scope, list whatever a reasonable client might assume is included, and the work that comes after delivery.

Keep it up to date: log every approved change at the end and raise the version number, so everyone works from the same copy.

Delete this box, the example and the checklist before you send it.

This is a template, not legal advice. Laws differ by country and state; for large sums or valuable rights, have a lawyer where you live review it before anyone signs.

Client

Client contact

Prepared by

Date

Version

1.0

Start

Final delivery

Part of

The contract or proposal that sets the fees, and its date

Objective

What the client needs, what this work will produce, and who will use it.

Deliverables

#

Deliverable

Specification

Due

D1

D2

D3

See an example

Objective: New copy for a family-run bakery's website, to bring in wholesale orders from cafés. The readers are café owners comparing suppliers.

D1 Homepage: 400–600 words with a headline, three short sections and a call to action, as a Google Doc.
D2 Wholesale page: 500–700 words with the order process and delivery area, plus a meta title and description.
D3 About page: 500–700 words, built from one 45-minute interview with the owners.

Out of scope: photography, page design, uploading pages to the website, and blog posts.
Assumptions: prices and the delivery area stay as they are until launch.

In scope

  1. Discovery:

  2. Research:

  3. Drafting:

  4. Revisions: [2] rounds per deliverable. A round is one consolidated set of comments from the approver.

  5. Handoff: final files as [format], sent to [name].

Out of scope

Out-of-scope work can be added through the change process below.

Client responsibilities and assumptions

  • Materials: The client provides [materials] by [date].

  • Approver: [Name] approves the work. Comments from anyone else reach [your name] through them, in one set per round.

  • Comments: The client returns comments within [5] business days of each delivery. If comments or materials arrive late, later dates move by the same number of business days.

  • Assumptions:

Acceptance

[Name] reviews each deliverable against its specification above and accepts it in writing. Comments in a revision round cover the work in this scope. New requests go through the change process.

A deliverable with no comments after [5] business days counts as accepted. Optional; delete if not agreed.

Changes

Either side can ask for a change in writing. [Your name] replies within [3] business days with its effect on deliverables, dates and cost. Nothing changes until [name] approves the change in writing. Approved changes are recorded in the change log below and become part of this scope.

Approval

Approval is a signature below or a written reply, such as an email, that names this version.

Client

Prepared by

Signature

Name

Title

Date

Change log

#

Change

Effect on dates and cost

Approved by, date

1

2

Before you send

  • Every empty field and bracket is filled in, the grey notes replaced or deleted, and the blue colour removed

  • Every deliverable has a format, a size and a due date

  • Out of scope names the things this client is most likely to assume are included

  • One approver is named, and the client has agreed to the comment window

  • The contract or proposal named in Part of exists and sets the fees