---
title: "Where do commercial assumptions belong in a tender?"
description: "Place approved assumptions in the required documents. Reconcile price, technical offer and contract, keeping private cost notes separate."
canonical: "https://zephior.com/insights/control-commercial-assumptions-in-a-bid"
last-updated: 2026-09-05
---

# Where do commercial assumptions belong in a tender?

> Place approved assumptions in the required documents. Reconcile price, technical offer and contract, keeping private cost notes separate.

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

## Definition

Put a buyer-facing commercial assumption in the location and form required by the tender, and ensure every affected response, price and contract statement carries the same approved meaning. Keep private estimating judgments separate unless disclosure is required. The deliverable is a submission placement record linking each approved position to exact final files and fields, with the supporting internal decision retained separately. A required assumptions schedule is not blanket permission to condition the offer. If a premise changes an obligation, it needs the appropriate procedural and legal review before publication.

## Problem

The assumptions log is approved, the technical response promises full compliance, and a note under the price says additional visits will be charged separately. Each document has passed a different review. Together they offer incompatible deals. Exporting the entire internal assumptions log would expose cost and negotiating information without resolving the contradiction. Deleting the price note would hide the missing cost if the delivery plan and approval still rely on it.

## Point of view

Review the package the buyer will receive, not just the register the team maintains. The task here starts after assumptions have been identified: decide what must be disclosed, where it belongs and whether the final documents agree. The examples, forms, clause labels, prices and limits are fictional. Sources were checked on 5 September 2026. The legal references have different jurisdictions and procedural scopes; they do not supply a universal document hierarchy or replace qualified advice on the actual offer.

## An approved log is not proof of an approved submission

Collect the files and portal answers intended for release. Include the cover letter, technical response, price workbook, assumptions schedule, contract response and supplier attachments. Record their versions and the current buyer instruction that governs each one. The review fails if it compares yesterday’s price with today’s technical method, even when both files are individually approved.

Use the existing assumptions register as an input. It records uncertain premises and their treatment; this review checks what actually reaches the buyer. For every material approved position, identify the destination document, field or paragraph and the reviewer who has checked it. Then work in reverse: inspect conditions found in the final files and show which approved record authorizes them. This second direction catches a standard footer that never appeared in the log.

The internal record and the buyer-facing explanation serve different purposes. An estimator may expect a certain productivity rate and retain evidence, contrary cases and an approval limit. The buyer needs the promised service and any permitted, relevant conditions, not automatically the supplier’s margin threshold. But keeping a calculation private does not justify concealing a limit on what the supplier will deliver. Decide by the statement’s effect and the tender’s disclosure requirements.

The output is a placement record for the frozen submission, not another register of every unknown in the project. It should answer a practical question: if the approver selects one commercial position, can the reviewer show its required public wording, all affected documents and the final treatment of conflicting text? Where an assumption has never been assessed, return it to the assumptions or clarification workflow before attempting to place it.

## Read what the sentence would make the buyer accept

“We expect two visits” may be an internal estimate. “The fixed price includes only two visits” limits the offered service. “Further visits are chargeable” asserts a payment entitlement. The sentences may originate from one spreadsheet cell but need different review. Do not publish the third as a harmless assumption because it appears under an assumptions heading.

Apply the same test to buyer actions. An internal plan may rely on prompt access, an available supervisor or an approved design. A submitted sentence assigning those tasks to the buyer, promising an extension of time if they do not occur, or excluding the resulting cost changes the commercial position unless that treatment is already established by the applicable documents. Cite the existing duty precisely when one exists; do not expand it while paraphrasing.

The legal consequences depend on the regime. German VgV §57(1)(4) addresses exclusion for changes or additions to procurement documents. French Code Article L2152-2 defines an irregular offer by reference to unmet consultation requirements, including incompleteness. These rules are reasons to examine substance before placement. They do not let the writer determine that a proposed condition is minor or acceptable merely because its financial effect seems small.

For US federal sealed bidding within the applicable FAR rules, 14.404-2(d) addresses rejection of conditions modifying invitation requirements or limiting liability. Price, quantity, quality and delivery matter to that substantive assessment. Check the actual invitation and any applicable agency deviation. This is not a rule for every negotiated RFP; an allowed negotiation route still needs its own instructions and authority.

**Classify the proposed sentence before assigning a location**

| Statement type | Publication question | Treatment |
| --- | --- | --- |
| Private estimating judgment | Does the buyer require this basis or supporting data? | Retain internally unless the applicable disclosure requirement calls for it |
| Required pricing explanation | What must the prescribed field explain? | State the approved basis without replacing the required price calculation |
| Existing buyer responsibility | Does the source impose the same duty and timing? | Reference accurately in the required response location |
| New service limit or charge | Would the offered obligation change? | Obtain deviation review; no publication route can make a prohibited term permissible |
| Unresolved source question | Has a decision been reached at all? | Return for clarification or authorized treatment before release |

## Use the buyer’s fields without inventing a new hierarchy

Read the instructions for technical and commercial separation before copying text. A price-free technical envelope must not acquire a rate or price condition simply because the same sentence is relevant to the delivery method. Preserve the technical obligation in the technical answer and disclose the commercial effect in the permitted commercial field. If the rules require a cross-reference or repetition, provide it; do not invent a cross-reference that circumvents a separation requirement.

An assumptions schedule can request the basis of an offer while the tender still prohibits departures from mandatory terms. Check its instructions together with the declaration of compliance and contract response. Where a schedule has no applicable entries, follow the buyer’s required blank or nil-response convention. Do not declare “no assumptions” when a hidden price condition still limits the offer.

If the proposed treatment is a variant, check that route separately. EU Directive 2014/24 Article 45 requires the relevant authorization or requirement and specifies minimum and presentation requirements for variants. Article 56(1)(a) connects award to compliance with procurement requirements. A bidder-created annex cannot supply the missing permission. Apply the actual national implementation and tender conditions to the case.

Contract incorporation and document precedence also require the actual clauses. Do not assume that a later annex overrides the contract, that a commercial schedule always outranks the technical response, or that a buyer signature adopts every attached note. Have the legal reviewer identify the controlling documents and resolve contradictions before submission. A hierarchy clause is a rule to interpret, not a reason to knowingly submit two incompatible commitments.

**Illustrative placement map; replace these destinations with the actual buyer forms**

| Buyer document | What belongs there when required | What must not be smuggled into it |
| --- | --- | --- |
| Technical answer T6 | Method, service scope and delivery dependencies | Prices where the technical envelope excludes them |
| Price schedule C3 | Required prices and explicitly requested calculation notes | Unapproved changes to quantities, formulas or included work |
| Assumptions form A2 | Permitted statements of the offered basis | A new right to charge or refuse work hidden as an expectation |
| Contract response D1 | The required acceptance or permitted departures | A clean acceptance inconsistent with another submitted qualification |
| Cover letter and attachments | Only the required or approved accompanying material | Standard supplier terms that contradict the reviewed offer |

## Removing a price condition requires more than deleting a sentence

The fictional Larkbridge tender covers equipment commissioning at 12 sites. Its stipulated fixed-price requirement includes up to six additional mobilisation visits if scheduled access fails. T6 promises that scope. C3, however, says repeat visits are chargeable, and A2 says the price assumes access succeeds on the first appointment. The internal model contains no repeat visits. The buyer’s defined requirement is clear in this example; the conflict is in the bidder’s package, not a missing fact to be solved by inventing a buyer duty.

The selling price is EUR 420,000 excluding VAT. Modelled delivery cost, including allocated overhead but excluding financing and tax, is EUR 362,000. Contribution is EUR 58,000. A fully specified adverse case adds six visits, each with 64 paid crew-hours at EUR 80 per hour, plus EUR 12,000 total travel. The added cost is EUR 42,720, leaving EUR 15,280, or 3.64% of revenue. Against a fictional 8% approval floor of EUR 33,600, the original economics do not support simply deleting the charge condition.

For a conforming alternative, the example supplier obtains a firm, all-inclusive reserve arrangement costing EUR 19,000 for the full six-visit obligation, with matching sites, response windows and travel. It replaces the adverse-case visit and travel costs rather than being added to them. Revised model cost is EUR 381,000 and contribution is EUR 39,000, or 9.29%, leaving EUR 5,400 above the illustrative floor. Operations verifies that the arrangement can deliver the required visits; finance separately assesses the excluded costs and payment needs before commercial approval.

Only after those checks can the release team remove the additional-charge statement from C3, replace the access-success condition in A2 with the permitted description of the included scope, and confirm T6 and D1 agree. The internal record keeps the original estimating assumption, rejected wording, new supplier evidence and revised approval. The public offer does not need the private margin calculation unless the tender requires it, but it must accurately show the work included in the price. This example demonstrates one permitted conforming decision, not a general right to change a bid after submission.

**Larkbridge: one approved treatment across the final documents**

| Location | Conflicting draft | Release treatment after approval |
| --- | --- | --- |
| T6 technical method | All six additional visits included | Retain the requirement and describe the verified reserve method without prices |
| C3 price schedule | Repeat visits charged separately | Remove the charge condition; fixed price remains EUR 420,000 |
| A2 assumptions form | Successful first access is a condition of price | Replace with the permitted statement of included scope, without a new buyer duty |
| D1 contract response | Unqualified acceptance | Confirm it matches the revised package and has the required legal approval |
| Internal cost and approval record | EUR 362,000; no repeat visits modelled | EUR 381,000 supported cost; EUR 39,000 contribution and separate exclusions review |

## Look beyond the visible assumptions page

Inspect the files the buyer will open, including the submitted workbook rather than only a printed total. Check comments, notes, hidden sheets, footers and attached supplier quotations for statements that affect the offer. A standard quotation may bring a shorter validity period, different payment terms or a service exclusion back into the package. Determine whether it must be attached and what approved treatment is permitted; do not casually rewrite a third party’s quotation.

Perform the same check after export. Tracked changes, old appendix pages, a scanned note or a portal answer pasted before the latest review can preserve a withdrawn condition. Search helps locate candidate wording, but it cannot establish the legal effect of every sentence. Compare the full meaning with the approved position. “Included unless access is unavailable” is not equivalent to “included,” even if the main paragraph uses the correct words.

Keep the original internal evidence and a clean submission copy. Remove review comments and unnecessary cost detail from the latter when the buyer has not required them, without deleting records needed for internal retention. Redaction must not remove a qualification the buyer needs to evaluate, nor can confidentiality justify withholding required pricing evidence. If an open-book or other disclosure requirement applies, obtain the prescribed approval and provide the required information through its authorized route.

For multilingual submissions, compare obligations, units, conditions and exceptions, not merely fluent language. An English expectation can become a firm buyer undertaking in another language if the translator changes its modal meaning. Record the governing-language rule where one exists, but reconcile material differences anyway. Do not rely on the buyer to resolve contradictions that the release review could have caught.

## Sign off the exact package, including deliberate omissions

The placement record identifies the approved statement and every required destination. Include a reason when an internal note does not appear externally: for example, a private productivity estimate that neither limits the offer nor falls within a disclosure requirement. That is different from omitting a contractual condition to make the offer look compliant. The approver must be able to see the difference without reopening every email.

For Larkbridge, the release evidence points to the corrected cells in C3, the final paragraph in A2, the matching scope in T6 and the approved D1 response. It also records the reserve arrangement and revised commercial decision. If one document changes afterward, its prior placement check is no longer proof for the new version. Recheck the affected documents and their dependencies before release.

Keep approval roles specific. The cost owner confirms arithmetic and inclusions; delivery confirms the proposed service; the legal reviewer assesses qualifications and incorporation; the authorized commercial owner accepts the exposure. The release manager verifies that the approved results are present in the exact submission. A single “reviewed” label cannot explain which of those decisions was made.

Use a completion rule that can fail. A mandatory disclosure without a location, an unapproved condition, or incompatible technical and commercial commitments blocks the affected package until resolved. Hundreds of matching fields do not cancel one conflicting price entitlement. Retain the submitted versions and receipt evidence so the post-submission team works from what the buyer actually received.

**Submission placement record, completed internally for each material position**

| Record element | Evidence expected |
| --- | --- |
| Approved meaning | Exact statement, relevant requirement and permitted treatment |
| Public destinations | File versions, form fields, pages or portal entries actually checked |
| Private support | Cost model, supplier confirmation and approvals retained in the authorized record |
| Omitted internal material | Reason disclosure is not required and no offer limitation is being hidden |
| Conflict closure | Old wording located and removed or replaced in every submitted occurrence |
| Release proof | Responsible reviewers, final package identity, submission and receipt evidence |

## Do not treat a submitted assumption as an agreed contract term

Acknowledgement of a file is evidence of receipt, not proof that the buyer accepted every proposed condition. Keep the status of a disclosed position separate from its contractual treatment. If a buyer asks about it, identify the exact submitted passage and the scope of the request before preparing a response. A colleague’s memory of an approved draft is not the submitted record.

Do not plan to repair material wording later. French Code Article R2152-2 permits buyer-authorized regularization of the irregular offers concerned, provided they are not abnormally low and substantial characteristics remain unchanged. The availability and limits of any correction depend on the applicable procedure. Seek review before sending a replacement assumptions schedule, revised price or explanation that changes what was offered.

An amendment or authorized revision can require the placement review again. If the fictional six-visit obligation becomes eight, the reserve arrangement covering six is insufficient evidence for the changed scope. Reopen the supplier commitment, price approval and all affected public documents. Updating only the assumption row would leave the old support attached to a new promise.

At handover, delivery receives the final accepted contract documents and the relevant unresolved matters, with access restricted appropriately. The pre-bid assumptions log explains how the offer was developed; it is not independent authority to charge for work or demand a buyer action. Where the accepted agreement differs from the submitted position, the responsible contract owner must identify that difference before planning performance.

## Useful outcomes

- Each buyer-facing position has a prescribed destination in the released package.
- Internal cost reasoning is separated from conditions the buyer must understand.
- The price, method and contractual commitment describe the same scope.
- Removed or superseded assumptions no longer survive in submitted attachments.
- The release approver can inspect the exact wording and evidence behind each placement.

## Workflow

1. **Fix the package under review.** Identify the current buyer instructions and the exact technical response, price schedule, assumptions form, contract response and attachments intended for submission.
2. **Separate the two audiences.** Distinguish internal estimating evidence from statements that define the offered obligation. Determine required disclosure without concealing a material condition or exposing unnecessary private calculations.
3. **Assign the permitted destination.** Map each approved statement to the buyer’s named field or schedule, including repeated disclosure where required. Check price separation, page limits and whether deviations are allowed.
4. **Reconcile one complete deal.** Trace each position across method, quantity, price, timetable and contract wording. Resolve cost or obligation conflicts through authorized decisions before changing the public text.
5. **Inspect the final exports.** Check rendered files, workbook notes, attachments and portal entries. Remove obsolete wording from the submission copy while retaining the original review history.
6. **Record release and subsequent changes.** Approve the exact files and placements. Retain the sent package and buyer responses; reopen affected documents if an amendment or permitted revision changes a position.

## Key decisions

- Is this an internal estimate, a required explanation or a condition of the offer?
- Which buyer instruction determines where it must appear?
- Does the wording alter a responsibility, price entitlement, deadline or remedy?
- Are the technical and financial documents presenting compatible commitments?
- Has removing a condition been supported by a new commercial decision?
- What final-file evidence proves the approved treatment reached the submitted package?

## Risks

- An assumptions form is mistaken for permission to change mandatory terms.
- An internal cost limit appears as a customer-facing service cap.
- A commercial note contaminates a price-free technical submission.
- A qualification is deleted from prose but remains necessary to the approved economics.
- An old supplier attachment reintroduces excluded standard terms.
- An acknowledgement of receipt is recorded as agreement to a condition.

## Metrics

- Approved public positions with verified final-file locations
- Contradictions remaining between technical, price and contract documents
- Withdrawn conditions still found in the submission copy
- Required disclosures absent from the prescribed field
- Late edits awaiting renewed commercial and release approval

## Frequently asked questions

### Should we attach the whole internal assumptions register?

Only where the actual submission requirements call for that information and the required approval exists. Usually the first task is to identify the required buyer-facing statements and their destinations. Preserve private evidence internally without hiding conditions that affect the offered service.

### Does an assumptions form mean qualifications are allowed?

No blanket permission follows from the form’s title. Read its instructions, the compliance declaration, contract response and rules for departures. A statement that changes scope, payment or responsibility needs the appropriate review even if placed in that form.

### Can we repeat a commercial assumption in the technical response?

Follow the prescribed separation and disclosure rules. Keep technical obligations consistent, but do not put prices into an envelope that excludes them. Repeat or cross-reference only as the actual instructions permit or require.

### Can we delete an unapproved condition just before submission?

Deletion alone is not enough if the cost model or delivery plan still needs that condition. Obtain an approved conforming treatment or another permitted decision, then update all affected documents and review the final package again.

### Does document precedence solve contradictory statements?

Have the legal reviewer apply the actual hierarchy and incorporation clauses. Do not assume the latest appendix wins or deliberately leave conflicting promises for the buyer to interpret. Resolve the intended commitment before release.

### How much estimating detail should remain private?

Keep unnecessary internal calculations out of the submission, subject to the actual disclosure requirements. A required open-book schedule or price justification changes what must be supplied. Confidentiality does not excuse omission of information the procedure requires.

### What proves this review is complete?

The exact released files show every required approved position, contain no unresolved contradictions and exclude superseded wording. The placement record links those checks to commercial, delivery and legal decisions, while the original internal history remains preserved.


## Primary sources

- [Directive 2014/24/EU, Articles 45 and 56(1)(a): variants and tender compliance](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02014L0024-20260101), European Union
- [VgV §57(1)(4): changes or additions to procurement documents](https://www.gesetze-im-internet.de/vgv_2016/__57.html), Gesetze im Internet
- [Code de la commande publique, L2152-2: irregular offers](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000037703649), Légifrance
- [Code de la commande publique, R2152-2: limits on regularization](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000037730501), Légifrance
- [FAR 14.404-2(d) and (e): conditions affecting sealed-bid requirements](https://www.acquisition.gov/far/14.404-2), U.S. General Services Administration


## Related articles

- [How to stop RFP assumptions becoming hidden commitments](https://zephior.com/insights/keep-an-rfp-assumptions-register)
- [How to manage tender exceptions and qualifications](https://zephior.com/insights/manage-rfp-exceptions-and-qualifications)
- [Does your bid price cover the work you promise?](https://zephior.com/insights/reconcile-scope-and-price-before-submission)
- [Should you ask the buyer or record an assumption?](https://zephior.com/insights/choose-between-clarification-and-assumption)