The statement of work is the contract

There is a standard shape to a services engagement: a master agreement carrying the legal terms, and underneath it a numbered statement of work describing the actual job. The master agreement gets reviewed by counsel on both sides and negotiated for weeks. The statement of work gets drafted by the vendor, skimmed by a project manager, and signed.

That allocation of attention is exactly backwards. Courts have been consistent about this: a contractor is responsible for delivering what the statement of work expressly identifies, and nothing else. If a deliverable is not named in it, it is not owed. Every warranty, indemnity and liability cap in the master agreement is a remedy for failing to deliver something. The statement of work is the document that says what that something is.

Public-sector buyers have this codified. The Federal Acquisition Regulation puts performance-oriented documents second only to those mandated by law in its order of precedence, requires needs to be stated as functions to be performed or performance required, and warns against dictating detailed design solutions prematurely. A commercial statement of work that cannot say what is performed and how performance is measured is behind a standard the government has held itself to for decades.

Passive voice is a liability¶

“The router will be configured.” “The integration will be tested.” “Data will be migrated.” Read those again and ask who is doing it. Passive voice omits the actor, which is a grammatical curiosity in an essay and an unallocated obligation in a contract. Disputes have turned on exactly this.

Write it in the active voice with a named party every time: “Vendor will configure the router.” “Vendor will complete the integration; Customer will test it against the criteria in section 4.” It reads like a downgrade in prose style. It is an upgrade in enforceability.

Read the assumptions section as a price list¶

Most vendor statements of work carry a list of assumptions and contingencies. They look like housekeeping. They are the most commercially significant paragraphs in the document, because each one is simultaneously an excuse for missing a date and a trigger for additional fees.

“We assume the customer will provide test environments and development licences” is not an assumption. It is a requirement, and it belongs in the document as one: what exactly is required, who provides it, by when, and what happens if it is late. Rewriting assumptions as dated obligations on both sides costs an hour and removes most of the arguments you would otherwise have in month four.

Acceptance, or the absence of it¶

Acceptance testing is the single most valuable protection in a services engagement and the one most often missing. Two patterns to watch for. The first is deemed acceptance: language saying a deliverable is accepted if you do not reject it within some short window, which converts your own busy fortnight into a waiver. The second is an unbounded correction period, where the vendor is obliged to fix nonconformities but never obliged to fix them by any particular date.

• Acceptance criteria stated objectively, in the statement of work, before work begins. “To the customer’s reasonable satisfaction” is a criterion that can only be resolved by litigation.
• A defined number of correction cycles and a hard limit on how long each one may take.
• Rework to meet the agreed criteria at the vendor’s cost, always.
• A stated remedy if a deliverable is never accepted: terminate as to that deliverable, refund the fees paid for it.
• Staged acceptance on anything long: installation, integration, user acceptance, then final.

The mechanism that makes all of this real is a holdback. A percentage of the fee for each phase, released on acceptance of that phase. It is not a trust exercise; it is the thing that keeps the last ten percent of the work, which is where the defects live, from becoming somebody else’s problem.

Payment against milestones, not against Tuesdays¶

Fees tied purely to elapsed time reward elapsed time. Tie them to objective milestones and accepted deliverables instead. Where a monthly cadence genuinely is the right structure, as with a dedicated team, hold back a slice of each invoice against acceptance at the phase boundary.

The related question is fixed fee versus time and materials. Time and materials puts the entire budget risk on you, which is sometimes correct and often just a symptom of a project nobody scoped. The honest route out is a short, paid scoping engagement: give the vendor enough access to understand your environment, then convert to a fixed price. A vendor who will not commit to a price after being paid to look is telling you something.

The rest of the checklist¶

• Named people on both teams, with roles, and a limit on replacing the key ones.
• Every date calculable from a defined starting event, not from “project commencement”.
• A change process: priced, written, signed, before the work starts.
• Reporting cadence and format, agreed rather than assumed.
• An escalation path with names and timeframes, written while everyone is still friendly.
• A risk register with owners and mitigations, not a paragraph of disclaimers.
• No legal terms in the statement of work. Ownership, warranty, indemnity and liability belong in the agreement and nowhere else.

Why a vendor would want this¶

It looks adversarial written down, and it isn’t. A vague statement of work is not an advantage to the party doing the work; it is a guarantee of an argument later, usually in the week the client had planned to go live. The specificity that protects you from paying for something you did not want is the same specificity that protects us from building something nobody asked for.

This is most of what our discovery phase produces, and it is deliberately the point at which our own leverage is lowest. You get an architecture, a sequenced plan, an estimate range with its assumptions exposed, and a statement of work specific enough to hand to a competitor. Some clients do exactly that. It is a fair outcome and we price for it.