Where residential CD sets break down—and how production teams can catch the problems before drawings reach the field.

Category: Construction Documentation / QA/QC
Audience: Architects, builders, contractors, BIM managers and AEC production teams
Estimated reading time: 10–12 minutes

VISUAL 1 — HERO IMAGE

Alt text: Where construction documentation breaks down across plans, sections/elevations, details, schedules, coordination and final issue.

A Drawing Set Can Be “Complete” and Still Fail in the Field

A construction-documentation package can contain hundreds of sheets, details, schedules and annotations—and still leave critical questions unanswered.

The problem is rarely that the project has too few drawings. More often, the problem is that the information does not agree.

A dimension may conflict with an overall dimension. A window may appear in the plan but not match the elevation. A wall type may be correct in the model but represented incorrectly in a detail. A structural opening may not align with the architectural layout. A revision may be made in one location but missed somewhere else.

Each issue may look minor during production. On site, however, these small inconsistencies can turn into:

RFI → clarification → rework → delay → additional coordination

That is why construction-document QA/QC should not be treated as a final formatting exercise. It is a production-control process.

Table of Contents

1. 1. Why Construction Documentation Failures Matter
2. 2. The 15 Failure Points
3. 3. Geometry and Dimension Failures
4. 4. Drawing-to-Drawing Coordination Failures
5. 5. Information and Schedule Failures
6. 6. Consultant Coordination Failures
7. 7. Model-to-Sheet Failures
8. 8. Revision and Issue-Control Failures
9. 9. What Should Be Checked Before Issuing?
10. 10. A Practical Pre-Issue Workflow
11. 11. Conclusion
12. 12. FAQs

1. Why Construction Documentation Failures Matter

A construction drawing communicates design intent to people who may not have been involved in creating the design.

That includes:

• Contractors
• Subcontractors
• Estimators
• Fabricators
• Consultants
• Permit reviewers
• Site supervisors
• Project managers

They depend on the documents being consistent, understandable and sufficiently coordinated.

When information is missing or contradictory, the field team has to stop and ask: “Which information should we follow?”

Not every RFI is caused by poor documentation. Design development, unforeseen site conditions and legitimate construction questions will always generate RFIs. But documentation errors can create avoidable questions.

The objective of QA/QC is not to eliminate every question. It is to eliminate questions that the drawing set should already have answered.

2. The 15 Construction Documentation Failure Points

The framework below focuses on failures that commonly appear when project information moves from design through BIM production, documentation, coordination and final issue.

#	Failure	Typical consequence
01	Dimensions don’t reconcile	Layout uncertainty
02	Plans and sections disagree	Incorrect interpretation
03	Doors/windows don’t match schedules	Procurement or installation issues
04	Wall types aren’t consistently represented	Assembly confusion
05	Details don’t match the design	Field interpretation
06	Detail references are incorrect	Wrong information used
07	Revisions don’t propagate	Outdated information
08	Architectural/structural openings conflict	Site coordination
09	MEP requirements are discovered late	Rework or routing conflicts
10	Model information doesn’t match sheets	Documentation inconsistency
11	Generic details are used without project review	Missing project-specific information
12	Annotations are incomplete or ambiguous	Interpretation problems
13	Permit information is inconsistent	Review comments or resubmission
14	PDF output introduces problems	Poor issued documents
15	No independent pre-issue review	Errors survive to issue

VISUAL 2 — 15 FAILURE-POINT FRAMEWORK

Alt text: Fifteen construction-documentation failure points grouped under geometry, documentation, coordination, information and issue control.

3. Failure #1 — Dimensions Don’t Reconcile

One of the most basic documentation checks is also one of the most frequently overlooked.

A plan may show overall dimensions, partial dimensions, room dimensions, wall offsets and opening dimensions. But do they actually agree?

Example: Overall building dimension = 40′-0″, while the individual dimension chain adds up to 40′-4″.

The problem is not simply a wrong number. The contractor now has to determine which number represents the intended design.

Common causes include:

• Design changes
• Wall movement
• Dimension strings not updated
• Manual annotation
• Inconsistent reference points
• Information copied from earlier drawings

How to catch it:

Do not only compare the dimension against the Revit model. Check the dimension chain against itself.

Prevention:

Where possible, use model-driven dimensions and include a dedicated dimension review before issue.

4. Failure #2 — Plans and Sections Disagree

A floor plan communicates horizontal information. A section communicates vertical information. They must describe the same building.

Inconsistencies can occur when floor levels, ceiling heights, roof geometry, slab thicknesses, wall assemblies or openings change.

QA/QC test:

Select critical elements and trace them across Plan → Elevation → Section → Detail. Do not review each drawing as an isolated document.

5. Failure #3 — Doors and Windows Don’t Match Their Schedules

Schedules are not secondary documentation. They are structured project information.

A door tag might say D-04 while the schedule shows a different size, type or configuration. The same issue can occur with windows.

Check:

For representative and critical openings, verify Plan Tag ↔ Model Element ↔ Schedule ↔ Elevation.

6. Failure #4 — Wall Types Aren’t Consistently Represented

Wall assemblies can contain information about structure, insulation, sheathing, air/water control layers, finishes and fire-resistance requirements.

A wall type may be correctly configured in the BIM model but incorrectly represented in a section or detail.

Trace critical wall types through:

Plan → Wall Type / Legend → Section → Detail

7. Failure #5 — Details Don’t Match the Actual Design

Generic details can accelerate production. They can also create problems when copied into a project without being properly reviewed.

A detail might show an assembly, material, thickness, waterproofing approach, structural condition or window system that no longer matches the project.

A beautifully drafted wrong detail is still wrong.

8. Failure #6 — Detail References Are Incorrect

A drawing can contain excellent details and still fail if references do not point to the correct destination.

Check:

• Detail number
• Sheet number
• Reference location
• Detail title
• Actual condition represented

Simple rule: Never review a reference without following it.

9. Failure #7 — Revisions Don’t Propagate Through the Set

A revision can look complete in one drawing while related documentation still reflects the previous condition.

For example, a window change may appear in the floor plan while the elevation, schedule or wall section still shows the old condition.

Better approach:

Every significant design change should trigger an impact review. Ask: “Where else does this information appear?”

10. Failure #8 — Architectural and Structural Openings Conflict

Architectural and structural models can each appear correct independently. The problem emerges at the interface.

• Door or opening conflicts
• Beam crossing an architectural opening
• Structural column occupying a required space
• Stair geometry not matching structural framing
• Roof geometry conflicting with framing

A useful coordination sequence is:

Clash detected → design intent reviewed → solution agreed → model updated → drawings checked

Closing a clash without resolving the underlying design condition is not sufficient coordination.

11. Failure #9 — MEP Requirements Are Discovered Too Late

MEP coordination can become particularly difficult in residential projects because available service zones may be limited.

A ceiling cavity may need to accommodate ductwork, plumbing, electrical services, lighting, structure and access requirements.

Typical symptoms:

• Ceiling conflicts
• Insufficient service space
• Plumbing routes crossing structure
• Equipment access problems
• Unplanned bulkheads
• Shaft conflicts

Prevention:

Bring major MEP constraints into the coordination process before architectural documentation is finalized.

12. Failure #10 — The BIM Model Doesn’t Match the Issued Sheets

A model can be correct while the drawings are still wrong.

Final documentation includes view settings, filters, annotation, detail components, tags, dimensions, crop regions, schedules and sheet placement.

Model QA ≠ Drawing QA

Both are required because the issued PDF—not the internal Revit environment—is the actual deliverable.

13. Failure #11 — Generic Details Are Used Without Project Review

Standard details are useful production tools. The problem occurs when “standard” becomes “automatic.”

A standard detail should be treated as a starting point, not proof that the project condition has been resolved.

Before issuing it, ask:

• Does this assembly exist here?
• Are the materials correct?
• Does the structural condition match?
• Does the waterproofing approach match?
• Does it match the plan and section?

14. Failure #12 — Annotations Are Incomplete or Ambiguous

Construction documentation is not only geometry. Information is communicated through notes, dimensions, tags, keynotes, symbols, legends, references and schedules.

The objective is not to add more notes. It is to provide the information required to remove meaningful ambiguity.

15. Failure #13 — Permit Information Is Inconsistent

Permit documentation has requirements that depend on the jurisdiction, project type and applicable codes.

A package may contain the correct design but still require revisions because information is missing, contradictory, incorrectly referenced or incomplete.

QA/QC should therefore include a project-specific permit checklist. This is not a replacement for professional code review; it is a production control to help confirm that required information is present.

16. Failure #14 — Problems Appear Only in the Final PDF

The Revit model can look fine and the sheets can look fine, yet the exported PDF can reveal lineweight, text, cropping, reference, sheet-order or visibility problems.

The final deliverable is not Revit. It is the issued PDF/document package.

Review the actual output that the client, contractor or authority will receive.

17. Failure #15 — No Independent Pre-Issue Review

The person who creates a drawing becomes familiar with its appearance. After reviewing the same sheet repeatedly, the brain can begin to recognize what it expects to see rather than what is actually there.

An independent reviewer approaches the document differently.

Production: create and coordinate the documentation.
QA/QC: challenge the documentation.

VISUAL 3 — ONE CHANGE, MULTIPLE CONSEQUENCES

Alt text: A window change propagating through the floor plan, elevation, window schedule, wall section, detail and architectural/MEP/structural coordination.

18. One Change Can Create Six Problems

This is why documentation QA/QC cannot be reduced to a checklist of isolated errors.

Example: A WINDOW CHANGES

• Floor Plan — opening position changes.
• Elevation — exterior composition changes.
• Window Schedule — size/type changes.
• Wall Section — head/sill condition may change.
• Detail — interface may require modification.
• Coordination — structural or MEP interfaces may be affected.

One design change can have six or more documentation impacts.

Experienced BIM production teams therefore do not only ask, “Was the change made?” They ask, “Where does this information exist elsewhere in the project?”

VISUAL 4 — HOW A DOCUMENTATION ERROR REACHES THE JOBSITE

Alt text: A six-step chain from design change to missed update, drawing conflict, RFI, field clarification and rework or delay.

19. From Documentation Error to RFI

The chain often looks like this:

Design Change → Missed Update → Drawing Conflict → RFI → Field Clarification → Rework / Delay

The RFI itself is not necessarily the problem. The question is whether the documentation could have answered it before construction. If yes, the issue belongs in the production and QA/QC process.

20. What Should Be Checked Before Issuing?

A strong pre-issue review should cover five areas.

1. Geometry

• Walls
• Openings
• Levels
• Roofs
• Stairs
• Major elements

2. Documentation

• Dimensions
• Tags
• Notes
• References
• Details
• Schedules

3. Coordination

• Structural
• MEP
• Architectural interfaces
• Consultant information

4. Information consistency

• Model
• Views
• Sheets
• Schedules
• Details

5. Final issue

• Revisions
• Sheet index
• PDF output
• Legibility
• Issue date
• Final review

The exact checklist should always be adapted to the project, client requirements and applicable jurisdiction.

21. A Practical Pre-Issue Workflow

Stage 1 — Model Setup

• Project standards
• Levels
• Grids
• Families/types
• Links
• View structure

Stage 2 — Production

• Geometry
• Dimensions
• Openings
• Documentation
• Schedules

Stage 3 — Coordination

• Structural interfaces
• MEP interfaces
• Major penetrations
• Critical clearances

Stage 4 — 90% CD Review

• Completeness
• Details
• References
• Schedules
• Notes
• Consultant coordination

Stage 5 — Final Issue

• Revision control
• Sheet index
• PDF output
• Legibility
• Final consistency
• Independent review

This is safer than performing one massive QA/QC review after the entire set is complete, because earlier reviews can catch issues before they propagate through the package.

22. The 15-Point Failure Prevention Checklist

☐ Do all major dimensions reconcile?

☐ Do plans agree with sections and elevations?

☐ Do door/window tags agree with schedules?

☐ Do wall types agree across drawings and details?

☐ Do details represent actual project conditions?

☐ Do all references point to the correct destination?

☐ Have revisions been propagated through affected documentation?

☐ Are structural openings coordinated?

☐ Are major MEP requirements coordinated?

☐ Does the model agree with the issued drawings?

☐ Have generic details been project-reviewed?

☐ Are annotations sufficient and unambiguous?

☐ Has the project-specific permit checklist been reviewed?

☐ Has the actual PDF been checked?

☐ Has an independent person performed the final review?

If several answers are “not sure,” the package probably isn’t ready to issue.

23. Conclusion

Construction documentation failures rarely begin as dramatic mistakes. They usually begin as something small: a dimension wasn’t updated, a schedule was overlooked, a section still showed the previous condition, a detail was copied without being reviewed, a consultant change wasn’t propagated, or a revision was made in one view but missed in another.

Individually, these problems may seem insignificant. Collectively, they can create confusion after the drawings leave the office.

The goal of BIM and construction-document QA/QC is therefore not simply to produce a visually complete drawing set. It is to maintain information consistency from design through documentation and into construction.

The strongest production workflow asks three questions repeatedly: What changed? Where else does that information appear? Does the final issued document still communicate one coordinated version of the project?

24. Frequently Asked Questions

Why do construction drawings generate RFIs?

RFIs can arise for many legitimate reasons, but incomplete, contradictory or ambiguous documentation can create avoidable questions during construction.

Can BIM eliminate construction-documentation errors?

No. BIM can improve information coordination and reduce certain types of errors, but models, views, schedules, annotations and issued documents still require QA/QC.

Is a clash-free BIM model enough?

No. A technically resolved clash does not necessarily mean the condition is practical to install, access, maintain or construct.

Should QA/QC happen only before final issue?

No. Reviews should occur at meaningful project milestones so problems are identified before they become deeply embedded in the production set.

Who should perform the final review?

A qualified reviewer who understands the project and documentation standards should ideally review the package independently from the person who produced every sheet.

Should every drawing be checked in the same way?

No. High-risk drawings and interfaces deserve deeper review. The QA/QC process should reflect project complexity and risk.

Can standard details be used in construction documents?

Yes, where appropriate, but they should be reviewed and adapted to the actual project conditions rather than inserted without verification.

Why review the final PDF if the Revit model is correct?

Because the issued PDF is the actual deliverable. Export, view settings, annotation, lineweights and sheet composition can introduce problems that are not obvious inside the model.

How AtekOne Supports AEC Production

AtekOne Design Solutions provides BIM and AEC production support for architecture, construction and related AEC teams.

BIM Modeling | Revit Production | Construction Documentation | Permit Drawing Sets | Shop Drawings | BIM Coordination | CAD-to-BIM | Scan-to-BIM | AEC Production Support

The objective isn’t simply to add more drawings to a project. It is to help AEC teams turn design information into coordinated, usable and production-ready deliverables.

For firms and builders that need additional production capacity, external BIM/AEC production support can be used for defined project scopes, documentation milestones and production workloads without requiring an immediate expansion of the permanent team.

Explore AtekOne’s BIM & AEC Production Services →
https://atekone.com/