Estimating
Why estimate traceability matters
Where did this number come from? Why quantities, sources, formulas, assumptions, and revisions must remain visible — especially when AI assists the estimator.
August 8, 2026 · Infrenta Team · 3 min read
Every serious bid review eventually asks the same question:
Where did this number come from?
If the room cannot answer, the number is not an estimate. It is a claim.
Traceability is the discipline of keeping the answer attached to the number: quantity, source pricing, productivity, formula, assumptions, escalation, indirects, markups, and the revision that was issued. It is not a PDF stamp. It is a graph you can walk.
Quantities
A dollar total is a quantity times a rate, unless it is an allowance pretending to be a measurement. Traceability starts by saying which.
If the quantity came from a layout revision, say which revision. If it was typed, say it was typed. If it was factored from DC megawatts, say the factor. Silent factors become folklore, and folklore does not survive an owner’s engineer.
Source pricing
Rates come from somewhere: a vendor quote, a library, a historical job, an override, a guess. Those are not the same epistemic class.
A quote has a vendor, a date, and a validity window. A library rate has a vintage. An override has a person. If the cell only shows 4.25, you have already lost the argument about whether it is still true.
Productivity
Labour and equipment burn time. Productivity is an assumption about the ground, the weather, the access, and the crew. When productivity is baked into a unit rate, you cannot change the calendar without laundering the rate.
Traceable estimating keeps hours and production visible so a superintendent can disagree with a number that will become their plan.
Formulas
Formulas should be boring and inspectable. Immediate formulas — quantity × rate, build-up sums, markup on cost — are the opposite of a macro that nobody owns.
If a total cannot show its immediate formula, it cannot be reviewed. It can only be trusted or rejected as a blob.
Assumptions
Foundation type, origin country, coating spec, winter construction, and spare-part philosophy are assumptions. They belong next to the numbers they move. An assumption buried in a kickoff deck will not be in the RFQ.
Escalation
Escalation is time-shaped risk. If it is spread into every kilogram, you cannot remove it when the purchase is immediate, and you cannot defend it when the index moved the other way.
Keep escalation attributable: index, period, scope.
Indirects
Duration-based indirects exist because a longer job costs more even if the direct quantity did not change. If indirects are a round lump, a foundation change that adds six weeks will not show up until the field is already there.
Markups
Markup is policy. Cost is physics and market. Mixing them produces a sell price that cannot be unpacked when a customer asks for a cost-plus view or when procurement needs a should-cost.
Keep cost, markup, and sell price distinct. Markups and adjustments describes how Infrenta treats that split.
Revisions
Traceability without revisions is a screenshot. The question is not only where the number came from, but *which issued number* you are explaining. Drafts move. Issued revisions should not.
AI makes this more important, not less
Assistance that suggests rates, extracts quotes, or maps BOM lines will touch more nodes than a human types. That is the point. It is also the hazard.
If a model suggests twenty numbers and you cannot see which nodes changed, you cannot review the estimate. You can only hope. Hope is not a bid strategy.
The correct architecture is:
- deterministic compilation of the commercial graph
- a trace for any numeric root
- optional language on top of the trace, never instead of it
That is why Explain This Number is a product principle rather than a slogan. See Explain This Number.
What traceability is for
It is for the estimator who has to answer the room. It is for the second estimator who inherits the file. It is for procurement, which should buy the issued quantity. It is for project controls, which needs a baseline. It is for the post-mortem, which otherwise becomes a story about personalities.
Connected software can keep the graph. It cannot force a team to stop pasting totals into slides. The teams that keep the graph will still lose some jobs. They will lose fewer arguments about jobs they already won.
If you cannot open a number, you do not own it. If you do not own it, you cannot stand behind it. That is the whole issue.
Related articles
Estimating
Why solar estimating breaks at scaleAI & Technology
AI in construction estimating: where it actually helpsGeotechnical
From geotechnical report to foundation decision