How to Estimate Government Contract Values Before You Bid

A contract notice lands in your feed. The scope matches your capabilities. The buyer is in your target market. The deadline gives you enough time to prepare.

One piece of information is missing: the budget.

This happens more often than it should. Only about 40% of EU contract notices include an estimated value. The rest arrive with a blank field where the budget should be. For suppliers deciding whether to invest 15,000-30,000 EUR in bid preparation, that blank field is a problem.

Without a value estimate, you cannot calculate expected return. You cannot compare opportunities. You cannot allocate resources rationally. You are, in effect, bidding blind.

This guide shows you how to estimate contract values before you invest in a bid — using signals embedded in tender documents, historical award data, and structured estimation methods.

Why contract values are hidden

Contracting authorities omit estimated values for three main reasons.

No legal obligation. EU procurement directives require estimated values for threshold determination, but disclosure in the published notice is not always mandatory. Below-threshold contracts — under 143,000 EUR for central government services, under 221,000 EUR for sub-central authorities — are more likely to omit values entirely.

Strategic ambiguity. Some buyers deliberately withhold estimates. They believe that publishing a budget anchors supplier pricing. If a buyer estimates 500,000 EUR and publishes it, they expect bids clustered around 500,000 EUR — even from suppliers who might have priced at 350,000 EUR.

Internal uncertainty. Buyers sometimes do not know the value themselves. New procurement categories, innovative solutions, or cross-departmental requirements can make internal estimation difficult. Rather than publish an unreliable number, they publish nothing.

The result: 60% of contract notices across Europe provide no budget guidance. Suppliers must estimate on their own or bid without knowing the stakes.

Where to find value signals in tender documents

A contract notice without an estimated value is not empty of value signals. The information is scattered — across the notice, the specifications, and the procurement context. You need to know where to look.

The notice itself

Lot structure. A procurement divided into 8 lots signals a different scale than a single-lot contract. More lots generally means larger total value. Each lot description provides scope clues — staffing levels, geographic coverage, equipment quantities — that bound the likely value range.

Procedure type. Open procedures can be used at any value, but contracting authorities tend to reserve competitive dialogue and negotiated procedures for complex, high-value contracts. A competitive dialogue for IT services is unlikely to be worth less than 500,000 EUR. The administrative overhead would not justify it.

Contract duration. A 4-year contract is worth roughly 4x a 1-year contract for the same scope. Duration appears in nearly every notice, even when value does not. A 48-month managed services contract with 15 FTEs at market rates gives you a workable estimate range.

CPV codes. The primary CPV code places the contract in a category with known benchmarks. IT consulting (72000000) has different value distributions than cleaning services (90910000) or medical equipment (33100000). Each category has a median contract value that serves as a starting anchor.

The specifications document

The tender specifications almost always contain more value signals than the notice summary.

Staffing requirements. If the buyer specifies "minimum 5 FTE on-site, including 1 project manager and 1 senior architect," you can estimate labor costs using market day rates for those roles in that geography. Five FTEs for 36 months at 600 EUR/day average is approximately 3.2M EUR in labor alone.

Volume indicators. Quantities, transaction volumes, user counts, and site numbers all imply scale. "Support for 15,000 end users across 40 locations" is a different contract than "support for 200 users at headquarters."

Service level requirements. 24/7 support with 4-hour response times costs meaningfully more than business-hours support with next-business-day response. SLA tiers directly impact pricing.

Technology requirements. Specified platforms, certifications, and infrastructure requirements narrow the market and set price floors. A requirement for SAP S/4HANA implementation sets a different baseline than a requirement for open-source CRM deployment.

The procurement context

Budget publications. Many contracting authorities publish annual procurement plans or budget documents. These are public records — and they often include line items that correspond to upcoming tenders. A municipal IT budget of 2M EUR per year, with 800,000 EUR allocated to "digital transformation," bounds the likely value of their digital transformation tender.

Prior Information Notices. PINs published 6-12 months before the contract notice sometimes include estimated values that the contract notice omits. Check TED for PINs from the same buyer in the same category.

Using historical award data as benchmarks

Past performance is the strongest predictor of future contract value. Buyers who spent 400,000 EUR on IT support last cycle are unlikely to spend 4M EUR this cycle — unless the scope has fundamentally changed. Award history provides the baseline.

Same buyer, same category

The most direct benchmark: what has this specific buyer paid for similar services before?

Search the buyer's award history for contracts with matching or adjacent CPV codes. If the City of Munich awarded a 3-year facilities management contract at 2.1M EUR in 2023, their 2026 re-procurement of the same scope will be in the same range — adjusted for inflation, scope changes, and market conditions.

Duke indexes historical award values across 30 countries, making this lookup systematic rather than manual. For any buyer in the database, you can see the value, duration, CPV code, and winning supplier of their previous awards.

Same category, same geography

When buyer-specific history is unavailable — perhaps the buyer is new to this procurement category — widen the search. What do similar buyers in the same country pay for this category?

Regional benchmarks are more useful than pan-European averages. A managed print services contract for a Dutch municipality operates in a different cost environment than the same contract for a Romanian ministry. Labor rates, market maturity, and competitive intensity vary by geography.

Filter by CPV code, country, and buyer type (central vs. sub-central government) to get a relevant comparison set. The median award value across 20-30 comparable contracts gives you a reliable center estimate.

Award-to-estimate ratio

For contracts that did include an estimated value, compare the estimate to the final award. This ratio — the award-to-estimate ratio — tells you how much buyers in a given market and category overshoot or undershoot their own estimates.

Across Duke's dataset, this gap averages 15-25%. Estimates tend to run high. But the ratio varies by sector:

These ratios apply in reverse when you are working from an award benchmark to estimate a future tender. If you know a similar contract was awarded at 600,000 EUR, and the category's typical ratio is 80%, the buyer likely estimated 750,000 EUR for that contract.

Four estimation methods

No single method gives you a precise number. Triangulating across multiple methods gives you a range — and a range is enough for a bid/no-bid decision.

Method 1: Comparable contract analysis

Find 5-10 awarded contracts with matching characteristics:

• Same CPV code (at minimum the 2-digit division level)
• Same country or comparable labor market
• Same buyer type (central government, municipal, utility)
• Similar scope and duration

Calculate the median and interquartile range (25th to 75th percentile). This gives you the likely value band.

Example. You find 8 awarded contracts for "IT consulting services" (72200000) in Belgium, all 24-36 months duration, for sub-central government buyers. Award values: 180K, 220K, 310K, 350K, 400K, 480K, 520K, 750K EUR. Median: 375K. IQR: 265K-500K. Your estimate: 250,000-500,000 EUR range.

Method 2: Bottom-up resource costing

When the specifications include staffing or volume requirements, build the estimate from the bottom up.

1. List required roles and FTE counts from the specifications
2. Apply market day rates for that geography and skill level
3. Multiply by contract duration
4. Add overhead: equipment, travel, subcontracting, margin

Example. Specifications require: 1 project manager (850 EUR/day), 3 senior consultants (700 EUR/day), 2 junior consultants (450 EUR/day). Duration: 24 months. Working days: approximately 220 per year.

Estimated contract value: approximately 1.9-2.0M EUR.

Method 3: Lot structure analysis

For multi-lot procurements, analyze the lot structure to estimate total value and individual lot values.

Each lot has scope indicators: geography covered, service lines included, volume expected. If Lot 1 covers "Northern region — 5 sites" and Lot 2 covers "Southern region — 12 sites," Lot 2 is likely 2-2.5x the value of Lot 1. Estimate one lot, scale to the others.

Framework agreements with lots provide ceiling values more often than single contracts — because the buyer needs the ceiling for budget authority. When one lot in a framework includes a maximum value, use it to calibrate estimates for the remaining lots.

Method 4: Threshold inference

EU procurement rules require different procedures above and below specific thresholds. The procedure type used tells you which side of the threshold the buyer believes they are on.

• Published on TED as an open procedure → above 143K EUR (services, central government) or above 221K EUR (services, sub-central)
• Published only on a national platform, not on TED → likely below EU thresholds
• Competitive dialogue or innovation partnership → almost certainly above 1M EUR

Threshold inference does not give you a precise value. It gives you a floor. A contract published on TED for IT services is worth at minimum 143,000 EUR. Combined with other signals, this narrows the range.

When estimated value matters most

Not every procurement decision requires a precise value estimate. Estimation matters most in two scenarios.

Resource allocation

Bid preparation costs 1-3% of contract value. A 100,000 EUR contract justifies 1,000-3,000 EUR in bid prep. A 5M EUR contract justifies 50,000-150,000 EUR.

If you cannot estimate the contract value, you cannot size the bid team, set the bid budget, or decide how many other pursuits to defer. The risk: over-investing in a small contract (negative ROI even if you win) or under-investing in a large one (losing a significant opportunity due to a thin proposal).

The calculation is straightforward:

Expected value = contract value x win probability x margin

A 2M EUR contract at 25% win probability and 15% margin yields an expected value of 75,000 EUR. Spending 30,000 EUR on bid preparation is rational. Spending 30,000 EUR on a 200,000 EUR contract with the same parameters (expected value: 7,500 EUR) is not.

Without a contract value estimate, this calculation cannot happen.

Bid/no-bid decisions

Contract value determines whether an opportunity passes the minimum threshold for pursuit. Every organization has a floor — the minimum contract value that justifies the fixed cost of bid preparation.

For a mid-sized IT services firm, that floor might be 300,000 EUR. Below that, the bid cost to contract value ratio makes pursuit uneconomical. Above that, the opportunity enters the qualification pipeline.

A contract notice without a value estimate cannot be scored against this criterion. It sits in limbo — possibly a 5M EUR opportunity worth maximum effort, possibly a 50,000 EUR contract that should be passed immediately. Without estimation, you either pursue everything (wasting resources) or skip uncertain opportunities (missing revenue).

Building a value estimation process

Ad hoc estimation works for occasional bids. At scale — managing 20-50 active pursuits — you need a repeatable process.

Step 1: Capture available signals

For every new opportunity that enters your pipeline, extract and record:

• Published estimated value (if present)
• Lot count and structure
• Contract duration
• Procedure type
• CPV code(s)
• Staffing and volume indicators from specifications
• Buyer name and country

This takes 10-15 minutes per opportunity and provides the raw material for estimation.

Step 2: Run comparable analysis

Search for 5-10 historical awards matching the CPV code, geography, and buyer type. Record the median and range. This is where procurement intelligence tools pay for themselves — manual searches across national platforms and TED take hours per opportunity. Duke's historical award database provides this in seconds.

Step 3: Triangulate

Apply at least two estimation methods. If comparable analysis suggests 400,000-600,000 EUR and bottom-up costing suggests 520,000 EUR, you have a high-confidence estimate in the 450,000-550,000 EUR range. If the methods diverge — comparables suggest 200,000 EUR but bottom-up costing yields 800,000 EUR — investigate why before proceeding.

Step 4: Score and prioritize

Assign the estimated value range to the opportunity and use it in your bid/no-bid scoring. A 2M EUR contract with moderate competition and strong buyer fit scores differently than a 200,000 EUR contract with the same qualitative profile.

Step 5: Track accuracy

After award, compare your pre-bid estimate to the actual award value. Track the ratio over time. Your estimation accuracy should improve as you build sector and geography expertise. If your estimates consistently overshoot by 40%, recalibrate your benchmarks.

The cost of not estimating

Suppliers who skip value estimation face two failure modes.

Chasing small contracts with big budgets. Without value signals, a well-written contract notice for a 50,000 EUR requirement looks the same as one for a 500,000 EUR requirement. If your bid team spends 20,000 EUR preparing a proposal for the 50,000 EUR contract, you need a 100% win rate and 40%+ margin just to break even on the bid cost.

Passing on large contracts by default. When value is unknown, risk-averse teams default to conservative resource allocation. They submit a lean proposal when the contract value justified a full team effort. The result: a thin proposal that loses to a competitor who sized the opportunity correctly.

Both failure modes are preventable. Historical data, specification analysis, and structured estimation give you enough precision to allocate resources rationally. Not perfectly — but rationally.

The tools exist. The data exists. The question is whether you build it into your process or continue bidding with one eye closed.