The dangerous sub bid is rarely the one with an obviously wrong total. It is the one whose bottom line looks perfectly competitive while the line items underneath have been rearranged to move risk and cash onto your job. That rearrangement is what "unbalanced" and "front-loaded" describe, and you cannot see it from the cover sheet — you have to read the unit prices. The four checks below do exactly that, deterministically, so the same pattern gets flagged every time. They are the risk core of subcontractor bid analysis, and each one is just arithmetic you can run on a leveled field of bids.
What unbalancing and front-loading actually are
An unbalanced bid keeps the total roughly where it should be but moves the money around between line items. The sub prices some items far above cost and others far below — sometimes down to a penny — so the sum still reads competitive while the individual numbers are distorted. A front-loaded bid is one specific flavor of that: the dollars get pulled toward items billed early in the job, most often mobilization, so the sub collects cash before the work that justifies it has actually happened.
Subs do this for reasons that are usually rational from their seat, and that is exactly why it is common rather than rare:
- Cash flow. Front-loading mobilization or early items gets money in the door sooner, which funds payroll and equipment before progress billings catch up. It is an interest-free advance paid by your project.
- Quantity-overrun games. If a sub believes a unit-priced item will overrun the engineer's estimated quantity, they price that item high and offset it by pricing a likely-underrun item low. The total looks fair at bid quantities; the sub profits when the field quantities land where they expected.
- Hiding a thin number. A penny-priced line can bury work the sub does not want to draw attention to, or shift cost onto an item where your tab is less likely to scrutinize it.
None of this requires bad faith to hurt you. Even an honest sub front-loading for cash flow is moving risk onto the owner and onto you. The job of detection is not to assign motive — it is to surface the pattern so you can ask the question before award.
The four deterministic rules, with the math
These fire on numbers, not judgment, which is what makes them defensible. Run all four across the leveled field — every bidder mapped to your scope, unit prices lined up per item, a peer median computed for each row.
1. Unbalanced unit price: any unit price ≤ $1.00
A unit price at or below a dollar on a real scope item is almost never a real cost. It is a placeholder that pushes cost off this line and onto another. Suppose five subs price "Remove Existing Pipe" between $34 and $52 per LF, and one bids $0.01 per LF. That penny is not a saving — the cost of that removal still exists, it has just been relocated to an item the sub expects to bill more of. The rule is flat: any unit price ≤ $1.00 on a priced scope item gets flagged for a reason. The fix is to ask where that cost actually went and confirm it is carried somewhere legitimate.
2. Peer outlier: a unit price > 2× or < 0.5× the peer median
For each scope item, take the median of every bidder's unit price — the median, not the average, so one wild number can't drag the benchmark. Then flag any price more than double or less than half of it. Example: on "12-inch RCP," the unit prices come in at $80, $84, $88, $91, and $95, so the peer median is $88. The flag band is anything above $176 or below $44. A sixth sub at $190/LF trips the high side; a seventh at $30/LF trips the low side. The high one is often a quantity-overrun play or a genuine misread; the low one is often a number that won't survive the first change order. Either way the line earns a written explanation.
3. Total-bid outlier: a total > 20% off the field
Step back from the line items and look at the whole number. If the field of totals clusters and one bidder sits more than 20% away from it, that gap is rarely a pure pricing decision — it is usually a scope misunderstanding. Say the package field is $2.40M, $2.55M, $2.61M, and $2.58M, a field around $2.55M. A bid at $1.95M is roughly 24% low and trips the rule; a bid at $3.20M trips it on the high side. The low one almost always missed something — traffic control, dewatering, a phase — and the "saving" is a future change order. The high one carried something nobody else did, or read the plans differently. The flag tells you to find out which before you crown a low bidder.
4. Front-loaded mobilization: mobilization > 10% of the total
Mobilization is the classic front-load vehicle because it bills first. Take the mobilization line as a share of the bid total; if it exceeds 10%, flag it. On a $2.55M bid, the 10% line is $255,000. A sub carrying $330,000 of mobilization (about 13%) is pulling roughly $75,000 forward relative to the threshold — cash collected before the work de-risks. Sometimes that is legitimate: a job with heavy early equipment moves or a remote site genuinely costs more to mobilize. The rule does not assume abuse; it forces you to confirm the early draw is justified by the early work, not by the sub's cash needs.
| Flag | Threshold | What it usually means |
|---|---|---|
| Unbalanced unit price | Unit price ≤ $1.00 | Cost shifted off this item — penny-priced to game quantity overruns or hide it elsewhere. |
| Peer outlier | > 2x or < 0.5x the peer median for that item | A misread quantity, a typo, or a number that won't survive a change order. |
| Total-bid outlier | Total deviates > 20% from the field | A scope misunderstanding — the low one missed something, or the high one carried something nobody else did. |
| Front-loaded mobilization | Mobilization > 10% of total bid | Cash pulled forward; the sub gets paid before the work de-risks. A schedule and cash-flow exposure. |
One note on the peer-outlier and median math: it needs no government data to work. The benchmark is the field of bids in front of you, normalized to a peer median, so the same checks run in any US state. Built-in state-DOT pay-item baselines exist for a couple of states as a head start on mapping line items, but they are never required for the rules above to fire.
How to respond to a flag
This is the part estimators get wrong in both directions. A flag is not an automatic disqualification, and it is not something you wave off because the bidder is cheap. A flag is a forced question with a written answer.
- A penny unit price means you ask where that cost is carried and confirm it. If it is genuinely covered in a lump item and the sub will hold the unit price for overruns, that may be fine — but you write down why.
- A peer outlier means you check the quantity and the description against your scope. A 2× price on an item with a wrong takeoff is a different problem than a 2× price the sub will honestly hold.
- A total-bid outlier means you reconcile scope before anything else. A bid 24% low with a missing phase is not the low bid; a bid 24% low that genuinely found efficiency is a real win you should be able to point to.
- A front-loaded mobilization means you confirm the early draw matches early work, and if it doesn't, you negotiate the billing curve or carry the exposure knowingly.
The discipline that protects you is recording the reason. When you override a flag and proceed anyway, that override should be logged with your justification, so six months later — on a $40M job, in front of an owner or a partner — the answer to "why did we accept that bid?" is a sentence you already wrote, not a memory you have to reconstruct. The flags catch the pattern; the written reason is what makes the award defensible.
Running all four without losing the thread
Each of these rules is simple. Running all four across 8–12 bids, every package, on bid day, by hand, is where they get skipped — and the one you skip is the one that costs you. Bid Reasoner applies the four rules deterministically across the leveled field, attaches a page-cited evidence quote to each flag so you can see exactly where the number came from, and logs every override with its reason into an audit trail. The result is that the math runs the same way every time and your attention goes to the four conversations that actually matter. If you want the broader workflow these checks sit inside, start with subcontractor bid analysis.