Procurement Foundations: Need, Specification and Value

Review questions

Integrated Summary: From Need to Comparable Specification and Value

This subject connects four decisions that should come before serious supplier comparison: What is the real need? How should it be expressed as measurable requirements and specifications? Should the organization buy at all, deliver internally, or use a hybrid route? How should price be separated from total cost, value and risk? These questions make procurement a value-management process rather than a purchase-order function.

Procurement is broader than transactional purchasing. It begins with the business need and stakeholders, moves through the route to the required outcome, market analysis, sourcing, evaluation and negotiation, and continues after selection into performance, relationship and risk management until the arrangement or asset ends. Recording receipt or matching an invoice may be important purchasing activities, but they are not the whole procurement process. When users, operations, finance and security want different things, conflicts, mandatory conditions, preferences and trade-off authority should be clarified before market engagement.

A need is not a product name. “We need three units of model X” states an assumed solution, while “we need additional peak-hour capacity” leaves room to test alternatives. Demand analysis uses data with visible assumptions. The simple average of 120, 140 and 160 is 140, but that does not prove next month’s demand if seasonality, inventory or business activity changes. Make-or-buy is not a price-only choice either; it weighs capability, capacity, speed, control of knowledge, flexibility, lifecycle cost, risk, dependency and data constraints. A temporary hybrid route may fit some facts, but different facts can change the decision.

Once the need is established, it is translated into requirements and specifications. A requirement states what must be achieved or constrained; a specification organizes these requirements for market use; an acceptance criterion defines how success will be verified; and a preference improves attractiveness without making a solution unfit if absent. “High-quality service” is insufficient. A performance threshold with a defined population and measurement start/end can be verified. Functional/performance specifications focus on the result, while prescriptive specifications define characteristics or methods. Neither is universally superior; use enough detail to protect the outcome and support comparison without unjustified market lock-in.

Price is not total cost of ownership. In the worked example, simplified TCO was 17,500 for offer A and 16,100 for B. B’s purchase price was 1,200 higher, yet its simplified TCO was 1,400 lower within the included items. That does not establish that B is “better,” because the calculation excluded discounting, tax, residual value, downtime and other elements, and it did not prove specification compliance, service quality or risk. In another exercise, C was 14,600 and D was 13,100, making D 1,500 lower despite the higher purchase price. The lesson is to state the calculation boundary rather than manufacture false precision.

Keep four decision lenses visible: direct price; TCO within a defined boundary; value as achievement of the required outcome relative to what the organization gives up; and risk as uncertainty that may affect performance, cost or continuity. Some risk effects may be estimated financially, but turning a risk into a number does not remove the need to show and manage it. If a lower-TCO offer fails a valid mandatory condition such as a critical start time, lower cost does not make it automatically acceptable. Check pass/fail conditions first, then compare value, cost and risk among eligible alternatives.

Use fictional cases or non-confidential data when applying this subject. If a specification becomes enforceable legal wording or a question turns on contract law in a particular jurisdiction, that sits outside this lesson and needs the appropriate qualified function. The logic to carry into the next subject is clear: define the need, test demand, decide the sourcing route, write measurable criteria, and use price, TCO, value and risk without collapsing them into one unexplained judgment.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1Which activity best represents a procurement decision rather than a purchasing transaction?
  2. Question 2What is the strongest starting point before comparing suppliers?
  3. Question 3What is the most appropriate action?
  4. Question 4Which statement about procurement stakeholders is most accurate?
  5. Question 5Which statement describes a need rather than jumping to a solution?
  6. Question 6Demand over three stable months was 120, 140 and 160 units. What is the simple average?
  7. Question 7Which factor set is strongest for a make-or-buy decision?
  8. Question 8What is the most reasonable next step?
  9. Question 9Which statement is closest to a performance specification?
  10. Question 10Which acceptance criterion is most verifiable?
  11. Question 11Which item should normally be treated as a preference rather than mandatory if it does not affect solution fitness?
  12. Question 12What is the best action before issuing the request for offers?
  13. Question 13In the example: 12,000 price + 600 installation + 900 training + 1,200 annual maintenance for three years + 400 end-of-life. What is simplified TCO?
  14. Question 14Which statement is correct if offer B has a purchase price 1,200 higher but simplified TCO 1,400 lower?
  15. Question 15What is the most accurate distinction among value, risk and TCO?
  16. Question 16Offer C has simplified TCO 14,600 and offer D 13,100. How much lower is D?