Two buyers, two purchases, two disasters — in opposite directions. Their story explains better than any definition why the specification is the most underrated document in procurement. The video tells it in three minutes; here it is in two acts.
Act one: the purchase that said too little. A site manager needs pumps and the requisition says just that: “some pumps”. The buyer, in good faith, finds a great price. What arrives is the wrong size, in the wrong material, unsuitable for the fluid it should move. Now everyone is in a meeting: the supplier insists he delivered exactly what was ordered — and he is right. With no specification, there is no yardstick; nobody can even say, formally, that the goods are wrong. Weeks lost, money burned, relationship strained.
Act two: the purchase that said too much. Another buyer, scarred by act one, swings to the other extreme. Her specification prescribes everything: an aerospace-grade alloy for a garden-variety application, tolerances no one will ever measure, and — the classic move — one brand name, “or equivalent”. Half the market does not bother to bid; the other half prices in every gold-plated requirement. She gets exactly what she asked for, at a price nobody wanted to pay, from the only two suppliers left in the race. This failure is quieter than the first, because over-specification punishes you invisibly: in the offers that never arrive.
The moral. A good specification is the narrow path between the two acts: a clear description of what you are buying — what it must do, the quality and standards it must meet, quantities and tolerances, and how conformance will be checked. Where possible it speaks in performance terms, saying what the item must achieve and letting suppliers propose how, so the market can surprise you. And it contains everything the need requires, and nothing more. Written that way, it does two jobs at once: it tells suppliers what to offer, and later it becomes the yardstick every delivery is checked against.
