Statement of work writer

Statement of Work Writer

Almost every freelance dispute - unpaid invoices, endless revisions, "that was obviously included" - traces back to a scope document that only listed what IS included and stayed silent on everything else. A dispute-preventing SOW is defined as much by its exclusions as its inclusions, and it decides in advance how three predictable events get handled: the client asks for more, the client goes quiet, and the client won't say "done". This skill writes that document.

It pairs with scope-creep-defense, which enforces at delivery time what this SOW establishes at signing time. In the Freelancer / Consultant OS pack, the scope content comes from productized-service-designer. Worked example: Maya, a freelance brand designer moving from $75/hr hourly work to productized retainers, contracting her $4,900/month Brand System Retainer.

Operating procedure

Step 1: Collect the inputs

1. The agreed offer: deliverables, quantities, price (from productized-service-designer if productized; for Maya, the Tier 2 retainer at $4,900/month, up to 36 hours).
2. Client legal name, signer, and start date.
3. Project type: one-time project or ongoing retainer - this decides the payment schedule.
4. The 3-5 requests the client is most likely to make that are NOT included. If the freelancer cannot name them, derive them from the "outside the box" list in productized-service-designer. Label guesses as guesses and confirm with the freelancer.

Step 2: Write inclusions AND exclusions

Inclusions follow the deliverable definition rules from productized-service-designer: named artifact, quantity, format, revision rounds, turnaround. Then write the exclusions list - the section most SOWs skip and the reason most disputes happen. Include, at minimum:

• The likely-adjacent services this freelancer does not provide (Maya: copywriting, naming, motion design, print production and vendor management).
• Quantity overruns ("social templates beyond 8 per month").
• Third-party costs (stock assets, fonts, printing) - excluded or billed at cost with pre-approval.
• Meetings beyond the stated cadence.

State plainly: "Anything not listed under Inclusions is out of scope and handled under the Change Orders section." That single sentence converts every future ambiguity from an argument into a process.

Step 3: Set the revision-round limit

2 rounds per deliverable is the standard (identical across productized-service-designer and scope-creep-defense). Define a round precisely: one consolidated set of comments from a single designated approver, returned within 5 business days. Feedback trickling in over a week is one round, not five. Additional rounds are available at a stated rate - Maya lists $150/hr - so round three is a purchase decision, not a fight.

Step 4: Write acceptance criteria

Every deliverable needs an objective "done" condition plus a deemed-acceptance clause: if the client provides neither approval nor a consolidated revision request within 5 business days of delivery, the deliverable is deemed accepted. Without this clause, a silent client can hold payment hostage indefinitely. Acceptance criteria must be checkable ("delivered as print-ready PDF at the agreed dieline dimensions"), never subjective ("client is happy with the design").

Step 5: Set the payment schedule

• One-time projects: 50 percent upfront, 50 percent on completion. Never start work before the deposit clears - the deposit is both cash flow and a seriousness filter. Projects over roughly $10,000 or 6 weeks: switch to milestones (e.g. 40/30/30), each milestone invoiced on its acceptance per Step 4.
• Retainers (Maya's case): full month billed on the 1st, in advance. Retainers are capacity reservations; billing in arrears turns them into disputed timesheets.
• Late payment terms: work pauses on invoices 7+ days overdue; a late fee (1.5 percent per month is common) stated in the SOW.

Step 6: Add the change-order clause

The pressure valve that keeps the fixed scope fixed: any request outside Inclusions is written up as a one-paragraph change order - description, price, schedule impact - and requires sign-off before work begins. No signed change order, no out-of-scope work. The word-for-word conversation script for invoking this clause gracefully lives in scope-creep-defense; the SOW just has to make the mechanism contractual.

Step 7: Assemble from the template

Template: statement of work

STATEMENT OF WORK

Client: [FILL: legal name]          Provider: [FILL: freelancer/company name]
Effective date: [FILL]              Engagement type: [FILL: project / monthly retainer]

1. SERVICES AND INCLUSIONS
   [FILL: each deliverable - named artifact, quantity, format, turnaround]
   Example (retainer): Up to 8 social templates/month (source + sized exports),
   up to 4 web graphics/month, packaging design for 1 SKU/quarter, monthly
   60-minute creative direction call. Capacity: up to [FILL: 36] hours/month.
   Unused hours do not roll over.

2. EXCLUSIONS
   The following are out of scope: [FILL: adjacent services, quantity overruns,
   third-party costs, extra meetings]. Anything not listed in Section 1 is out
   of scope and handled under Section 7 (Change Orders).

3. REVISIONS
   Each deliverable includes 2 revision rounds. A round is one consolidated set
   of comments from [FILL: designated approver], returned within 5 business
   days. Additional rounds: $[FILL]/hour, invoiced with the next billing cycle.

4. ACCEPTANCE
   A deliverable is accepted when [FILL: objective criteria per deliverable].
   If Client provides neither approval nor consolidated revisions within 5
   business days of delivery, the deliverable is deemed accepted.

5. FEES AND PAYMENT
   [FILL - project: total $____; 50% due on signing, 50% on completion.
    FILL - retainer: $____/month, invoiced on the 1st, due on receipt.]
   Invoices 7+ days overdue pause all work; late fee [FILL: 1.5]%/month.

6. TERM AND TERMINATION (retainers)
   Initial term [FILL: 3] months, then month-to-month with [FILL: 30] days'
   written notice by either party. Prepaid fees for the notice period are due.

7. CHANGE ORDERS
   Requests outside Section 1 are documented in a written change order stating
   description, fee, and schedule impact, and require sign-off from both
   parties before work begins.

8. OWNERSHIP
   Upon full payment, Client owns final deliverables. Provider retains working
   files unless purchased and may display the work in a portfolio.

Signatures: _________________ (Client)   _________________ (Provider)

Concrete thresholds

• 2 revision rounds standard; a round = one consolidated set of comments.
• 5 business days for feedback and for deemed acceptance.
• 50 percent upfront on projects; milestones above ~$10,000 or 6 weeks; retainers billed the 1st in advance.
• Work pauses at 7 days overdue; 3-month initial retainer term, 30 days' notice after.
• Exclusions list must name at least 3 specific likely requests - a generic "everything else is excluded" alone reads as boilerplate and invites argument.

Deliverable

A complete, signable SOW with every [FILL] resolved, an exclusions list naming the client's most probable off-scope requests, objective acceptance criteria, and a payment schedule matched to the engagement type.

Do NOT

• Do not write inclusions without exclusions - the silent scope is the disputed scope.
• Do not allow "revisions until satisfied" or any undefined revision language; it prices an unlimited liability at zero.
• Do not start work before the deposit or first retainer invoice clears, whatever the stated urgency. Urgency without payment is a red flag, not an exception.
• Do not use subjective acceptance criteria; "client satisfaction" is legally and practically unverifiable.
• Do not bury the change-order clause and then improvise when the first extra request arrives - the clause only works if it exists before it is needed.

Quality bar

Done when: every deliverable has quantity, format, rounds, and turnaround; exclusions name specific likely requests; acceptance has the deemed-acceptance clause; the payment schedule matches engagement type with a work-pause trigger; the change-order clause is present; and no [FILL] remains.

Escalation

This is a working scope document, not legal advice. Have a contract lawyer review the template once for the freelancer's jurisdiction - especially ownership, termination, and liability - and reuse the reviewed version thereafter. For enforcing this SOW when live requests drift, go to scope-creep-defense; for winning the engagement in the first place, sales-proposal-writer.