For consultants once the client says yes
SOW Generator From Your Consulting Proposal
Drop your agreed proposal or paste your call notes. Get a statement of work with clear scope, acceptance criteria, and every vague line flagged.
Free to start. No card needed.
Statement of work · Calder & Moss
- Out of scopeChanges to the ERP system, training for sales reps, and any branch beyond the six named.
- Deliverable 2 · accepted whenThe CFO approves the discount rules in writing, or [5] working days pass with no written comments.
- Payment 2 of 3[fee] on acceptance of Deliverable 2, invoiced within [7] days.
- Line that invites scope creep“Support the rollout as needed” → “Up to [4] half-day sessions with branch managers, ending [date].”
What you'll get
A statement of work from your proposal, with scope creep flagged
- What's in scope, and an explicit list of what isn't
- Every deliverable with the test it must pass to be accepted
- Vague lines quoted from your proposal, each with a tighter rewrite
Before and after
Your proposal in. A SOW with clear edges.
The proposal Calder & Moss accepted: Option 2, a pricing diagnostic and new discount rules, a fixed fee, three phases over ten weeks, and one line promising to “support the rollout as needed”.
Out of scope: changes to the ERP system, training for sales reps, and branches beyond the six named in the proposal. Deliverable 2: Discount rules. Accepted when: the CFO approves them in writing, or [5] working days pass with no written comments. Lines that invite scope creep As written: “support the rollout as needed” (proposal, Option 2). Why it's risky: no limit on time, people or end date. Tighter: “Up to [4] half-day sessions with branch managers, ending [date].”
The vague line, why it's risky, and a version both sides can sign.
Why it works
What is a statement of work, and what should it include?
A statement of work, or SOW, sets out exactly what you will deliver, how the client will accept it, and what you won't do. Oregon's state procurement guide defines it as the parts of a contract that describe the work to be performed or the products to be delivered. It also calls the SOW the gauge against which performance is measured. River reads the proposal your client agreed to, or your call notes, and writes the SOW from it, so each promise becomes a defined deliverable.
Scope creep usually starts with one soft line. Oregon's guide tells writers to avoid words like assist, work with, help and best efforts, because each party can read them differently. River quotes every line like that from your proposal in a section called Lines that invite scope creep. It says why each one is risky and gives a tighter version with a number, a limit or a date. Fees, dates and quantities your material doesn't give stay as bracketed placeholders for you to fill.
Use it once the client has said yes, before kickoff. If you haven't written the proposal yet, start with the consulting proposal generator and bring the result here. Prefer to fill in the sections yourself? Use the statement of work template. When the SOW is agreed, a RACI matrix template turns its deliverables into who does what. River can also draft the list of data to request from the client in the same space, using the SOW you just wrote.
What lands in your doc
What's in your statement of work
- Objectives carried over from your proposal, each tied to the deliverable that achieves it
- In-scope work, plus a separate out-of-scope list naming what the client might assume is included
- Each deliverable with acceptance criteria: what it contains, who signs it off, and by when
- Assumptions and client responsibilities, such as data, access and decisions, each with an owner and date
- Milestones and a payment schedule, with amounts and dates in brackets unless your proposal states them
- A change-request process, and every vague line from your proposal quoted with a tighter rewrite
How it works
From proposal to statement of work
Drop your proposal
Drop the proposal your client agreed to, or paste your call notes and the emails that followed.
River maps every promise
It reads everything first, listing each promise, deliverable, date and fee with where it appears.
Get your SOW
The statement of work lands in your doc, with placeholders wherever your material leaves a gap.
Tighten and sign
Accept the tighter rewrites you agree with, settle the placeholders, then send it for signature.
How to write a statement of work by hand
Start with deliverables, not tasks. List each thing the client will receive, such as a report, a workshop or a model, and write acceptance criteria for it. Oregon's guide describes acceptance standards as the objective criteria used to decide whether the work meets requirements. In practice that means three facts per deliverable: what it must contain, who signs it off, and how many working days they have to review it. Without them, "done" means whatever each side remembers agreeing.
Describe the work as results wherever you can. US federal buying rules ask agencies, where they can, to describe services work in terms of the required results, not how it is done or how many hours it takes. Results give both sides a fair test of whether the work is done. Then write the out-of-scope list. Name what the client could reasonably assume is included: implementation after your recommendation, extra sites or teams, system changes, training, travel and further review rounds.
Write every obligation in the active voice, with a named owner: "the client will provide the branch sales ledger by [date]", not "data will be provided". Oregon's guide warns that passive sentences blur who is responsible for an action. Tie each payment to a milestone or a deliverable, so an invoice follows something both sides can see. Finally, set out how changes work: who raises a change request, who assesses its effect on scope, time and fee, and that new work waits for written approval.
Questions consultants ask
Common questions
What is a statement of work?
A statement of work is the part of a consulting agreement that says what will be delivered, by when, how it will be accepted and how it is paid. Oregon's procurement guide calls it the heart of the contract. It turns the option your client chose in the proposal into specific deliverables, dates and responsibilities that both sides sign.
What is the difference between a proposal and a SOW?
A proposal confirms the problem, the objectives and the options, and asks the client to choose. A SOW comes after that choice and defines the chosen work precisely: deliverables, acceptance criteria, responsibilities, milestones, payments and how changes are handled. Write the proposal to win the work, then the SOW to run it, so both sides know what done looks like.
What are acceptance criteria in a SOW?
They are the tests a deliverable must pass before the client signs it off. Good criteria name what the deliverable contains, who approves it, and how long they have to review it. For example: "Accepted when the CFO approves the discount rules in writing, or 5 working days pass with no written comments." River writes criteria like these for every deliverable.
How does a SOW prevent scope creep?
By making the edges of the work visible. An explicit out-of-scope list, deliverables with acceptance criteria, and a change-request process give both sides a shared answer when a new request arrives. River also reviews your proposal for open-ended phrases such as "as needed" or "support the rollout", quotes each one, and offers a tighter version with a limit or a date.
Will it set my fees or payment terms?
No. Amounts, dates and payment terms come only from your proposal or notes. Where they are missing, the SOW shows a bracketed placeholder such as [fee] or [date] and lists it under To confirm before signing. River ties each payment to a milestone or a deliverable, so you can see what triggers each invoice, but the numbers stay yours to set.
Is a SOW legally binding?
It can be. Oregon's procurement guide treats a SOW as legally enforceable and subject to contract law, so word it with care. River drafts the work description: scope, deliverables, acceptance, responsibilities and payments. It doesn't write liability, intellectual property or confidentiality terms, so use your own contract for those, and ask a lawyer when the stakes are high.
Is my client's proposal kept private?
Files you drop go into your own River space and stay there unless you share them. Under River's privacy policy, nothing you upload is used to train AI models, and River's AI providers are bound by their agreements with River not to train on it. If your contract with the client limits where its documents can go, check that first.
Your next step
More for your project
Agree the edges before the work starts
Drop your agreed proposal or paste your call notes. Every vague line comes back quoted, with a tighter version to sign.