The Problem
A 2025 survey of 170 architects by AORBIS ("Beyond the Specs 2025") identified recurring specification problems that generate downstream project cost. The most common: specifications copied from prior projects with minimal modification, products specified that have been discontinued or superseded, and conflicts between drawing intent and specification language that don't surface until a contractor submits an RFI or a substitution request.
These aren't isolated errors. They are predictable outcomes of a manual process that depends on individual memory, reused templates, and deadline-driven review cycles. When a spec lists a product that hasn't been available for two years, the contractor generates an RFI and requests a substitution. The engineer reviews it, the back-and-forth adds days to the schedule, and neither party bills for the time. When drawings and specifications conflict, the conflict typically surfaces in the field, where resolution is the most expensive.
A 2025 Springer Nature study found that BIM adoption reduces design errors by 30 percent and RFIs by 25 percent across multiple construction project case studies. (Das, Khursheed & Paul, Discover Materials, 2025) The inverse is instructive: firms operating without structured, coordinated documentation processes carry the inverse risk. A 25 percent reduction in RFIs on a project running 50 active RFIs is 12 to 13 fewer resolution cycles, each of which takes the better part of two weeks and absorbs engineer time that wasn't budgeted for it.
What's Driving It
The specification problem has two root causes. The first is a workflow design problem: most MEP firms don't have a defined process for auditing specifications against current product availability, current project drawings, and current code language before they are issued. Specs get written, reviewed at a high level, and issued under deadline pressure. Detailed cross-referencing happens, if at all, after the fact, when a contractor flags a discrepancy.
The second is a knowledge currency problem. Specifications require current knowledge of available products, current editions of referenced standards, and current applicable code sections. That knowledge changes continuously. A spec section written eighteen months ago referencing a standard that has since been revised, or a product that has been discontinued, is a document waiting to generate a problem.
Neither root cause reflects a failure of engineering skill. They reflect a process that puts the burden of currency and consistency entirely on the individual engineer, without systematic support.
What Resolution Looks Like
A specification workflow with structured AI support changes where the burden falls. Instead of the engineer bearing full responsibility for cross-referencing every product reference, code citation, and drawing coordination point, the system flags conflicts and currency issues before the document is issued. Discontinued products get surfaced. Conflicts between spec language and drawing content get identified at the review stage rather than the field stage. Referenced standards get checked against current editions.
The engineer still owns every technical decision in the spec. What changes is that the document they're reviewing has already been checked against the inputs they would otherwise have to verify manually. The hours that went into that verification are recovered. The errors that slipped through manual review are reduced.
For MEP firms producing specifications on multiple concurrent projects, the cumulative effect is significant: fewer RFIs per project, fewer substitution requests, fewer field conflicts that trace back to documentation that didn't get audited before it was issued.
QP designs specification workflows using the same logic applied in regulated engineering environments, where a document that's wrong at issuance creates problems that are expensive to unwind. That discipline transfers directly to commercial MEP work, where a specification error discovered in the field is a field problem by the time anyone finds it.
The Bottom Line
Specifications govern the project. A specification that is inaccurate, outdated, or inconsistent with the drawings doesn't just create administrative work. It creates contractual risk and field conflict. The cost of an undetected specification error compounds with every project phase it travels through.
The manual process of writing and reviewing specifications is not the problem. The absence of a structured workflow that systematically checks specifications before they leave the team is.
Sources: AORBIS "Beyond the Specs 2025" (survey of 170 architects); Das, Khursheed & Paul, "The impact of BIM on project time and cost: insights from case studies," Discover Materials, Vol. 5, Article 25, Springer Nature, 2025 (DOI: 10.1007/s43939-025-00200-2)
If your specification process relies on individual engineers catching their own errors under deadline pressure, that's a workflow worth examining.
Quantum Precision helps MEP firms design documentation workflows that reduce downstream friction at the source.
See how a spec audit workflow works →