What a statement of work adds to a services agreement

In one line. A statement of work (SOW) sets out one job: what is being done, by whom, by when and for what fee.

People usually meet the pair when a client sends two attachments for one project. The first is long and general, full of clauses about liability and confidentiality. The second is short and specific and reads like a plan. The deal is not written twice. It is written once, in two layers.

It depends on how it is written. Most SOWs sit under a services agreement, often called a master services agreement. The SOW names that agreement and date at the top and takes its standing terms from it. Read on its own it looks thin, because the missing parts live in the agreement above.

An SOW can also be written to stand alone, carrying its own terms. That is common for a single small job between two sides who do not expect a second one, and it is closer in shape to a consulting agreement.

The difference is not the title on the front. It is whether the document points at another one and takes its terms.

A useful test is to read the first paragraph. A dependent SOW usually says something like "This Statement of Work is made under the Services Agreement between the parties dated 3 March 2026", and then lists only the job. A standalone one has its own clauses on payment, ownership, liability and termination further down. If it has neither the reference nor those clauses, it is worth asking which terms are meant to apply.

The dividing line is usually the same, whoever drafts the pair.

In the statement of work:

• the description of the work and what counts as a deliverable
• dates or milestones
• who is doing it, including named people if that matters
• what the client supplies (content, access, approvals)
• the fee for this job and what triggers each invoice
• anything specific to this job, such as a named tool or platform

In the services agreement:

• confidentiality and intellectual property
• warranties, indemnities and the liability cap
• payment terms in general, such as days to pay
• termination and notice
• governing law

The standing terms are signed once. The SOW is written per job and expected to move.

Most agreements carry an order-of-precedence line. It usually says the services agreement wins, with a carve-out letting an SOW vary named terms if it says so expressly.

Example

If this Agreement and a Statement of Work conflict, this Agreement prevails, unless the Statement of Work expressly states that it overrides a named clause of this Agreement.

In Plain English: the master terms win, unless the SOW clearly says it is changing a specific clause. That carve-out is worth reading before signing the second document, because it decides how much an SOW can quietly change.

Scope moves, dates move, a deliverable is added. Depending on how the pair was drafted, the change is:

• a new SOW
• an amendment to the current SOW
• a change note the SOW itself provides for

In each case the change is usually written down and signed by both sides, rather than agreed in a message thread. A version of a document is a fixed thing, and a signature attaches to one version. The entire agreement clause is often why side conversations do not count.

Most often when a new job starts under an agreement that is already in place. Nothing about the relationship is being renegotiated, so only the SOW is signed, and it names the agreement it belongs to.

On Contracts.io, describe the job in a sentence and Lex drafts a statement of work that points at your services agreement. Share one link, and both sides agree and sign. It is free for the other side.