The Acceptance Criteria Clause: What It Means and How to Negotiate It (2026)

What is an acceptance criteria clause? An acceptance criteria clause defines the tests a deliverable must pass before the customer is treated as having accepted it, and sets out what happens if it passes or fails. It answers the question every project eventually argues about: is this done, and good enough to pay for? The clause links completion to objective criteria rather than to opinion, and ties acceptance to the trigger for payment, warranties and the start of ongoing obligations. You see acceptance criteria most in software development, equipment supply, construction and milestone-based services. Without it, "acceptance" becomes a matter of who argues hardest: the supplier says the work is finished and wants paying, the customer says it is not and withholds payment. A clear clause replaces that fight with a test. This article is general guidance, not legal advice. Acceptance interacts with sale-of-goods, consumer and contract law that varies by jurisdiction, so adapt any clause to your deal and your law with a qualified professional. ## What a good acceptance criteria clause covers - The criteria. The objective, testable standards the deliverable must meet, usually in a specification or test plan.

• The test. Who tests, how, where, and over what period.
• The acceptance period. How long the customer has to test and respond.
• Pass or fail. What acceptance means, and what rejection means.
• Cure and re-test. The supplier's right to fix and re-submit, and how many times.
• Deemed acceptance. Whether silence or use counts as acceptance.
• Consequences. What acceptance triggers: payment, title, warranty start, go-live. ## Sample acceptance criteria clause wording Use this as a starting point and adapt the brackets. ``` ACCEPTANCE 1. Acceptance Criteria. A Deliverable is accepted when it conforms in all material respects to the Specification and passes the Acceptance Tests set out in Schedule [ ]. 2. Acceptance Testing. On delivery the Customer shall have [N] days (the "Acceptance Period") to carry out the Acceptance Tests. 3. Acceptance or Rejection. Within the Acceptance Period the Customer shall give written notice that the Deliverable is accepted, or is rejected with reasonable detail of the failures against the Acceptance Criteria. 4. Cure and Re-Test. If rejected, the Supplier shall correct the Deliverable and re-submit it within [N] days, and a new Acceptance Period applies. If it fails again after [N] cycles the Customer may [reject and recover sums paid for that Deliverable / accept with an agreed reduction]. 5. Minor Defects. The Customer shall not reject for minor defects that do not materially affect use; such defects shall be logged and corrected within [N] days without delaying acceptance. 6. Deemed Acceptance. If the Customer uses the Deliverable in live operations [other than for testing], or does not respond within the Acceptance Period after a reminder, the Deliverable is deemed accepted. 7. Effect of Acceptance. Acceptance triggers [the related Milestone payment], starts the warranty period, and does not waive the Customer's rights for defects not reasonably discoverable on test.

- **Acceptance period (clause 2).** Give the customer enough time to test properly, but bound it so the supplier is not left waiting forever.
- **Rejection (clause 3).** Require rejection to state the specific failures, so the supplier knows what to fix and cannot be rejected on a whim.
- **Cure and re-test (clause 4).** Give the supplier a fair chance to fix, but cap the cycles. After a set number of failures the customer needs a real remedy: a refund, a price reduction, or the right to walk away from that deliverable.
- **Minor defects (clause 5).** Stop the customer from rejecting a whole deliverable over trivial issues. Log and fix them instead.
- **Deemed acceptance (clause 6).** This protects the supplier from a customer who goes silent or quietly uses the work without accepting it. Pair it with a reminder so acceptance is not deemed by accident.
- **Effect (clause 7).** Be explicit about what acceptance triggers, and preserve the customer's rights for latent defects that testing could not reveal. ## Negotiation points **If you are the customer:** - Insist the criteria and test plan are agreed in detail, in a schedule, before work starts.
- Keep a real remedy after repeated failures, not just endless re-tests.
- Preserve rights for latent defects not discoverable on test.
- Resist a deemed-acceptance trigger based on mere passage of time without a reminder. **If you are the supplier:** - Pin the criteria down so acceptance is objective, not a moving target.
- Require rejection to cite specific, criteria-based failures.
- Include a minor-defects rule so you are not rejected over trivia.
- Include deemed acceptance for live use and for silence after a reminder, so payment is not held up indefinitely. ## Common mistakes to avoid - Vague criteria that turn acceptance into an argument.
- No acceptance period, so it is unclear when the customer must decide.
- No cap on re-test cycles, trapping the supplier in endless fixes or the customer in a broken deliverable.
- No deemed-acceptance rule, so a silent or using customer blocks payment forever.
- Rejection on trivial defects.
- Acceptance that silently waives all later defect claims. ## A note on jurisdiction Acceptance clauses are mainly a matter of drafting, but background law shapes them and it varies by jurisdiction. In many systems the law implies a right to reject goods or works that do not conform, and consumer-protection rules can add non-excludable rights for consumers. In India the contract runs under the Indian Contract Act, 1872, with the Sale of Goods Act, 1930 relevant to goods and the Consumer Protection Act, 2019 where a consumer is involved. In the UK, the Sale of Goods Act 1979 and the Consumer Rights Act 2015 are relevant. The key point is that a commercial acceptance clause can shape but not always exclude statutory rights, especially for consumers. Treat the interaction with sale-of-goods and consumer law as jurisdiction-specific and get local advice. Last verified October 2026. ## Keeping acceptance from becoming a dispute The acceptance clause is clean on the page. The mess comes later: which version of the spec was signed, what the test plan actually said, whether rejection notices cited real criteria, how many cure cycles have been used, and whether a deliverable was ever formally accepted. On a big project that history scatters across emails and trackers, and it is exactly what a payment dispute turns on. Drafting acceptance criteria, reviewing the risky versions and tracking the spec, the tests and the trail of notices can sit in one AI workspace tuned to how your company contracts, so the history a payment dispute turns on stays together rather than scattered across emails. [Adira](https://adiralaw.com) is one such workspace for acceptance terms and the milestones tied to them. This guide alone is enough to negotiate a fair acceptance criteria clause.