Quality Control in Construction Documentation: Review Processes, Backcheck, Coordination Reviews, and Standard of Care

Examines QA/QC procedures used during the production of construction documents, including internal review workflows, backcheck procedures, interdisciplinary coordination reviews, and the legal concept of the architect's standard of care as it applies to documentation quality.

ARE · Project Development & Documentation

Overview

Construction documents are the bridge between design intent and built reality. When errors or coordination failures slip through, the consequences range from costly change orders to structural failures. Quality control in construction documentation is the systematic set of processes that catch problems before they leave the office.

This topic covers four connected areas. First, the review processes that firms use to check their own work, from redline markups to formal sign-off procedures. Second, the backcheck step, where the original reviewer confirms that corrections were actually made. Third, coordination reviews, which ensure that architectural drawings agree with structural, mechanical, electrical, and plumbing documents. And fourth, the standard of care, the legal benchmark that defines what level of quality the profession owes to clients and the public.

For the ARE, you need to understand how these processes fit together and apply them to realistic project scenarios. A firm that skips coordination reviews or treats backchecks as optional is not just producing sloppy documents; it is exposing itself to professional liability claims. These QC procedures are how architects meet their legal obligation to produce documents with the skill and diligence ordinarily exercised by competent practitioners. A structured QC process catches errors before they reach the field, where the cost of correction is 10 to 100 times higher than fixing them during document production.

Essential

Getting a set of construction documents out the door without errors is harder than it sounds. Multiple disciplines produce hundreds of sheets, and every dimension, note, and detail must agree with the rest of the set. Quality control is the structured process that makes this possible. ## QA vs. QC: Know the Difference Quality assurance (QA) is the system. It covers the firm's written procedures, standards, checklists, and protocols that govern how work gets produced. Think of QA as the playbook. Quality control (QC) is the act of checking. It means reviewing specific deliverables against the playbook to find and fix errors before documents leave the office. QC is hands-on; QA is the framework that tells you what to check and when. On the ARE, getting these two confused is a common trap. If a question asks about establishing review procedures for a firm, that is QA.

Professional

Consider a mid-size firm producing construction documents for a 200,000-square-foot mixed-use building with ground-floor retail, four floors of office space, and two levels of below-grade parking. The structural system is post-tensioned concrete, the envelope is a curtain wall system with stone veneer base, and the MEP systems include a central chilled water plant. Twelve consultants are involved. The project architect establishes a QC plan at project kickoff. It identifies review milestones at 50% DD, DD completion, 50% CD, 90% CD, and final CD. At each milestone, a designated reviewer (a senior associate not on the production team) performs a discipline-specific review using the firm's standard checklist, supplemented by project-specific items for the post-tensioned structure and curtain wall system. At the 50% CD review, the reviewer identifies 47 comments across 22 architectural sheets.

TLDR

QA is the system (procedures, checklists, protocols). QC is the act of checking specific deliverables against that system.
Internal reviews happen at project milestones (DD, 50% CD, 90% CD, 100% CD) using phase-specific checklists and independent reviewers.
Backcheck is the reviewer's follow-up to confirm that corrections from the initial review were actually made. Without it, the QC process is incomplete.
Coordination reviews check for conflicts between architectural and consultant drawings (structural, MEP, fire protection). BIM clash detection assists but does not replace professional judgment.
The standard of care does not require perfection. It requires the skill and diligence a reasonably competent architect would exercise under similar circumstances.
Coombs v. Beede (1896) is the seminal case establishing that design professionals are not guarantors of a perfect result.
Risk-based review depth means complex or unfamiliar projects get more rigorous reviews than straightforward ones.
Title block sign-offs identify who designed and who reviewed each sheet, creating clear accountability.
Consultant QC includes requiring quality plans with proposals and rating consultant performance over time.

ELI5

Think about turning in a big school project. You wrote a report, drew diagrams, and your lab partners each contributed their own sections. Before handing it in, you'd want someone else to read it and check for mistakes. That is quality control. In architecture, the "big project" is the construction documents. These are the drawings and instructions that tell the builder exactly how to construct the building. Hundreds of pages. Thousands of dimensions. And a bunch of different specialists (structural engineers, mechanical engineers, electrical engineers) each contributing their own drawings. So here is how firms check their work: The Review: Someone who did not draw the plans reads through them with a checklist. They mark every mistake they find with a red pen (or digitally). This person is like your teacher marking up a draft.

AREProject Development & Documentation

Quality Control in Construction Documentation: Review Processes, Backcheck, Coordination Reviews, and Standard of Care

2 min read220 words

Why QC in Construction Documents Matters More Than You Think

Want to track your progress and access more study tools?

Create a free account