Quality Assurance vs Quality Control in Architecture Practice
Distinguishes quality assurance (process-based prevention) from quality control (output-based detection) and examines how architecture firms implement QA/QC programs across project phases to reduce errors, manage risk, and deliver higher-quality buildings.
Why QA and QC Are Not the Same Thing
Here's a distinction that trips up candidates on the PcM exam constantly: quality assurance and quality control sound similar, but they operate at completely different levels of a firm's practice.
Quality assurance (QA) is about the system. It's the policies, procedures, checklists, training programs, and review protocols a firm puts in place to prevent errors from happening in the first place. Think of QA as the infrastructure that makes good work repeatable.
Quality control (QC) is about the output. It's the act of checking drawings, specifications, calculations, and other deliverables to catch errors that already exist. A redline review of a set of construction documents? That's QC.
Why does this matter for practice management? Because a firm that only does QC is playing defense. You're catching mistakes, sure, but you're catching them late, when they're expensive to fix. A firm with a strong QA program prevents those mistakes from occurring, which reduces rework, lowers professional liability exposure, and produces more consistent project outcomes.
The ARE tests whether you understand this distinction and, more importantly, whether you can evaluate which approach applies in a given scenario. You'll need to recognize when a firm should invest in process improvement (QA) versus when it needs to inspect deliverables more carefully (QC), and how the two work together across schematic design, design development, construction documents, and construction administration.
Want to track your progress and access more study tools?
Create a free account