An outcome-based specification defines the result a supplier must achieve rather than prescribing every method used to produce it. It gives the supplier room to design the solution while holding it accountable for measurable performance.
What should the specification contain?
- Business objective and intended users
- Required outputs and service conditions
- Measurable acceptance criteria
- Constraints such as safety or interoperability
- Evidence and testing requirements
- Remedies for non-performance
Outcome-based vs. prescriptive specification
A prescriptive specification tells the supplier how to perform the work or which design to use. An outcome-based specification describes what must be achieved. A hybrid may prescribe critical controls while leaving other design choices open.
When is it useful?
The approach can encourage innovation where suppliers understand the solution space and the buyer can measure results. It is less suitable when outcomes are ambiguous or when law, safety and compatibility require a specific method.
How should performance be measured?
Use clear baselines, units, measurement periods, data sources and acceptance thresholds. Distinguish the supplier's controllable performance from external factors and define how disputes will be resolved.
What are the main risks?
Weak definitions can produce technically compliant but commercially poor results. Buyers should test whether every outcome is observable, attributable and enforceable before the request is issued.
