Statement of work red flags

SOW Red Flags: Statement of Work Review

A statement of work is where the business promise becomes operational. If scope, dependencies, acceptance, or change orders are vague, the project can drift fast.

Use this page before kickoff or before signing a project addendum. Load an SOW sample into TermsHuman or paste your own project language for a plain-English risk read.

SOW risk lives in scope, dependencies, acceptance, and changes

Review statements of work for deliverables, milestones, assumptions, client inputs, dependencies, acceptance criteria, change requests, fees, expenses, timelines, and termination.

TermsHuman explains common contract language and risk patterns for education only. It is not a law firm, does not provide legal advice, and cannot tell you whether to sign. For material obligations, ask qualified counsel in your jurisdiction.

Reading notebook · Scope and changes

A new request needs its own record

A missing input and an extra deliverable are two different events. Keep the original milestone visible while recording what is missing, what is newly requested, and which decisions remain open.

Original scope · Fictional

Output
One English landing-page draft.
Input
Approved English copy, due on day 1.
Milestone
First draft on day 5.

Request on day 3 · Not yet agreed

Output requested
Add a Spanish version.
Input status
English copy is still missing; no Spanish copy has been supplied.
Milestone decision
Delivery date, acceptance criteria, and any cost effect remain unagreed.
  1. Day 1 · Record the dependency

    Log that the approved English copy has not arrived.

  2. Day 3 · Record the new request

    Keep the Spanish version separate from the missing original input.

  3. Next step · Find the change procedure

    Identify who can agree changes and how scope, inputs, timing, acceptance, and any charges would be recorded.

This timeline does not automatically extend a deadline, add a fee, or amend an agreement. Those outcomes depend on the actual terms and the parties’ decisions.

For a versioned record of the work, amount, timing and approval, use the five-field change order checklist.

Source lens: FAR 37.602(b)(1)–(2) describes required results and measurable performance standards for performance work statements in U.S. federal procurement. Paragraph (c) lists scope, period and place, required results, and constraints for a statement of objectives.

The page displayed FAC 2026-01, effective March 13, 2026, when consulted on October 30, 2026. This is a public-procurement example, not a requirement for every private SOW. The fictional change record above is a teaching aid, not a FAR change-order rule.

What to check first

The best SOWs make it clear what is included, what is excluded, and what happens when reality changes.

  • Deliverables, milestones, formats, quality standards, acceptance criteria, and review windows.
  • Assumptions, exclusions, dependencies, client inputs, access, and approval deadlines.
  • Timeline, kickoff, completion dates, delay rules, and resource commitments.
  • Fees, expenses, payment milestones, holdbacks, taxes, and invoice disputes.
  • Change orders, out-of-scope work, termination, ownership, and MSA conflicts.

Common SOW red flags

SOW problems usually show up as unpaid work, delayed acceptance, or arguments about what complete means.

  • Deliverables are described as all services needed or as reasonably requested.
  • No objective acceptance criteria or deemed acceptance deadline.
  • Client dependencies are missing even though the vendor depends on them.
  • Change requests are required without added fees or schedule relief.
  • The SOW conflicts with the MSA without saying which document controls.

Before you sign

Treat the SOW as the operating manual for the project.

  • Add examples of what is out of scope.
  • Create a clear path for approvals, feedback, and missed client deadlines.
  • Confirm whether final payment depends on acceptance, launch, or delivery.

Statement of work FAQ

What is a statement of work?

A statement of work describes a specific project or service under a larger agreement, including deliverables, timeline, price, assumptions, and acceptance process.

How is an SOW different from an MSA?

An MSA usually sets general legal terms. An SOW defines the specific work, milestones, fees, dependencies, and project deliverables.

What is deemed acceptance?

Deemed acceptance means deliverables are considered accepted if the client does not reject them with specific reasons within a stated review period.

Should an SOW include exclusions?

Yes. Exclusions make it clearer what is not included and reduce disputes about out-of-scope requests.

What happens if a client causes delay?

The SOW should say whether deadlines extend, fees change, resources are reallocated, or the vendor can invoice for waiting time.