Pre-Construction QA: Catching Errors Before They Reach the Field

What pre-construction QA actually covers

Pre-construction QA covers the document checks that need to happen before drawings, specifications, and related construction information are relied on in the field. It focuses on accuracy, coordination, completeness, and buildability so the project team can identify document issues before they become construction problems.

Document QA vs field QC: where this fits

Pre-construction QA is a subset of quality assurance, the preventive half of the QA/QC program that operates entirely on documents before a shovel touches the ground. Field QC catches defects after the work is done. For the full QA/QC framework, see construction QA/QC.

What the pre-construction QA review examines

A pre-construction QA review examines drawing coordination across disciplines, specification to drawing consistency, code compliance, constructability, and the completeness of the document set, focusing on how these elements align within the full set of construction documents before issue for construction.

Why pre-construction document review matters

Pre-construction document review matters because document errors are easier to correct before they affect procurement, sequencing, and field labor. Once construction begins, the same issue can trigger RFIs, change orders, rework, downtime, and schedule pressure.

The cost curve: finding issues early vs late

The cost curve is simple: an error caught during design review costs a fraction of what the same error can cost once crews, materials, and subcontractors are already committed. The FMI/PlanGrid Construction Disconnected report found that 52% of rework was caused by poor project data and miscommunication, which makes early document QA a direct risk-control step, not an administrative review.

What drawing errors actually cost

Drawing errors become expensive because they create non-productive labor, resequencing, waiting time, duplicated work, and avoidable coordination effort. FMI Corporation estimated that more than $177 billion is lost annually in U.S. construction due to rework, data inefficiency, and miscommunication, showing how document quality problems scale beyond isolated field mistakes.

The link between document errors and RFIs

Unresolved drawing conflicts, missing details, and specification-to-drawing discrepancies are among the primary generators of RFIs during construction. When the answer changes scope, pricing, sequence, or responsibility, the same document gap can also become a change order, which is why pre-construction QA focuses on resolving these issues before they reach the field.

The pre-construction QA process

The pre-construction QA process works best as a structured sequence, not a loose drawing review. Each step narrows the risk, moving from document completeness to discipline checks, coordination, compliance, and final issue tracking.

Step 1: Assemble the full document set

The review must include all project documents together, not disciplines in isolation: architectural, structural, civil, and MEP drawings; all specification divisions; applicable codes and amendments; approved submittals or RFI responses; zoning approvals; and permit conditions. This step is often skipped when reviewers check drawings without cross-referencing specifications, which can hide conflicts between what is drawn and what is required.

Step 2: Discipline-by-discipline review

Each discipline is reviewed for internal consistency before cross-discipline checking begins. The review checks dimension strings, detail references, sheet index completeness, note conflicts, and other issues within the same drawing set. This step keeps basic architectural, structural, civil, or MEP errors from being confused with coordination conflicts between disciplines.

Step 3: Cross-discipline coordination check

Cross-discipline coordination is where the highest-frequency document issues surface. Structural elements may conflict with MEP routing, architectural ceiling heights may be inconsistent with structural depth, and civil grades may conflict with architectural floor elevations.

A plan check at this stage helps surface these overlaps before they turn into field conflicts.

Step 4: Spec-to-drawing verification

Specifications and drawings are often produced by different teams, which can leave them out of sync. Common failures include drawings that reference a product or system not specified, specifications that call for a performance standard not reflected in the drawing details, and Division 01 requirements that are not carried through to the technical divisions.

Step 5: Code compliance review

Code compliance review checks drawings against applicable building codes, local amendments, and referenced standards. It flags code edition conflicts, such as drawings referencing a superseded code edition, along with occupancy classification inconsistencies and ADA/accessibility gaps in dimensional details.

Step 6: Issue log and resolution

Every finding must be logged with the drawing or specification reference, issue description, discipline responsible, and resolution required. Issues without a log entry cannot be tracked to closure. The log becomes the pre-construction QA record for RFI tracking, change order disputes, and lessons learned.

What a pre-construction QA review should catch

A pre-construction QA review gives the project team a practical, discipline-specific view of the document issues most likely to affect construction. It looks for common drawing mistakes, coordination gaps, missing information, and inconsistent requirements before those issues reach the field.

Architectural coordination issues

Architectural coordination issues often surface as layout inconsistencies or missing information that affects other disciplines. Common problems include partition layouts that do not align with structural grids, reflected ceiling plans that do not account for MEP routing space, and incomplete or conflicting detail references within the drawing set. These issues matter because architectural drawings define the spatial framework that other disciplines rely on.

Structural coordination issues

Structural coordination issues usually appear where framing systems interact with architectural layouts and building systems. Common problems include beam depths that conflict with ceiling heights, slab openings that do not align with MEP requirements, and inconsistencies between structural plans and detail sections. These issues can block routing paths, affect coordination, and force redesign or field adjustments if they are not identified early.

MEP coordination conflicts

MEP conflicts with structure are the highest-frequency coordination issue type across projects. Common issues include ductwork routing that conflicts with structural beams and joist spaces, plumbing drain slopes that conflict with floor-to-floor height assumptions, and electrical panel locations that are not coordinated with architectural partitions.

These are the issues that generate the most RFIs if they are not caught during pre-construction review.

Spec-drawing discrepancies

Specification and drawing discrepancies occur when written requirements do not match what is shown on the drawings. Common problems include drawings referencing products or systems not specified, specifications calling for performance standards not reflected in details, and mismatches between general requirements and technical sections. These gaps create ambiguity in scope, responsibility, and pricing during construction and often lead to RFIs or clarification requests.

Code compliance gaps

Code compliance gaps appear when drawings do not fully align with applicable codes and accessibility requirements. Common issues include incorrect occupancy classifications, missing or inconsistent egress information, and ADA or accessibility dimensions that are incomplete or non-compliant. These issues typically result in plan review comments, resubmissions, or required corrections if they are not resolved before submission.

Who performs pre-construction QA

Pre-construction QA is performed by four distinct reviewer types, each with different scopes and limitations. These include the design team, the general contractor, third-party reviewers, and AI-assisted tools that support document review.

Design team self-review

Design team self-review catches internal errors before drawings are issued. It is effective because the team understands design intent, but it also has blind spots due to familiarity with the documents, which can make gaps and conflicts harder to detect.

GC pre-construction review

GC pre-construction review focuses on sequencing, means and methods, and coordination gaps that affect buildability. It is often part of a constructability review, where the contractor evaluates how the documents translate into field execution.

Third-party plan review

Third-party plan review provides independent eyes on the document set. It helps identify code issues, missing information, and coordination gaps that internal teams may overlook, but it adds time and cost to the process.

AI-assisted review

AI-assisted review processes the full document set to identify coordination conflicts and code gaps across disciplines. It is a support tool for document analysis, not a replacement for engineering judgment or professional responsibility.

When to perform pre-construction QA

Pre-construction QA should follow standard AEC design milestones because each phase has a different review scope and cost consequence. Issues caught early are easier and less expensive to resolve, while later-stage issues carry higher coordination, schedule, and field impact.

At schematic design

In schematic design, pre-construction QA focuses on concept-level coordination failures. The review checks whether major program, site, structure, circulation, code, and building system assumptions are aligned. Issues found at this stage are the least expensive to correct because the design is still flexible and major decisions have not yet been fixed.

At design development

At design development, QA becomes the primary window for discipline coordination. Architectural, structural, civil, and MEP systems are developed enough to compare across disciplines, but not so final that changes create major rework. This phase is where spatial conflicts, system assumptions, and coordination gaps should be identified and resolved.

At construction documents

At construction documents, QA focuses on documentation completeness, internal consistency, and spec alignment. The review checks whether drawings, schedules, notes, details, and specifications reflect the same requirements. This phase helps catch missing references, inconsistent details, and spec-to-drawing discrepancies before the documents are used for permitting or bidding.

At issued for construction

As issued for construction, QA acts as the final gate before construction begins. This is the most critical checkpoint because the document set is complete and drives field execution. AI-assisted review adds the most value at this stage by processing the full document set to identify coordination conflicts and code gaps at scale.

How InspectMind supports pre-construction QA

InspectMind supports pre-construction QA at the issued-for-construction stage, where the full document set is assembled and the volume of cross-checks exceeds what manual review can reliably cover. It processes drawings and specifications together to identify coordination conflicts, code gaps, and spec-drawing inconsistencies across disciplines.

InspectMind has identified more than 187,000 issues across 500+ firms, reflecting the scale of document-level risk at IFC. A plan check helps teams surface these issues before they translate into RFIs, change orders, or field delays, while professional judgment drives final decisions.

Frequently asked questions

How long does a pre-construction QA review take?

Manual review of a mid-size project document set can take days to weeks, depending on the number of disciplines, drawing sheets, specifications, and review scope. AI-assisted review can return document-level findings within hours because it processes the full set quickly, but engineering judgment is still needed to evaluate, prioritize, and resolve those findings.

What is pre-construction QA?

Pre-construction QA is the systematic review of construction documents like drawings, specifications, codes, and submittals before construction begins. It identifies errors, coordination conflicts, and code gaps at the document stage, where they are least expensive to resolve, before they generate RFIs, change orders, or rework in the field.

What is the difference between pre-construction QA and field QC?

QA and QC support different parts of the construction process. QA in construction focuses on quality plans, assurance procedures, and proactive review before work starts, while field QC checks built work against quality standards during construction phases.

Who is responsible for pre-construction document review?

The project manager, design team, general contractor, and third-party reviewers may all support pre-construction QA. Construction companies often use a QA tool or quality management system to track quality issues, quality objectives, and review findings.

What documents should be reviewed in pre-construction QA?

Pre-construction QA covers architectural, structural, civil, and MEP drawings; all specification divisions; applicable building codes and local amendments; approved submittals or RFI responses already issued; and any zoning approvals or permit conditions. The full document set must be reviewed together, not by discipline in isolation, to catch conflicts between what is drawn and what is specified.