Why "acceptable" is not a standard
Standards like "acceptable to the Client", "to a high standard", or "meets industry standards" feel like quality requirements but decide nothing. Acceptable to whom? Which industry standards? Who judges whether they are met? Each phrase simply defers the disagreement to a later moment, when the parties are already in conflict.
If a dispute comes, you end up arguing about what the words meant rather than about what actually happened. That is the weakest possible position to be in.
Measurable criteria turn opinion into fact
Compare "the software must be acceptable" with "the system must process 10,000 transactions per hour with an error rate below 2% during load testing under the protocol in Appendix B". The second is testable. Either the throughput was hit or it was not; either the error rate was under 2% or it was not. The argument becomes a question of fact the test answers, not a battle of opinions.
Measurable criteria do double duty: they tell the supplier exactly what to build, and they give both sides an objective record if quality is later challenged.
Acceptance criteria are an evidence trail
The deeper point is that acceptance criteria are not only about defining quality - they are about making a future claim provable. A measurable criterion plus a defined test produces evidence: a result you can point to. A vague standard produces only competing recollections.
TCS v DBS is the cautionary tale. Across a huge IT contract, fundamental questions about performance standards remained unclear, and when the parties fought over quality and delay, neither could adequately prove its case. The criteria were not built to generate provable facts.
What to specify
Tie each material deliverable to a concrete acceptance criterion: a performance figure, an error or defect threshold, a defined test or protocol, and the conditions under which the test is run. Where a deliverable is qualitative, find a proxy you can measure, or a defined sign-off against a specification, rather than leaving it to "satisfaction".
Put the test protocol in a schedule so both sides know in advance how acceptance will be judged. The goal is that, on the day, acceptance is a measurement, not a negotiation.
Criteria are only half the mechanism
Measurable criteria tell you whether the work passed. They do not, by themselves, tell you what happens next - who records the result, who signs off, what happens on failure, and what notice unlocks a remedy. That is the acceptance procedure, and it matters just as much, as the companion guide explains.
In review, check that acceptance criteria are measurable and that they connect to a procedure and a set of remedies. A criterion with no procedure behind it is a standard you may not be able to enforce.
Use at the desk
Practical checklist
- Replace "acceptable", "high standard", and "industry standard" with measurable criteria.
- Tie each material deliverable to a figure, a threshold, or a defined test that passes or fails.
- Set out the test protocol and conditions in a schedule, agreed in advance.
- For qualitative deliverables, use a measurable proxy or sign-off against a specification.
- Connect acceptance criteria to a documented procedure and to remedies.
- In review, treat a vague acceptance standard as a future dispute and push for measurability.
This guide is informational only and is not legal advice. It does not replace advice from licensed counsel on the facts of a specific transaction.
Product demo
Use the guide for context. Use Veqtor for the Word documents.
Watch Claude compare negotiation drafts and create a separate Word document with proposed tracked changes.
See Veqtor work with Word redlines