Where SoWs go to die
Procurement writes it, legal edits it, delivery ignores it. Three functions, three versions of the truth, no single owner. The bad SoW is rarely a legal failure. It is an organisational one, and it is built from bespoke authoring at every step.
Follow a document through a large organisation and the decay is visible. Procurement drafts something workable. Legal strips out anything that reads as a firm commitment and adds qualifiers that protect the organisation in the abstract. By the time it reaches the delivery team who will run the work, it protects everyone and describes nothing, so delivery keeps a private spreadsheet of what was actually agreed. The signed contract becomes a document of record that no one uses to run the project.
Now there are two scopes: the one that was signed and the one being delivered against. Each is authored, and re-authored, by a different function optimising for its own concern, and they diverge a little more every week. When a dispute lands, legal reaches for the signed version and delivery reaches for the spreadsheet, and the distance between them is the size of the problem.
No one in the chain is doing a bad job. Procurement buys, legal protects, delivery delivers. The failure is that no single structure travels through all three, so each function reinvents its portion and the document as a whole is optimised for nothing.
A structure that survives the handoff changes this. When all three functions work in the same defined fields, edits happen inside the structure instead of degrading it, and the signed document and the delivered document are the same document, because there was only ever one.
The instinct behind most weak SoWs is to write each one fresh. Every freshly authored scope is a novel document that no one has reviewed, priced, or tested against delivery, and that novelty carries a commercial cost the buyer rarely sees until it arrives. The standard inverts the instinct. It begins from a baseline the enterprise has already approved, eleven sections and fifty-one elements, and permits variation only where the work genuinely differs. The schema turns that structure into data, the substrate AI needs to extract obligations, score risk, and govern a portfolio, rather than generate one more unreviewed draft. One approved structure travels through procurement, legal, and delivery, so three functions stop authoring three contracts.
The launch
statementofwork.org launches on 10 August at the World Commerce and Contracting APAC Summit in Sydney. The full standard and engagement types, and the first learning and certification modules go live the same day. You signed up before any of it was public, which means you see it first.