River
Y CombinatorBacked by Y Combinator
FREE TEMPLATE

Consulting Statement of Work Template

Four documents and four sheets built so every rejection routes to one outcome: re-performed free, priced down, change ordered, or accepted and invoiced.

Free download  ·  No account needed

Acceptance Log  ·  Ravenstone Logistics  ·  warehouse operating model review, 46,000 fixed fee

Six events, four outcomes, and two of them cost you nothing

RefWhat came backOutcomeMoney
A-01D-01 assessment report accepted on 24 Apr by the named approverAcceptedMilestone released
A-02D-02 model reconciles to 3.4 percent. Schedule C says within 1 percentRe-performedNo increase in price. Round 1 of 2
A-03D-02 round two asks for two customer segments that are not in Schedule CChange orderCO-02, four days, 3,200. D-02 stays accepted
A-04Second workshop ran with five of the eight named attendees, two of them left after 40 minutesReduced valueMinus 1,900. No re-performance possible in the window
A-05D-03 options paper delivered 3 Jun, no response by 17 JunDeemed acceptedInvoiced 17 Jun under clause 6.4
A-06D-01 reopened on 11 Jul to hold back the final invoiceRefusedAccepted 24 Apr and closed. Routed to change control

A-03 is the row that pays for the engagement. The comment was reasonable, the client was not being difficult, and nothing in it cited anything in Schedule C. Every template online calls that a cure period at no additional charge. It is a change order, and the deliverable it arrived against is still accepted and still invoiced while the new work gets priced.

A-06 only works because A-01 carries a date and a name. Acceptance is an event rather than a mood. Once it has happened, reopening it needs a stated ground, and a preference expressed eleven weeks later is not one.

Fixed fee 46,000. Final position 47,300: five milestones of 9,200, less 1,900 of reduced value on D-04, plus a 3,200 change order.

Search this and the templates are better than they used to be. The free ones now ship objective acceptance criteria, a ten day review window, deemed acceptance on silence, a cure period, milestone fees tied to acceptance, and change control by written amendment. That is a real bar and most independents are below it. What none of them decides is the only question that matters when a deliverable comes back: whose fault is it, and therefore who pays for the next version.

A rejection routes to one of four outcomes here, and only two of them are free. FAR 52.246-4 gives the buyer re-performance at no increase in contract amount where services do not conform to the requirements, and where re-performance cannot fix it, a price reduction reflecting the reduced value of what was performed. A workshop that happened with three of eight people cannot be re-performed. Comment that cites nothing in the criteria is a change order, and the deliverable stays accepted and stays invoiced.

The fourth outcome is refusal. Acceptance is an event with a date and a named signatory. FAR 46.501 makes it an acknowledgment that the work conforms, so a deliverable accepted in April is not reopened in July to justify withholding the last invoice. The payment clock needs both halves nailed too, which is why the milestone sheet defines what makes an invoice proper at this client. A scope change later needs its own paper, which is the change order pack. Build it from the proposal that won the work, or take the files blank.

Five deliverables, one that cannot be re-performed, and the invoice that bounced

Acceptance bases are written as things two people who disagree can both count. Assumptions carry the mechanism their failure triggers, agreed before signature rather than argued in month three.

Deliverable Register

Fictional third-party logistics client, Ravenstone. Five deliverables, one review window each.

RefDeliverableAccepted whenApproverRe-do?
D-01Current state assessment reportCovers the four named sites, every figure cited to an export listed in Schedule B, and each of the twelve kickoff questions answered or recorded as a gapRuth Calloway
operations director
Yes
D-02Cost to serve modelReconciles to the FY25 statutory accounts within 1 percent at total cost, and runs for the 340 customer and product combinations in Schedule CTom Eddowes
finance director
Yes
D-03Target operating model options paperThree options, each carrying a cost, a headcount and a named risk, each mapped to the twelve kickoff questionsRuth CallowayYes
D-04Two decision workshopsBoth sessions held with at least six of the eight named attendees present throughout, minuted within three working daysRuth CallowayNo
D-05Implementation roadmapEvery initiative carries an owner and effort in client days, sequenced against the capacity data supplied under AS-03Both approversYes

D-04 is the row that changes the contract. A workshop cannot be re-performed: the eight people were in a room on a Tuesday and they will not be again inside the engagement. So its acceptance basis has to be a threshold somebody can count while it is happening, six of eight present throughout, and its failure outcome is a stated amount rather than a free rerun nobody can schedule.

Every approver is one person who can say yes without asking anybody. D-05 needs two, which is written down rather than discovered, because a deliverable needing two signatures inside one review window is a deliverable that sits until somebody chases it.

Accepted when is written to be countable. Within 1 percent. Six of eight. Twelve questions. Nothing here says to the client's reasonable satisfaction, which is not a criterion but a deferred argument.

The four outcomes

One test decides which: does the comment name something in the acceptance schedule?

What the comment doesOutcomeWho paysWhat happens to the deliverable
Names a criterion in the schedule, and the criterion is not metRe-performanceNobody. No increase in priceStays rejected until it conforms. The round is counted
Names a criterion that is not met, and re-performance cannot fix itReduced valueYou, by a stated amountAccepted at the reduced price, with the shortfall recorded
Names nothing in the scheduleChange orderThe client, priced before work startsStays accepted and stays invoiced
Names a criterion that is metRefused, with the evidenceNobodyAccepted. Silence past the window is also acceptance
Arrives after acceptanceRefused unless a named groundThe client, if they still want itClosed. Routed to change control

The whole table turns on one question, and it takes a minute per comment. Does this name something in the acceptance schedule? Yes puts it on you and it is free. No puts it on them and it is priced. Page one collapses both into a cure period at no additional charge, which is a commitment to do unlimited free work in exchange for the appearance of being easy to deal with.

Two rounds are included and the third is chargeable. That clause is unenforceable without a count, and it is trivially enforceable with one, because both sides are reading the same number off the same sheet before anybody gets annoyed.

Refused is a real outcome and it needs evidence rather than tone: the criterion, the delivered artifact, and the line in it that satisfies the criterion.

Payment Milestone Schedule

Two clocks per milestone, and an invoice that is not proper starts neither of them.

RefTriggerAmountClockStatus
M-01Signature9,200Invoiced 11 Apr, due 11 MayPaid 6 May
M-02D-01 accepted9,200Accepted 24 Apr, invoiced 24 Apr, due 24 MayPaid 29 May
M-03D-02 accepted9,200Returned 28 May, no line for CO-02. Corrected same day, due 27 JunPaid 26 Jun
M-04D-03 accepted9,200Deemed accepted 17 Jun, invoiced 17 Jun, due 17 JulPaid 21 Jul
CO-02Change order signed3,200Invoiced with M-04, due 17 JulPaid 21 Jul
M-05D-05 accepted7,3009,200 less 1,900 of reduced value on D-04Open

An invoice is proper at this client when it quotes purchase order 45-118207, states cost centre 4120, is addressed to accounts payable rather than to the sponsor, shows the VAT number, and carries one line per milestone with any change order on its own line. That sentence lives in the statement of work because M-03 is otherwise the week nobody writes down: an invoice returned for a missing line is not a payment dispute, it is an administrative bounce, and it restarts a thirty day clock.

Payment is due on the later of thirty days from a proper invoice and thirty days from acceptance. Both clocks matter, which is why milestones tied to acceptance with no acceptance mechanism behind them turn a fixed fee into an open-ended one.

M-04 and CO-02 were paid four days late together, which is a fact for the next renewal conversation rather than a complaint for this one.

Assumption Register

Six of the eight rows, and the point of the sheet is the mechanism column.

RefAssumptionWhoseIf it failsMechanism
AS-01Written feedback on each deliverable inside its review windowClientDeemed accepted on the last day of the windowAcceptance, clause 6.4
AS-02Three named people per site available for half a day eachClientDates move day for day, no change to priceSchedule
AS-03A run level export at customer and product grain by 21 AprClientD-02 re-scoped to the summary grain, acceptance basis becomes Schedule C-2Descope
AS-04No more than two review rounds per deliverableSharedThird round is chargeable at 800 a dayChange order
AS-05Site work stays within the four named sitesClientA fifth site is chargeable at 800 a day plus travelChange order
AS-06At least six of the eight named attendees at each workshopClientRescheduled once at no charge, then a stated reductionReduced value

The mechanism column is the whole register. A list of assumptions is a list of things to argue about in month three. The same list with an agreed mechanism against each line is a decision already taken, at the one moment in the engagement when both sides were pleased with each other. Five mechanisms cover everything: acceptance, schedule, descope, change order, reduced value.

AS-03 is the row that saves the margin. An export that never arrives normally becomes unpaid work at the wrong grain, delivered late, and then argued about. Naming the descope in advance means the deliverable changes rather than the fee, and the conversation is three sentences long.

Every assumption belongs to somebody. A register where all six are shared is a register nobody will act on when one of them fails.

What's in the pack

01

Deliverable Register

The acceptance basis per deliverable written as countable tests, the one named approver with authority to give it, the review window, and whether the deliverable can be re-performed at all.

02

Acceptance Log

Every delivery, every comment and the outcome it routed to, with the round count that turns a two-round clause into something both sides read off the same sheet.

03

Payment Milestone Schedule

Milestone, trigger, amount, and what makes an invoice proper at this client, item by item, with both payment clocks running side by side.

04

Assumption Register

Each assumption with whose it is and the mechanism its failure triggers: acceptance, schedule, descope, change order or a stated reduction.

05

Statement of Work

Scope and exclusions, the deliverable schedule, the acceptance and payment clauses, and the client's own obligations written as dated items rather than as goodwill. Built for fixed-scope, deliverable-based work; an engagement that is genuinely ongoing advisory access fits a retainer better than a SOW with a rolling extension.

06

Acceptance Criteria Schedule

The tests, written so a reviewer and you reach the same verdict without a conversation. Where a bid already offered an acceptance basis, the response you wrote is where these come from.

07

Change Control Procedure

What counts as an instruction, who is authorised to give one, what has to be priced before any work starts, and the window for claiming an adjustment. Pricing one properly, on all three of its costs, is the change order pack.

08

What Acceptance Closes

The four outcomes with the test that routes between them, the narrow grounds on which an acceptance reopens, and the sentence that refuses everything else.

How to use it

  1. 1

    Open in River, or take it blank

    Open the pack in River and send the agreed proposal with the client's master agreement, or download the Word documents and CSV sheets and fill them in yourself.

  2. 2

    Write tests, not adjectives

    Every acceptance basis has to be countable by two people who disagree. Within 1 percent. Six of eight present. Twelve questions answered or recorded as gaps.

  3. 3

    Name the mechanism now

    For each assumption, agree before signature what its failure triggers: a new date, a descope, a priced change order, or a stated reduction.

  4. 4

    Log every comment

    Route each one to an outcome the day it arrives, count the rounds, and record acceptance as an event carrying a date and a name.

Frequently asked questions

Is this template free?

Yes. The zip is Word documents and CSV sheets, no account and no card. Edit with AI is the optional half: the agent reads the agreed proposal and the client's own master agreement, then writes acceptance tests a reviewer and you would both score the same way. The rest sit in the template library.

What format are the downloaded files?

Four Word documents and four CSV sheets in one zip. The sheets carry the columns that do the work: acceptance basis, named approver, re-performable, round count, outcome, mechanism. Open them in Excel, Numbers or Google Sheets. The statement of work and the schedules are .docx.

My client will never sign a deemed acceptance clause.

It is the federal default, and it is tighter than the ten days here. Under FAR 52.232-25 acceptance is deemed to occur constructively on the seventh day after the services are performed, unless there is a disagreement over quantity, quality or compliance. Ten working days is generous by comparison.

Why does a proper invoice definition belong in a statement of work?

Because the payment clock does not start until the invoice is one. The federal rule lists ten required items and returns a defective invoice within seven days with the reasons, which is a week gone. So the milestone sheet records what this client needs on the page: the purchase order, the cost centre, the addressee, a line per milestone.

The comment is reasonable but it is not in the criteria. Do I really charge?

Yes, and the register is what makes it easy. Two rounds are included per deliverable and the count is visible to both sides. A comment that names nothing in the acceptance schedule is new work, the original deliverable stays accepted, and its milestone stays invoiced while the change order is priced.

What if the deliverable cannot be re-performed?

Then its acceptance basis is a threshold somebody can count in the room, and its failure outcome is a stated price reduction. A workshop that ran with five of eight named attendees cannot be run again inside the engagement window, so the register carries the amount rather than a free rerun nobody can schedule.

How does this sit against the master agreement?

The master agreement holds the terms that outlive the project: liability, insurance, intellectual property, confidentiality. This holds the project: scope, deliverables, acceptance, milestones. Where they conflict the master agreement wins unless the scope says otherwise and both sides sign. The intake pack reads it in week one.

Decide who pays before it matters

Take the Word documents and CSV sheets blank, or send River the agreed proposal and the client's master agreement and get acceptance tests written against it.

Edit with AI