Free statement of work template
that actually defines what "done" means.

Scope creep, disputes over acceptance, and unpaid invoices almost always trace back to a statement of work that left something undefined. This page walks through the 9 sections every SOW needs, why vague language in each one creates legal exposure, and how to write them so they hold up. Preview your AI-drafted statement of work free — no credit card.

Free preview · no credit card · not legal advice

What is a statement of work?

A statement of work (SOW) is the project-level document in a services engagement. It defines exactly what will be delivered, when, at what cost, and what "complete" and "accepted" look like. The SOW answers all the questions that a master service agreement deliberately leaves open — scope, deliverables, timeline, fees, and milestones.

A well-written SOW prevents three of the most common contractor disputes: scope creep (work keeps growing without additional compensation), acceptance disputes (the client says it's wrong; the contractor says it's done), and payment disputes (deliverables delivered but no clear trigger for payment). None of these require going to court if the SOW is precise enough to resolve them on its face.

Use a SOW with a master agreement

The master service agreement or IC agreement covers standing legal terms (IP, liability, confidentiality). The SOW covers project-specific details. Sign the master once; attach a new SOW for each project.

Use a standalone SOW for one-off projects

For a single project with a new client, a self-contained SOW that includes the essential legal terms can stand alone as the entire contract — if it's comprehensive enough. Clausio checks for the required elements.

Use change orders for scope changes

When the client wants something beyond the original SOW, a written change order amends the agreed scope, timeline, and fee. Without a change-order process, additional work gets absorbed as "included" — and goes unpaid.

9 sections every statement of work needs

These are the sections Clausio checks for when reviewing your SOW. Each one resolves a category of disputes before they happen.

SOW-01

Project overview and objectives

Why it matters: A one-paragraph description of why the project exists and what it is supposed to accomplish gives context for interpreting everything else in the SOW. When a deliverable is ambiguous, courts and arbitrators look to the stated purpose of the engagement to resolve the ambiguity. Without a stated objective, there is no anchor for that interpretation.

What Clausio checks: That the SOW states the project purpose and intended outcome in plain terms — not just the deliverable list, but why it matters. Flags if the SOW jumps straight to deliverables with no context.

SOW-02

Deliverables — specific, testable, complete

Why it matters: This is the most important section of the SOW. A deliverable defined only as "a website" or "marketing materials" creates a dispute waiting to happen. Specific deliverables with format, quantity, and output type reduce the chance of disagreement about what was promised and leave no room for the contra proferentem rule to be used against you.

What Clausio checks: That each deliverable is described with enough specificity to determine completion — format, quantity, technical specification, or functional requirement. Flags vague deliverable descriptions that could generate scope disputes.

SOW-03

Timeline and milestones

Why it matters: Without a timeline, the contractor has no agreed deadline — and no legal obligation to deliver by any particular date. Without milestones, there is no agreed payment schedule trigger. A "time is of the essence" clause elevates a deadline to a material term — missing it may allow the client to terminate without proving other breach.

What Clausio checks: That the SOW specifies a project start date, milestone dates (if any), a final delivery date, and whether time is of the essence. Flags if the timeline is left entirely open-ended.

SOW-04

Acceptance criteria and review process

Why it matters: Without acceptance criteria, the client has effectively unlimited ability to reject deliverables as "not quite right" — leaving the contractor doing unpaid revision work indefinitely. Clear acceptance criteria define what passes, what triggers a revision request, and how many rounds of revision are included before additional work is billed separately.

What Clausio checks: That the SOW defines what the client must do to formally accept each deliverable (or batch), specifies the review period, limits the number of included revision rounds, and states what happens if the client fails to respond within the review period.

SOW-05

Fees and payment schedule

Why it matters: Without a payment schedule tied to milestones or deliverable acceptance, the contractor has no contractual right to demand payment at any particular time. Milestone-based payment also gives the contractor leverage — completing a milestone triggers payment, and withholding subsequent work until receipt is a clear contractual right rather than a negotiating tactic.

What Clausio checks: That the total fee, rate, or pricing structure is specified; that payment triggers are tied to milestones, deliverable acceptance, or calendar dates; and that invoicing and payment-due terms are defined.

SOW-06

Client responsibilities and dependencies

Why it matters: Projects fail on time and budget more often because of client-side delays than contractor-side ones. If the contractor needs access, content, approvals, or decisions from the client to deliver, and the client delays, the contractor faces a difficult choice: absorb the delay or claim breach. A SOW that explicitly lists client obligations and what happens when they're missed shifts responsibility fairly and protects the contractor's timeline and fee.

What Clausio checks: That the SOW lists what the client must provide (access, assets, approvals, timely feedback) and that it specifies what happens to the timeline and fee if the client fails to deliver these on schedule.

SOW-07

Change-order process

Why it matters: This clause is what prevents scope creep from consuming a project's profitability. Without a defined change-order process, requests for additional work often end up treated as "included" by default — either because the contractor feels pressure to comply, or because the client genuinely believed it was in scope. A written change-order requirement means any work beyond the original SOW requires a signed amendment specifying additional scope, timeline, and fee.

What Clausio checks: That the SOW specifies how changes to scope, timeline, or fee must be requested and approved — typically in writing, signed by both parties — and that work performed without a signed change order is not required.

SOW-08

IP ownership — deliverables vs. pre-existing work

Why it matters: A SOW is often where IP ownership is most practically important — the contractor is delivering specific work product, and the client needs to own it to use it. Without a written assignment, the contractor retains copyright in everything delivered, regardless of payment. Equally important: the SOW should carve out the contractor's pre-existing tools, frameworks, and libraries so the client doesn't inadvertently claim ownership of them.

What Clausio checks: That the SOW includes a copyright assignment (or references the master agreement's IP clause), and that pre-existing IP owned by the contractor is explicitly excluded from the assignment. Flags if IP ownership is silent.

SOW-09

Governing law and conflict with master agreement

Why it matters: When a SOW is used alongside a master service agreement, the SOW should specify which document controls in the event of a conflict — usually the SOW governs for project-specific terms and the master agreement governs for legal terms. Without this, courts must interpret which document is more specific and therefore prevails, which creates uncertainty.

What Clausio checks: That a governing-law clause is present (either in the SOW or by reference to the master agreement), and that the SOW states the order of precedence if it conflicts with any master agreement.

Get your statement of work drafted and checked — free.

Answer five plain-English questions. Clausio drafts a tailored statement of work and flags any of the 9 sections above that are missing or under-specified. Preview the full document for free — no credit card required.

Preview my statement of work →

Free preview · no credit card · not legal advice

What gets flagged in statements of work

These are the patterns Clausio catches most often in SOWs.

Deliverables undefined

Deliverable described as "a complete website" with no pages, features, or functional requirements (SOW-02) flagged. Courts interpret ambiguous scope against the drafter. Clausio prompts for specific deliverable definitions with format and acceptance conditions.

No acceptance criteria

SOW lacks any review period or acceptance process (SOW-04) flagged. Without a defined review window, the client can delay acceptance indefinitely — triggering payment delay for the contractor. Clausio adds a review period and deemed-accepted provision.

No change-order clause

No written requirement for change orders (SOW-07) flagged. Without it, scope additions become implied by course of dealing. Clausio adds a change-order clause requiring written, signed approval for any out-of-scope work.

Statement of work questions

Other contract resources

Freelance contract template →

The core standalone template covering IP ownership, payment terms, IC classification, and termination — use it with or instead of a master agreement + SOW structure.

Service agreement template →

A master service agreement governs the standing legal terms — IP, confidentiality, liability — that you don't want to renegotiate with each new SOW.

Independent contractor agreement →

The IC agreement focuses on worker classification, tax treatment, and the IC relationship — the required foundation when engaging self-employed contractors.

Retainer agreement template →

When an ongoing engagement is better structured as a monthly retainer than a per-project SOW — with clear rules about included hours and out-of-scope work.

NDA template →

Share confidential information during project scoping or before an SOW is signed — with the DTSA whistleblower notice that most templates omit.

What clauses does a freelance contract need? →

A deep-dive into the ten required clauses — including IP ownership, payment terms, and governing law — and the US law behind each one.

Get your statement of work drafted and checked — free.

Five questions. A tailored SOW with defined deliverables, acceptance criteria, payment triggers, and a change-order process. Preview free, no credit card required.

Preview my statement of work →

Free preview · not legal advice · consult an attorney