The question owners actually need answered isn't "which review is better, peer review or constructability review." It's narrower than that: which one is built to catch a conflict that doesn't live inside any single discipline's sheets, but in the seam between two of them? That's a different test than code compliance or calculation accuracy, and it's the one a lot of document sets quietly fail even after passing a rigorous peer review.
Both reviews happen before construction starts. Both put an outside set of eyes on the drawings. But a peer review and a constructability review are scoped to answer different questions, and the cross-discipline conflict — the duct that collides with a beam, the fire-rated wall with more penetrations than its detail accounts for, the structural grid that doesn't reconcile with the mechanical riser three sheets away — falls squarely on one side of that line, not the other.
Peer Review Was Built to Check One Discipline Against Itself
Peer review has its deepest roots in structural engineering and building envelope work, where an independent professional checks another engineer's calculations, code compliance, and design logic. That heritage still shapes how the service is usually scoped today: a structural peer review checks structural work, an envelope peer review checks the envelope, and even where a peer review is broadened to cover coordination with adjacent trades, the reviewer is judged on design credentials in that discipline, not on field or cross-trade experience.
That scoping isn't a flaw — it's the right tool for what a peer review is actually for. Confirming a calculation is correct, or that a design meets code, requires exactly the kind of same-discipline expertise a peer review is staffed with. The problem only shows up when a peer review's discipline-by-discipline structure gets asked to do a job it was never built for: catching a conflict that only exists when two disciplines' sheets are read against each other.
Why a Discipline-Siloed Review Structurally Can't See the Seam
Interdisciplinary coordination and verification is exactly the kind of check that gets neglected when documents are reviewed in single-discipline silos — because each reviewer, reading only their own discipline's sheets, has no way to see that another discipline's equally correct drawing occupies the same physical space. The structural sheet is internally consistent. The mechanical sheet is internally consistent. Read separately, both pass. Read together, a duct runs straight through a beam that was never coordinated against it.
A related failure shows up when disciplines model or draft at different levels of detail — one team finalizing dimensions and routing while another is still working from a schematic layout. Coordination breakdowns concentrate exactly at those mismatches, because the review process on either side has nothing to check the other side's assumptions against.
This is the same structural gap covered in our companion piece comparing what each review is scoped to check: a peer review's boundary is drawn around a discipline, and a conflict that lives outside that boundary — at the interface between two disciplines — simply isn't inside the frame the reviewer is looking through.
What a Constructability Review Is Actually Built to Do at the Interface
A constructability review inverts that frame. Instead of one reviewer checking one discipline's sheets against that discipline's own standards, a constructability reviewer reads every discipline's sheets against every other discipline's sheets, from the specific vantage point of the crew that has to build all of it in the same physical space. The reviewer isn't asking "does this calculation check out" — they're asking "does this duct, this beam, and this fire-rated wall all fit together the way the set implies they do."
That's why the qualifying background is different. A constructability reviewer needs to have actually drawn or built from sets like the one in front of them — someone who has routed MEP against a structural grid before, and knows from firsthand experience which interface points collide most often, structural framing against duct and pipe runs foremost among them. That's field pattern-recognition, not design credentials, and it's what lets a reviewer catch a seam conflict that two discipline-correct sheets, each internally sound, would otherwise hide from a same-discipline reviewer entirely.
That 48% figure is worth sitting with. The FMI/PlanGrid study that produced it broke the number down further — roughly 26 percentage points from poor communication between team members, and roughly 22 from poor or inaccessible project information. Neither of those causes is a design-accuracy failure a peer review is scoped to catch; both are exactly the kind of seam problem a review built around reading disciplines against each other exists to close before it reaches the field.
A Concrete Example: Two Sheets That Each Pass Peer Review and Still Collide
Take a mechanical riser routed against a structural grid on a multi-story build. A structural peer review confirms the beam sizing, connection details, and load path are correct — the sheet passes on every standard a structural engineer would apply to it. A separate mechanical peer review, if one even happens, confirms duct sizing and equipment selection are correct on the mechanical sheet. Both reviews can close out clean. Neither one, by design, ever puts the structural sheet and the mechanical sheet side by side to check whether the riser's routed path and the beam's placement actually leave clearance for each other — that comparison is a different discipline of scrutiny entirely, and it's the one a constructability review is specifically staffed to run.
The conflict doesn't surface because either sheet was drawn carelessly. It surfaces because nobody's review scope ever put the two sheets in the same frame. That's the distinction that matters more than which review is generically "more thorough" — a peer review can be extremely rigorous within its discipline and still never touch a cross-discipline seam, because the seam was never inside its scope to begin with.
Can a Peer Review Ever Cover Cross-Discipline Conflicts?
Only if it's explicitly scoped to, and even then it's doing a second job on top of its first one. Some firms do offer combined QC and constructability peer reviews that fold interdisciplinary coordination checking into a broader review engagement — but that's a deliberate scope expansion, not something a standard, discipline-specific peer review does by default. An owner relying on a peer review to also catch cross-discipline conflicts needs to confirm, in writing, that interdisciplinary coordination is actually part of what's being checked — not assume it's implied because the reviewer is qualified and thorough within their own discipline.
Key takeaways
- A standard peer review's unit of analysis is one discipline's sheets, checked against that discipline's own design standards — not against another discipline's sheets.
- Cross-discipline conflicts hide specifically because each discipline's drawings can be internally correct and still occupy the same physical space as another discipline's equally correct drawings.
- A constructability review's reviewer background — field or document-production experience across disciplines — is what makes reading disciplines against each other possible in the first place.
- The FMI/PlanGrid study found 48% of U.S. construction rework ties to poor project information and miscommunication — failure modes a same-discipline peer review isn't scoped to catch.
- A peer review can cover cross-discipline conflicts only if it's explicitly scoped to do so in writing; that isn't the default shape of the service.
Frequently Asked Questions
Does a peer review ever catch cross-discipline conflicts?
Occasionally, incidentally, but not by design. A standard peer review is scoped to check one discipline's work against that discipline's own standards, so a reviewer might happen to notice an obvious cross-discipline issue in passing, but nothing in the review's structure requires reading two disciplines' sheets against each other. Catching that kind of conflict reliably requires a review explicitly scoped for interdisciplinary coordination — which is a different, broader engagement than a standard peer review.
Why can two sheets each pass peer review and still conflict with each other?
Because each sheet is being checked against its own discipline's standards in isolation, not against the other discipline's sheets. A structural sheet can be fully correct on load path and connection detailing, and a mechanical sheet can be fully correct on duct sizing and routing logic, while the two together still show a duct running through a beam neither reviewer ever compared against the other.
What background should a reviewer have to catch cross-discipline conflicts?
Field or document-production experience across multiple disciplines, not design credentials in a single one. Someone who has actually routed MEP against a structural grid, or drawn a penetration detail that had to reconcile with a fire rating, has the pattern recognition to see a seam conflict that a reviewer checking only one discipline's standards has no reason to look for.
Should a project get both a peer review and a constructability review?
For any set with multiple trades sharing tight coordination, yes — they're checking different things and neither substitutes for the other. A peer review protects against a design-accuracy failure inside one discipline; a constructability review protects against a coordination failure at the seam between disciplines. Skipping either one leaves a specific, identifiable category of risk uncovered in the set.