Engine · Closeout · LIVE

Closeout reconcile. Bid against actual cost.

Bid vs Actual is the Trueleveler engine that, at project closeout, reconciles the awarded bid line-by-line against final job cost. CSI-by-CSI variance with root-cause attribution — was it the field, the buyout, the COs, or the estimate itself?

Try it now

Bid vs Actual runs on your original bid and PO log and needs a free account (no card). It has no sample data yet, and the no-signup demo only levels bids.

Per CSI
division variance
5
root-cause categories
3
inputs: bid, POs, change orders
Closeout
when it runs

See it run

A screen recording of Bid vs Actual on sample project data, with a voice-over and subtitles.

Transcript

See which trade ran over.

Reads bids, purchase orders, change orders.

Bid versus Actual compares every trade.

The overrun is traced to the change orders behind it.

01 · Why most firms never run this

The loop that never closes.

Bid-vs-actual reconciliation is the most-skipped step in construction. Everyone knows it should happen. Nobody does it consistently. Three reasons:

Reason 1

The data lives in 4 places

Original bid in the estimator's spreadsheet. Buyout numbers in the PM's tracking sheet. Actuals in accounting. COs in a folder somewhere. Reconciling means cross-referencing four systems that don't speak the same language.

Reason 2

Closeout is exhausting

The team that ran the project is already three jobs deep into the next ones. Going back to do BvA the right way means budgeting a week of senior estimator time on a job that's already in the rearview.

Reason 3

Nobody likes the answer

BvA exposes patterns that are uncomfortable. The estimator routinely under-prices Division 16. The PM routinely over-spends on changes. Surfacing these is politically delicate — better to just bid the next job.

This engine builds the reconciliation from the data already in the project's memory. It surfaces patterns calmly — not finger-pointing, just data.

02 · The variance report

One row per CSI division. One root cause per row.

The output is a structured variance report. Each CSI division gets a row showing bid, buyout, actuals, COs, and the delta — with a root-cause attribution for divisions flagged as significant overruns (variance above +15%) or significant wins (below -10%).

03CONCRETEBid $1.84M · Final $1.79M · Variance -2.7% · Buyout savings + tight execution. Under budget
05STEELBid $980K · Final $1.01M · Variance +3.1% · Below firm threshold. Within tolerance
09FINISHESBid $640K · Final $698K · Variance +9.1% · Root: 22 owner-directed CO line items (cabinetry upgrades). Not estimator error. Owner scope
15PLUMBINGBid $720K · Final $812K · Variance +12.8% · Root: original estimate priced PEX. Spec required Type L copper. Not caught at takeoff. Estimate gap
16ELECTRICALBid $1.42M · Final $1.64M · Variance +15.5% · Root: site condition changes (3 unexpected utility relocations) + 6 CO line items. Field + scope
23HVACBid $1.20M · Final $1.18M · Variance -1.7% · Tight buyout, clean execution. Use this sub again. Reliable
ΣTOTALBid $11.2M · Final $11.5M · Variance +2.6% · Within the +15%/-10% significance band. 2 divisions outside — root cause: estimate gap (Div 15) + field changes (Div 16). 2 outside the band
5 root-cause categories

Estimate gap (under-priced takeoff) · Owner scope (CO-driven, not estimator fault) · Field condition (site reality differed from drawings) · Buyout swing (vendor pricing moved between bid and award) · Execution (sub over-ran their own bid). Each variance is tagged with the dominant cause — sometimes more than one applies and we weight them.

★ · Pairs with

It works alone. It's better in a chain.

Bid vs Actual works alone. It also uses the change orders, pay application actuals and procurement actuals that other engines already hold for the project.

  • CO Review — CO totals + verdicts feed the "owner scope" root-cause attribution.
  • Procurement Tracker — committed and spent procurement amounts feed the variance, and a variance traced to material overruns opens the procurement log.
03 · FAQ

Things everyone asks first.

What if our project didn't use Trueleveler from the start?

BvA still works — you import the bid, the final cost report, and the CO log; the engine builds the variance report from those three. The root-cause attribution loses precision (it can't cross-check against Procurement deliveries or Schedule Risk for field-condition flags) but the basic CSI variance + 5-bucket categorization is intact.

Run BvA on a closed job. See the patterns.

Bring a recently-closed job to a call. We'll process bid + actuals + COs live and produce the variance report on screen.

Try Free for 14 Days →