Skip to content

Delivery

Statement of work template for software projects: what a SOW must include

A checklist to run before you sign, ending in a test you can give to someone who has never heard of the project.

Computing America. Applications, integrations, data analysis and AI/ML engineering.

Send the SOW
Updated 4 min readComputing America
A bound contract on a desk, flagged with many sticky tabs, a fountain pen across it.

In short

  • A deliverable the statement of work doesn't name is hard to claim was owed.
  • Passive voice in a statement of work is an unallocated obligation. Name the acting party in every commitment.
  • The assumptions section is a price list: each assumption is both an excuse for a missed date and a trigger for extra fees. Rewrite each one as a dated obligation on a named party.
  • Acceptance needs objective criteria agreed before work begins, a bounded number of correction cycles, and a stated outcome if a deliverable can't pass.
  • Write the holdback percentage and the event that releases it into the statement of work.

A statement of work must name each deliverable with an acting party and a date, set objective acceptance criteria, and tie payment to accepted milestones. The master agreement's warranty, indemnity and liability cap are remedies for failing to deliver something, and the statement of work is where that something is named.

Fig. 1
  1. Deliverables

    Each with an acting party and a date

    Within: Statement of work: names what is owed.
  2. Acceptance

    Objective criteria and bounded correction cycles, so work can be rejected

    Within: Statement of work: names what is owed.
  3. Payment

    Tied to accepted milestones, with a hold-back released on a named event

    Within: Statement of work: names what is owed.
  4. Master agreement

    Warranty, indemnity and liability cap

    Within: Remedies if it is not delivered.

Acceptance is the clause that lets you reject work, and payment is released only against what it accepts.

SourceStructure of a services engagement as described in this article; a planning figure, not a quotation from any contract.

Passive voice is a liability

“The router will be configured.” “The integration will be tested.” “Data will be migrated.” Who does each of those? Passive voice leaves out the actor, and in a contract that's an obligation no one has been assigned.

Write every commitment with a named party: “Vendor will complete the integration; Customer will test it against the criteria in section 4.” It reads worse as prose and it's the version you can enforce.

Read the assumptions section as a price list

Vendor assumptions look like housekeeping. Each one is also an excuse for missing a date and a trigger for additional fees.

“We assume the customer will provide test environments and development licenses” is a requirement, and it belongs in the document as one: what is needed, who provides it, by when, and what happens if it's late. Rewriting assumptions as dated obligations on both sides is a short edit to make before you sign.

Acceptance, or the absence of it

Acceptance is the clause that lets you reject work. Two patterns to watch for. Deemed acceptance says a deliverable is accepted if you don't reject it within a short window, which turns your own busy two weeks into a waiver. An unbounded correction period leaves you waiting with no point at which the deliverable counts as failed.

  • Acceptance criteria stated objectively, in the statement of work, before work begins. “To the customer's reasonable satisfaction” invites dispute.
  • A defined number of correction cycles and a hard limit on how long each may take.
  • An obligation to rework within each cycle until the criteria are met or the cycles run out. Who bears the cost belongs in the master agreement, or in the contract that governs the engagement.
  • What happens to a deliverable that still can't pass after the last correction cycle: it stays unaccepted and the part of its fee tied to acceptance stays unpaid. Termination and refund rights belong in the master agreement or the contract that governs the engagement.
  • Staged acceptance on anything long: installation, integration, user acceptance, then final.

Payment against milestones, not against Tuesdays

Tie fees to objective milestones and accepted deliverables, and hold back part of each phase's fee until that phase is accepted. Write the percentage and the event that releases it into the statement of work.

Time and materials puts the whole budget risk on you. Sometimes that's right, and sometimes it signals a project no one scoped. The way out is a short, paid scoping engagement that gives the vendor enough access to understand your environment, then converts to a fixed price.

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 and signed before the work starts.
  • Reporting cadence and format, written down.
  • An escalation path with names and timeframes, written while the relationship is still friendly.
  • A risk register with owners and mitigations in place of a paragraph of disclaimers.
  • No boilerplate legal terms in the statement of work. Ownership, warranty, indemnity, liability, termination and refunds belong in the master agreement.

The statement of work template: headings in order

A software statement of work that carries these headings, in this order, names what is owed before it says how it is paid for. Each line says what goes under the heading.

  1. 1.Deliverables: each one named, with the party who delivers it and a date.
  2. 2.Responsibilities: every commitment written in the active voice, with a named party for the vendor and for the customer.
  3. 3.Assumptions and dependencies: each one rewritten as an obligation, with what is needed, who provides it, by when, and what happens if it is late.
  4. 4.Acceptance criteria: stated objectively, before work begins.
  5. 5.Correction cycles: the number of cycles, a hard limit on how long each may take, and what happens to a deliverable that still cannot pass.
  6. 6.Staged acceptance: for long work, installation, integration, user acceptance, then final.
  7. 7.Fees and milestones: fees tied to accepted deliverables, with the hold-back percentage and the event that releases it.
  8. 8.People: named people on both teams, with roles, and a limit on replacing the key ones.
  9. 9.Schedule: every date calculable from a defined starting event.
  10. 10.Change process: changes priced, written and signed before the work starts.
  11. 11.Reporting: the cadence and the format.
  12. 12.Escalation: names and timeframes, written while the relationship is still friendly.
  13. 13.Risk register: risks with owners and mitigations in place.

Ownership, warranty, indemnity, liability, termination and refunds are not headings in this template. They belong in the master agreement.

Next step

Send us the statement of work.

The one you are about to sign, from us or from anyone. We will mark the clauses that decide what you actually receive, and the ones that quietly move a risk from the vendor onto you.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing