How to Write a Construction Quality Control Plan

Most general contractors have written a QC plan before, usually for a bid submission or because the specification demanded one. Fewer have written one that an owner's reviewer accepted on the first pass. Reviewers reject plans constantly, and almost always for the same handful of reasons: a plan that reads like a template, responsibilities with no name attached, and inspection steps that don't connect to this project's actual spec sections.

This guide walks through the sections a QC plan needs, how to structure the ITPs that carry most of the weight, and where drawing review fits before any field inspection begins.

1. Confirm what the contract actually requires

Before drafting anything, read the contract's quality clause and Division 01 quality requirements section. Federal work following USACE or NAVFAC standards typically mandates a specific format and calls it a Contractor Quality Control (CQC) plan. Design-build and institutional owners often ask for a Project Quality Plan (PQP) that covers both QA and QC in one document. Note the required submittal deadline, since most contracts require the plan before or shortly after notice to proceed, not before the first pour.

2. Build the six core sections

A QC plan that survives submittal review contains these sections at minimum. Skipping any one of them is a common reason plans come back marked up.

3. Structure each ITP the same way

Inspection and Test Plans are where most rejected plans fall apart. A usable ITP covers each of these fields for every spec section on the project, not just the trades an owner is likely to spot-check.

Hold points and witness points do different jobs. A hold point stops work until the QC inspector (or sometimes the owner) signs off, used for irreversible steps like concrete placement or closing in a wall before rough-in inspection. A witness point notifies the owner or third-party inspector that a check is happening, but work can continue if nobody shows up. Mislabeling a hold point as a witness point is a specific, common rejection flag on ITPs for structural and life-safety work.

4. How a QC plan differs from a QA plan

A QC plan documents inspection and testing of completed work. A QA plan documents the process, standards, and training used to prevent defects in the first place. Many specifications bundle both into one Project Quality Plan, which is why the terms get used interchangeably in practice even though they describe opposite halves of a quality system. For the full breakdown of the distinction with examples of each, see QA vs QC in construction.

5. Why owners and CMs reject QC plans

Reviewers see hundreds of these documents. The plans that get returned with markups almost always share one of these problems:

• The plan is a generic template lightly edited from a past project, with placeholder text or another project's name still in it
• QC responsibilities list job titles only, with no named individuals or contact information
• ITPs are boilerplate paragraphs that don't cite this contract's spec sections or hold points
• No defined non-conformance or corrective-action workflow, or one that has no disposition authority named
• No tie between the QC organization chart and the actual project org chart submitted elsewhere in the bid package
• Documentation section describes report formats that don't match what the owner's specification actually requires

6. Where drawing review fits into the plan

Field inspection is not the first QC checkpoint on a project. Reviewing the drawing set itself, checking for coordination conflicts, missing details, code issues, and spec-to-drawing mismatches, is the earliest and cheapest QC step, and a strong QC plan references it explicitly rather than starting the quality narrative at first concrete pour. A plan that only describes field inspections is describing half the QC program.

7. Keep the plan alive after it's approved

An approved QC plan that sits in a binder is worthless. Update the ITP log as spec sections close out, trend the NCR log monthly to catch systemic issues, and revise the org chart when QC staff change, since a plan with outdated names is a documentation gap an owner's auditor will flag at closeout. The drawing QA/QC checklist is a useful companion document for the preconstruction section specifically.

Documents that never get updated stop reflecting how the project actually runs. When a QC plan and the field diverge, the gaps that show up are the same ones that eventually surface as drawing errors and claims late in the project.

Construction Quality Control Plan FAQs