A coordination error caught during design development takes hours to resolve. The same error caught during construction administration takes weeks and costs real money. The question of when to run a drawing quality assurance check is not procedural housekeeping. It determines whether your team fixes a problem cheaply in the drawing set or expensively in the field.
This article maps specific QA check types to each design phase milestone: design development (DD), construction documents (CD), and issued for construction (IFC). Each phase demands a different category of review. Running the wrong check at the wrong phase wastes time. Skipping the right check at the right phase creates liability.
About 14 min read
Run drawing QA checkUpload drawings, specs, and codes. Eligible work emails get a $100 credit and cited issues in hours.
5+ issues or full refund · No demo required
A coordination error that survives DD review gets locked into the bid set. Contractors price it, the GMP absorbs it, and the error becomes a contract condition rather than a design correction. Fixing it at that stage requires a change order, a schedule impact, and a design revision that cascades across multiple discipline sets.
This compounding effect is why phase gates carry formal review obligations, not just internal team checkpoints. The AIA Document B101 phase completion obligations establish phase completion as a contractual milestone with defined deliverable expectations. Each gate is a structured opportunity to catch a category of error that becomes more expensive to correct at every subsequent phase.
The mechanism works in one direction. As a drawing set progresses from DD through CD to IFC, the cost and contractual complexity of correcting any given issue compounds. A missing occupancy classification at DD is a correction. The same missing classification at IFC is a change order, a permit revision, and potentially a contractor claim.
Drawing quality assurance is not a single checklist applied at 100% completion. It is a phased process where the check type changes because the document status changes. The sections below define what to look for at each gate and why earlier or later review fails for each category.
The DD set is the last phase where design assumptions can be challenged without triggering scope changes or schedule impact. Design development drawings represent a critical decision point. If an occupancy classification assumption is wrong at DD, it can be corrected before structural sizing, egress calculations, and MEP systems are locked in. If it survives to CD, the correction cascades across multiple disciplines simultaneously.
The QA focus at DD is on completeness of design intent and interdisciplinary alignment. Annotation accuracy and code-citation completeness are CD-stage concerns. Trying to review DD drawings for permit-ready notation is reviewing the wrong thing at the wrong time.
Before DD sign-off, the team must confirm the IBC Chapter 5 determinations against the architectural floor plans and the site data. Occupancy group, construction type, allowable building area, and height must all reconcile with what the drawings actually show. This is the single highest-value QA check at the DD stage.
A mismatch between the building's programmed occupancy and its proposed construction type is a DD-stage error. If it survives to CD, the correction requires a redesign of the fire-rated assembly schedule, the egress system, and potentially the structural system. Those three cascading revisions affect four to six discipline sets. Catching the mismatch at DD means editing one table.
This check is what answers the question of what a design development drawing checklist must cover first. Before checking coordination between disciplines, confirm that the fundamental code assumptions underlying all discipline designs are correct.
At DD, the structural grid, MEP system routing zones, and architectural layout must be checked for gross conflicts. This is not clash detection in the building information modeling (BIM) sense. It is a review of whether the structural framing strategy is compatible with the mechanical equipment rooms shown on architectural plans, whether vertical circulation cores align across disciplines, and whether the civil grading and drainage design is consistent with the building's first-floor datum.
This check requires cross-referencing at least three discipline sets simultaneously. That cross-discipline scope is exactly where single-discipline internal reviews consistently fail. The drawing coordination process for a DD set must treat the structural, architectural, and civil documents as a single coordinated package, not three separate reviews.
A vertical circulation core that does not align between the architectural and structural plans at DD becomes a framing conflict at CD. Catching it now takes a markup. Catching it after the structural engineer has sized and scheduled every member costs revision time across both discipline sets.
DD specifications are outline specs. They name systems and materials without full section detail. A QA check at DD must confirm that the materials and systems named in the outline spec are consistent with what the drawings actually show.
A DD set that shows a steel moment frame but references a masonry specification outline carries a conflict that will grow in complexity through the CD phase. A set that shows a chilled water HVAC system but references a packaged rooftop unit specification has the same problem in the mechanical discipline. These are not annotation errors. They are design intent conflicts. For a detailed breakdown of how these conflicts compound as specs develop into full-section documents, see the article on spec vs drawing conflicts.
The CD set is what the building department reviews for permit, what contractors price for their bids, and what the engineer of record (EOR) seals. An error surviving into construction documents does not just affect design. It affects contract pricing, permit approval, and potentially the EOR's professional liability.
The QA focus shifts from design intent alignment to annotation accuracy, code citation completeness, schedule-to-drawing consistency, and spec section coordination. These are high-volume, cross-referencing checks that manual review regularly misses on sets larger than 40 sheets.
At CD, every element shown on the drawings must be findable in the corresponding schedule, and every schedule entry must match what appears on the drawing sheets. Door schedules, window schedules, finish schedules, structural member schedules, and equipment schedules must all reconcile with the floor plans and details.
The failure modes are specific and common. A door schedule that lists a fire rating for a door that is not shown as fire-rated on the floor plan creates a code compliance gap that AHJ plan examiners frequently flag. A beam schedule that calls out a W12x26 while the framing plan shows W12x19 at the same gridline creates a procurement conflict the contractor will price inconsistently. Catching either error before permit submission takes minutes. Correcting it after the permit is issued means a revision to the stamped documents.
The CD set submitted for permit must include specific code citations, accessible route designations, fire-rated assembly labels with UL design numbers or equivalent, egress capacity calculations, and occupant load postings. Missing or incorrect citations are among the most common plan check comments issued by authorities having jurisdiction (AHJs).
A drawing quality assurance check at this stage confirms that each required notation type is present, correctly referenced, and consistent with the design intent. This is the specific category of check an AI plan check performs before permit submission. Catching missing UL assembly numbers or incorrect accessible route callouts before the set reaches the plan examiner reduces permit correction cycles directly.
At CD, the specifications are full-section documents, not outlines. Every product, system, and material referenced in the specifications should have a corresponding drawing reference, and every drawing callout should have a corresponding specification section.
A specification section for a product that does not appear anywhere in the drawing set creates scope ambiguity. A drawing callout that references a non-existent specification section produces the same problem from the other direction. Contractors will price these gaps inconsistently. Some will include the cost, others will not, and the variance surfaces as RFI prevention failures during construction. The scope ambiguity created by a missing spec-to-drawing link at CD routinely produces field-stage change orders.
The CD set must be reviewed for conditions that are technically code-compliant but physically difficult or impossible to build as drawn. A constructability review at the CD stage catches these conditions before they reach the field.
Common examples include a wall assembly that requires access from two sides simultaneously, a mechanical shaft that cannot be maintained without demolishing a structural member, and a foundation detail that requires excavation below an adjacent footing without a shoring strategy shown. None of these conditions necessarily fails a code check. All of them produce field RFIs, delays, or cost overruns when the contractor encounters them during construction.
Issued for construction (IFC) drawings are not the architect's CD set with a new stamp. They are a contractor-assembled document package that incorporates the permit-issued CD set, all addenda issued during bidding, request for information (RFI) responses received before contract execution, value engineering substitutions accepted by the owner, and any architect's supplemental instructions (ASIs) issued between permit and construction start.
The IFC set is the document of record for construction. The CD set is the document of record for permit. They are related but not identical, and treating them as synonyms is where the most expensive coordination failures originate.
The liability implication is direct. If a conflict exists between the CD set and an addendum, the IFC set resolves that conflict, but only if the addendum was correctly incorporated. If the general contractor (GC) assembles an IFC set that misses an addendum revision, the conflict survives into construction. The QA check at IFC is a reconciliation check, not a design review. The design is already set. The question is whether the document package accurately reflects all formal modifications made to it.
The IFC drawing quality assurance check must confirm that every addendum issued during bidding has been incorporated into the relevant drawing sheets. It must also confirm that no addendum revision conflicts with the original CD drawing it modifies. This is a drawing revision control problem, not a design intent problem.
A drawing transmittal log and a numbered addendum register are the baseline controls for this check. If either is absent, the IFC set cannot be verified as complete. The check is straightforward when records are maintained: compare each addendum item against the corresponding sheet in the IFC package and confirm the revision appears.
This is the most frequently skipped QA step in the entire construction document cycle. Teams that complete rigorous CD-stage reviews often assume the IFC set is a clean copy. It frequently is not.
Value engineering substitutions accepted between bid and contract must appear consistently across all affected drawing sheets and specification sections. A substitution that replaces a specified curtain wall system with an alternate manufacturer must be reflected in the window schedule, the glazing specifications, and the detail sheets. Recording it only in the VE log is insufficient.
A QA check at IFC must trace each accepted substitution through every drawing and specification reference that the original product touched. Failure to do this produces field-stage RFIs when the contractor orders the substituted product and discovers the detail sheets still show the original system's anchoring and flashing conditions.
That gap is not a design error. It is a document assembly failure that a structured IFC review would have caught before the first anchor was ordered.
InspectMind reviews full document sets, drawings and specifications simultaneously, and returns a structured issue report with sheet references and code citations. Design teams and GCs upload a PDF drawing set before permit submission or before issuing for construction, and the review identifies coordination conflicts, schedule inconsistencies, missing code notations, and spec-versus-drawing mismatches across all disciplines.
The platform is self-serve, starting at $50 per upload, with no per-user fees and a guarantee of five or more issues or a full refund. For teams running a pre-construction QA check at the CD stage, the review processes the full set and returns findings in hours, not weeks.
Design development drawings define the design intent, system selections, and interdisciplinary coordination at roughly 60% completion, according to the architect's basic services framework. Construction documents are the fully annotated, code-cited drawing and specification set submitted for permit and used for contractor pricing. The primary QA difference is scope: DD review checks design assumptions and gross coordination conflicts, while CD review checks annotation accuracy, schedule consistency, and specification coordination.
Issued for construction drawings incorporate the permit-issued CD set plus all modifications made after permit: bidding addenda, pre-contract RFI responses, accepted value engineering substitutions, and any ASIs. The IFC set is the construction document of record. It may differ from the CD set in ways that are legally significant, and the QA check at IFC must verify that every modification was correctly incorporated.
Before permit submission, the drawing set should be checked for drawing-to-schedule consistency across all discipline schedules, permit-required notations and code citations including UL assembly numbers and accessible route designations, specification-to-drawing cross-references, and constructability conflicts. These checks address the categories of error that AHJs most frequently flag during plan check and that contractors most frequently price inconsistently during bid.
Gross MEP coordination conflicts, including mechanical equipment room sizing, vertical shaft alignment, and structural-to-duct routing conflicts, should be resolved at DD. Detailed MEP coordination, including precise routing, clearances, and dimensional accuracy review, occurs at CD. Conflicts that survive to IFC produce field RFIs and are resolved at the highest possible cost.
A drawing coordination checklist at DD must cover three areas: IBC Chapter 5 code assumption verification (occupancy group, construction type, allowable height and area), interdisciplinary alignment between the structural grid, MEP routing zones, and architectural layout, and specification outline consistency with what the drawings show. These three checks address the categories of error that cascade most severely if they survive to CD.
Yes. DD-stage review is specifically designed for sets that are not yet complete. The check types appropriate at DD, code assumption verification, interdisciplinary alignment, and outline specification consistency, do not require a complete drawing set. Waiting for 100% completion to run any QA check is the most common cause of late-stage coordination failures. Each design phase milestone carries specific review obligations that are most cost-effective when performed at that gate.
Upload PDF drawings and specs. Get flagged issues with evidence and code citations in hours.
5+ issues or full refund · No demo required
Sample report: 282 issues found|Pricing after first check
227,181+ customer-visible issues across 2,000+ customer accounts
