---
title: "Is a tender value a budget, estimate or binding ceiling?"
description: "Classify each published amount by purpose, scope, period, tax basis and authority before using it to qualify, price or forecast a tender."
canonical: "https://zephior.com/insights/interpret-estimated-tender-value"
last-updated: 2026-09-03
---

# Is a tender value a budget, estimate or binding ceiling?

> Classify each published amount by purpose, scope, period, tax basis and authority before using it to qualify, price or forecast a tender.

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

## Definition

A tender value-basis record is a source-linked classification of one monetary figure. It preserves the amount and currency exactly as published, then records the procedure, lot or group it covers, duration, options, renewals, tax basis, publication stage, source field, governing definition and observed time. Its normalized role is regulatory_estimate, planning_estimate, framework_maximum, disclosed_budget_ceiling, evaluation_value, award_value, mixed_or_conflicting or insufficient_evidence. The record states what the number can support and what it cannot support. It never converts an estimate into a promise of spend or a bid-price limit by inference.

## Problem

Tender portals often place one prominent number beside a label such as estimated value, total value, maximum value or budget. Search results then repeat it without the surrounding definition. The number may aggregate every lot, include optional years, exclude VAT, exist only for a procurement threshold or describe all call-offs under a framework. A pricing workbook may contain another total used solely to compare offers. A buyer may also publish an actual affordability limit in the instructions. Flattening those values creates bad decisions: viable tenders are rejected internally, bids are priced against the wrong term, framework ceilings become revenue forecasts, and an offer is assumed compliant because it sits below an unrelated estimate.

## Point of view

Read the noun around the number before reading the digits. Identify the legal regime, notice type, source field, scope, duration, tax treatment and purpose. Under Article 5 of Directive 2014/24/EU, the estimated procurement value is a total amount payable net of VAT, including stated options and renewals, calculated for applying the procurement rules at a defined time. Current eForms keeps Estimated Value in BT-27 and Framework Maximum Value in BT-271. Those fields are related but not interchangeable. A disclosed price ceiling needs its own operative wording and consequence. An agent may classify and compare the evidence. It must not decide that an offer is legally admissible, change a commercial model or submit a price without the authorized reviews.

## An estimated tender value is usually not a bid-price ceiling

Treat the prominent value as an unidentified monetary claim until its definition is attached. “Estimated value” commonly helps the buyer value the procurement and select the applicable rules. “Framework maximum value” describes a different boundary. “Budget” can mean an internal appropriation, a public affordability limit or an informal planning figure. None of those labels should be normalized from the word value alone.

A useful answer names the role and its allowed use. For example: “BT-27-Procedure reports EUR 4.8 million net of VAT for the whole procedure over the base and optional term. It is a regulatory_estimate. It supports procedure-size qualification but does not prove an annual budget, minimum spend or maximum admissible bid.” A different answer may read: “Section 3.2 states that evaluated prices above EUR 2.6 million net of VAT for the four-year base term will be rejected. This is a disclosed_budget_ceiling for that comparison only.”

Keep the raw text beside the normalized role. If the source says “anticipated”, “indicative”, “estimated maximum”, “funding available”, “not to exceed” or “evaluation value”, preserve that phrase and its location. If the operative effect is unclear, return insufficient_evidence. A neat label cannot repair missing buyer wording.

**Value roles and the decisions they can support**

| Role | Evidence needed | Do not infer |
| --- | --- | --- |
| regulatory_estimate | Governing valuation rule and scoped field | Price ceiling or funds |
| planning_estimate | Dated forecast or pipeline statement | Commitment to procure |
| framework_maximum | Express framework maximum and scope | Likely or guaranteed spend |
| disclosed_budget_ceiling | Controlling limit plus consequence | Scope beyond its wording |
| evaluation_value | Pricing instruction and formula | Expected demand or revenue |
| award_value | Result or contract notice | Original budget or full outturn |
| mixed_or_conflicting | Material sources disagree | A winner among the numbers |
| insufficient_evidence | Definition or scope is missing | Any binding effect |

## BT-27 and BT-271 answer different questions

Article 5 of Directive 2014/24/EU defines the estimated procurement value as the total amount payable, net of VAT, estimated by the contracting authority. It includes options and renewals explicitly set out in the procurement documents, as well as relevant prizes or payments. The estimate is valid when the call for competition is sent or, without one, when the procedure starts. That makes it a dated valuation for the procurement regime. The provision does not turn every published estimate into an offer cap.

Current eForms stores Estimated Value in BT-27 at procedure, group, lot or part level. The TED schema guide describes it as an aggregated amount and a rough buyer estimate at the launch of the call for competition or earlier. Store its exact field context. BT-27-Procedure and BT-27-Lot can be numerically related without being interchangeable, and a value shown on a planning notice may be less settled than one in the current competition pack.

Framework Maximum Value is BT-271. The eForms regulation defines it for the whole duration, including options and renewals, and across all contracts to be awarded within the stated framework scope. For EU framework agreements, the Court of Justice held in Simonsen & Weel that the estimated quantity or value and a maximum quantity or value must be stated, and that the framework no longer has effect once that limit is reached. That is a materially different finding from BT-27.

The maximum is still not a sales forecast. It can cover several buyers, lots, suppliers and future call-offs, while none may be guaranteed. Record who shares the limit and whether it applies to the whole framework, one group or one lot. A supplier-specific revenue scenario requires call-off rules, minimum commitments, likely demand and allocation evidence that BT-271 does not provide.

**Facts to retain from an eForms value**

| Field | Question | Stored answer |
| --- | --- | --- |
| field_id | Which business term and context? | BT-27-Procedure, BT-27-Lot or BT-271-Lot |
| scope | Which object does it cover? | Procedure, group, lot or part |
| duration_basis | Which periods are included? | Base, options and renewals |
| tax_basis | Is VAT included? | Net under Article 5 |
| currency | Which published unit? | ISO currency code without conversion |
| valid_at | When was the estimate formed? | Dispatch or procedure-start basis |
| value_role | Estimate or framework maximum? | Separate normalized state |

## A binding price limit needs words that create a limit

Look for the consequence attached to the amount. A controlling instruction may say that the total evaluated price must not exceed a stated sum, that offers beyond available funding are unacceptable, or that a schedule cell has a fixed upper bound. Capture the exact clause, defined price, tax basis, period, lot and treatment of options. A heading that merely says budget is weaker than an operative sentence.

Source authority matters. A current procurement document or formal clarification can control bidder action. A press release, committee paper or pipeline plan may explain context without setting the submission rule. An amount mentioned in a portal summary can conflict with the downloadable price schedule. Do not resolve that conflict by selecting the newest timestamp alone. Identify which document governs the price and whether an amendment replaced it.

Silence is not a hidden ceiling. If the estimate is lower than the bidder’s modeled price, the record can flag commercial tension and prompt review, but it cannot declare the offer non-compliant. Conversely, a bid below the estimate is not proven affordable or competitive. Scope, evaluation method, abnormally low price rules and internal margin remain separate questions.

Where the effect is material and wording stays ambiguous, prepare a clarification question or route the clause to the procurement and legal reviewers. The agent should show the two plausible readings, affected calculation and last safe decision time. It should not contact the buyer or rewrite the price without authorization.

## A UK maximum payable estimate still needs a purpose label

Section 4 and Schedule 3 of the Procurement Act 2023 govern valuation for the Act. Current Cabinet Office guidance explains that the general rule estimates the maximum value payable under the contract and includes relevant variables such as additional supplies, extension or renewal options. The guidance says the estimate is VAT-inclusive and is used to determine whether the contract sits above or below the applicable threshold.

The word maximum in that methodology is easy to misread. It describes how the contracting authority forms the statutory estimate. It does not by itself tell a supplier that any tender above the published figure must be rejected. For that decision, inspect the tender notice, assessment methodology, pricing instructions and contract terms for an actual affordability or price constraint.

UK and EU values may therefore use different tax bases even when the procurement looks similar. Never convert one silently. Retain the published amount and VAT treatment, and store any gross or net comparison as a derived value with rate, assumption and calculation time. Threshold analysis and supplier pricing should not share an unlabeled number.

## Three visible totals can all be correct and still mean different things

A fictional authority procures a managed data platform for four years with a two-year extension option. Its eForms competition notice shows BT-27-Procedure at EUR 4.8 million net of VAT. The lot estimates are EUR 2.5 million, EUR 1.4 million and EUR 900,000 across the same full potential term. Their sum reconciles to the procedure estimate. The record classifies all four amounts as regulatory_estimate.

The pricing workbook evaluates the base four-year term at stated sample volumes. Its calculated comparison total is EUR 2.3 million. The instructions say those volumes are used only to compare tenders and do not create a purchase commitment. That number is evaluation_value. It should drive the scoreable workbook calculation, but it is not the authority’s expected six-year spend.

A separate commercial instruction states that any evaluated base-term total above EUR 2.6 million net of VAT will be rejected as unaffordable. The clause names the same calculation and gives a consequence, so EUR 2.6 million is disclosed_budget_ceiling for the evaluated base term. It does not cap charges under the optional years, which are outside the defined comparison.

An amendment later raises the ceiling to EUR 2.7 million while leaving BT-27 unchanged. The agent stores a new ceiling event, links it to the amended instruction and marks the earlier ceiling superseded. It does not edit the EUR 4.8 million estimate or pretend the authority increased expected spend. The pricing owner receives the new compliance boundary and reruns the approved calculation.

**Classified values in the fictional procurement**

| Amount | Role | Permitted use |
| --- | --- | --- |
| EUR 4.8m net | Procedure regulatory estimate | Size and scope qualification |
| EUR 2.5m, 1.4m, 0.9m net | Lot regulatory estimates | Lot-level qualification |
| EUR 2.3m net | Evaluation value | Reproduce scoreable comparison |
| EUR 2.6m net | Superseded disclosed ceiling | Historical compliance record |
| EUR 2.7m net | Current disclosed ceiling | Base-term price gate |

## Return the amount, its meaning and the boundary on its use

An inspectable result contains value_id, amount_raw, amount_decimal, currency, tax_basis, source_label, source_field, source_anchor, notice_id, notice_version, procedure_id, lot_ids, publication_stage, duration_basis, option_basis, governing_definition, normalized_role, operative_effect, valid_at, observed_at, predecessor_value, conflicts, allowed_uses, prohibited_inferences, confidence, review_owner and recheck_trigger. Derived conversions stay separate from the published value.

The agent may retrieve public sources, extract monetary fields, align scope and duration, apply a documented definition, compare versions and warn when the bid approaches an explicit ceiling. It must stop when the controlling clause is missing, tax treatment is unresolved, values cover different objects, a currency conversion would determine the commercial decision or legal effect is disputed.

Changing a price, excluding an opportunity, approving an exception, asking the buyer a question or submitting a commercial schedule remains outside this evidence task. The output can recommend the next review and supply the exact clause. It does not grant itself procurement, finance or legal authority.

## Useful outcomes

- Every amount retains its original label, digits, currency, source location and observation time.
- Procedure, group, lot and contract values remain separate instead of being added automatically.
- Base term, optional periods and renewals are visible beside the amount they influence.
- Net and gross values are not compared until the tax basis is made explicit.
- Regulatory estimates are not treated as buyer appropriations or bidder price limits.
- Framework maxima are recognized as aggregate boundaries without becoming purchase guarantees.
- Evaluation figures remain distinct from expected spend, contract value and submitted price.
- Only explicit, controlling buyer wording supports a disclosed_budget_ceiling finding.
- Conflicts and missing definitions lead to review rather than a fabricated commercial answer.

## Workflow

1. **Freeze the observed figure.** Capture the exact label, amount, currency, punctuation, source URL or file, notice version, page or field identifier and retrieval time before calculating anything.
2. **Name its object and period.** Identify the procedure, group, lot, contract or evaluation scenario, then record base duration, options, renewals and any shared scope.
3. **Read the governing definition.** Use the current regulation, notice schema and buyer documents to determine why the figure exists and whether VAT or other components are included.
4. **Classify the value role.** Choose regulatory estimate, planning estimate, framework maximum, disclosed budget ceiling, evaluation value, award value, conflict or insufficient evidence.
5. **Reconcile related amounts.** Compare only values with aligned scope, period, tax basis and currency. Preserve unexplained differences and later corrections as separate evidence.
6. **Issue a bounded use decision.** State whether the figure may inform procedure coverage, opportunity size, price compliance, scenario planning or none of them, with the evidence and review needed.

## Key decisions

- Which legal regime and procurement stage produced the value?
- Does the amount cover the whole procedure, a group of lots, one lot or one contract?
- Is it valid for the base term only or for the full term including options and renewals?
- Does its definition use a net-of-VAT or VAT-inclusive basis?
- Is the number a rough estimate, a maximum, a minimum, an evaluation multiplier or an awarded amount?
- Does a controlling document say that offers above the amount will be rejected or are unaffordable?
- For a framework, does the amount apply to all call-offs, a group, a lot or one supplier?
- Has a correction or clarification changed the amount or its meaning?
- Can the value support qualification while remaining unusable as a pricing constraint?
- Which missing fact must a commercial, procurement or legal reviewer resolve?

## Risks

- A search result strips the amount from its field label and notice version.
- An annual run rate is compared with a whole-life estimate.
- Optional years are removed even though the governing estimate includes them.
- An EU net value is compared directly with a UK VAT-inclusive estimate.
- Lot values are summed although a group maximum shares one budget across them.
- A regulatory estimate is presented as approved buyer funding.
- A framework maximum is forecast as guaranteed supplier revenue.
- An evaluation scenario is mistaken for committed volume or expected spend.
- An undisclosed internal affordability amount is treated as a published bid ceiling.
- An agent changes price or bid status from a weak value classification.

## Metrics

- published values with source, field, scope, period and tax basis attached
- amount comparisons blocked until their bases align
- framework estimates and maxima stored in separate fields
- price ceilings supported by explicit controlling wording
- corrections linked without overwriting earlier values
- qualification decisions that cite permissible and prohibited uses
- value conflicts routed to a named reviewer
- commercial actions withheld when the value role is uncertain

## Frequently asked questions

### Is the estimated value in a tender the buyer’s available budget?

Not by default. It may be a statutory or planning estimate covering a defined scope and term. Treat it as available funding only when an authoritative source says so and states the relevant scope.

### Can our bid exceed the published estimated value?

The estimate alone does not answer that question. Check the pricing instructions, evaluation method, affordability wording and contract terms for an explicit limit, then obtain the required commercial or legal review.

### Does BT-27 include contract extensions?

Under Article 5 of Directive 2014/24/EU, the estimated value includes options and renewals explicitly set out in the procurement documents. Verify the regime, field scope and current notice.

### Is a framework maximum guaranteed revenue?

No. It bounds the stated framework scope across the relevant contracts and term. It does not prove that the buyer will order that amount or that one supplier will receive it.

### Why can the procedure value differ from the pricing-sheet total?

They may cover different terms, options, lots, quantities, tax bases or purposes. Record both and align those dimensions before deciding whether the difference is an error.

### Should an agent add all lot estimates?

Only after confirming that the lots are disjoint, use the same period and tax basis, and are not constrained by a shared group maximum. Preserve any buyer-published procedure total separately.

### Does estimated value use the same VAT basis everywhere?

No. Article 5 of the EU directive uses net-of-VAT value, while current UK Procurement Act valuation guidance uses VAT-inclusive value. Check the regime rather than guessing from currency.

### What should the agent return when the label is only “budget”?

Preserve the label, find its definition and consequence, and return insufficient_evidence if those are absent. Do not promote an ambiguous budget reference to a binding ceiling.


## Primary sources

- [Directive 2014/24/EU, Article 5 on estimated procurement value](https://eur-lex.europa.eu/eli/dir/2014/24/2026-01-01/eng), EUR-Lex
- [TED eForms guidance for procedure, lot and part values](https://docs.ted.europa.eu/eforms/latest/schema/procedure-lot-part-information.html), Publications Office of the European Union
- [eForms BT-27 Estimated Value fields](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/BT-27.html), Publications Office of the European Union
- [eForms BT-271 Framework Maximum Value fields](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/BT-271.html), Publications Office of the European Union
- [Court of Justice judgment in Simonsen & Weel, C-23/20](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62020CJ0023), Court of Justice of the European Union
- [Procurement Act 2023, Schedule 3 on estimating contract value](https://www.legislation.gov.uk/ukpga/2023/54/schedule/3), The National Archives
- [Cabinet Office guidance on valuation of contracts](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-define-phase/guidance-valuation-of-contracts-html), UK Cabinet Office


## Related articles

- [Framework agreement: call-offs, value and bidder risk](https://zephior.com/glossary/framework-agreement)
- [How to find framework opportunities before call-offs](https://zephior.com/insights/find-framework-opportunities-before-call-offs)
- [How to estimate the full cost of bidding for a tender](https://zephior.com/insights/how-to-estimate-tender-bid-cost)
- [How to qualify a tender when the budget is missing](https://zephior.com/insights/qualify-a-tender-without-budget-information)