A clarification answer impact record connects one authoritative buyer response to every bid object that depends on the point it resolves or changes. It preserves the question, answer, source, publication time, audience, lot and prior working basis; states the buyer’s new or confirmed proposition without adding an interpretation; then records the effect on solution choices, quantities, price, timetable, risks, evidence, narrative, attachments, partner commitments and approvals. Each affected object has an owner, required action, decision state and verification result. The record closes only when the accepted answer is reflected consistently in the releasable bid baseline. It does not decide whether a message is legally an amendment, replace procedure-specific advice or prove that no later buyer information exists.
A transport authority is buying support for electric-bus charging equipment at eight depots. The draft solution uses one mobile engineering team for the eastern depots and one for the western depots. Clarification Q&A 17 states that two Priority 1 failures at different depots must each receive an engineer on site within 45 minutes. The question log is changed to “answered,” and the service description gains one sentence about concurrent incidents. The rota still has only two engineers on duty, the spares model assumes a single critical failure, the price workbook contains the old headcount, the subcontractor covers only weekday overflow, and the implementation plan repeats the earlier staffing figure. Every file is individually polished. Together they describe a service that cannot meet the answer.
Treat an applicable buyer answer as a controlled change event, even when it arrives as two lines in a portal Q&A. Freeze the previous bid basis before editing. Extract the smallest proposition that the buyer has confirmed, narrowed, expanded, replaced or left unresolved. Trace its direct and downstream dependencies from the solution decision into capacity, calculations, plans, evidence, claims, commitments and release approvals. Record “no change” only after a named person tests a specific object. Recalculate rather than adjusting the visible total. Reopen every decision whose facts or exposure changed. A question may be answered while its impact remains open; closure belongs to the bid baseline, not the inbox.
Authority
An answer can be visible before it is safe to use
Start with the exact buyer event. Preserve the question identifier, answer text, issuing account or document, source URL or message reference, publication and observation times, audience, procedure stage and affected lots. If the answer points to a revised schedule, drawing or notice, that object is part of the evidence. A summary written by the bid team is not a substitute for the buyer’s record.
Official regimes do not give every Q&A message the same legal effect. Under the UK Procurement Act, changes to the terms of a covered procurement engage section 31 and the associated guidance. FAR 15.206 requires a solicitation amendment when the United States Government changes requirements or terms. The World Bank rules distinguish written clarifications from modifications introduced through a written addendum. UNCITRAL’s Model Law also treats a clarification and an addendum as related but distinct acts. Apply the rule and documents for the actual procurement.
Use an answer only within its proved scope. A public reply may apply to all interested suppliers; a message in a restricted stage may apply only to participating suppliers; a response can be lot-specific. If the issuer, audience, scope or relationship to the current documents remains uncertain, keep `applicability_unresolved`. Reversible analysis may continue, but the answer must not silently replace the bid basis.
An answer that changes the work does not automatically change the deadline. UK section 54 and EU Directive Article 47 contain their own rules on time after relevant information or significant changes. Germany addresses the issue in VgV section 20; France does so in Code Article R2151-4. The bidder records only a deadline that the buyer has changed through an authoritative route.
Change statement
Write the old basis and the buyer’s answer as testable propositions
Freeze what the bid relied on immediately before the answer. That may be a sourced requirement, a provisional interpretation, an approved assumption or a design decision. Name the actor, action, object, quantity, unit, location, period and condition only where they determine the result. “Coverage model changed” is too weak. “The eastern mobile team was sized for one Priority 1 depot incident at a time” can be tested.
Next, state the answer without improving it. If Q&A 17 says that two incidents at different depots must each meet the 45-minute on-site time, preserve those elements. Do not infer that three simultaneous incidents are permitted, that the clock starts from a preferred event or that remote diagnosis pauses it. The answer may settle one axis and leave others open.
Classify the relationship between the two propositions. `confirmed` means the existing basis is supported. `narrowed` removes part of the earlier scope. `expanded` adds cases, volume, locations or duration. `replaced` makes the prior basis unusable. `conditional` adds a trigger or exception. `partial` answers only part of the question. `conflict` means the answer and another controlling source cannot yet be reconciled. These states drive different work and prevent every reply from being labelled simply “change.”
Preserve the old proposition after replacement. Without it, reviewers cannot find the documents, numbers and decisions that may still contain the former basis. The superseded record is a search key for the impact review, not an option the team may continue to use.
Impact radius
Trace the decision chain, not just matching words
A clarification often changes a solution decision before it changes a document. Concurrent response obligations alter the coverage model. The coverage model alters duty locations, shift overlap, travel assumptions, spares placement and subcontractor use. Those choices then change price, mobilisation, evidence and written commitments. Searching files for “45 minutes” will not find a rota described only as “east team.”
Begin with the affected requirement or buyer fact, then walk every relationship already used to build the response: requirement to solution decision, decision to resource and calculation, calculation to price, decision to risk and evidence, and each of those to a buyer-facing location. Include negative dependencies. A diagram may need no text change but can become misleading because it still shows one shared team.
Every candidate object receives an explicit disposition. `change_required` names the new work. `no_change_evidenced` records why the object remains valid. `decision_required` identifies an unresolved technical, commercial or legal choice. `blocked` names the missing source or authority. `out_of_scope` explains why the relationship does not apply. Absence from the trace is not a no-change decision.
Two-way checking matters. Forward review asks where the answer should have an effect. Backward review starts from every final number, claim, commitment and attachment in the affected area and asks which current requirement and solution decision support it. The second pass catches content that survived because nobody knew it was downstream.
| Object class | Impact question | Evidence needed to close |
|---|---|---|
| Solution decision | Does the method, architecture or operating model still satisfy the answered proposition? | Revised decision or tested no-change rationale |
| Capacity and schedule | Do people, assets, lead times, throughput and milestones still work under the new case? | Recalculation with controlled inputs and constraints |
| Price | Which quantity, rate, contingency, cash or margin driver changed? | Updated model cells, checks and authorized commercial result |
| Risk or assumption | Was an uncertainty resolved, disproved or replaced by a different exposure? | Updated state, consequence, owner and treatment |
| Evidence and claim | Does the cited proof cover the revised design, scale, location and period? | Current source at the same scope as the claim |
| Response artifact | Where does the buyer see the affected statement, number or depiction? | Exact final location, version and reconciliation result |
| Approval or partner input | Does the earlier decision still cover the changed fact and exposure? | Confirmed continuing scope or a new affirmative decision |
Disposition
“No change” is a review result, not an empty cell
Some answers confirm the solution. Others affect one branch but leave neighboring objects intact. Do not create work for its own sake. A no-change result is valuable when it names the tested object and reason. For example, a software licence line may remain unchanged because the licence is per depot and all eight depots were already included, even though engineering headcount increases.
Require the reviewer to identify the current version, test performed and boundary of the conclusion. “Checked pricing” does not show whether labour quantity, overtime, travel, subcontractor cover, contingency and margin were examined. “No change to annual software subscription; fee is fixed per eight named depots and concurrent incidents do not change the licensed count” does.
Do not use approval by timeout. If an owner has not reviewed a candidate dependency, keep `impact_unassessed`. If time is short, the release authority may accept a bounded residual risk only within delegated authority and with the unreviewed objects visible. A blank row cannot be converted into `no_change_evidenced` to make the dashboard green.
Sample the no-change set independently. The most dangerous surviving error often sits in a document that was reviewed but dismissed too quickly: a diagram, annex, calculation note, staffing table or partner letter rather than the main narrative.
Commercial effect
Recalculate from the changed driver to the offered price
An answer rarely changes “the price” directly. It changes a volume, frequency, service window, response condition, asset count, skill mix, risk allocation or delivery method. Record that driver first. Then rerun the model path through quantities, productivity, rates, escalation, contingency, cash timing, taxes where applicable and margin. The relevant commercial authority decides the result; a proposal editor must not absorb the difference by altering a visible total.
Keep the old and new calculation bases comparable. A change from one concurrent depot incident to two may require more duty engineers, but the result depends on travel zones, shift pattern, planned maintenance load, absence cover and subcontractor constraints. Show which inputs changed and which stayed fixed. If the answer invalidates the estimating method, replace the method and explain why rather than presenting a precise delta from incomparable models.
Price effects can travel in both directions. A clarification may remove contingency or support a simpler design. Record savings with the same discipline as increases. The GAO Cost Estimating Guide is useful for technical baselines, ground rules, sensitivity, risk and estimate updates; it does not set the price for a commercial tender. Apply the organization’s own estimating and approval policy.
Reconcile the approved commercial result across the pricing workbook, narrative, rate cards, resource plan, assumptions, contract schedule and any portal fields. A correct model is still a bid defect if the submitted number or stated headcount comes from the superseded baseline.
Unresolved edges
Do not make a partial answer finish the buyer’s sentence
A reply can answer the headline and leave the operative detail open. “Yes, simultaneous incidents are possible” does not define how many, which severity, whether the response clock runs independently or which depots can be affected. Record the settled proposition and preserve each remaining axis. The team can update work that depends only on the settled fact while holding decisions that need the missing value.
When an answer conflicts with a specification, schedule or later publication, do not choose the most convenient source. Record the exact propositions, source roles, versions and dates. Use the procurement’s stated precedence and amendment process, or seek an authorized resolution while the channel remains open. AN-079 owns reconciliation of conflicting instructions. AN-084 owns an ambiguous requirement. AN-102 owns the position after buyer silence.
If the buyer says a revised document will follow, distinguish notice of future change from the changed artifact. A team may prepare reversible alternatives, but it should not release a response on a file it has not received. Conversely, when the procedure expressly makes published Q&A part of the procurement documents, do not wait for a second label merely because the team prefers an addendum.
Late information creates a scheduling decision, not a private deadline extension. Replan the remaining work against the current official cutoff. If the applicable rules or documents provide a route to raise the time consequence, use that route with authority. Otherwise the bid lead must decide what can be completed, what must be held and whether the offer remains viable.
Release
Close the impact record only against the package that will be submitted
Completion is object-specific before it is answer-specific. Each impact row identifies the source version, prior basis, required disposition, owner, affected output, approval and verification. A changed document is not complete because it was saved. It must be the controlled version referenced by the final manifest or portal package.
Run a forward reconciliation from the buyer answer. Every change-required row should land in an approved object or an authorized decision not to change it. Then run a backward reconciliation over the affected submission area. Every material claim, number, diagram, staffing statement, risk position and attachment should resolve to the current requirement and solution baseline.
Preserve the superseded bid baseline and the delta. This protects review and recovery if a later buyer message changes the point again. It also prevents an older draft from returning through email, partner input or a restored file. Mark derived work with the answer version it uses and expire it when that source is replaced.
Only the release authority can accept open impact rows, and only within its delegation. The record must show the remaining uncertainty, affected objects, consequence and owner. A general “management aware” note does not release a technical impossibility or an unauthorized commercial exposure.
| Record part | Minimum content | Closure evidence |
|---|---|---|
| Answer identity | Procedure, stage, lot, question, issuer, source, time, audience and linked change object | Authoritative source retained and applicability accepted |
| Proposition delta | Previous basis, buyer answer, relationship, settled scope and remaining gap | Independent reading agrees with the bounded statement |
| Impact row | Object ID, version, dependency, disposition, owner, action and due time | Updated object or evidenced no-change result |
| Calculation | Changed drivers, model version, result, checks and comparison basis | Calculation rerun and commercial decision recorded |
| Risk and evidence | Closed uncertainty, new or changed risks, supporting proof and gaps | Owners and reviewers accept the current states |
| Approvals | Decision, person, authority, scope, conditions, object version and time | Every material changed exposure has affirmative authority |
| Package reconciliation | Forward and backward checks, manifest version, exceptions and reviewer | No unexplained old basis remains in the releasable package |
Worked case
One concurrency answer reaches nineteen bid objects
The bus-charging team records the answer as applicable to all eight depots and the service-response schedule. The previous basis allowed one active Priority 1 incident per region. Q&A 17 requires two incidents at different depots to meet the 45-minute on-site target independently. It does not define a third incident or pause the clock during remote diagnosis, so those points remain outside the settled proposition.
The first impact pass finds six solution objects: regional coverage, duty rota, travel-zone allocation, spares positioning, diagnostic handoff and subcontractor overflow. Four calculations depend on them: engineering headcount, overtime, vehicle cost and critical-spares holding. The response contains the old basis in the service method, mobilization plan, organization chart, SLA table, risk register, price workbook and a partner letter. Two approvals covered the former staffing and margin. Nineteen objects receive a disposition rather than one generic action for “Solution.”
Operations changes the rota to preserve two independent travel paths and rejects a tempting three-person shortcut because leave and planned maintenance would break it. The estimator reruns labour, vehicles and spares from the revised roster. The subcontractor declines night cover, so that branch closes as unavailable rather than remaining in the method statement. A previous travel risk closes, while recruitment lead time and depot-access permissions become active risks. Technical, delivery and commercial authorities approve their changed decisions.
An independent reviewer starts with the final package. The organization chart now shows four duty engineers, but the mobilization appendix still says two vehicles. That row reopens, the appendix is corrected and its approval repeated. The answer impact record closes only when the manifest points to the reconciled files and the old baseline is marked superseded. The team has not proved the whole bid correct. It has proved that this answer no longer leaves a known contradiction behind.
What good looks like
Useful outcomes from tender clarification response impact analysis
- The official answer and the bidder’s previous working basis remain visible together.
- The team distinguishes confirmation, change, partial resolution, conflict and unresolved applicability.
- Every direct and second-order dependency has an evidenced disposition.
- Solution diagrams, operating methods, quantities and delivery plans use the same accepted proposition.
- Cost and price effects are recalculated from changed drivers instead of patched at the total.
- Closed risks, assumptions and exceptions are reopened where the answer changes their basis.
- Approvals are repeated only where facts, commitments or exposure have materially changed.
- No-change decisions name the object, reviewer, test and version they cover.
- The next release baseline can be traced from the answer to every changed output and back again.
Operating model
How to run the work
- 01
Fix the answer identity
Record the procedure, lot, question, authoritative source, publication or receipt time, intended audience and any linked addendum before using the answer.
- 02
Preserve the previous basis
Snapshot the requirement, interpretation, solution decision, assumption and bid objects that were active immediately before the answer arrived.
- 03
Write the answer proposition
State exactly what the buyer confirmed or changed, including scope, quantities, units, periods and conditions. Keep any remaining gap separate.
- 04
Trace the impact radius
Follow the changed proposition through solution elements, calculations, risks, evidence, response locations, attachments, partners and approvals.
- 05
Assign each disposition
Give every potentially affected object an owner and one state: change required, no change evidenced, further decision required, blocked or out of scope.
- 06
Recalculate and reapprove
Update the underlying technical and commercial drivers, verify the result, reassess risks and obtain fresh authority where the earlier approval no longer applies.
- 07
Reconcile the package
Check forward from the answer to every affected output and backward from each final claim, number and commitment to the current basis.
- 08
Release or hold the baseline
Release a new controlled bid version only after impact rows are closed or explicitly accepted by the proper authority. Preserve the superseded state.
Evaluation
Questions that change the decision
- Is this answer authentic, current and applicable to this procedure, stage, bidder audience and lot?
- Does the procedure treat the response itself as controlling information, or point to a separate formal addendum?
- What exact proposition did the team use before the answer arrived?
- Did the buyer confirm, narrow, expand, replace or only partly resolve that proposition?
- Which solution decisions depend directly on the changed fact or instruction?
- Which prices, resources, dates, risks, claims and commitments depend on those solution decisions?
- Which objects can retain their current content, and what test proves that result?
- Which calculation must be rerun from its drivers rather than adjusted manually?
- Which prior approval, partner commitment or exception decision has lost its factual basis?
- Does the remaining response time support a compliant revision without assuming a deadline extension?
- What evidence proves that the new released baseline contains no surviving use of the superseded basis?
Failure modes
Where teams lose control
The question is marked closed while dependent bid work remains unchanged.
A portal answer is treated as a formal amendment without checking the procedure and linked documents.
The team edits the answer narrative but leaves diagrams, tables or attachments on the old basis.
A keyword search misses a dependency expressed with different terminology.
A no-change state means “not reviewed” rather than a completed impact test.
The price total is patched without updating quantities, resources, rates or commercial assumptions.
An old risk is closed even though the answer creates a different delivery or capacity exposure.
An approval survives after the underlying scope, cost, liability or evidence has changed.
A partial answer is expanded into a convenient interpretation that the buyer did not give.
The team assumes that a material answer moved the submission deadline when no official change was issued.
One corrected local copy is mistaken for the controlled version that will actually be submitted.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- Time from authoritative answer publication or receipt to initial impact triage
- Number of potentially affected objects awaiting a disposition
- Number of change-required rows without an accepted owner
- Percentage of no-change rows with a named test and reviewer
- Count of calculations rerun from controlled inputs
- Count of reopened risks, assumptions, exceptions and approvals
- Number of superseded values still found during reconciliation
- Elapsed time from answer receipt to a releasable bid baseline
- Impact rows reopened after independent review
- Clarification answers closed with complete forward and backward traceability
Questions
Common questions
Does every buyer clarification require a proposal change?
No. An answer may confirm the current basis or affect no active bid object. Record the objects reviewed, the test and the reviewer before assigning a no-change disposition.
Can the clarification question be closed as soon as the buyer replies?
The communication can be marked answered, but the impact remains open until each dependent bid object is changed, shown to remain valid, blocked or accepted by the proper authority.
Is a portal Q&A answer always the same as a tender amendment?
No universal rule makes them identical. Use the applicable law, procurement documents, source and any linked addendum to determine the answer’s status and effect.
What if the buyer answers only part of the question?
Propagate only the proposition that was settled. Keep the unanswered axes visible and prevent work that depends on them from being released on an invented interpretation.
Should the team search and replace the old wording across the bid?
Text search can find candidates, but it cannot trace decisions expressed with different words or prove that calculations and diagrams remain valid. Review the dependency chain and then inspect the final artifacts.
How should price be updated after a clarification answer?
Identify the changed commercial driver, rerun the controlled model, repeat its checks and obtain authority for the result. Do not patch the visible total or hide the delta in margin.
Do previous bid approvals remain valid?
Only where their recorded scope still covers the same facts, object version, commitment and exposure. Material changes require a fresh decision from the relevant authority.
What if the buyer answer arrives shortly before the deadline?
Plan against the current official deadline unless the buyer changes it authoritatively. Triage the impact, use any permitted procedural route and let the release authority decide whether a consistent bid remains achievable.
Sources
Primary references
- Procurement Act 2023, section 12 on covered procurement objectives The National Archives
- Procurement Act 2023, section 31 on modifying a procurement The National Archives
- Procurement Act 2023, section 54 on time limits The National Archives
- UK guidance on modifying a competitive procurement, updated August 2026 UK Cabinet Office
- UK guidance on procurement time periods UK Cabinet Office
- Directive 2014/24/EU, including Articles 18, 22, 47 and 53 EUR-Lex
- German GWB section 97 on procurement principles German Federal Ministry of Justice and Federal Office of Justice
- German VgV section 8 on procurement documentation German Federal Ministry of Justice and Federal Office of Justice
- German VgV section 9 on electronic communication German Federal Ministry of Justice and Federal Office of Justice
- German VgV section 20 on time periods and extensions German Federal Ministry of Justice and Federal Office of Justice
- French Public Procurement Code Article R2132-6 on additional information Légifrance
- French Public Procurement Code Article R2151-4 on extending tender periods Légifrance
- French DAJ guidance on digital public procurement Direction des Affaires juridiques
- Federal Acquisition Regulation 15.206 on amending a solicitation Acquisition.gov
- Federal Acquisition Regulation 52.215-1 on proposal modifications and amendment acknowledgement Acquisition.gov
- World Bank Procurement Regulations for IPF Borrowers, seventh edition, paragraphs 5.30 and 5.31 World Bank
- UNCITRAL Model Law on Public Procurement, Article 15 United Nations Commission on International Trade Law
- WTO Agreement on Government Procurement, Articles X and XI World Trade Organization
- NASA Systems Engineering Handbook, requirements change and configuration management National Aeronautics and Space Administration
- GAO Cost Estimating and Assessment Guide U.S. Government Accountability Office
- HM Treasury Orange Book on risk, roles and changing information HM Treasury
- Government Functional Standard GovS 002 on change control and traceability Government Project Delivery Function
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Ziva
Proposal software for source-grounded RFP, RFI, DDQ and questionnaire response work.
Bid, proposal, presales, security and compliance teams. Start with the workflow, constraints and evidence you already have.