Distinguishing a tender estimate from an awarded contract value
Distinguish tender estimates, lot awards and signed contract values before aggregating procurement figures across markets.

An announcement for a large procurement opportunity can contain several amounts. A projected value, a ceiling across multiple years and a final award do not measure the same thing. Counting all three as realized spending can inflate a market estimate dramatically.
Label the stage before adding amounts
In a licensed or open contracting dataset, retain the buyer, process identifier, lot, currency and stage with every value. Make clear whether the amount belongs to a tender, award or signed contract. If an award covers multiple lots, identify the scope before comparing it with an estimate for a single lot. Open Contracting Data Standard release reference.
Confirm how the public portal displays it
Use the official data as the starting point. XtremeProxy is relevant when an authorized publisher needs to verify a localized portal or reproduce a regional rendering issue. A proxy adds little to a stable, complete public feed. Test a sample of records against the issuer’s notices and show how corrections flow through the aggregate. Readers should be able to reconstruct what the total actually includes.
Suppose one notice estimates a two-year service at 100,000 and one later lot is awarded for 40,000. Adding the figures would count two stages. Before calculating a procurement total, decide whether the question is market opportunity, committed spending or completed payments, and select the corresponding evidence.
The estimate and award are two stages of one contract
A tender estimates 1.2 million in a fictional currency and later awards a first lot worth 700,000. Adding those values would report 1.9 million for two records attached to one purchasing process. Identify the stage and lot before computing aggregates. A second lot may remain open, and a later contract amendment may change the committed amount. Preserve the estimate for budget analysis and keep award values in a separately defined series.
Do not double-count amendment totals
An amendment may state a new cumulative contract value or an incremental change. Read the issuer's stated meaning before summing the figures. Keep lot currency, tax treatment and purchasing stage alongside each amount. A contract with several awards may require a separate approved reconciliation for each lot.
A published award can identify a framework ceiling across several suppliers. Record whether the amount represents a ceiling, a committed award, a specific call-off or a later amendment. Combining every stage as expenditure can count one procurement several times and overstate what the authority actually purchased.
Separate options from committed amounts
A contract may offer an optional extension or a maximum ceiling. The award figure, committed amount and maximum possible value may all appear in the same procurement history. Ask what the dataset's total intends to measure. Preserve the extraordinary amounts with explicit labels rather than treating every number on the notice as money already committed.
Check whether an award notice expresses a unit rate or an extended total. A hypothetical contract might publish a rate of 40 per service visit and an estimated volume of 2,000 visits. Multiplying gives a modeled 80,000 under that volume assumption, while the published amount remains 40 per visit. Store the rate, unit and estimated quantity separately. A reader can then reproduce the scenario without mistaking the modeled total for money the authority has already committed or actually paid.
A joint award can name several suppliers against a single published value. Before assigning that value to every supplier record, check whether the issuer provides an allocation per supplier, an allocation by lot, or only one total for the group. Keep an unallocated group amount attached to the contract and list the named participants separately. A supplier-level ranking that repeats the full group total for each participant will overstate its aggregate, even when every copied figure accurately matches the published award notice.
Related fieldwork
Attach the purchasing stage and the quoted value basis to every amount before summing a report. Preserve uncertainty when the issuer does not identify a cumulative or incremental value. Tender award and budget values contrasts a tender budget with an award. Following a tender deadline from notice to amendment explains how amendments can change the controlling notice before the award stage begins. Check XtremeProxy location coverage.
Frequently asked questions
Can we assume a missing award value is zero?
No. Distinguish an undisclosed value, an unawarded lot and an actual zero-value record. Each has a different meaning for totals and for the completeness of a procurement dataset.


