A UK change notice does not make a modification permitted

Choose and prove the ground before the change

The direct answer is that notice publication is a transparency step, not the source of modification authority. Before changing a covered public or convertible contract, create a decision record for the contracting authority, contract and regime, supplier, current scope, term and estimated value, proposed text and effective date, operational reason, applicable section 74 or Schedule 8 ground, every condition of that ground, evidence, reviewer, approval, and unresolved issue. If no ground fits, the guidance says the subject matter requires a new procurement. ^[1]

Do not reduce the analysis to percentage arithmetic. Non-substantial modifications consider term, material scope change, and material change in economic balance. Below-threshold modifications have value and scope conditions plus ordering rules. Schedule 8 grounds add their own facts, such as an unambiguous original provision, unforeseeable circumstances, materialisation of a specifically identified known risk, incompatibility and cost duplication for additional supply, or corporate restructuring. Preserve the exact rationale used. ^[1]

Preserve the original notice and contract evidence

Some grounds depend on what was established before award. A modification provided for in the contract must be unambiguously provided for in the awarded contract and original tender or transparency notice and cannot change the overall nature. A known-risk modification depends on a specifically identified risk in the original notice and further conditions. Store the controlling versions and cited passages beside the proposed change rather than linking to a current page that can later be replaced. ^[1]

For cumulative or percentage rules, the calculation ledger should identify the original and immediately pre-change contract values where the guidance requires them, prior modifications by ground, term baseline, goods-services-or-works category, applicable threshold and date, currency and conversion rule, included options, scope comparison, and reviewer. Repeated small changes must remain connected so a user cannot assess each in isolation or combine a permitted and unpermitted change. ^[1]

Keep notice, standstill, execution, and publication distinct

The guidance says a contract change notice must be published before modification unless an exemption applies. Record the exemption analysis or notice identifier, fields and publication receipt, linked contract and proposed version, publication time, corrections, and accountable owner. If the authority chooses a voluntary standstill, preserve its start, duration, representations, disposition, and the decision to proceed. Do not mark the contract modified at the notice stage. ^[1]

Execution needs the final agreed text, signatures and authority, supplier identity, effective date, value and term effects, system changes, purchase controls, budget or finance effects, performance measures, implementation tasks, and acknowledgements. Where the Act requires publication of the modification or modified contract, capture that later publication separately. A procurement platform should show proposed, noticed, in standstill, approved, signed, effective, published, challenged, corrected, and superseded as different states. ^[1]

Test the regime boundary and a known-risk scenario

Run a representative public contract in which a cyber risk identified in the original notice materialises. Compare a narrowly necessary change with an unrelated feature request, calculate value and scope effects, assess public interest and a new-procurement alternative, publish the required notice, use a voluntary standstill, sign one approved version, and publish the modification if applicable. Add a prior small change, a call-off contract, a convertible contract, and a mistaken assumption that the contract is below threshold.

The Cabinet Office page, updated July 20, 2026 and reviewed October 7, supports the attributed guidance. It does not decide the lawful ground, value, scope, economic balance, notice exemption, standstill, transition rule, or procedure for a particular authority or contract. The article does not extend public-contract rules to a private procurement, below-threshold or light-touch contract, devolved context, legacy regime, defence or utilities circumstance, framework, call-off, or dynamic-market award without a current scope analysis and qualified procurement and legal judgment. ^[1]

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Procurement Technology Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.