Module v2.0 · Required
Scope the Need and Source the Market
Turn an ambiguous request into a shared, testable procurement scope before comparing supplier solutions.
Translate an operational problem into an outcome; separate must-have requirements from preferences; document assumptions, constraints, and acceptance evidence; write neutral supplier questions; run a scope-quality gate; and prepare an adopter-ready sourcing brief.
Start with the outcome
Define the operational result before choosing a supplier or solution.
A useful procurement request begins with the business outcome, service need, or operational problem. Describe who depends on the result, what is happening today, what must change, and what is explicitly out of scope. Avoid naming a preferred supplier or product until the need has been made understandable to someone outside the requesting team.
For example, a property manager may need fewer emergency HVAC callouts, a distributor may need more reliable pallet replenishment, or a manufacturer may need calibration support with documented turnaround. Each example starts with the operating result and then defines the service that can produce it.
- Write the current-state problem in observable terms
- State the desired outcome and who will use or accept it
- Define in-scope work, out-of-scope work, locations, quantities, and timing
- Name the decision owner and the people who must validate the need
- The need is understandable without insider context
- The desired outcome is observable or testable
- Scope boundaries and dependencies are visible
- A decision owner and affected stakeholders are named