Everyone wants outcome-based

Outcome-based contracting is the most requested model in services procurement and the least successfully written. Everyone wants to pay for results rather than effort. Very few produce a contract that does it.

The reason is that an outcome only functions commercially if it is measurable, and making something measurable is the work most authors skip. So the document says "the supplier will improve customer retention" and gets filed as outcome-based. Improve by how much, against what baseline, over what window, attributed to whom. Without those, "improve" is an aspiration with a payment attached.

What follows is reliable. The outcome cannot be measured, so it cannot anchor payment, so payment quietly reverts to days worked and deliverables produced. The contract sold internally as outcome-based runs as time and materials behind a more ambitious cover page. The organisation took on all the complexity of an outcome model and captured none of the benefit. PMI traces 47% of project failures to poor requirements management, and an outcome that was never defined is requirements failure in its purest form.

A working outcome model needs the outcome as a number, a baseline to measure change against, a window of assessment, and an explicit boundary around what the supplier is and is not accountable for, because outcomes always depend partly on forces outside their control. These are not things you reach for spontaneously at the keyboard. They are things you assemble from definitions made once and applied with discipline. It is the hardest of the four engagement types to write, and the one that punishes bespoke authoring most, because there is nowhere for an undefined outcome to hide once payment depends on it.

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. An outcome you cannot measure will not fit a field that asks how it is measured.

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.