Scope of Work

A scope of work is a written agreement between an agency and a client that spells out exactly what will be delivered, what is excluded, and how both parties will know the work is complete. It is not a legal contract. It is not a timeline. It is not a proposal. It is the reference document you point to when someone says "I thought that was included."

Most agencies skip writing a proper SOW because the project feels straightforward at kickoff. The client described what they want, the team understood it, and everyone is aligned. Three weeks later the client asks for a feature that was never discussed, the team has no written record of what was agreed, and the project absorbs work that was never scoped or priced.

The cost of skipping a SOW is rarely visible at first. It shows up as extra rounds of revisions that no one budgeted for, late-stage feature requests that feel too small to push back on, and a final invoice that does not reflect the actual work delivered. A signed SOW makes the invisible visible: here is what you are paying for, here is what you are not, and here is how we handle anything new.

Every SOW needs the same eight elements. Some agencies collapse a few of these into other documents, but each one must exist somewhere in writing before work starts. If a section is missing, that is where your next dispute will come from.

A SOW that lives in a folder and never gets referenced is just paperwork. The value of the document comes from using it during the project, not from having written it at kickoff.

When a client asks for something that falls outside the agreed scope, the response should be immediate, calm, and specific. The exact phrase: "That falls outside the current scope. Let me send you a change order for that." No apology. No negotiation on the call. The SOW is the shared reference point, and the change order is the process for adjusting it.

The two terms overlap and many agencies use them interchangeably. In practice, a scope of work focuses narrowly on deliverables and boundaries: what is in, what is out, and what "done" looks like. A statement of work is typically broader, covering timelines, payment terms, team responsibilities, and communication protocols alongside the deliverables.

If your client contract already covers timelines and payment, a focused scope of work is usually sufficient. If you are working with a larger organisation that requires a single comprehensive document, a statement of work may be more appropriate. The content matters more than the label. Whatever you call it, the deliverables, exclusions, and revision limits need to be in writing.

Even the best SOW cannot predict every client request. The goal is not to prevent all changes; it is to give you a process for handling them without losing money or goodwill.

When a client asks for work that is not in the SOW, issue a change order. The change order documents the new work, states the cost, describes the timeline impact, and requires written approval before you begin. No verbal agreements. No "we will figure out the cost later." The change order protects both parties: the client knows the price before committing, and the agency gets paid for every hour worked.

Agencies that treat scope boundaries as negotiable lose money on every project. Agencies that treat change orders as routine (not confrontational) build client relationships where both sides understand the rules. Your delivery process is only as strong as the SOW and change order process behind it.