A specification no real vendor can meet ends up as a delay with a document number.
It usually arrives in one of three forms. Tolerances copied from another project, such as a humidity band written for a semiconductor micro-environment carried into an OSD suite that never needed it. A component named from a previous job, so only one supplier can comply and every other bid comes back full of deviations. Or a delivery date that assumes lead times the market no longer offers.
The cost shows up quietly. Bids return with long clarification lists. Nothing can be compared like for like. The specification is reissued, the tender runs again, and the program loses weeks before a single unit is ordered.
What works better:
- Write performance requirements with the test that proves each one, not a product description.
- Separate mandatory from preferred, clearly and in writing.
- Check the critical items with two or three real vendors before issue. A short conversation costs far less than a retender.
Design into procurement is one of the handovers that decides a project. We write specifications the market can answer, and we check them against the market before they go out.
What is the strangest requirement you have found in an inherited spec?




