---
title: "Price the acceptance work before committing a tender"
description: "Connect acceptance tests, buyer decisions, defects and retesting to delivery cost and payment dates before approving the tender price."
canonical: "https://zephior.com/insights/define-acceptance-before-pricing-a-tender"
last-updated: 2026-09-06
---

# Price the acceptance work before committing a tender

> Connect acceptance tests, buyer decisions, defects and retesting to delivery cost and payment dates before approving the tender price.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-06; updated 2026-09-06. 17 minute read.

## Definition

Before pricing a tender, define acceptance as a source-backed decision about a particular deliverable, supported by specified evidence and made through the contract’s stated procedure. Record the required condition, test method, prerequisites, reviewer, decision period, defect treatment and consequences for the relevant milestone. The work product is an acceptance-to-price record: a reproducible test and decision plan with costed preparation, review support, correction scenarios and dated payment inputs. It supplies the acceptance assumptions to a funding forecast; it does not replace that forecast or create new contractual rights.

## Problem

The estimate ends when the system is installed. The buyer’s draft requires a witnessed test, an evidence pack, review by a separate authority and correction before the milestone can be certified. The supplier has priced installation and one demonstration, but has neither booked the test environment nor allowed for another review cycle. A nearly complete deliverable can therefore keep people and equipment on the project while the largest invoice remains unavailable. Adding an unexplained contingency percentage leaves the underlying promise unresolved.

## Point of view

Price the route to a supportable acceptance decision, including a failed attempt. Begin with the issued terms rather than a preferred house protocol. This dossier focuses on what must be proved and what happens when proof fails; the related payment guide owns the full dated funding calculation. All organisations, thresholds, costs and timelines in the examples are fictional. Sources were checked on 6 September 2026. Legal applicability, deemed acceptance and remedy effects require qualified review of the actual contract. No analysis here authorizes a test on live systems, a buyer notice, acceptance of defective work or a change to a submitted offer.

## Decide what the buyer is accepting

An installation task, an accepted deliverable and an achieved payment milestone can cover different things. A server may be installed while its access controls remain untested; the technical deliverable may pass while the operating manual needed for the milestone is missing. Read the scope, implementation schedule, testing provisions and price schedule together. Write the acceptance unit in ordinary language, with its version, location and excluded work, before estimating how to demonstrate completion.

Use a stable identifier for each unit. A four-site rollout might have four site decisions and one integrated service decision, or a single decision covering everything. The project plan’s work breakdown does not establish those rights. Record whether partial acceptance is expressly available and which payment, operational start or subsequent test depends on it. If the issued pack is inconsistent, preserve both clauses and seek a permitted clarification; do not choose the interpretation that releases cash earlier.

Separate the consequences as well. Approval of a design, receipt of equipment, authorization to operate, technical acceptance, final completion and release of retention need not happen together. Check which event starts support, transfers a specified risk or changes access responsibilities. A certificate can have a limited purpose while defect remedies survive. Ask the legal reviewer to settle that effect rather than allowing the estimating spreadsheet to turn a convenient date into a legal conclusion.

The England and Wales Model Services Contract, combined schedules version 2.2A, distinguishes Test Certificates from Milestone Achievement Certificates in Schedule 10. Other implementation tasks can be needed for a milestone, and certificates do not remove the supplier responsibilities identified there. Inspect the tailored contract before relying on that model structure.

**Minimum record for one acceptance unit**

| Record field | Evidence to retain | Pricing consequence |
| --- | --- | --- |
| Object and version | Exact scope, release, site and source clause | Work and evidence belong to a bounded output |
| Success criterion | Threshold, measurement method and exceptions | Tests can be estimated and challenged |
| Entry conditions | Data, environment, predecessor approvals and notice | Waiting and preparation are visible |
| Decision procedure | Reviewer authority, receipt proof and applicable clock | Completion and decision dates remain separate |
| Failure route | Severity, correction, retest and dispute rules | Additional work has an explicit basis |
| Commercial link | Milestone, invoice condition and surviving duties | Finance receives traceable inputs |

## A pass rate needs a population and a failure rule

For each requirement, identify the evidence that would let an authorized reviewer decide whether it is met. A functional criterion may need a scripted demonstration with inputs and expected outputs. A performance criterion needs a workload, duration, measurement point and treatment of exceptions. A documentation requirement needs a defined content list and usable format. Keep subjective review explicit: an approval based on editorial judgment cannot be presented as a numerical pass simply because the supplier prefers measurable criteria.

Define the population before the percentage. If a migration test checks record validity, state the source snapshot, record count, rejected records and reconciliation rule. If sampling is permitted, retain the selection method and limits of the conclusion; a sampled result does not certify every untested record. Missing tests need their own status. They cannot disappear from the denominator or be counted as passed because the relevant environment was unavailable.

Fictional Fenwick Records tests 10,000 imported records. Its issued protocol requires at least 99.5% to satisfy the specified structural validation and separately requires no unresolved critical access-control failures. The structural result is 9,980 valid records, or 99.8%, but three access-control cases fail the critical rule. The first threshold passes; the deliverable still fails the combined acceptance conditions. The 20 structurally invalid records remain recorded for treatment under the protocol. Neither a rounded score nor a change of denominator closes the critical defects.

Price the production of that proof. Include preparation of permitted test data, environment setup, instrumentation, internal checks, witness support and an evidence pack that another reviewer can inspect. Preserve configuration and version information so the result can be reproduced. Use authorized synthetic or appropriately controlled data where suitable. A bid assessment does not grant permission to copy customer records into a demonstration, expose credentials or run disruptive tests against production.

## Budget for the handoff to the person who can decide

The supplier’s test lead and the buyer’s witness may both agree that testing went well while neither has authority to issue acceptance. Identify the decision maker or contractual role, the evidence recipient and any required delegate. Check whether security, business operations and technical approval are parallel inputs or sequential prerequisites. Ask for the process through the permitted clarification route if the pack names only “the customer” and no workable decision path.

Then identify what starts review: a readiness notice, an agreed test appointment, delivery of a complete report or another specified event. Record the applicable calendar, receipt method, suspension conditions and restart rule after correction. The team’s five-day allowance for compiling evidence cannot be hidden inside a buyer’s ten-day review period. Conversely, do not add a new waiting period where the contract requires a decision without it. Keep the clause and the planning allowance in separate fields.

For a German work contract within its scope, BGB §640 distinguishes minor defects from grounds to refuse acceptance and sets conditions for deemed acceptance after a deadline. Consumer notice and known-defect reservation provisions also matter. It is not a general rule that silence, delivery or use accepts every service. Obtain advice on the applicable mechanism.

Buyer dependencies deserve the same precision as supplier tasks. Name the required environment, dataset, connection, participant or decision and its need date. Model the consequence if it is absent, while keeping entitlement to time or money separate from operational delay. A dependency note does not amend the contract or automatically relieve the supplier. The record should show what can continue, what must wait and which authorized notice or clarification would be needed.

## One failed attempt can add work and restart review

Use the issued defect categories, including who assigns severity and who resolves a classification dispute. Distinguish a defect against the agreed requirement from a new feature request, a test setup error and an unavailable prerequisite. The same observed failure can lead to different actions depending on its cause, but do not assert buyer responsibility before the evidence supports it. Retain the failed result, diagnostic evidence, classification and approval of the correction plan.

The French CCAG-TIC 2021, Article 34, separates admission, adjournment, admission with a price reduction and rejection. Its adjournment route gives a fresh verification period after corrected performance is presented again. These provisions matter only with the relevant incorporation and departures; they do not supply a universal retest clock or a bidder’s choice of remedy.

Fenwick’s fictional plan has test readiness on day 60, four elapsed days for tests and evidence, then six elapsed days for the buyer’s decision. Successful first-pass acceptance is therefore day 70. Assume the critical defects are confirmed at that decision. Correction takes five further days, a complete retest takes four, and the specified renewed review takes six. Acceptance in this successful second-attempt scenario is day 85. All durations and the continuous-calendar convention are stated teaching assumptions, not statutory limits or a promise that every defect can be corrected in five days.

Check what the retest actually repeats. A localized fix may still require regression tests across permissions or interfaces. Reusing a passed result needs a supported configuration and dependency argument, not an estimate-saving assumption. Equally, do not charge the entire original delivery again when only a defined subset must be repeated. Further failures, disputed severity and an unavailable second review slot need separate cases if material; one successful retest is not a worst-case ceiling.

**Fenwick scenario, elapsed days from a common project origin**

| Event | First attempt succeeds | One correction and retest |
| --- | --- | --- |
| Ready for specified testing | 60 | 60 |
| Tests and evidence complete | 64 | 64 |
| First buyer decision | 70, accepted | 70, critical defects block acceptance |
| Correction complete | Not needed | 75 |
| Retest evidence complete | Not needed | 79 |
| Acceptance in the modeled case | 70 | 85 |
| Assumed cash receipt for the affected milestone | 100 | 115 |

## Carry both the extra £13,780 and the later receipt

For this single Fenwick retest case, correction needs 64 additional paid hours at £85, and retesting with evidence preparation needs a separate 24 hours at the same rate. Keeping the dedicated test environment for the additional 15 elapsed days costs £420 per day. The resulting incremental delivery cost is £5,440 plus £2,040 plus £6,300, or £13,780. These are extra costs beyond the priced first attempt; the two labour allocations do not overlap and the environment rate contains no labour.

The case assumes a £180,000 milestone receipt 30 elapsed days after acceptance, including its reviewed invoice process. It moves from day 100 to day 115. This is an explicit cash forecast assumption, not a statement of a UK or other statutory payment period. The £180,000 has been delayed, not added to cost or permanently lost. Pass the revised receipt date and dated incremental outflows to finance’s full funding forecast. Do not call £13,780 the project’s peak borrowing need.

Check for buyer costs and contractual remedies before approving the allowance. Where incorporated and applicable, FAR 52.246-4 permits required reperformance of nonconforming fixed-price services without an increased contract amount, and addresses price reduction where reperformance cannot correct defects. It also specifies consequences for failure to act promptly. Read the actual clause and agency deviations; this is not a universal cap on inspection or failure exposure.

Fenwick’s arithmetic excludes financing, tax, buyer-charged retest costs, service credits, further failures and any extended live-operation duties. Record whether each is inapplicable, already costed elsewhere or unresolved. If live service starts before final acceptance, check who supports it and whether those staff can also correct defects. A contingency must have a coverage statement: which events it funds, what it excludes and which reviewer accepts the residual exposure.

**Incremental Fenwick costs for the modeled second attempt**

| Input | Calculation | Additional cost |
| --- | --- | --- |
| Correction labour | 64 hours × £85 | £5,440 |
| Retesting and evidence labour | 24 hours × £85 | £2,040 |
| Dedicated environment extension | 15 days × £420 | £6,300 |
| Incremental delivery total | £5,440 + £2,040 + £6,300 | £13,780 |
| Affected £180,000 receipt | Day 115 instead of day 100 | 15-day delay, not a £180,000 cost |

## Acceptance with open items needs its own commercial reading

An agreed open-items list can let a project proceed while preserving correction duties. Record the exact permitted state, outstanding defects, completion dates and consequences of missing them. Check whether the resulting certificate authorizes invoicing, operational start, both or neither. The supplier cannot replace a blocking defect with a “minor issue” label simply to reach the milestone. If the authority has discretion, a scenario may model its exercise but the base commitment needs an approved evidential basis.

Partial acceptance also needs a defined unit and consequence. Three completed sites do not automatically unlock three quarters of a payment due only on integrated acceptance. A proposed split must preserve the buyer’s required functionality and follow an allowed procurement route. Model the issued collective condition first, and label the split as an unapproved alternative until it is validly agreed. Reduced concentration of payment does not remove integration work or give the bidder permission to exclude the remaining site.

Within its German work-contract scope, BGB §641 links remuneration to acceptance and addresses separately priced parts where partial acceptance is provided. It also permits withholding an appropriate amount for defects under its conditions. Acceptance therefore does not always mean that every euro is immediately collectible. Have counsel and finance determine the actual payment right and deductions.

Keep a price reduction apart from correction cost and payment delay. If the buyer validly accepts a defect with a reduction, establish what obligation, if any, remains and whether other remedies survive. Do not automatically add full correction and the same defect’s agreed reduction if the reviewed branches are alternatives. Do not automatically remove correction either. The executed decision and governing terms determine the result; commercial preference cannot substitute for that decision.

## Give price approval a testable acceptance record

Put the record in front of the people who will deliver the promise. The test lead confirms method, evidence and facilities. Delivery confirms resources, dependencies and realistic correction capacity. Commercial and finance confirm cost placement, remedy scenarios and payment inputs. The contract reviewer resolves legal meaning and permissible departures. Record a named owner and approval scope for each conclusion; one general “approved” cell cannot show which unresolved interpretation was accepted by whom.

An unclear criterion needs a specific question. Cite the issued clause, identify the undecidable condition and explain the affected evidence or work. A useful question asks whether the required review covers the submitted configuration at a defined workload and what evidence starts the decision period. It does not send the buyer a private margin floor or assume a right to negotiate after selection. If a mandatory obligation remains unsupported, hold release or escalate a no-bid decision through the supplier’s authority process.

Once a permitted clarification is issued, update the test plan, delivery schedule, cost model and affected answers together. Check the final PDFs, price workbook and portal declarations, not only the internal register. Preserve the source, approval, version and unresolved exclusions. Reopen the record if an addendum changes the acceptance unit, defect threshold, reviewer, environment or payment link. A later internal change cannot amend the submitted offer.

An assistant can extract authorized clauses, draft the record, compare criteria, flag missing evidence and calculate disclosed scenarios. It must preserve unknowns and route disputed legal or technical conclusions to the responsible person. Accessing restricted data, booking resources, sending notices, changing a buyer-facing commitment, signing a certificate or submitting the bid needs separate authority. Completion of this task means the acceptance assumptions are inspectable and supported enough for the price decision, with remaining holds visible.

## Useful outcomes

- Each acceptance decision has an identified object, source and reproducible proof.
- Preparation and review support are included in the delivery estimate.
- Defect severity and retest rules produce explicit schedule and cost cases.
- The payment model receives reviewed dates rather than a guessed sign-off month.
- Unresolved criteria or unavailable reviewers reach an authorized bid decision.

## Workflow

1. **Identify the acceptance unit.** Resolve the deliverable, site, release or service period to be accepted, the controlling terms and the milestone that depends on that decision. Keep collective and independently acceptable work separate.
2. **Specify the proof.** Connect each criterion to a test method, dataset, environment, expected result and retained evidence. Mark unknown thresholds or discretionary judgments for the appropriate reviewer.
3. **Confirm the decision process.** Identify prerequisites, notice, witnesses, evidence receipt, authorized decision maker, review clock and the effect of silence. Separate the issued rule from internal scheduling assumptions.
4. **Cost a failed attempt.** Apply the actual defect categories and correction route. Estimate additional people, facilities, evidence preparation, retesting and any recoverable buyer costs without counting the same work twice.
5. **Trace the commercial consequences.** Move only the milestones, operational duties and receipt assumptions affected by the acceptance decision. Keep price reductions, cash delays and surviving obligations distinguishable.
6. **Release the supported position.** Obtain delivery, test, commercial and legal approvals. Reconcile permitted clarifications with the final plan and price; retain an unresolved hold where the bid cannot support mandatory acceptance terms.

## Key decisions

- What precise output must be accepted before this milestone is achieved?
- Can two competent reviewers reproduce the same result from the proposed evidence?
- Which defects block acceptance despite an otherwise high pass rate?
- Who can make the decision, and what starts or restarts their review period?
- Can an unaffected part be accepted and paid without the failed part?
- Which cost and date assumptions remain unsupported at price approval?

## Risks

- A successful demonstration is mistaken for contractually sufficient evidence.
- A percentage score conceals a critical failed requirement.
- An absent buyer reviewer is treated as automatic consent without a legal basis.
- A retest resets more work and review time than the estimate allows.
- Partial use is assumed to establish partial acceptance and invoice rights.
- A price reduction is treated as permission to leave a mandatory defect unresolved.

## Metrics

- Acceptance units with source-linked criteria and decision authority
- Test prerequisites secured by the required date
- Priced hours for evidence production and review support
- Added cost and elapsed time for each supported retest scenario
- Payment value dependent on a shared acceptance decision
- Unresolved acceptance interpretations at bid release

## Frequently asked questions

### Does a successful demonstration establish acceptance?

Only if it satisfies the actual acceptance procedure and required authority. A demonstration may be one test among several, and a passed test may still leave evidence, documentation or other milestone prerequisites outstanding.

### Should the price include unlimited retesting?

Read the obligation first. Estimate supported failure scenarios and identify exclusions and residual exposure. One funded retest is an estimating assumption, not a contractual limit on the duty to correct. Escalate an obligation the delivery model cannot support.

### Can the bidder treat buyer silence as acceptance?

Only where the applicable contractual or legal mechanism supports that conclusion and its conditions are met. Record the trigger, notice, deadline and effect, then obtain the appropriate review. An unanswered email alone is not a sufficient analysis.

### Is a delayed milestone receipt an extra delivery cost?

The delayed principal is a timing change, not automatically an expense or lost revenue. Additional labour, facilities and financing may cost money. Keep those amounts separate and send the dated changes into the full cash forecast.

### Can an agent approve the acceptance criteria for submission?

It can prepare comparisons and calculations within authorized access. Technical feasibility, legal effect and commercial commitment belong to the designated approvers. External notices, live tests, contractual acceptance and bid submission require separate authority.


## Primary sources

- [Model Services Contract, combined schedules v2.2A, Schedule 10](https://www.gov.uk/government/publications/the-model-services-contract-schedules-england-wales), UK Cabinet Office and Government Legal Department
- [BGB §640: acceptance of a work](https://www.gesetze-im-internet.de/bgb/__640.html), German Federal Ministry of Justice and Federal Office of Justice
- [BGB §641: remuneration becoming due](https://www.gesetze-im-internet.de/bgb/__641.html), German Federal Ministry of Justice and Federal Office of Justice
- [CCAG-TIC 2021, Article 34: admission and failure decisions](https://www.legifrance.gouv.fr/loda/article_lc/LEGIARTI000043320041), Légifrance
- [FAR 52.246-4: inspection of fixed-price services](https://www.acquisition.gov/far/52.246-4), US General Services Administration, Acquisition.gov


## Related articles

- [Will the tender payment schedule fund delivery?](https://zephior.com/insights/price-milestone-payments-in-a-tender)
- [How to answer an RFP implementation approach question](https://zephior.com/insights/answer-an-rfp-implementation-approach-question)
- [How to review tender contract terms before bidding](https://zephior.com/insights/how-to-review-tender-contract-terms-before-bidding)
- [What if your bid promises more than the draft contract?](https://zephior.com/insights/resolve-conflict-between-bid-and-contract)