An open-question disposition register is the release record for every material proposition that remains unanswered when the bid approaches final approval. Each row preserves the question, current source position, affected tender and response objects, available treatments, decision authority, chosen disposition, conditions, residual exposure, applied changes, closure evidence and release consequence. Closed does not always mean that the missing fact became known. It means that a person with the required authority made a permitted, evidenced decision and that the released bid consistently reflects it. A mandatory requirement that remains unsupported cannot be converted into an acceptable risk by an internal signature.
A regional flood authority is buying telemetry upgrades for 47 pumping and sluice sites. Final approval is scheduled for 16:00 on Thursday. The team still has six open questions. The specification and a drawing use different battery-autonomy figures. The pricing sheet asks for a site quantity that the buyer has not confirmed. A cyber certificate may be required with the tender, but the evidence owner expects it next month. The service lead has not chosen between two permitted data-retention periods. A subcontractor letter is still unsigned. One diagram carries an old product label that does not change the proposed design. The dashboard marks all six amber and the release note says “risks accepted.” That statement does not show which issue was resolved, which assumption the tender permits, who could approve a qualification, or which gap must stop the bid.
Close propositions, not coloured status cells. Start from the exact unresolved statement and the current tender source. Decide whether it is buyer-controlled, supplier-controlled, an evidence gap, a source conflict, a procedural question or a simple correction. Then select only a treatment that the procurement and the bidder’s authority allow. Resolution from source, a supplier design decision, a permitted disclosed assumption, an approved qualification, internal acceptance of residual execution risk and a bid stop are different outcomes. None can stand in for another. Final approval covers the exact response, price, attachments and conditions that implement the disposition. If the decision is missing or the bid still contradicts it, the row remains open.
Direct answer
A question is closed only when its disposition is both authorized and applied
Final approval does not require perfect knowledge. It requires a defensible treatment for every fact or decision that can change compliance, evaluation, price, delivery, contract exposure or submission validity. Some questions close because a current source answers them. Others close because the bidder must choose within a range the buyer already permits. A few may be carried as a disclosed assumption or qualification when the tender expressly allows that treatment. Residual execution risk can also be accepted by the person who owns it. A material requirement gap with no permitted treatment remains a stop.
The register must distinguish the information state from the release state. “Buyer has not answered” describes the information state. It does not decide whether the bid can proceed. The release decision might be proceed on a stated, permitted assumption; proceed after changing the solution; remove an optional claim; obtain a missing approval; or stop the bid. Conversely, “risk accepted” is not a useful information state. It says nothing about the requirement, evidence, answer branch or authority.
Closure also requires implementation. If the service lead chooses 90 days of data retention but the method statement still says 30 days, the decision has not closed the bid issue. If legal approves a limited contract qualification but the qualification is absent from the only schedule the buyer will read, approval has not reached the offer. The final reviewer needs the decision, the resulting file changes and the evidence that those changes survived packaging.
| Disposition | What it proves | What it cannot prove |
|---|---|---|
| Resolved from source | A current authoritative passage answers the proposition | That every dependent bid object was updated |
| Supplier decision approved | The bidder chose within its permitted design or offer space | That the buyer accepted a departure from its requirement |
| Permitted offer treatment | An assumption, qualification or variant is allowed and correctly placed | That the treatment is commercially attractive or legally harmless |
| Residual risk accepted | An authorized owner accepts remaining bidder exposure | That a mandatory condition has been satisfied |
| Stop | The current candidate cannot be released within the stated boundary | That the whole opportunity must always be abandoned |
Boundary
Freeze one release candidate before closing its questions
Record the procurement, procedure stage, selected lots, controlled tender-document and Q&A versions, response files, pricing workbook, declarations, appendices and planned approval time. Give the candidate an immutable release label or fingerprints where policy permits. Otherwise, a decision made against Thursday morning’s price can be attached to Thursday afternoon’s changed workbook. The register would look complete while referring to a bid that no longer exists.
Define materiality for this release, not for tender work in general. A spelling correction can be closed by the document owner when it changes no meaning. An outdated product name may need technical confirmation and a controlled correction. A missing certificate can affect admissibility. An unanswered volume can alter price and service capacity. The same sentence can touch several controls, so materiality follows the possible consequence rather than the length of the question.
Collect issues from every place where teams hide unfinished work: comments, review reports, assumptions logs, pricing notes, risk registers, email decisions, partner trackers, legal markups and portal messages. Preserve their original references, then split each into atomic propositions. Do not close a parent ticket until all child propositions have their own outcomes. The final approval packet should be shorter than the working register, but it must be derived from the complete set.
Classification
Who controls the missing fact determines the available disposition
A buyer-controlled question concerns the authority’s need, interpretation, data, timetable, site condition or permitted procedure. The bidder cannot settle it by confidence or seniority. Search the current official source boundary and use the permitted clarification route while it remains available. If no answer arrives, the bidder may use only a treatment the documents allow. Silence does not transfer ownership of the fact.
A supplier-controlled question calls for a design, staffing, method, price or commercial choice within the tender’s boundaries. Waiting for the buyer can become an excuse for avoiding an internal decision. Name the decision-maker, compare the allowed options and record the chosen commitment. A partner-controlled evidence gap needs a deliverable, due time and fallback. A legal or procedural uncertainty needs specialist review because a bid manager’s operational preference cannot establish legal effect.
Some rows change class after research. The flood-authority team first calls battery autonomy a design choice. The current technical schedule may instead state a mandatory 48-hour minimum, making the open item a compliance and evidence gap. Another row asks which retention period the buyer wants, but the specification permits 30 to 90 days and scores the bidder’s explanation. That question belongs to the supplier. Classification is a conclusion supported by sources, not a label inherited from the person who raised the issue.
| Control class | Typical evidence | First valid route |
|---|---|---|
| Buyer-controlled fact | Notice, specification, amendment or official answer | Resolve from source or use the authorized question path |
| Supplier choice | Permitted range, evaluation method and approved capability | Named technical or commercial decision |
| Evidence gap | Required proof, owner, validity and submission timing | Obtain evidence, replace the claim or stop |
| Source conflict | Two current passages with incompatible propositions | Run the controlling-source conflict review |
| Contract or procedural position | Tender terms and applicable regime | Authorized legal or procurement review |
| Execution uncertainty | Supported base plan, sensitivity and mitigations | Owner decision within appetite, if compliance remains intact |
Impact
Trace what each answer branch would change before asking for approval
Write the unresolved proposition so that two credible answers produce observable differences. “Battery unclear” is too broad. “Does requirement T-4.6 require every remote controller to sustain 48 hours without mains power, rather than the 24 hours shown on drawing E-17?” identifies the competing values and sources. Then trace both branches through equipment selection, enclosure size, installation labour, maintenance method, price, compliance answer, energy calculation and drawing. That is the decision surface.
Do the same for absence. If a cyber certificate is not available by submission, identify the exact tender rule, entity to which it applies, evidence form, timing and stated consequence. Separate a certificate required at tender from one required before contract start. Separate the prime bidder from a subcontractor. A promise to obtain evidence next month cannot fill a field that the buyer requires now, but it may be irrelevant if the current source expressly permits later satisfaction.
Impact mapping also prevents excessive stops. The stale product label on the flood-control diagram may not change the proposed hardware, performance or part number. If the technical owner confirms the identity and the controlled correction introduces no new claim, the issue can be repaired without reopening price or legal review. A narrow correction should not become a whole-bid crisis. A material gap should not be hidden behind the same amber colour.
Treatment
Assumption, qualification and risk acceptance solve different problems
An assumption states the basis on which the bidder built its offer when a necessary fact is unknown. It belongs in the offer only if the procurement permits it, and it must use the required schedule or response location. The assumption should name the uncertain fact, chosen basis and effect if the fact changes. It must not contradict a minimum requirement. A private calculation premise may support reversible work before release, but it is not automatically a buyer-facing assumption.
A qualification or exception proposes that the offer apply on terms different from the tender. That may be prohibited, may make an offer irregular or may be permitted through a named deviations schedule, negotiation or variant route. The EU, German, French, UK and US sources cited below do not create one supplier right to qualify any tender. Read the procedure’s documents and applicable rules. Approval by the bidder’s lawyer does not bind the buyer or cure an impermissible departure.
Risk acceptance addresses exposure that remains after the offer complies and its basis is clear. The delivery director might accept the chance that a permitted provisional quantity increases within a stated band, if the price mechanism, capacity and approval authority cover it. The same signature cannot accept that a mandatory certificate is absent or that the price sheet is incomplete. A useful test is simple: if the buyer evaluated the tender exactly as submitted, would the “accepted risk” still look like compliance? If not, the row needs another disposition.
| Proposed treatment | Required checks | Stop condition |
|---|---|---|
| Disclosed assumption | Permission, exact location, bounded basis, price and solution consistency | It weakens or contradicts a mandatory term |
| Qualification or exception | Procedure permits it, wording is exact, authority and downstream effects are approved | Exceptions are prohibited or the departure is unacceptable |
| Variant | Variants are allowed, minimum requirements met, separate price and evaluation treatment complete | The alternative is submitted as the required base offer |
| Residual-risk acceptance | Compliant base, quantified exposure, owner authority, mitigation and tolerance | Acceptance would stand in for missing compliance or evidence |
| Remove claim or scope | Removal is permitted and every reference, price and dependency is reconciled | The removed item is mandatory or leaves an inconsistent offer |
Procedure
Do not release a gap on the theory that the buyer can clarify it later
Post-submission exchanges differ by regime and procedure. Article 56 of Directive 2014/24/EU allows contracting authorities, subject to national law, equal treatment and transparency, to request some missing, incomplete or erroneous information. German VgV section 56 permits specified requests but allows the authority to state that it will not request documents and restricts performance-related supplementation. French rules permit some regularisation but not a substantial change. FAR 15.306 distinguishes limited clarifications from discussions that permit proposal revisions. These are buyer powers and bounded processes, not a bidder’s completion plan.
The final review must therefore judge the tender as the buyer can receive it at the deadline. Mark `post_submission_repair_assumed` as a release failure whenever a material row depends on the authority asking the right question later. The buyer may evaluate without discussions, reject a missing item, or limit the exchange to a clerical point. Even where correction is possible, the bidder does not control whether the route will be offered.
Keep pre-submission and post-submission actions separate. Before the deadline, an authorized team may still correct the controlled response, replace a complete submission where the portal and rules allow, or stop. After submission, respond only through the buyer’s authorized process and within its permitted scope. A future possibility cannot be backdated into evidence for Thursday’s approval.
Release
Final approval consumes closure evidence, not assurances
After a disposition is approved, work forward through every affected object and backward from the release candidate. Forward reconciliation checks the requirement, answer, diagram, calculation, price, assumption or exception schedule, contract response, declaration, attachment and approval. Backward reconciliation asks what current source and decision support each final claim, number and commitment. Any object that still points to the superseded branch reopens the row.
Give the release authority a compact packet: candidate identity, count of material propositions, disposition summary, stopped scope, conditional approvals with evidence, remaining compliant residual risks, and proof that changes were applied. Preserve the working register separately. A zero-open count is meaningful only if rows were not deleted, downgraded without evidence or moved to free text. Keep rejected options and superseded decisions so a late change can be assessed without reconstructing the week from email.
Set event and time triggers. A new amendment, buyer answer, partner withdrawal, evidence expiry, price rebuild, solution change or delayed approval can invalidate closure. Reopen only the affected rows and dependent objects, then issue a new release decision. Final approval is bounded to one candidate and one point in time. It is not a permanent statement that every underlying uncertainty disappeared.
What good looks like
Useful outcomes from close unresolved tender questions before final approval
- Every material question has one atomic proposition, current source position and accountable owner.
- Questions are linked to the exact response passages, prices, calculations, attachments and commitments they affect.
- Each row names a permitted disposition rather than a generic green, amber or red status.
- The decision authority is matched to the consequence, not merely to the department that found the issue.
- Assumptions and qualifications appear only where the tender permits them and in the required form.
- Internal risk acceptance is limited to exposure the bidder may lawfully and commercially accept.
- Mandatory compliance, missing authority and unsupported commitments stop the affected release scope.
- Every approved disposition is applied consistently to technical, commercial and contractual bid objects.
- Final approval receives a short decision packet with no silent open items and explicit reopen triggers.
Operating model
How to run the work
- 01
Freeze the release candidate
Name the exact tender version, lots, response files, price state, attachments, approval time and source baseline being considered for release.
- 02
Collect every open proposition
Bring together unresolved requirements, assumptions, comments, review findings, missing evidence, source conflicts and pending decisions without merging unlike questions.
- 03
Classify the control owner
Separate buyer-controlled facts, supplier choices, evidence gaps, procedural uncertainty, contract positions and execution risks because they have different treatments.
- 04
Trace the affected bid objects
Link each proposition to requirements, answers, calculations, price cells, schedules, contract comments, declarations and attachments before deciding its materiality.
- 05
Test the permitted treatments
Read the current procurement instructions and applicable rules before using an assumption, qualification, variant, correction or hoped-for later clarification.
- 06
Obtain the exact decision
Give the authorized decision-maker the proposition, evidence, credible options, consequence and latest safe decision time, then record the decision and conditions.
- 07
Apply and reconcile
Update every dependent object, repeat the relevant compliance and commercial checks and verify that no superseded wording remains in the release candidate.
- 08
Release, narrow or stop
Approve only the scope supported by closed rows, isolate anything outside that scope and stop the bid when a material mandatory or authority gap remains.
Evaluation
Questions that change the decision
- What exact proposition remains unresolved, and which source or evidence would answer it?
- Is the missing fact controlled by the buyer, by the bidder, by a partner or by an external authority?
- Which current bid objects change under each credible answer or decision branch?
- Does the procurement permit an assumption, qualification, exception or variant, and where must it appear?
- Would the proposed treatment alter a mandatory requirement, material price, evaluated commitment or contract term?
- Can the bidder accept the remaining exposure, or would acceptance merely rename non-compliance?
- Which person can decide this technical, commercial, legal, security, partner or release consequence?
- What evidence proves that the approved disposition reached every affected file and calculation?
- Does the disposition remain valid at the planned approval and submission times?
- Which event must reopen the row after approval?
Failure modes
Where teams lose control
A dashboard colour is treated as a decision even though no disposition or authority is recorded.
Several separate propositions are collapsed into one issue and receive one unsuitable answer.
A buyer-controlled unknown is silently converted into a supplier promise.
An internal risk acceptance is used to waive a mandatory tender condition.
A qualification is placed in the offer even though the instructions prohibit or constrain exceptions.
The team assumes the buyer will request clarification after submission and leaves a material omission.
An executive approves a decision outside their technical, legal or corporate authority.
The register says closed while an old value remains in the price, diagram or contract response.
A late partner document is promised without proof that it will be available when the tender requires it.
A source amendment or delayed answer arrives after approval but the disposition is never reopened.
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.
- material open propositions at release freeze
- rows with current source evidence and complete affected-object links
- rows closed by source, supplier decision, permitted offer treatment, residual-risk acceptance or stop
- dispositions signed by the required decision authority
- closed rows with unapplied changes in the release candidate
- mandatory or evaluated items still relying on post-submission repair
- elapsed time between disposition approval and reconciliation evidence
- questions reopened by a new source, partner fact or release change
- final release decisions issued with zero silent open items
Questions
Common questions
Can final approval proceed with open tender questions?
Only when every material proposition has an authorized, permitted disposition that is fully reflected in the release candidate. A missing mandatory requirement or decision authority remains a stop.
Is marking an issue as risk accepted enough to close it?
No. Record the exact exposure, compliant basis, owner authority, limits, mitigation and affected files. Risk acceptance cannot replace tender compliance or required evidence.
May the team use an assumption when the buyer has not answered?
Only if the procurement permits that treatment and the assumption does not contradict a mandatory term. State it in the required place with its price and solution effects.
Who should approve an unresolved question?
The authority follows the consequence. Technical, commercial, legal, security, partner and release decisions may require different people. The issue owner coordinates but does not inherit all authority.
Can we rely on the buyer asking for clarification after submission?
No. Correction and clarification powers vary and usually belong to the buyer. Approve the offer that will actually be submitted, not a version that depends on a future invitation to repair it.
Does a legal approval make a qualification acceptable to the buyer?
No. Internal legal approval addresses the bidder’s decision. The tender documents and applicable procedure determine whether a qualification, exception or variant may be submitted.
When should an unanswered question stop the bid?
Stop the affected release scope when the gap can change mandatory compliance, admissibility, a material commitment or price and no permitted, authorized treatment is complete before the cutoff.
When does a closed question reopen?
Reopen it when its source, answer, evidence, partner fact, decision condition, dependent bid object or release candidate changes, or when the recorded decision expires.
Sources
Primary references
- Procurement Act 2023, section 19 on competitive award UK Legislation
- Procurement Act 2023, section 23 on award criteria and assessment methodology UK Legislation
- Procurement Act 2023, section 31 on modifying a procurement UK Legislation
- Cabinet Office guidance on assessing competitive tenders, updated 17 August 2026 Cabinet Office
- Cabinet Office guidance on modifying a competitive procurement, updated 17 August 2026 Cabinet Office
- Cabinet Office guidance on competitive tendering procedures Cabinet Office
- Directive 2014/24/EU, including Articles 18, 45 and 56 EUR-Lex
- German VgV section 53 on the form and submission of tenders German Federal Ministry of Justice
- German VgV section 56 on examination and requests for missing documents German Federal Ministry of Justice
- French Public Procurement Code Article L2152-2 defining irregular tenders Légifrance
- French Public Procurement Code Article R2152-2 on regularisation limits Légifrance
- FAR 15.206 on solicitation amendments Acquisition.gov
- FAR 15.306 on clarifications, communications and discussions Acquisition.gov
- UNCITRAL Model Law on Public Procurement, Articles 15 and 16 United Nations Commission on International Trade Law
- World Bank Procurement Regulations, seventh edition, September 2025 World Bank
- Orange Book principles for risk ownership, appetite and treatment, updated 29 July 2026 HM Treasury and Government Finance 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.