Definition
An apples-to-apples comparison is what a general contractor produces before it ranks the subcontractor bids it receives for a scope package. Each sub quotes in its own format — one sends a single lump sum, another itemizes dozens of unit-price lines, a third names the same work differently and quietly drops an item or two. Comparing the cover-sheet totals as they arrive is an apples-to-oranges comparison: the numbers look like peers but measure different scopes and different units. An apples-to-apples comparison removes those differences first. Every bid is restated against one scope of work, missing items are priced in, and units are reconciled so a per-cubic-yard rate and a lump sum for the same task line up.
Only after that normalization do the totals mean the same thing. The phrase is shorthand for the discipline behind a fair ranking: don't compare numbers until they describe identical work.
A worked example
You receive two bids on a drainage package. Sub A sends a single lump sum of $580,000 for the whole scope. Sub B sends a 40-line unit-price bid that totals $558,000 — the apparent low by $22,000. Before comparing the totals, you restate both onto one scope. Reading Sub B's 40 lines against your SOW, you find no line for trench restoration, which your scope requires; priced at the field rate, that work is worth about $31,000. You add it, bringing Sub B to $589,000. Now the two totals describe the same work. After the apples-to-apples comparison, Sub A is the lower bid by $9,000 — the reverse of what the raw cover sheets showed.
Why it matters when you evaluate sub bids
On a heavy-civil package with 5 to 15 bidders, the bid that wins on raw total is often the one that excluded the most, because every exclusion becomes a future change order with that sub's name on it. An apples-to-apples comparison is the bridge between a stack of differently-formatted bids and a defensible award. You cannot honestly score price, run a scope-gap analysis, or justify the pick to an owner until the field is normalized. It is the difference between awarding to the lowest number and awarding to the lowest responsible price for your full scope — and it is what every later step, from the bid tab to the award memo, rests on.
How Bid Reasoner handles it
Bid Reasoner builds the apples-to-apples comparison for you. It reads each bid PDF, maps every line item to your scope of work, and runs a two-way scope-coverage gap analysis that surfaces exclusions — like Sub B's missing trench restoration — as gaps with page-cited evidence quotes. Normalization uses peer-median baselines so the method works in any US state with no government data required; built-in state-DOT pay-item baselines give you a head start in select states, but are never a requirement. On the leveled field, four deterministic risk rules fire: unbalanced unit prices at or under $1.00, peer outliers above 2x or below 0.5x the peer median, total-bid outliers beyond 20% of the field, and front-loaded mobilization over 10% of total. The result is a scope-equalized tab you can score across price, scope, schedule, compliance, performance, and risk — and rank in minutes.