Statements of Work: Writing One That Holds

A statement of work is the document that defines one specific project: what will be delivered, when, for how much, and how everyone will know it is done. It must state deliverables and acceptance criteria, the schedule and dependencies, the price and payment triggers, the assumptions behind the estimate, and the process for changing any of it. It is normally signed under a master agreement that supplies the legal terms.

The parts of a usable SOW

• Background and objective — one short paragraph on what the project is for. It helps a reader interpret everything below it.
• Deliverables — a numbered list, each one a thing that can be handed over and checked.
• Acceptance criteria — how each deliverable is judged, who judges it, and within how many days.
• Out of scope — the explicit exclusions. This is the highest-value section in the document and the most often missing.
• Schedule — milestones with dates, and what those dates depend on.
• Client responsibilities — access, data, approvals, content, people, environments.
• Assumptions — the facts the price and schedule rest on, and what happens if one turns out to be wrong.
• Price and payment — fixed fee, time and materials, or milestone-based, and what triggers each invoice.
• Change control — how a change is requested, priced and approved, and by whom.
• Key people, reporting cadence, and where the work happens.

What to look for

• Can you point at every deliverable and say how it will be judged? If not, the acceptance argument is already scheduled.
• Is there an acceptance window with a default — silence after N days means accepted? Otherwise a busy client can stall payment indefinitely without meaning to.
• Is 'out of scope' populated with real exclusions, or blank?
• Do the dates depend on client actions, and is the consequence of a late client action stated?
• For a fixed fee: how many revision rounds are included?
• For time and materials: is there an estimate, a not-to-exceed figure, and a duty to warn before passing it?
• Does the SOW say which document governs if it conflicts with the master agreement?
• Are the assumptions written down, or only in the estimator's head?

The clauses that cause disputes

Acceptance

Acceptance is the moment work becomes payable, so the clause that defines it is the clause that decides cash flow. Vague acceptance — the client approves when satisfied — hands one side an unlimited clock. Workable acceptance names the criteria, gives a review window, requires objections to be specific and in writing, and treats silence as acceptance. It also says what happens on rejection: a fix-and-resubmit cycle, with a limit on how many rounds are included.

Assumptions and dependencies

Every estimate rests on assumptions — the data will be clean, the environment will be available in week two, one reviewer will consolidate the feedback. Written down, an assumption that fails becomes a change order. Left unwritten, it becomes the provider's problem. This is the cheapest protection in the whole document and the most commonly skipped.

Change control

Scope creep is rarely one big request; it is fifteen small ones, each too minor to argue about. A change-control clause that is only used for large changes is not a process, it is an intention. Name the form, name who can approve, state that unapproved work is not performed, and use it for the small things too. The relationship survives a written change order far more comfortably than it survives an unexpected invoice.

Fixed fee versus time and materials

A fixed fee moves the risk of underestimating onto the provider, which is why fixed-fee SOWs need sharp scope and hard exclusions. Time and materials moves the risk onto the buyer, which is why they need an estimate, a not-to-exceed number, and an obligation to flag before it is passed. Disputes usually come from a document that reads like one model and prices like the other.

The best test of an SOW is to hand it to someone with no involvement in the project and ask what is being delivered and how they would know it was done. If they can answer, sign it. If they cannot, fix it now — it costs an hour today and a relationship later. This guide is general information rather than legal advice.