A cost estimator and a constructability review consultant can sit down with the exact same issued set and produce two reports that barely overlap. That surprises owners who assume a detailed estimate already covers "will this work" along with "what will it cost." It doesn't, structurally — the two disciplines are built to answer different questions, using different methods, and a set can sail through a rigorous estimate while still carrying coordination conflicts that turn into six-figure change orders once steel and ductwork meet in the field.
What a cost estimator is actually checking for
An estimator's job starts with a quantity takeoff: measuring every wall, slab, duct run, and conduit run shown on the drawings and converting that into a list of quantities in a standard format — cubic yards of concrete, linear feet of pipe, square footage of curtain wall — that can be priced against unit costs. The estimator reviews the drawings and specs closely, but the read is quantitative: does this sheet show enough information to count it, and does the specification confirm what material and finish it's made of. The output is a number, or more precisely a range, since the industry's own classification system (AACE's 18R-97) ranks estimates from Class 5 — a rough order-of-magnitude figure built on minimal project definition — down to Class 1, a fully detailed estimate built from a complete, coordinated set.
That last point matters more than it sounds like it should. An estimator's accuracy depends on the set being complete and internally consistent enough to count against. It doesn't require the set to be buildable. A duct routed through a beam it can't physically pass through still has a length, still gets measured, still gets priced — the estimator has no mechanism, and generally no scope, to check whether the beam and the duct were coordinated with each other in the first place. Pricing a conflict doesn't resolve it; it just prices the wrong version of the building.
What a constructability review consultant is actually checking for
A constructability review reads the same set through a different lens entirely. The Construction Industry Institute defines constructability as the use of construction knowledge and experience in planning, design, procurement, and field operations to achieve overall project objectives — which in practice means the reviewer is asking whether what's drawn can physically go together, in the sequence the trades will actually build it, without the design fighting itself. That's a cross-discipline read: does the structural beam depth shown on S-series sheets leave clearance for the duct routing shown on M-series sheets at the same grid line; does the electrical panel location on E-series conflict with the plumbing chase on P-series; does a wall type called out on the architectural set match what the structural set assumes is bearing.
None of that requires a quantity takeoff or a unit price. It requires overlaying disciplines against each other, sheet by sheet, and flagging the points where they disagree — the exact conflicts that don't show up as a pricing error because each discipline's drawing is internally consistent on its own. The set can be complete enough to count and price cleanly and still be uncoordinated enough to stop work in the field.
An estimator working from a Class 1 (fully detailed) estimate is confirming the set has enough information to price completely — not that the information across disciplines agrees with itself. Completeness and coordination are two different properties of the same set, and only one of them is what an estimate checks for.
Where the two roles overlap, and where they split
Both roles work from the issued set. Both read specs alongside drawings rather than drawings alone. Both are trying to protect the owner from a bad surprise later in the project. That surface similarity is exactly why owners sometimes assume a strong estimate already covers coordination — the estimator clearly went through the set in detail, so it feels redundant to pay for a second read.
The split is in what "going through the set in detail" means for each discipline. The estimator's detail is depth within a trade: how much concrete, how much conduit, at what unit cost. The reviewer's detail is breadth across trades: does this trade's assumption match that trade's assumption at the point where they physically meet. A takeoff can be exhaustive within the mechanical drawings and never once check the mechanical drawings against the structural drawings at the same coordinate. That cross-check is the entire job description of a constructability review, and it's largely absent from a cost estimator's scope by design — not because estimators are careless, but because it isn't what a takeoff is built to test.
The blind spot each role has
An estimator's blind spot is coordination: a conflict between two disciplines that are each internally consistent produces no pricing anomaly, so nothing flags it. It surfaces later — during shop drawing coordination, or worse, in the field — as an RFI, then a change order once the fix requires re-routing, re-fabricating, or re-sequencing work that's already been priced and, in some cases, already been ordered.
A constructability review consultant's blind spot runs the other way: a findings report tells an owner exactly where the set disagrees with itself and what it will cost in schedule and dollars if it's not fixed before bid, but it isn't a substitute for a priced estimate. A reviewer flags that a duct and a beam collide; the reviewer doesn't produce the line-item cost of the whole HVAC scope. Owners who skip the estimate because they've commissioned a review end up with a clean, coordinated set and no idea what it costs to build — the reciprocal version of the same mistake.
Why owners need both, not one instead of the other
Neither role is a smaller version of the other; they're answering questions that don't substitute for each other. An estimate without a constructability review can be accurate and still price a set that can't be built as drawn — the number is real, but it's pricing the wrong building. A constructability review without an estimate confirms the set is coordinated but tells an owner nothing about whether the coordinated version is affordable. The full scope of what a constructability review consultant delivers is explicitly the coordination layer, not the pricing layer — the two are meant to run in parallel, ideally before bid, so an owner is pricing a set that's already been checked for the conflicts an estimator isn't scoped to catch.
The cost of skipping that check shows up later as real change order exposure rather than as a line item anyone budgeted for, and it's the same gap covered in the exposure framework for design errors and omissions: a conflict that isn't caught pre-bid doesn't disappear, it just moves from the review stage to the field stage, where it costs more to fix and comes with a schedule impact an estimate was never built to predict.
Key takeaways
- A cost estimator measures and prices quantities within each trade; a constructability review consultant checks whether trades agree with each other at the points where their work physically meets.
- A set can be complete enough to estimate accurately (even at AACE Class 1 detail) and still carry uncaught cross-discipline coordination conflicts — completeness and coordination are separate properties.
- An estimator's blind spot is coordination conflicts that don't show up as pricing anomalies; a reviewer's blind spot is that a findings report isn't a priced estimate.
- Skipping either role doesn't eliminate its blind spot — it just defers the cost to later, typically as an RFI or a change order once the conflict surfaces in the field.
- The two scopes are meant to run in parallel pre-bid: a coordinated set gives the estimate something real to price, and a priced estimate tells the owner what the coordinated version actually costs.
Frequently Asked Questions
Does a detailed cost estimate already catch coordination conflicts?
Not by design. A quantity takeoff measures and prices what's shown within each trade's drawings; it doesn't cross-check one trade's assumptions against another's at the points where their work overlaps. A set can support a fully detailed (AACE Class 1) estimate and still contain uncaught conflicts between disciplines, since those conflicts don't register as pricing errors.
Can a constructability review replace a cost estimate?
No. A constructability review confirms the set is buildable as drawn and flags cross-discipline conflicts with their cost and schedule exposure, but it isn't a substitute for a priced, quantity-based estimate. An owner needs both: a coordinated set to price, and a price for the coordinated version.
Who typically catches a structural-MEP clash first, the estimator or the reviewer?
Usually the reviewer, and often before the estimator would ever encounter it. A takeoff can price a duct run and a beam independently without either quantity revealing that they physically occupy the same space; a constructability review is specifically checking whether the structural and mechanical sheets agree at that grid line.
Is it worth paying for both a cost estimator and a constructability review consultant on the same project?
For any set with multiple trades in tight coordination, yes — they're answering different questions and neither one's output substitutes for the other's. Running both before bid means the estimate is pricing a set that's already been checked for the conflicts a takeoff isn't built to find.