---
title: "How to stop RFP assumptions becoming hidden commitments"
description: "Build an RFP assumptions register that makes uncertain premises, impacts, approvals and replacement evidence visible before the bid binds delivery."
canonical: "https://zephior.com/insights/keep-an-rfp-assumptions-register"
last-updated: 2026-09-04
---

# How to stop RFP assumptions becoming hidden commitments

> Build an RFP assumptions register that makes uncertain premises, impacts, approvals and replacement evidence visible before the bid binds delivery.

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

## Definition

An RFP assumptions register is a controlled list of propositions temporarily treated as true so defined bid work can proceed despite missing proof. Each record states the proposition in testable terms, distinguishes it from buyer fact and supplier fact, identifies the exact uncertainty that made it necessary, preserves supporting and contrary evidence, maps every affected price, solution, schedule, response, contract or delivery object, names the owner and approval authority, sets a review trigger and records whether and where the assumption may be disclosed. It is not a list of requirements, a risk register, a silent permission to deviate or proof that the buyer accepts the premise.

## Problem

Proposal teams make assumptions as soon as an RFP leaves a material fact open. One estimator expects clean data, a solution architect expects an available interface, a mobilisation lead expects buyer staff on time and a writer turns those expectations into confident future-tense prose. The price, plan and answer can therefore depend on different unstated versions of reality. A late clarification, revised volume or delivery review then invalidates several outputs at once. If the premise never appears explicitly, nobody can test it, approve the exposure, disclose it in the required place or remove the commitment before submission.

## Point of view

Treat an assumption as a temporary, falsifiable bridge over one named evidence gap. Write what must be true, for whom, over what period and within what boundary. Show why work cannot yet rely on a proved fact or an approved decision. Link the premise to every output that changes if it is false, test the most decision-sensitive alternatives and obtain authority at the level of the resulting exposure. Replace the assumption when evidence or a buyer answer arrives. If the premise changes the offered obligation or departs from the procurement documents, route it to the prescribed qualification or commercial review instead of hiding it in polished narrative.

## Do not call every unknown an assumption

An assumption is a proposition the team temporarily treats as true without enough proof because named work needs a basis. It should exist only where a confirmed rule, fact or decision is unavailable. If the buyer states the service starts on 1 April, that is a sourced requirement. If the supplier has approved a particular hosting region, that is a decision. If a named buyer data feed must arrive before migration, that is a dependency. If late arrival could delay acceptance, that is a risk. These objects can be related, but calling all of them assumptions destroys accountability.

Ground rules also differ from assumptions. The GAO Cost Estimating and Assessment Guide describes ground rules as agreed estimating standards and assumptions as judgments about conditions postulated as true without positive proof. That distinction transfers usefully to bids. A buyer-defined currency, response period or required baseline governs the work. A supplier estimate of missing transaction volume remains an assumption until the procedure or evidence resolves it.

A qualification or exception is different again. It changes, conditions or refuses an offered obligation. An assumption may reveal why a qualification is needed, but the internal register cannot substitute for the buyer-prescribed deviation schedule. If the bid says service levels apply on the assumption that a dependency is always available, that condition may have contractual effect and needs the appropriate review and placement.

**Choose the correct record before work continues**

| Object | Test | Proper treatment |
| --- | --- | --- |
| Buyer fact | Is it explicitly stated in a current source? | Cite the source and version |
| Supplier fact | Can the company prove it now? | Link controlled evidence |
| Decision | Has an authorized person selected a course? | Record authority and rationale |
| Dependency | Must another event or party deliver something? | Name trigger, owner and fallback |
| Risk | What uncertain event could affect objectives? | Assess exposure and treatment |
| Assumption | What unproved premise is temporarily used? | Test, approve and expire it |
| Qualification | Does the offer condition or depart from an obligation? | Use the prescribed disclosure and approval route |

## Write one proposition that evidence can overturn

“Buyer will support transition” cannot be governed. Name the party, act, object, quantity, quality, location and time: “The buyer will provide a complete and validated asset inventory for the 14 named sites in the agreed import layout no later than 20 working days before migration rehearsal.” The statement is not more credible because it is detailed. It is more useful because the team can identify missing terms, ask a precise question and recognize contrary evidence.

Split compound assumptions when one part can be true while another is false. Timely delivery, completeness, accuracy, format and permission to use data are separate propositions. They may share a group identifier, but each needs its own test and consequence. Avoid negatives such as “there will be no material data issues.” State the positive condition the plan relies on and define materiality through an actual threshold or decision effect.

The 2025 AQuA Book defines an assumptions log as assumptions that have been risk assessed and signed off, and asks for description, quantified effect and reliability, date, reason, maker and approver. A bid record should add procurement scope, source gap, supporting and contrary evidence, dependent objects, disclosure state and review trigger. Those additions connect analytical discipline to the places where an offer can bind.

**Minimum record for a working bid assumption**

| Field | Question it answers | Example |
| --- | --- | --- |
| assumption | What exactly is treated as true? | Validated inventory arrives 20 working days before rehearsal |
| scope | Where does it apply? | Lot 2, fourteen sites, transition plan v4 |
| basis | Why is it plausible but unproved? | Draft timetable and prior buyer response |
| reliability | How strong is that basis? | Indicative only; current RFP is silent |
| impact | What changes if false? | Discovery effort, rehearsal date, price and acceptance |
| owner | Who obtains the missing evidence? | Transition lead |
| approver | Who may accept the exposure? | Bid director and commercial lead |
| review trigger | When must it reopen? | Buyer answer, addendum or 48 hours before price freeze |
| disclosure | May it appear in the offer? | Pending legal review of assumptions schedule |

## Show why the assumption exists and what would replace it

Link the exact tender passage, missing field, unanswered question, absent buyer input or unresolved supplier evidence. Record what was searched and what was not available. “Not found in the reviewed RFP pack” is narrower than “the buyer did not specify.” If the source set is incomplete, the register should say so. An assumption created because an annex could not be opened has a different treatment from one created because a complete pack intentionally leaves a volume open.

Supporting evidence is not proof unless it covers the same object and period. A prior contract, industry benchmark or subject expert can provide a basis, but the record must preserve why it is comparable and where it is not. Contrary evidence belongs beside it. A draft transition plan showing ten days and a clarification slide showing twenty days should not be averaged into fifteen. Their authority and applicability must be resolved elsewhere.

Define the resolution test when the assumption is created. It may be a buyer clarification, issued addendum, approved data sample, site survey, named internal certificate or executive decision. Record the expected date and the last event at which the bid can safely change. A vague “to be confirmed” creates no obligation to confirm and no signal when work should stop.

- Preserve the exact source locator and version behind the uncertainty.
- Distinguish no evidence from evidence not yet reviewed.
- Keep expert judgment attributable and bounded to the expert’s domain.
- Name the observation that would confirm, change or disprove the proposition.
- Set the last safe resolution event before the affected output is frozen.

## Test the bid at the point where the assumption breaks

Do not attach one generic impact score. Link the exact pricing cell, staffing model, architecture choice, mobilisation activity, service level, answer paragraph, contract clause and approval that relies on the premise. Some assumptions affect only drafting order. Others change a pass-fail condition or make the promised start date impossible. Materiality follows the consequence, not how confident the author feels.

Test credible alternatives. The 2026 Green Book recommends scenario analysis and simple what-if questions for assumptions where proportionate. The Infrastructure and Projects Authority guidance calls for sensitivity analysis around cost values and continuous review as information matures. In a bid, ask which input first changes the design, margin, delivery capacity, evaluation claim or decision to proceed. Preserve the tested cases and their outputs rather than storing only “high impact.”

Use ranges only where the range has a basis. A best case, working case and adverse case can be useful if each is defined. A made-up probability adds false precision. The Orange Book emphasizes best available information, explicit roles, sensitivity, confidence, connected risks and time-related volatility. Apply those ideas proportionately: a minor formatting premise may need a quick owner check, while an assumption capable of erasing margin needs structured commercial review.

**Impact test rather than a colour alone**

| Case | Condition tested | Decision effect |
| --- | --- | --- |
| Working | Inventory complete 20 days before rehearsal | Base transition plan remains feasible |
| Late | Inventory arrives 10 days before rehearsal | Add discovery shift or move rehearsal |
| Incomplete | Twenty percent of assets lack required fields | Manual discovery and price reserve required |
| Unavailable | No usable inventory before planned start | Start date and offered transition method require a new decision |

## The evidence owner does not automatically accept the exposure

Assign at least two responsibilities where the assumption is material. The owner finds evidence, monitors the trigger and updates the record. The approver accepts a defined residual exposure or chooses another treatment. A solution lead may know whether a technical premise is realistic but lack authority to accept unpriced work. A commercial lead may approve a contingency but cannot declare regulatory compliance. Legal review can interpret a proposed qualification without proving operational feasibility.

Approval must name the actual proposition, tested impact and permitted use. “Assumptions approved” at a general gate is too broad when the register changes afterwards. Record approval time, response version, conditions and expiry. If an assumption changes materially, prior approval no longer applies. If several premises combine into a larger exposure, make the connection visible and escalate the combined case.

The Construction Playbook links pricing to uncertainty and risk allocation, and recommends proactive risk management, scenario testing and consideration of allowable assumptions in its public-works context. The lesson is not that every procurement accepts an assumptions schedule. It is that scope uncertainty, price mechanism and risk ownership must agree. A fixed price based on silent buyer actions is not made safe by keeping those actions in an internal spreadsheet.

- Operational owner confirms feasibility and the evidence-closing action.
- Finance or commercial owner validates price and margin exposure.
- Legal or compliance owner reviews any condition on the offered obligation.
- Bid authority chooses whether the proposal may proceed with residual uncertainty.
- Release owner proves that final outputs use the approved version.

## An internal assumption does not alter the buyer’s requirements

First use the clarification route and deadline stated in the procedure. A timely, neutral question can replace several private interpretations with one buyer-issued answer. If the buyer changes the requirement, look for the authoritative addendum and update every linked record. The UNCITRAL Model Law provides a bounded illustration: it describes pre-deadline clarification and says a modification to solicitation documents is issued as an addendum. In US federal negotiated procurement, FAR 15.206 similarly places amendment of changed requirements with the contracting officer, not with an offeror’s internal note.

Do not plan on a post-submission rescue. EU Directive 2014/24 Article 56 permits requests to submit, supplement, clarify or complete certain information under equal treatment and transparency, subject to national implementation. German VgV section 56 allows specified requests but lets the buyer state that documents will not be requested later, and generally excludes later provision of performance-related documents relevant to award evaluation. French Code Article R2152-2 allows regularization in stated circumstances but prohibits changing substantial characteristics. FAR 15.306 distinguishes limited clarifications from discussions that permit proposal revision and says communications before the competitive range cannot cure deficiencies or materially alter technical or cost elements.

Compliance still depends on the actual regime and procurement documents. UK Procurement Act 2023 section 19 defines the most advantageous tender as one satisfying the authority’s requirements and permits disregard for a procedural breach. French Code Article L2152-2 defines an irregular offer as one that does not respect consultation requirements, including incompleteness. These examples do not create one worldwide rule. They show why an assumptions register must not silently convert a mandatory requirement into a negotiable premise.

If uncertainty remains, decide where the position belongs. Some procedures provide a assumptions schedule, commercial commentary field, deviation register or alternative-offer route. Others prohibit qualifications or require an unqualified acceptance. Follow that structure exactly. If disclosure is permitted, state the premise, affected obligation and consequence plainly enough for the evaluator to understand. If it is not permitted and the exposure cannot be accepted, redesign, reprice where allowed or reconsider the bid.

**Treatments are procedure-specific**

| Situation | Possible treatment | Do not assume |
| --- | --- | --- |
| Question deadline open | Submit a precise clarification through the stated channel | A private answer from a contact binds the buyer |
| Buyer issues an answer | Verify audience, lot, version and authority | Every informal response changes the RFP |
| Assumptions schedule required | Disclose the approved premise in that schedule | Mentioning it elsewhere is equivalent |
| Qualifications prohibited | Seek approved compliant treatment or stop | A footnote avoids the prohibition |
| Post-submission exchange possible | Follow the buyer’s request within its exact scope | A material omission will be curable later |

## A transition promise depends on a buyer asset inventory

A managed-service RFP requires transition of fourteen sites within eight weeks of contract start. The buyer names an existing asset inventory but does not state its fields, accuracy or delivery date. The draft solution quietly assumes a validated inventory will arrive twenty working days before migration rehearsal. Pricing includes two discovery analysts for five days. The response promises the eight-week transition without naming the dependency.

The register splits timely delivery, completeness, field quality and permission to use the inventory. The transition lead owns a clarification asking for sample fields and planned release timing. Testing shows a ten-day delay can be covered by resequencing, but an incomplete inventory adds fifteen analyst-days and makes the rehearsal date conditional. Commercial review rejects absorbing that adverse case under the base price. Legal review identifies the buyer’s required assumptions schedule as the only permitted disclosure location.

The buyer later issues an addendum promising an export fifteen working days before rehearsal but without a completeness threshold. The timely-delivery assumption closes as a buyer fact. The quality premise remains active with a narrower statement, a manual-discovery allowance and an approved disclosure. The transition plan, staffing calculation, price note, assumptions schedule and executive summary all reopen. The final answer keeps the eight-week outcome only under the now-visible and approved operating basis.

**Example assumption propagation**

| Record | Before buyer answer | After addendum |
| --- | --- | --- |
| Delivery timing | Twenty working days assumed | Fifteen working days confirmed |
| Inventory quality | Complete and validated assumed | Required fields still unproved |
| Transition plan | Base sequence | Discovery starts earlier and rehearsal gate added |
| Price | Five analyst-days | Approved allowance for additional discovery |
| Buyer-facing position | Hidden in draft narrative | Placed in required assumptions schedule |
| Release state | Blocked | Approved after linked outputs agree |

## Close the premise, not merely the register row

Use states that describe evidence and decision, not progress theatre. Candidate means the proposition is detected but not yet accepted for work. Working means an authorized team may use it within a named boundary. Pending clarification means a buyer question is live but the present basis remains unchanged. Confirmed means adequate evidence now supports the proposition and the downstream records should cite that evidence. Disproved means dependent work must reopen. Superseded means a newer controlled record replaces it. Release blocked means the residual exposure lacks authority or permitted treatment.

An assumption is not closed when someone types “resolved.” Link the confirming evidence or decision, record what changed and propagate the result. Search the final response, pricing workbook, implementation plan, staffing model, commercial schedule and contract comments for the old value and its paraphrases. Recheck approval after propagation. If the assumption remains active at submission, prove that its internal use and any buyer-facing disclosure match the approved position.

Keep the register focused through entry and exit rules. Record premises that change a deliverable, score, compliance position, price, capacity, timetable, margin, contract exposure or approval. Minor drafting choices can stay in normal work notes. Review at source updates, clarification responses, design changes, price freeze, red-team review, contract review and final release. The useful measure is not how many assumptions were logged. It is whether material uncertainty reached the right decision before it became an accidental promise.

**Assumption lifecycle states**

| State | Meaning | Required next action |
| --- | --- | --- |
| candidate | Unproved premise detected | Classify and assess materiality |
| working | Approved for bounded internal use | Collect evidence and monitor triggers |
| question_pending | Buyer clarification submitted | Continue only within current approval |
| confirmed | Adequate evidence supports the proposition | Replace assumption links with evidence |
| disproved | Evidence contradicts the proposition | Reopen every dependent object |
| superseded | A newer record controls the same premise | Retain history and use the replacement |
| release_blocked | Exposure or treatment lacks authority | Escalate, redesign or stop release |

## Useful outcomes

- Every material working premise is visible before it changes an answer, design, price, timetable or delivery obligation.
- Buyer statements, supplier facts, estimates, decisions, dependencies, risks, qualifications and assumptions remain distinguishable.
- Each assumption names the missing evidence or unresolved question that prevents a fact-based position.
- Impact links reveal exactly which calculations, responses, attachments and commitments must reopen after a change.
- Materiality is tested through bounded alternatives instead of a vague high, medium or low label alone.
- Operational, financial, contractual and compliance exposure reaches the person authorized to accept it.
- Buyer-facing disclosure occurs only in the location, form and stage permitted by the procurement.
- Confirmed, disproved and superseded assumptions leave an auditable history without remaining active in the final bid.

## Workflow

1. **Find the unproved premise.** Review source gaps, calculations, solution choices, schedules and draft commitments for propositions being treated as true without adequate evidence.
2. **Write a bounded test.** State subject, condition, quantity, unit, time, location and threshold tightly enough that later evidence can confirm or disprove the premise.
3. **Record basis and uncertainty.** Link the source gap, available evidence, contrary signals, reason for proceeding, confidence basis and question that would resolve the assumption.
4. **Trace every affected object.** Connect the record to pricing inputs, solution elements, milestones, claims, contractual positions, attachments and delivery work that rely on it.
5. **Test material alternatives.** Change the premise across credible cases and record when compliance, feasibility, margin, capacity, score or approval changes.
6. **Approve and place the position.** Obtain the correct operational, financial, legal or executive authority and decide whether to clarify, disclose, qualify, redesign, reprice or stop.
7. **Resolve and propagate.** Recheck at each trigger, replace the assumption with verified evidence or an approved decision and update every dependent output before release.

## Key decisions

- Is this proposition truly unproved, or is it already a buyer fact, supplier fact, requirement, approved decision or calculation?
- What precise evidence gap prevents the team from using a confirmed value or condition?
- Can the proposition be confirmed or disproved by a named observation, document, answer or event?
- Which bidder entity, lot, service, site, period and response version does it affect?
- What work may continue while the premise remains open, and what must stay blocked?
- Which credible alternative first changes price, feasibility, compliance, timetable or promised outcome?
- Who owns obtaining the evidence, and who has authority to accept the residual exposure?
- Does the procurement permit a clarification, an explicit assumption, an alternative offer or a qualification?
- Where must an authorized buyer-facing position appear so the evaluator cannot miss it?
- Which dependent objects reopen when the premise is confirmed, disproved, changed or overtaken by an amendment?

## Risks

- A descriptive note can be mistaken for buyer acceptance of the premise.
- An assumption can conceal a direct departure from a mandatory requirement.
- Different teams can use incompatible values under one vague assumption label.
- A likely value can be presented as a fact without a source or reliability basis.
- Pricing can change while the technical and contractual narratives retain the old premise.
- A low-confidence assumption can survive because no review event or expiry was recorded.
- The person who owns evidence collection can be mistaken for the authority accepting commercial exposure.
- A buyer clarification can arrive without reopening downstream answers and calculations.
- Every minor unknown can enter the register and hide the few assumptions capable of changing the bid decision.
- An internal assumption can leak into buyer-facing prose in language that sounds like an unconditional promise.

## Metrics

- material assumptions with a testable proposition, evidence gap, owner and approver
- active assumptions linked to every affected price, response, solution and contract object
- assumptions with quantified or scenario-based impact rather than an unsupported risk label
- assumptions resolved before their last safe decision or release event
- buyer answers and amendments propagated to all dependent outputs
- final-response claims checked against still-active internal assumptions
- approved buyer-facing assumptions placed in the prescribed response location
- disproved assumptions that triggered timely redesign, repricing or bid reconsideration

## Frequently asked questions

### What is the difference between an RFP assumption and a risk?

An assumption is an unproved proposition temporarily treated as true so work can proceed. A risk is an uncertain event or condition that could affect an objective. One assumption can create several risks, and a risk can exist without an assumption. Link them where useful, but give each its own owner, treatment and closure test.

### Should every assumption be disclosed to the buyer?

No. First follow the procurement documents and the approved legal and commercial position. Some assumptions are internal planning devices that must be resolved before submission. A premise that conditions the offered obligation may need disclosure in a prescribed schedule or may be prohibited entirely. Never hide a material qualification inside narrative.

### Can a confidence percentage make an assumption safe?

No. A percentage needs a defensible method and does not replace evidence, impact testing or authority. Record the basis and test credible alternatives. If 70 percent confidence and 30 percent confidence produce the same decision, precision adds little. If a small change breaks the offer, resolve or treat the exposure.

### Who should approve a material bid assumption?

The approver must control the consequence. Technical feasibility belongs with the accountable technical or delivery owner, price and margin with commercial authority, legal effect with qualified legal review and the final proceed decision with the bid authority. Evidence collection ownership alone does not confer those powers.

### What if the buyer never answers the clarification?

Keep the assumption unresolved. Recheck the procedure, last safe decision and permitted disclosure route. Test compliant alternatives and obtain authority for any residual exposure. Do not convert silence into agreement. A separate no-answer decision should determine whether the bid can proceed, needs redesign or must stop.

### Can one assumption apply to several lots or proposal sections?

Only when the scope and consequence are genuinely identical. Preserve lot, entity, service, period and response version. Share one proposition where appropriate, then keep separate dependency links and decisions. A buyer answer may confirm it for one lot while another remains open.

### When should an assumption block release?

Block the affected output when the premise could change compliance, feasibility, a material claim, price, contractual exposure or delivery commitment and no authorized treatment exists. Unrelated work may continue. The block should name the missing evidence, responsible owner and latest resolution point.

### How do we prevent old assumptions surviving in the final bid?

Give every assumption stable dependency links, review triggers and a release state. When evidence arrives, search every linked output and relevant paraphrase for the old premise, update them, then repeat approval. At final review, reconcile all active assumptions with the submitted response, schedules, price and contract position.


## Primary sources

- [The AQuA Book, 2025 edition, assumptions and decisions logs](https://www.gov.uk/guidance/the-aqua-book), UK Government Analysis Function
- [The Green Book 2026, risk, uncertainty and scenario analysis](https://www.gov.uk/government/publications/the-green-book-appraisal-and-evaluation-in-central-government/the-green-book-2026), HM Treasury
- [The Orange Book, Management of Risk, updated July 2026](https://www.gov.uk/government/publications/orange-book/the-orange-book-management-of-risk-principles-and-concepts), HM Treasury and Government Finance Function
- [Cost Estimating Guidance, assumptions, sensitivity and ownership](https://www.gov.uk/government/publications/cost-estimating-guidance/cost-estimating-guidance), UK Infrastructure and Projects Authority
- [The Construction Playbook, risk allocation, pricing and allowable assumptions](https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/1102386/14.116_CO_Construction_Playbook_Web.pdf), UK Cabinet Office
- [GAO Cost Estimating and Assessment Guide, ground rules and assumptions](https://www.gao.gov/pdf/product/705312), US Government Accountability Office
- [Procurement Act 2023, section 19, award following competitive tendering](https://www.legislation.gov.uk/ukpga/2023/54/section/19), The National Archives
- [Directive 2014/24/EU, Article 56, consolidated version at 1 January 2026](https://eur-lex.europa.eu/eli/dir/2014/24/2026-01-01/eng), EUR-Lex
- [German Procurement Regulation, section 56, requests for documents](https://www.gesetze-im-internet.de/vgv_2016/__56.html), German Federal Ministry of Justice and Federal Office of Justice
- [French Public Procurement Code, Article L2152-2, irregular tenders](https://www.legifrance.gouv.fr/loda/article_lc/LEGIARTI000037703649), Légifrance
- [French Public Procurement Code, Article R2152-2, regularization limits](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000037730501), Légifrance
- [FAR 15.206, amending the solicitation](https://www.acquisition.gov/far/15.206), Acquisition.gov
- [FAR 15.306, exchanges with offerors after receipt of proposals](https://www.acquisition.gov/far/15.306), Acquisition.gov
- [UNCITRAL Model Law on Public Procurement, clarifications and addenda](https://uncitral.un.org/sites/uncitral.un.org/files/media-documents/uncitral/en/2011-model-law-on-public-procurement-e.pdf), United Nations Commission on International Trade Law


## Related articles

- [How to close unresolved tender questions before approval](https://zephior.com/insights/close-unresolved-tender-questions-before-release)
- [How to manage tender exceptions and qualifications](https://zephior.com/insights/manage-rfp-exceptions-and-qualifications)
- [Where do commercial assumptions belong in a tender?](https://zephior.com/insights/control-commercial-assumptions-in-a-bid)
- [Which RFP conditions can stop a bid before scoring?](https://zephior.com/insights/extract-pass-fail-gates-before-drafting)