WorkflowProcurement & Strategic Sourcing

Statement of Work Review

SOW review you work through with the agents — every clause checked, every fix cited, before anyone signs

See one case, screen by screen ↓
Watch with transcript →

Built forServices buyersBudget ownersLegal counselVendor managersCategory managers

The Problem Today

Buyers read each supplier's statement of work in spare time, so vague scope and inflated rates get signed.

8.6%
of contract value lost on average to weak contracting published

Four documents, read side by side

  • Statement
  • Agreement
  • Rate card
  • Playbook
  • Paying twice for workChange orders for work already in the signed scope
  • Cash out before deliveryLarge payments on signature, before anything is accepted

The Solution

  1. Linked to its agreementMatched to its master agreement, rate card and the original request
  2. Vague scope rewrittenEach deliverable gets an output, owner, date and acceptance test
  3. Rates checked to the cardEach role's rate matched to its row; any excess flagged with the amount over
  4. Counsel and owner approveLegal wording to counsel; the budget owner signs on the buyer's advice

Built-in controls

  • Each note cites its passage
  • Each finding re-checked independently
  • Nothing signed or released without a person

What You Get

Cash goes out as work is accepted, and fewer change orders pay a second time for scope already bought.

  • Payments tied to deliveryCash moved from signature to accepted deliverables
  • A fix ready for each findingEach open check comes with a proposed fix and its source
  • IP and data terms matchedOwnership and data terms checked against the master agreement
In short

What is Statement of Work Review?

Statement of Work Review is SOW review software for services procurement. Seven agents read each services SOW before signature, check its scope, rates, payments and legal terms against the MSA, the rate card, the procurement playbook and the requester's brief, and propose a cited fix for each problem. The buyer works through the findings with the agents; counsel decides legal wording and the budget owner approves and signs.

How to choose AI solutions for back-office and enterprise work →

Updated

The problem

A supplier-written SOW gets signed with vague scope and off-card rates

The SOW is usually the supplier's Word file, on the supplier's template, with the supplier's assumptions. The buyer has a day or two of spare time to read it against an MSA of 60 to 120 pages, a rate card kept in a spreadsheet exhibit, a procurement playbook and the budget owner's brief, and to spot anything non-standard before pulling counsel in by email. Approvers further up the delegation of authority see the value on a PDF, not the content.

What gets missed comes back after signature. “Support the transformation” instead of deliverables with an acceptance test turns a fixed fee into a stream of change orders. A role billed above the card hides in a price build-up nobody re-adds. Forty percent on signature leaves before anything is delivered, deemed acceptance removes the buyer's lever, and the supplier keeps the IP or touches personal data with no data-processing terms. Later, a milestone invoice is paid before acceptance and a change order pays again for work already in scope.

typical8.6%of contract value lost on average to weak contracting
typical39%of the $303B flowing through vendor management systems is bought under SOWs
Where a SOW's review days goestimated
By hand9 days
With the solution1.9 days
  • Finding the MSA, rate card and request it belongs to1 → 0.1 d
  • Reading scope and deliverables against the brief2 → 0.3 d
  • Re-adding the price and checking rates and expenses1 → 0.1 d
  • Payments, acceptance, IP, data and notice against the playbook2 → 0.4 d
  • Chasing counsel and the supplier by email2 → 0.6 d
  • Approval summary and the delegation-of-authority chain1 → 0.4 d

Estimated split for a typical services SOW, from arrival to approval-ready, by hand and with the solution. The working solution's sample company shows a median of 9.0 days before and 1.6 days after, in one quarter.

How it works

Where a statement of work review sends each clause

What comes in
SOWs inevery services SOW · Word, PDF, scans, with the MSA, rate card and request
Agents at work
Intake agentclauses and links
Then
Scope agentmeasurable deliverables
Rate agentagainst the rate card
Payment agentpaid on acceptance
Terms agentMSA and playbook
Then
Checker agentre-computes blind
Then
Routing agentapprovals, then delivery
A person decides
Buyer, counsel, budget ownerdecide every change and sign
What comes out
Signed SOW, measurable
PO with payments on acceptance
Change orders tested
One case, step by step

A $480,000 transformation SOW through review, from supplier draft to signed PO

A consultancy sends the company a $480,000 fixed-fee SOW for digital transformation support in the Distribution division, against the budget owner's request and a $500,000 budget line. Here is how a services procurement buyer works it through with the agents, screen by screen, in the working solution.

A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.

  1. 01Thursday morning

    The agents have already said what needs the buyer

    Services procurement buyer

    The buyer's Today screen: 12 SOWs in review worth $5.32M, 4 waiting for the buyer, 7 high-severity notes open, each with a proposed fix, and $708,900 protected this quarter. Beside the list, the agents talk to the buyer. The routing agent has ranked the morning; overnight, the checker agent re-checked a change order from a design studio and found 8 of its 20 assets already in the signed scope.

    Routing agent: “Morning. 4 SOWs wait for you; the first is due today. The consultancy's is the biggest: 3 high notes on $480,000.”

  2. 02The biggest SOW first

    The SOW as a document, with the agents' notes in the margin

    Services procurement buyer

    The SOW opens as the supplier wrote it, clause by clause. Next to each problem clause sits a note: scope too vague, key people not named, rate above the rate card. The top bar shows $480,000 against a $500,000 budget, fixed fee with 40% on signature, 16 weeks, and 46 checks run: 37 passed, 3 high, 4 medium, 2 low open. The intake agent has already linked the master services agreement, its rate card Exhibit C and the budget owner's request.

    Checker agent: “I re-computed all 9 findings from the sources without seeing the other agents' working: 9 of 9 agree.”

  3. 03§2.1 Scope

    One sentence of scope becomes three deliverables from the brief

    Scope agent

    The only deliverable is to “support the digital transformation” of the division. It fails all five parts of the deliverable test: a measurable output, an owner, a date, an acceptance test, what is out of scope. The scope agent rewrites it from the budget owner's own request: D1 a current-state assessment of the six distribution centers by week 4, D2 a roadmap of at least 12 prioritized initiatives with business cases by week 9, D3 a slotting pilot at one distribution center measured against the D1 baseline by week 16.

    In the company's own signed SOWs, a deliverable like this had change orders on 61% against 18%, a change-order risk of about $67,000. The scope agent does not invent scope the request does not support.

  4. 04§4.1 Rates

    A Principal at $295 an hour; the card says $260

    Rate agent

    The rate agent re-adds the price build-up and matches each role to the rate card. The Principal is billed at $295 an hour; Exhibit C, row 3, caps the role at $260, and clause C.4 says no SOW may exceed the card without written agreement. 320 hours × $35 = $11,200 over. One click on the source opens the rate card with the passage the agent relied on highlighted.

    “The highlighted passage is what the agents relied on. Opened from the record; it cannot be edited here.”

  5. 05The buyer asks

    “Why is 40% upfront a problem?”

    Buyer and payment agent

    The buyer asks in plain words. The payment agent answers with its sources: $192,000 would leave on signature, before anything is delivered; the playbook allows 10% mobilization and the rest on written acceptance, and calls anything above 20% a walk-away. It opens the note on §5.2: a new schedule of 10%, 25%, 30% and 35% tied to D1 to D3, adding up to $468,800, with each step of how it checked, a confidence of 98% and the checker's agreement.

    $145,120 of cash moved behind delivery. The payment agent does not move a payment the budget owner has not seen.

  6. 06The buyer instructs

    “Make the pilot 6 weeks”

    Buyer and scope agent

    The buyer tells the agents what to change. The scope agent redrafts D3 as a 6-week pilot at the distribution center, measured on the last 4 weeks of warehouse data and still finishing by week 16, and marks it as a proposal on §2.1. Nothing in the SOW changes until the buyer accepts it.

    Scope agent: “Done, as a proposal: D3 is now a 6-week pilot … Nothing changes in the SOW until you accept it on §2.1.”

  7. 07Nine decisions

    Seven accepted, and the two legal notes sent to counsel

    Services procurement buyer

    Each note is accept, edit or reject with a reason code: “Matches our playbook”, “Matches the rate card”, “Rate exception requested”. The buyer accepts scope, rate, payments, the expense cap of $37,504 (8% of fees under the travel policy), a 10-business-day acceptance window, named key people and 30 days' notice. The IP clause and the missing data-protection terms go to counsel: legal wording is counsel's decision. The SOW now shows each change tracked, and its value falls to $468,800.

    Legal notes are never accepted in bulk: they go to counsel.

  8. 08The supplier replies

    Eight accepted, one counter on IP, inside the fallback

    Terms agent

    The buyer sends the redlines with a cover note the routing agent drafted. The consultancy's partner accepts eight changes but wants to keep the firm's own diagnostic toolkit. The terms agent reads the counter clause by clause and maps it to the playbook's IP positions: the company owns the deliverables, the supplier keeps its background IP with a perpetual, royalty-free license. That is the fallback position, so it is acceptable, with counsel's approval.

    Terms agent: “No walk-away position is touched.” Approving legal wording stays with counsel.

  9. 09One page, then the signature

    Counsel approves the wording; the budget owner signs

    Counsel and budget owner

    The routing agent builds one page for approvers (what we get, when, what we pay, what changed from the supplier's first version and why) and routes it by the delegation of authority: $468,800 sits in the $100,000 to $500,000 band, so counsel approves the legal wording first and the budget owner approves on the buyer's recommendation. Counsel approves with a reason code. The budget owner chooses the reason code “Within the budget line; deliverables measurable”, types a name and signs. The routing agent sends the SOW to the supplier for e-signature and creates the purchase order.

    The agents read, check, propose and route. Each acceptance, approval and signature is a person's, with a reason code.

  10. 10After signature

    The signed scope keeps working

    Scope agent and routing agent

    Change orders are tested against what was already bought: the design studio's change order asks $18,600 for 20 social assets, but 8 of them are the carousel cards already in §2.3 of its signed SOW. The agents propose $11,160 for the 12 new ones, and because the SOW would grow more than 25%, the budget owner and the category manager approve again. On Delivery, another supplier's $64,500 invoice is held: milestone 2 has no recorded acceptance.

    The routing agent releases no invoice without a recorded acceptance.

Who it’s for

The buyer, budget owner, counsel and vendor manager on one SOW review

Each seat's week with a services SOW, by hand and then with the agents.

Services procurement buyer
Works each SOW through
Before
Could not read each SOW against the MSA, the rate card and the playbook, so read the first page and hoped.
Now
Opens each SOW with the agents' notes beside each clause and a fix ready for each; asks and instructs them in plain words, and decides each change with a reason code.
Budget owner
Approves and signs
Before
Wanted one page: what is delivered, when, and what it costs.
Now
Approves one page built from the agreed SOW (three deliverables from the budget owner's own request, payments on acceptance, each change with its reason) and signs with a reason code.
Counsel
Decides legal wording
Before
Wanted to see only the clauses that moved off the playbook, and why.
Now
Gets only the legal notes, each with the MSA clause and playbook position behind it, and the supplier's counter mapped to preferred, fallback and walk-away.
Vendor manager
Watches delivery and invoices
Before
Saw change orders only after the money was already spent.
Now
Sees milestone invoices held until acceptance, late milestones with the service credit in the SOW, and overruns forecast from billing against progress.
The agents

The agents behind each margin note, and what each may not do

The SOW is read clause by clause against the MSA, rate card and playbook; each finding is re-checked before a fix is proposed, and people decide and sign.

Intake agent

Reads the SOW in Word, PDF or a scan, from the SOW inbox, an upload or a request; splits it into clauses and finds the MSA, rate card and request it belongs to; extracts value, billing model, term, roles, rates and payments.

  • Never edits the document
  • Stops on an unreadable page and asks for the native file; never guesses a value
Scope agent

Tests each deliverable for a measurable output, an owner, a date, an acceptance test and what is out of scope; rewrites failing ones from the requester's brief; checks acceptance and key people; compares change orders with the signed scope.

  • Never invents scope the request does not support
  • Asks the budget owner when the request is silent
Rate agent

Re-adds the price build-up, compares each role and rate with the MSA rate card, caps expenses under the travel policy and, on signed SOWs, compares billing with progress to forecast overruns.

  • Never accepts a rate above the card
  • Exceptions go to the category manager
Payment agent

Checks the upfront share against the playbook, reshapes the schedule so payments follow accepted deliverables and adds up to the fee, and computes service credits for late milestones.

  • Never moves a payment the budget owner has not seen
Terms agent

Compares IP, data, confidentiality, liability and termination with the MSA and the playbook's preferred, fallback and walk-away positions; looks for staff-augmentation and off-payroll signals; reads the supplier's reply and maps each counter to the playbook.

  • Never approves legal wording: each legal change goes to counsel
  • Proposes wording only from the clause library
Checker agent

Re-computes each finding from the clause and its sources without seeing the other agents' working; its agreement shows on each note.

  • Cannot remove a finding, only hold it
  • A disagreement goes to the buyer with both workings
Routing agent

Routes approvals by the delegation of authority and clause type, builds the one-page approval, sends for e-signature and creates the purchase order; after signature, watches milestones, acceptance, invoices and change orders.

  • Never signs
  • Never releases an invoice without a recorded acceptance
Buyer, counsel and budget owner

Accept, edit or reject with a reason; sign.

Ask in plain words

Instructions to the agents, and their cited answers

The agents are at hand on each screen. Ask about any clause, rate or invoice, or give an instruction. Each answer cites the SOW, the MSA, the rate card or the playbook, and nothing changes until a person accepts it. These answers use the sample data.

Why is 40% upfront a problem?

Because nothing has been delivered yet: $192,000 would leave on signature. Our playbook allows 10% mobilization and the rest on written acceptance; above 20% is a walk-away. I tied the other 90% to D1 to D3.

Make the pilot 6 weeks

Done, as a proposal: D3 is now a 6-week pilot at the distribution center, measured on the last 4 weeks of warehouse data, still finishing by week 16. Nothing changes in the SOW until you accept it on §2.1.

Which change orders repeat work we already bought?

One: the design studio's change order asks $18,600 for 20 assets; 8 of them are the carousel cards already in §2.3. I propose $11,160 for the 12 new ones.

Does finance need to sign?

No. $468,800 is in the $100,000 to $500,000 band: the budget owner approves and signs on the buyer's recommendation. Above $500,000 the divisional finance director would also sign.

The screens

The SOW with a margin, the rate card and the change-order test

From the working solution, on its sample data. Pick one to see it large.

TodayWhat needs the buyer today, ranked by due date with the agents' proposal ready on each, what is waiting on others, and the agents' conversation.
The SOW with a marginThe supplier's SOW clause by clause, the agents' notes level with each clause, the value, billing model, term and open checks on top, and the review team beside it.
Scope too vagueThe five-part deliverable test, the change-order risk from the company's own SOWs, and three deliverables rewritten from the requester's brief.
The rate card behind a noteEach citation opens its source: here the MSA rate card, with the Principal row and clause C.4 highlighted.
How the agents checkedThe proposed payment schedule, each step the agent took, its sources, its confidence and the checker's re-computation.
Ask and instructThe buyer asks why 40% upfront is a problem and tells the agents to make the pilot six weeks; each answer cites its source.
Changes tracked in the SOWNine decisions made, the value down to $468,800 and each accepted change tracked in the document.
The supplier's replyThe supplier's answer clause by clause, and the terms agent's read of its IP counter against the playbook's preferred, fallback and walk-away positions.
Approve and signThe budget owner's reason code, typed signature and confirmation, after counsel has approved the legal wording.
One page for approversWhat we get, when, what we pay and what changed and why, with the approval chain under the delegation of authority and the purchase order created.
Delivery of signed SOWsBilling against progress on each signed SOW, a milestone invoice held until acceptance, and the late-delivery credit in the SOW.
Change ordersA change order tested line by line against the signed scope, the amount for new work only, and how far the SOW has grown against the re-approval limit.
Rules and thresholdsUpfront share, rate tolerance, expense cap, acceptance window, notice, change-order limits, duplicate scope and when to ask a person.
Governance

Who decides what in SOW review, and the record behind it

Each note cites its passageEach value and each agent statement links to the SOW clause, MSA section, rate card row, playbook position or request sentence it came from, and opens with that passage highlighted.
A second agent re-checks each findingThe checker agent re-computes each finding from the sources without seeing the other agents' working. It cannot remove a finding, only hold it, and a disagreement goes to a person with both workings.
People decide, with a reason codeThe buyer accepts, edits or rejects each change with a reason code. Counsel decides legal wording, the category manager rate exceptions, and the budget owner approves and signs under the delegation of authority; above $500,000 the finance director signs too.
Agents do not sign or releaseThe agents read, check, propose, draft and route. They do not accept, approve, sign, send or release anything, and no invoice is paid before its milestone is accepted in writing.
Rules change only by approved proposalThresholds and playbook positions are versioned. A change is a proposal the Head of Procurement approves, and it applies to SOWs that arrive afterwards. Rate cards change only with the agreement they belong to.
A record that cannot be editedEach action by a person or an agent is on the audit trail with what it relied on, kept 7 years and read only, even for administrators. Internal audit exports an evidence pack per SOW.
Configuration

Playbook positions and the delegation of authority behind each review

What the agents flag and who approves are settings. A change is a proposal that the Head of Procurement approves, and it applies to SOWs that arrive afterwards.

SettingDefaultChoose from
Largest payment before a deliverable is accepted10%Your share of the fee, changed by approved proposal — the playbook allows up to 15% only where the supplier buys equipment or licenses for you, and walks away above 20%
Rate above the rate card allowed0%Any rate above the card goes to the category manager as an exception
Expense cap, share of fees8%From the travel policy, unless the SOW sets a lower cap
Shortest review window for acceptance10 business daysWith one rework cycle and acceptance in writing by the budget owner, as the playbook sets
Longest notice to end for convenience30 daysThe playbook walks away above 60 days
Re-approve a change order above10% of current value, or 25% above the signed value in allBudget owner and category manager approve again, as the playbook sets
Flag a SOW that repeats another by more than60%Compared with the company's signed SOWs
Ask a person when an agent is less sure than90%Below it, the agent asks a person; separately, the checker re-computes every finding
Connections

Where the SOW, its agreement and its invoices already live

SOW inboxWord, PDF and scans, as suppliers send them
Procurement intakerequests and briefs, the source for rewritten scope
ERPpurchase orders, invoices and payment holds
Vendor management systemworker roles and time sheets for time-and-materials SOWs
E-signatureapprovals and signatures
Document storeMSAs, rate cards, SOW versions and evidence packs
What it changes

Less overspend and faster approval from statement of work review

Each figure carries its label: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
50%
less overspend from off-card rates and change orders for work already bought
Average contract8.6% of value lost
Targethalf of it kept
target
100%
of SOWs signed with measurable deliverables and payments on acceptance
target
2days
from a SOW arriving to approval-ready, against nine days by hand
By hand9 days
With agents≈ 2 days

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” and “published” = published figures (WorldCC, ROI of Contracting Excellence — 8.6% average contract value erosion; SIA, VMS spend rises to $303B with increase in SOW, 2026 — 39% under SOWs). Names on the screens are sample data.

Questions

SOW review software, answered for services procurement leads

What is Statement of Work Review?

Statement of Work Review is SOW review software for services procurement. Seven agents read each services SOW before signature, check its scope, rates, payments and legal terms against the MSA, the rate card, the procurement playbook and the requester's brief, and propose a cited fix for each problem. The buyer works through the findings with the agents; counsel decides legal wording and the budget owner approves and signs.

How does it check rates against the MSA rate card?

The rate agent re-adds the SOW's price build-up and matches each role to its row on the rate card in force. Any rate above the card is flagged with the difference on the SOW's hours: in the working solution, a Principal at $295 against $260, $11,200 over 320 hours. A justified exception is sent to the category manager to decide.

Can it turn vague scope into measurable deliverables?

Yes. The scope agent tests each deliverable for a measurable output, an owner, a date, an acceptance test and what is out of scope. When one fails, it rewrites it from the requester's own brief, citing the sentence each new deliverable comes from, and asks the budget owner when the brief is silent rather than inventing scope.

Who decides on IP, data protection and other legal terms?

Counsel. The terms agent compares IP, data, liability and termination with the MSA and the playbook and proposes wording only from the clause library, but each legal change goes to counsel. When the supplier counters, the agent maps the counter to the playbook's preferred, fallback and walk-away positions so counsel sees what moved and why.

Does it flag staff augmentation written up as a SOW?

Yes. The terms agent looks for worker-classification signals such as supervision by your managers, your shift pattern or a single-person supplier. In the working solution it flags a labor SOW whose operatives report to the client's shift supervisors, and a UK single-director company that needs an off-payroll status determination before the start date.

What happens after the SOW is signed?

The same agents keep it honest. A milestone invoice is held until the acceptance is recorded, each change order is tested line by line against the signed scope, late milestones are flagged with the remedy in the SOW, and billing is compared with progress to forecast an overrun before the cap is hit.

Who can accept a change, approve the SOW or release an invoice?

Only people. The agents do not accept, approve, sign, send or release anything. The buyer decides each change with a reason code, counsel decides legal wording, the category manager rate exceptions, and the budget owner approves and signs under your delegation of authority. Each action is on a read-only audit trail.

What do you calibrate it on before our first SOW?

The Agentic Solution Engine builds and deploys it from your requirements and documents: your MSAs and rate cards, playbook, clause library, delegation of authority and a sample of signed SOWs. It goes live once each quality gate has passed. Set-up includes calibrating the agents on 20 of your signed SOWs. We will walk you through it on your own SOWs first.

Try SOW review
on a sample of your own SOWs.

We'll run Statement of Work Review on a sample of your own SOWs, against your MSAs, rate cards and playbook.