Scope of work

Where a project brief explains the goal, the scope of work is the operational detail both parties can point to: twelve page templates, one contact form connected to the client's email, two rounds of design revisions, training session included, hosting excluded. It is often attached to a contract or statement of work.

The exclusions matter as much as the inclusions. Most disputes start with something each side assumed the other was handling, such as copywriting, photography, translations or content entry.

How it works

A scope is usually drafted by the supplier after a discovery phase and reviewed line by line with the client. It breaks the project into deliverables and milestones, states who provides what (text, images, logins), defines how many revision rounds are included and describes what "done" means for each item.

Changes after signing go through a change request: the new item is described, priced and scheduled, and both sides approve it before work starts. That process is what keeps a scope meaningful.

Acceptance criteria turn each item into something testable. "Contact form" becomes "contact form with name, email, phone and message fields, spam protection, sends to two addresses, shows a confirmation message". At the end of each milestone the client checks the delivered work against those criteria, and anything missing is fixed before the next payment is due. Scopes come in two broad shapes. A fixed-scope agreement lists deliverables and a fixed price, which suits work that is well understood, such as a brochure site. A time-and-materials agreement sets an hourly or daily rate and a budget cap, with the scope described as priorities rather than promises, which suits work where requirements will change. Many projects combine the two: a fixed price for the agreed core and a rate for anything added later, with that rate written into the document from the start.

Example

A travel agency's scope lists: homepage, about, contact, a destinations section built in the CMS so staff can add trips, an enquiry form per trip, migration of 40 existing trip pages, basic on-page SEO, two revision rounds on design and one on build, and a one-hour training call. It excludes new photography, translation and ongoing maintenance, which are quoted separately.

Two weeks after launch the agency's manager asks for a currency switcher on trip pages. The developer checks the scope, sees it is not listed, and sends a short change request with an estimate. The manager decides it can wait until the next season, and nobody argues about whether it was included.

Why it matters for your business

A precise scope is what makes a fixed price fair. It lets you compare quotes on the same basis, know what you are paying for and avoid surprise invoices. It also protects the supplier from unlimited requests. The cost is time upfront and some loss of flexibility; if the project is genuinely exploratory, a time-based arrangement with a looser scope and regular check-ins can serve you better. Before signing, read each line and ask, "How would I check this was delivered?" Any line you cannot answer needs rewriting.

Common mistakes

• Writing vague items such as "website design" with no number of pages, templates or revisions.
• Leaving content responsibility undefined, so the project stalls waiting for text nobody agreed to write.
• Accepting extra work informally without a change request, which leads to scope creep and arguments about payment.
• Forgetting post-launch items such as hosting, backups and maintenance, which then appear as unexpected costs.

Questions people ask

Is a scope of work legally binding?

It is binding when it forms part of a signed contract or is referenced by one. On its own, an unsigned scope is a description of intent. Have a contract that refers to the scope so both sides know the deliverables are enforceable. This is general information, not legal advice.

What happens if I want something outside the scope?

You raise a change request. The supplier estimates the extra time and cost, and you decide whether to add it, swap it for something already in scope or leave it for a later phase. Nothing should start until both sides agree.

How detailed should a scope of work be?

Detailed enough that someone outside the project could check whether each item was delivered. Number of pages, features, revision rounds, integrations, who supplies content and what is excluded should all be stated. Anything ambiguous will eventually be argued about.