Scope of Work

What this document is

A scope of work is the part of a project agreement that does the detailed talking. While the main contract handles money, dates, and signatures, the scope of work lists every deliverable — pages, screens, photos, drawings, features — together with the things deliberately left out, the number of revision rounds, and how the client confirms each item is accepted. It usually attaches to a freelance service agreement or contract as a schedule both sides sign.

For anyone charging a fixed price, this document is where the money is defended. 'Website design' can mean five pages or fifty; 'photo coverage' can mean four hours or a full day with edits. Scope creep — the slow expansion of a project at the original price — thrives on that vagueness. A signed scope of work converts every 'could you also just…' into a visible change with a price tag.

When to use it

• You quoted a fixed price and the client's idea of the project is fuzzier than yours.
• A design, development, or construction project has enough moving parts that 'the work' needs its own page.
• Previous projects with this client suffered from endless small additions.
• The client's team has several people who each request changes — one signed list keeps them aligned.
• You are the client and want to know precisely what the quoted price includes before approving it.

When not to use it

• On its own with no contract around it — a scope of work defines the work but does not set payment terms, ownership, or cancellation. Pair it with a service agreement.
• For time-based engagements billed hourly or on retainer, where a description of the service areas in the consulting agreement does the job.
• For tiny one-off jobs where one plain sentence in a simple service contract covers the work.
• For public-sector or formal tenders that dictate their own scope format.

Information you will need

• The project name and the contract or quotation it attaches to
• Every deliverable, itemized — quantity, format, and size where relevant
• Explicit exclusions: the requests you can foresee but are not including
• Number of revision rounds per deliverable and what one round means
• Milestones or delivery order, if the work is staged
• What the client must provide — content, logins, access, approvals — and by when
• How acceptance works: who confirms, in what form, within how many days
• The rate or process for work outside the scope

Clauses included

How to sign it

Both parties sign the scope of work itself, even though it attaches to a signed contract — it is the page people actually argue about, so it deserves its own signatures and date. Merge it with the main agreement into a single PDF so neither page circulates alone.

When the scope changes mid-project — and on real projects it does — record the change in writing with its price and any new dates, signed or clearly confirmed by both sides. A trail of small signed changes is what keeps the final invoice unarguable.

Keep the signed scope next to the deliverables themselves. When the client questions an item, you want the list and the delivered files side by side.

Common mistakes

• Writing deliverables without quantities — 'social media graphics' instead of 'ten 1080x1080 graphics'.
• Leaving out the exclusions section entirely, because naming exclusions felt awkward during the sale.
• Allowing 'reasonable revisions', which every client reads as unlimited.
• No deadline on client feedback, so the project stalls and the final payment stalls with it.
• Accepting scope changes verbally in meetings and hoping to bill them later.
• Failing to tie milestone payments to specific scope items, leaving payment triggers vague.

Frequently asked questions