---
title: "Test tender change control before you bid"
description: "Check whether buyer-driven changes have a usable instruction, assessment, pricing and delivery route before accepting the tender contract."
canonical: "https://zephior.com/insights/review-tender-change-control"
last-updated: 2026-09-06
---

# Test tender change control before you bid

> Check whether buyer-driven changes have a usable instruction, assessment, pricing and delivery route before accepting the tender contract.

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

## Definition

A pre-bid change-control review tests how the proposed contract would turn a buyer request into an authorized, deliverable and commercially recorded change. The work product is a change-process readiness record linking the existing baseline, change trigger, instruction authority, assessment effort, price and time effects, execution rule, notices and revised documents. It identifies gaps to resolve before bidding. It does not process an actual customer instruction or grant permission to negotiate a change after award.

## Problem

The response promises flexibility. The draft contract asks for a detailed impact assessment within a few days, allows the buyer to direct certain changes and leaves part of the price discussion until later. Delivery assumes that no work starts before a signed quotation. Finance assumes every assessment is recoverable. Neither assumption has been checked. A process diagram showing request, approve and deliver hides the point where the supplier can incur work without an agreed final price.

## Point of view

Test the proposed procedure against a specific change before promising that it will work. Follow the authority and cost of each step, including the assessment itself. Separate ordinary change approval from any contractual duty to proceed while terms remain disputed. The examples below are fictional planning exercises, not records of customer work. Primary sources were checked on 6 September 2026. Applicable law, incorporated terms, notice effects and public-procurement permissions require qualified review. This dossier concerns future delivery changes; changes to the live competition or an already submitted bid need their own stage-specific analysis.

## Find the change before choosing the form

A buyer asks for a daily data feed where the schedule describes a monthly manual export. Start with those two outputs, not with a blank variation form. Record the delivery frequency, recipient, format, security conditions and service hours on each side of the comparison. A daily file may require a new interface, monitoring and incident handling. It might also fall within an already priced option. The classification needs the issued scope and pricing documents together.

Build a compact baseline reference containing the relevant clause, schedule version, quantity range, assumptions, delivery date and acceptance conditions. Include formal clarifications and incorporated attachments. This is a targeted comparison for the proposed change mechanism, not another inventory of every contract obligation. When two documents conflict about the original duty, retain that conflict for resolution. A change estimate cannot safely charge the buyer for work the supplier may already owe.

Distinguish new requirements from defect correction, ordinary operational choices and the exercise of a defined option. A supplier replacing its own failed implementation does not establish additional entitlement merely by raising a change request. Conversely, unchanged transaction volume does not prove unchanged effort when support hours or approval responsibilities expand. Record the classification, evidence and reviewer. Use unresolved where the text will not support a conclusion.

Choose a scenario that could expose a weakness in this tender. A service expansion tests staffing and recurring charges; removal of a site tests avoided costs and minimum commitments. Use invented quantities if no authorized project data is available, label them as assumptions and keep them out of the submitted commercial response until reviewed. The purpose is to test the proposed procedure before accepting it.

**Readiness record for one proposed change scenario**

| Field | Evidence | Decision it supports |
| --- | --- | --- |
| Baseline and difference | Issued version, existing duty and requested output | Whether the change route applies |
| Request and direction | Authority, required form and actual trigger | Whether analysis or execution is required |
| Assessment | Inputs, allowed duration, resource and payment rules | Whether a usable estimate can be produced |
| Net consequences | Added work, avoided work, recurring term and dependencies | Cost, price and date positions |
| Interim conduct | Existing-service duty, disputed-change rule and notices | What must happen before final agreement |
| Closure | Valid instrument, revised documents and receipt evidence | When the new baseline can be relied on |

## An estimate request and an instruction have different effects

Identify the buyer role allowed to ask for an assessment, the role allowed to direct performance and the role allowed to approve price. They may differ. Check the supplier side too: a technical lead can confirm feasibility without having authority to amend the agreement. A meeting invitation, ticket status or approved design does not by itself establish the effect of a contractual instruction. Read the required communication form and delegation evidence.

The England and Wales Model Services Contract schedules, version 2.2A, set out change control in Schedule 18. The ordinary contractual route includes impact assessment and a signed Change Authorisation Note, with specified exceptions for earlier implementation. Review the tailored provisions and any written authority before treating signature as an absolute prerequisite to starting work.

FAR 52.243-1 provides for certain written changes by the Contracting Officer within the contract’s general scope. Its applicable alternatives matter, including for services. The clause provides a route for adjustment and says a dispute does not excuse proceeding with the changed contract. Check the incorporated version and agency deviations; a supplier policy requiring prior price agreement cannot replace that rule.

The review must therefore answer two questions separately: what creates a valid direction, and what remains to be agreed afterward? Extract notice periods, recipients, required contents and evidence of receipt for price or time claims. Ask counsel about uncertain authority, unlawful work, safety concerns or conflicting duties. Do not reduce all such cases to either start immediately or stop everything. In particular, the existing service may remain due while a proposed change is assessed.

## The impact assessment consumes capacity before approval

A useful impact assessment can require architecture work, partner quotations, security review and a revised test plan. Before promising a response time, identify the information needed and which party supplies it. A clock beginning on receipt of a request creates a different obligation from a clock beginning after complete inputs arrive. Do not insert the latter condition into the bid merely because it would be easier to meet. Resolve the issued rule through an allowed channel.

Find how the contract treats the cost of assessment: included service effort, a separately approved estimate, a requester-funded activity or a conditional recovery. Then test a rejected request. Who pays for the analysis already performed? An assessment fee may need advance authorization or a cap; a partner may charge even if the buyer declines the change. Keep the legal recovery rule beside the internal budget so a forecast does not turn into a claim of entitlement.

Define the assessment output tightly enough to review. It should state the changed deliverable, dependencies, options, net resource difference, price basis, schedule effect, acceptance amendments and remaining uncertainty. Use a range where quantities remain open, with the decision that would narrow it. A precise total built on an unknown interface specification makes the uncertainty harder to see. Escalate a response deadline that cannot accommodate the necessary evidence.

Protect existing delivery capacity. Name the people who would prepare the assessment and the work they would postpone. Check whether urgent requests can arrive concurrently and whether the contract permits prioritization. The pre-bid outcome may be a priced analysis allowance, a confirmed resource arrangement or a clarification question. It cannot be an assumption that the same specialist will complete two full-time assignments at once.

## Price the difference over the remaining service term

In a fictional exercise, Ashcombe Hosting replaces a monthly manual export with a daily feed for eighteen remaining service months. All amounts below use one hypothetical currency unit and internal cost rates. The implementation estimate includes eighteen design hours at 100, seventy-two build hours at 95 and twenty-four test hours at 90. These are distinct activities totaling 10,800. Eight hours of the original manual-export setup have not been performed and will no longer be needed, so 760 is deducted.

The recurring comparison is separate. The new feed needs twelve operations hours per month at 65 and a platform charge of 180: 960 a month. It removes four monthly manual-export hours at 65, saving 260. The net recurring increase is 700 a month, or 12,600 across eighteen months. Adding the net implementation cost of 10,040 gives 22,640. These figures do not include the earlier change-impact assessment, financing, tax or other remedies; assessment funding must be resolved independently.

The deduction depends on the old setup being genuinely avoidable. If it has already been completed, the 760 is sunk expenditure and cannot be credited as a future saving. The recurring deduction likewise requires the old export work to end when the new feed begins. A parallel-running month would change the comparison. Confirm the effective date, handover conditions and any retained manual fallback before using the result.

Internal cost is an input to the commercial decision. The contract may specify rates, an adjustment method or another valuation basis; the customer price is not automatically 22,640. Keep assessed cost, proposed charge, agreed adjustment and amounts already invoiced in separate fields. Include supporting quantities and assumptions so the reviewer can change one input without reconstructing the whole estimate. Check partner fees and minimum commitments against dated quotations rather than a percentage allowance.

**Ashcombe: fictional net cost for eighteen remaining months**

| Component | Calculation | Internal cost change |
| --- | --- | --- |
| Design, build and testing | 18 × 100 + 72 × 95 + 24 × 90 | +10,800 once |
| Avoided unperformed setup | 8 × 95 | -760 once |
| Net implementation | 10,800 - 760 | +10,040 once |
| New monthly operation | 12 × 65 + 180 | +960 per month |
| Avoided monthly export | 4 × 65 | -260 per month |
| Net remaining operation | (960 - 260) × 18 | +12,600 |
| Modeled total | 10,040 + 12,600 | +22,640, not the buyer price |

## Approval time belongs in the implementation forecast

Ashcombe’s ordinary fictional process first estimates the assessment effort in three working days. The buyer approves that estimate in two, the team completes the assessment in five, and the authorized change decision takes four more. With these stages sequential, implementation can start after fourteen working days. Twelve days for the design and build work and four days of testing then put readiness at day thirty. The requested day twenty-five is missed by five days before any delivery contingency is considered.

The durations are exercise assumptions, not deadlines supplied by any cited law or model. They expose a conflict between the requested date and the proposed decision route. Check when each clock starts, which calendar applies and whether stages can overlap without relying on unavailable inputs. State whether the final date means technical readiness, buyer acceptance or operational start. A shortened test is not equivalent to an earlier accepted delivery.

A separately reviewed accelerated route uses two days for the first estimate, one for its approval, three for assessment and two for the change decision. That permits a day-eight start and day-twenty-four readiness, leaving one working day against the request. It is a conditional alternative: the contract must allow the route, the competent parties must authorize it and the required people must confirm availability. The arithmetic alone proves none of those conditions.

For a contract requiring execution before final price agreement, model the relevant instruction date and notice work instead. Keep the unresolved price and time positions visible while performance proceeds as required. A commercial dispute should not erase the operational record of instructed scope, actual hours or delays. Equally, a buyer’s urgency does not itself create authority to use a production system, share protected data or bypass mandatory verification.

**Ashcombe: sequential working-day planning cases**

| Stage | Ordinary case | Conditional accelerated case |
| --- | --- | --- |
| Estimate the assessment effort | 3 days | 2 days |
| Approve that effort | 2 days | 1 day |
| Complete impact assessment | 5 days | 3 days |
| Authorized change decision | 4 days | 2 days |
| Implementation may start | Day 14 | Day 8 |
| Design, build and testing | 12 + 4 days | 12 + 4 days |
| Readiness against day 25 | Day 30, five days late | Day 24, one day spare |

## An agreed workflow does not settle procurement permission

Public contracts can require a further assessment of whether the modification is permitted and whether notices or publication are needed. The buyer’s willingness to sign and the supplier’s ability to deliver answer different questions. Assign the applicable regime and proposed ground to a qualified procurement reviewer. Preserve the factual inputs they need, including the original scope, change history and value basis, without declaring legality from a small percentage alone.

German GWB section 132 addresses modifications to public contracts during their term. Its conditions include rules for specified review clauses and options, alongside other grounds. Agreement under a contract’s change procedure is not a substitute for that statutory analysis. Confirm applicability and the precise ground rather than treating every modest price movement as automatically permitted.

The UK guidance on contract modifications under the Procurement Act 2023, updated 20 July 2026, distinguishes modification grounds and transparency requirements. A mechanism in the contract does not alone settle the assessment. Check the relevant procurement regime, the conditions for the proposed ground and any notice or publication duty with the responsible reviewer.

The French DAJ guidance on additional or modified services under the 2021 CCAG framework distinguishes financially valued instructions from instructions lacking valuation. Price disagreement and missing valuation have different consequences, subject to conditions and timely observations. Read the incorporated CCAG and departures before assuming either a general right to refuse work or unconditional acceptance of provisional prices.

## Define what a completed change must leave behind

The readiness review ends with a decision about the proposed process. Name the unresolved clause or operational gap, its consequence and the permitted action before bid release. If the answer depends on the buyer amending a mandatory term, use the competition’s authorized clarification or qualification route where available. Otherwise the bid authority must decide whether a supported bid remains possible. Do not promise compliance on the private expectation that delivery will renegotiate later.

For changes that the future contract can support, define the closure evidence now: a valid instruction or agreed instrument as applicable, final or provisional commercial status, effective date, affected scope and remaining reservations. Link it to revised schedules, acceptance criteria, partner commitments, operational instructions and invoice references. Preserve previous versions. A signed price page with an unchanged test plan can leave the team proving the wrong deliverable.

Give each record a stable change identifier and distinguish requested, under assessment, instructed, commercially unresolved, agreed, implemented and verified states where those distinctions apply. Record who changed a state and the evidence supporting it. Never use approved as shorthand for every kind of permission. A service manager should be able to tell what to do next without reading a private conversation, and finance should see why an amount is billable rather than merely estimated.

An assistant can extract clauses from authorized documents, draft this record, compare versions and check the arithmetic. It must preserve unknown authority, missing source text and unresolved legal interpretation for human review. Reading and drafting do not authorize sending a buyer notice, accepting terms, signing, ordering partner work, booking resources, changing a live service, disclosing protected information or submitting a bid. Each external act needs the appropriate explicit permission.

## Useful outcomes

- The bid identifies which requests change the priced baseline and which belong to existing obligations.
- Instruction authority and the rule for starting changed work are supported by the issued contract.
- Assessment effort, net delivery cost and buyer pricing remain separately visible.
- The delivery plan includes decision time and any permitted accelerated route.
- An unresolved mandatory change obligation reaches the authorized bid decision.

## Workflow

1. **Establish the comparison.** Identify the current scope, volumes, options, assumptions, milestones and version. Classify the proposed scenario against that baseline before calling it additional work.
2. **Read the instruction route.** Identify who may request an assessment, direct a change and approve commercial terms. Extract required form, notice recipients, clocks and the duty pending disagreement.
3. **Price the assessment and consequences.** Check the time, resources and payment basis for analysis itself. Estimate added and avoided work, remaining recurring costs and affected third-party commitments.
4. **Test the delivery date.** Sequence estimation, approval, prerequisites, execution and verification. Use an accelerated path only where both the contract and confirmed resources support it.
5. **Check permission and closure.** Route legal and procurement conditions to qualified owners. Define the instrument, evidence and document changes needed to establish the revised baseline.
6. **Decide the bid position.** Record supported commitments, permitted clarification requests and unresolved holds. Do not make acceptance depend silently on a future amendment the buyer has not agreed.

## Key decisions

- Is the scenario new scope, an option, a volume variation or correction of existing non-performance?
- Which communication can legally require action, and which only asks for information?
- Who funds analysis if the buyer rejects the proposed change?
- What work must continue while price or time relief is unresolved?
- Can the proposed decision sequence meet the requested implementation date?
- What evidence makes the revised baseline usable by delivery and finance?

## Risks

- An informal conversation is treated as approval to expand scope.
- A valid instruction is ignored because the supplier expects bilateral price agreement first.
- Removed work stays in the estimate while all replacement work is added.
- Assessment costs are assumed recoverable without a contractual basis.
- A commercial agreement is mistaken for sufficient public-procurement permission.
- The signed change never reaches acceptance tests, partner orders or invoicing records.

## Metrics

- Change scenarios with a traceable baseline and classification
- Instruction routes with named authority and notice evidence
- Unfunded assessment hours per rejected change scenario
- Net one-off and remaining-term cost by accepted assumption
- Working days between request and authorized implementation start
- Affected documents awaiting a reconciled change reference

## Frequently asked questions

### Should the bid promise that no changed work starts before both parties sign?

Only if that promise fits the proposed contract. Some clauses allow a valid unilateral direction and require performance while adjustment is disputed. Identify the instruction authority, required form, interim duty and notice route. Do not substitute an internal sales rule for the contract or assume an informal request is a valid direction.

### Is every buyer request a chargeable change?

No. Check the original scope, quantity range, options and existing correction duties. A request may fall within an already priced obligation. Record the difference and legal classification before estimating entitlement; keep uncertain interpretation open rather than choosing the most profitable baseline.

### Who pays if an impact assessment is rejected?

The answer depends on the incorporated assessment provisions and any valid advance authorization. Analysis may be included, separately recoverable or subject to conditions and limits. Model the rejected-request case and any partner fees before promising an assessment service in the bid.

### Can a delivery deadline be met by accelerating approval?

Only when the applicable procedure permits that route and the necessary decision makers and resources are confirmed. Show the ordinary and conditional sequences separately. Removing review days from a spreadsheet does not authorize early execution or establish capacity.

### What is the minimum useful output of this review?

A source-linked scenario record showing the baseline difference, authority, assessment funding, net cost and time effects, execution rule, notices, required permissions and revised documents. End with a supported bid position or a named unresolved hold, not a generic promise to manage changes cooperatively.


## Primary sources

- [Model Services Contract schedules, England and Wales: version 2.2A, Schedule 18](https://www.gov.uk/government/publications/the-model-services-contract-schedules-england-wales), UK Cabinet Office and Government Legal Department
- [FAR 52.243-1: changes in fixed-price contracts](https://www.acquisition.gov/far/52.243-1), US General Services Administration, Acquisition.gov
- [GWB section 132: contract modifications during the term](https://www.gesetze-im-internet.de/gwb/__132.html), German Federal Ministry of Justice and Federal Office of Justice
- [Procurement Act 2023 guidance: contract modifications](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-manage-phase/guidance-contract-modifications-html), UK Cabinet Office
- [2021 CCAG guidance: additional or modified services](https://www.economie.gouv.fr/files/files/directions_services/daj/marches_publics/textes/guideCCAG/Fiche1_11_Prestations_supp_modif.pdf), French Ministry of Economy, Direction des affaires juridiques


## Related articles

- [How to review tender contract terms before bidding](https://zephior.com/insights/how-to-review-tender-contract-terms-before-bidding)
- [Does your bid price cover the work you promise?](https://zephior.com/insights/reconcile-scope-and-price-before-submission)
- [Price the acceptance work before committing a tender](https://zephior.com/insights/define-acceptance-before-pricing-a-tender)
- [Which buyer obligations must flow down to bid partners?](https://zephior.com/insights/map-contract-flow-down-to-bid-partners)