Threshold Blindness
Procurement thresholds shape the scope rather than the scope determining the threshold.
Procurement thresholds shape the scope rather than the scope determining the threshold. Requirements are artificially narrowed, phased, or split to stay under a threshold — excluding the requirements that would have pushed the total over.
Recognition signals
- Scope is explicitly sized to stay just under a procurement threshold. The estimated value lands at $240K when the next threshold is $250K. The number isn't a coincidence — it's the product of working backwards from the governance tier.
- "Phase 1 only" where Phase 2 is inevitable but not scoped. The programme needs the full scope to deliver value, but scoping it all would trigger a higher governance tier. Phase 1 is sized to the threshold, not to a logical delivery boundary.
- Requirements stripped to functional-only to reduce estimated value. Non-functional requirements, integration, data migration, and transition are excluded — not because they're unnecessary, but because including them pushes the estimate over the line.
- Direct engagement used for complex work that warrants competitive tension. The work is genuinely complex, but the governance overhead of a formal process makes direct engagement attractive. Complexity is reframed as urgency to justify the shortcut.
- Multiple small procurements from the same vendor for what is effectively one programme. Each engagement sits under the threshold independently. Together, they represent a programme-scale commitment with none of the programme-scale governance.
Structural cause
Why this happens
Procurement thresholds create step functions in effort and time. Going from $240K to $260K might change the process from "three quotes" to "full public tender" — adding months. The rational response for a time-pressured programme is to shape scope to fit the easier threshold. Nobody intends to cut corners; the threshold creates an incentive structure that produces it.
The mechanism is economic, not malicious. Each threshold represents a discontinuity in procurement effort. Below the line: weeks, a panel of three, minimal documentation. Above the line: months, public advertising, evaluation panels, probity advisers, standstill periods. The governance overhead is designed to protect the organisation from poor purchasing decisions — but the overhead itself creates an incentive to avoid triggering it.
The invisibility comes from the gap between the stated scope and the actual need. The procurement file shows a well-scoped Phase 1 engagement under threshold. What it doesn't show is the requirements that were excluded, the phases that will inevitably follow, or the total programme cost that nobody has calculated. The governance tier that was avoided was the one designed to catch exactly these risks.
Risk mapping
| Risk | Description |
|---|---|
| P5 | Threshold-driven scope manipulation — scope shaped to fit governance tiers rather than delivery needs |
Self-assessment
When to worry
- The scope was explicitly sized to stay under a procurement threshold
- Phase 1 was sized to avoid the next governance tier, not to a logical delivery milestone
- Requirements were stripped to keep the estimated value down
- Multiple separate procurements from the same vendor for what is effectively one programme
When you're OK
- Procurement threshold applied to total programme cost, not individual phases
- Phase boundaries align to delivery milestones with documented rationale
- Scope justification is delivery-driven, not threshold-driven
Related reading
- Specification Gap — stripped requirements are a Specification Gap created deliberately to stay under threshold
- Evaluation Theatre — when scope is artificially narrowed, the evaluation that follows is narrowed too
The corners cut to avoid governance become the delivery risks that governance was designed to prevent.
A procurement readiness assessment maps total programme cost against governance thresholds and identifies where scope has been shaped to fit process rather than delivery. 10fifteen — programme governance assessments.