Three clauses decide whether a specification is useful or merely long: the one that says what the product must do, the one that says how it will be checked, and the one that says what happens when it fails. A specification that states all three can be enforced; one that omits any of them produces a dispute about interpretation rather than a decision about the delivery.
This is a field Q&A on writing specifications for public contracts. It covers prescriptive versus performance language, the brand-lock problem, what documentation can reasonably be required, and the clauses that survive a challenge.
Prescriptive versus performance language
The distinction is useful and frequently misapplied. Prescriptive language states how the product must be made or from what; performance language states what the product must achieve. Both are legitimate, and the choice should follow from what the buyer can actually verify.
Where a fleet can measure an outcome, performance language is usually better, because it allows different routes to the same result. Where the outcome is difficult to measure within a contract term, prescriptive language for the properties that determine it is the practical alternative. The failing specification is the one that prescribes a process the buyer cannot check while leaving the properties it can check unstated.
Avoiding brand-locked specifications
A brand reference is the most common way a public specification narrows competition without intending to. The usual defence is that a specific product is known to work, which is a legitimate concern and can be addressed without naming it.
Three drafting practices keep the field open while protecting the requirement. State the properties that make the known product suitable, with the values and the test methods. Add an equivalents clause that says how an alternative will be assessed and on what evidence. Keep any genuine single-source justification on the record, so that a brand reference is a documented decision rather than a habit. Standards for material values and their test methods are published by ASTM International and ISO.
Certification and documentation demands
Documentation requirements are where specifications most often overreach, and the cost falls on the buyer as well as the bidder. A requirement that a supplier produce a record it does not generate either excludes qualified offers or produces paperwork assembled to satisfy the clause.
The workable test is whether the record exists in the normal course of production and whether it tells the buyer something it will use. Under that test, the batch reference, the dimensional record for named dimensions, and the material declaration with its standards all qualify; a general quality assurance statement does not.
Testing clauses that stand up
Two clauses matter here and both are short. The first names the tests, values and tolerances, with the units, so there is no ambiguity about what will be measured. The second fixes the method when a lot is disputed: who measures, with what, and whose instrument applies. Without the second, two honest measurements of the same lot can disagree, and the disagreement is resolved by argument rather than by evidence.
A clause that states a value without a tolerance, or a requirement without units, is the one that fails in practice. Each omission means a bidder has to assume, and assumptions differ.
The units and measurement problem
Units are the least interesting clause and the one that causes the most avoidable failures. A specification written in one system and produced in another produces parts that are close but wrong, and the error is usually discovered at fitting rather than at delivery.
State the units explicitly, state the conversion basis for any dimension that is quoted in both, and state the inspection method with its resolution. Where a dimension is critical, quoting it in both systems with the conversion stated removes an ambiguity that is otherwise silent.
Reasonable delivery and packaging requirements
Delivery clauses overreach when they miss the product.
That happens where a delivery window is tied to the buyer’s convenience with no allowance for production, or where packaging requirements add cost without protecting the goods.
The clause that pays is the marking requirement: each package identified with the batch reference and the item, so that receipt, inspection and use can be linked. That single requirement supports the testing clause, the acceptance process and any later claim.
Currency and payment provisions
Currency and payment terms are commercial rather than technical, and they interact with the specification in one way that matters. A supplier priced in a foreign currency and paid on a schedule that depends on a long inspection period carries a financing cost, and that cost appears in the price. Where the inspection period is longer than it needs to be, the fleet is paying for it.
State the currency, the conversion basis if the price may be paid in another, and a payment trigger tied to acceptance rather than to shipment. Those three remove most of the disputes that arise between finance and procurement after an award.
Records retention
Retention requirements should match the period over which a claim or an audit could arise. A record kept for the life of the asset supports a warranty question; the same record discarded after delivery does not. Nothing about that overreaches, and it is worth stating explicitly rather than leaving to a default.
The buyer’s own obligation to retain its receiving records is worth mirroring in the contract. Where a supplier’s record is retained and the buyer’s is not, a dispute has evidence on one side only.
Review before publication
Three checks catch most overreach before it goes out. Whether each requirement can be assessed by a receiving inspector, so the clause is enforceable. Whether each requirement is met by more than one likely bidder, so the field is open. And whether each requirement is tied to something the fleet needs, so the clause is doing work rather than copying precedent from a template.
The third check is the one that reduces documents. Requirements inherited from a previous specification often survive because nobody asked whether they still applied. The receiving checks that apply a specification in practice are described on the delivery inspection page.
What compliance costs the honest bidder
Every additional requirement costs a compliant bidder time and money, and those costs appear in the price. A specification that asks for three records costs less to comply with than one that asks for nine, and where the extra six are unused the fleet has paid for them anyway.
That is the practical argument against overreach: it narrows the field and raises the price without improving the product. Equipment and material standards that support the clauses are maintained by SAE International, ISO and ASME, and public sector procurement practice is published by the National Association of Counties and the American Association of State Highway and Transportation Officials.
SENTHAI manufactures plow edges, wear plates and carbide inserts in Rayong, Thailand, and issues each lot with the batch reference, dimensional record and material declaration a public specification typically requires, which is what allows a compliant bid to be assessed at delivery rather than on paper. Specification clauses that need confirming against a sample record can be raised through the contact page, and the wider clause set is described on the municipal bid specification page and the tender specification page.
FAQ
Should a government specification be prescriptive or performance based?
Prescribe what has to fit and perform on the machine, and leave the material route open where more than one can meet it. A specification that prescribes the process as well as the outcome narrows the field without improving the product, and one that prescribes neither cannot be evaluated.
How do you avoid writing a brand-locked specification?
By naming the measurable properties and the test methods instead of a manufacturer’s designation, and by including an equivalents clause that states how an alternative will be assessed. Naming a brand is defensible only where no other product can meet a documented requirement.
What documentation can a public buyer reasonably demand?
Records the supplier already produces: the batch reference, the dimensional record for the dimensions named in the specification, and the declaration of the material values with the standards applied. Demanding records a supplier does not generate either excludes qualified bidders or produces paperwork that means nothing.
What makes a testing clause enforceable?
A named method, a named instrument resolution, and a stated consequence for failure. A clause that requires testing without specifying the method cannot settle a dispute, because both parties can measure honestly and reach different conclusions.
Send the clauses you intend to publish and the patterns involved. The SENTHAI engineering desk will confirm which requirements can be met and which records will travel with each lot.