A construction quality plan (often called a project quality plan, PQP or QA/QC plan) sets out how quality will be managed and proven on one specific project: who is responsible, which procedures apply, how work will be inspected and tested, how non-conformances are handled and what records will be handed over. It applies the company's quality management system to the project's contract and specifications. A good one is short enough to be read, specific enough to be audited against, and linked directly to the inspection and test plans and records that prove the work.
What a construction quality plan is for
Most contractors already have a company quality manual, often certified to ISO 9001. The project quality plan answers a different question: given this contract, this client, these specifications and these subcontractors, what will we actually do here?
It serves three audiences:
- The client, who usually requires the plan as a contract deliverable and reviews it before work starts.
- The project team, who need to know which procedures, forms and hold points apply to their work.
- Auditors, internal or external, who use it as the baseline to check the project is doing what it said it would.
If you want a reference on structure, ISO 10005 gives guidance specifically on quality plans. Your contract and the client's specifications will usually add their own requirements on top.
Project quality plan vs quality management plan
The terms overlap and companies use them differently. Broadly:
- A quality management plan is sometimes the owner's or programme-level document, describing how quality will be governed across several contracts.
- A project quality plan or construction quality plan is the contractor's document for one contract or scope.
- A QA/QC plan usually means the same as a project quality plan, sometimes with more emphasis on the inspection and testing regime.
Check what your contract calls it and what it requires. The content matters more than the title.
Section-by-section outline
The outline below works for most construction and EPC projects. Scale it to the job: a small building package needs a few pages; a major process plant needs more, but mostly in the appendices.
| Section | What it should contain |
|---|---|
| 1. Purpose, scope and applicability | Contract, scope of work, sites, phases, what's excluded |
| 2. Quality policy and objectives | Reference to the company policy; a few measurable project objectives |
| 3. Organisation and responsibilities | Quality organogram, named roles, authority to stop work and release holds |
| 4. Reference documents | Contract, specifications, codes and standards, client procedures, with revisions |
| 5. Document and record control | Numbering, revision control, transmittals, record retention |
| 6. Procurement and supplier quality | Supplier approval, vendor inspection, material certificates, receipt inspection |
| 7. Subcontractor quality management | Flow-down of requirements, subcontractor ITPs, surveillance |
| 8. Inspection and testing | ITP register, intervention points, test procedures, ITR templates |
| 9. Control of measuring and test equipment | Calibration register and traceability |
| 10. Personnel competence | Qualifications for welders, NDT operators, electricians, inspectors |
| 11. Non-conformance and corrective action | How NCRs are raised, dispositioned and closed; concessions |
| 12. Audits and surveillance | Audit schedule, scope, follow-up of findings |
| 13. Quality reporting and KPIs | What is reported, to whom, how often |
| 14. Completion and handover records | What goes into the dossier, per system or area |
| Appendices | ITP register, procedure list, form list, organogram |
The main body should explain how things work. Long lists (every procedure, every form, every ITP) belong in appendices or registers that can be updated without reissuing the whole plan.
Linking the quality plan to ITPs and checksheets
This is where most quality plans fail. The plan says "all work will be inspected in accordance with approved ITPs" and stops there. Six months later nobody can trace a line in the plan to a signed record on a tag.
The link should be explicit:
- The quality plan lists the ITPs the project needs, by discipline or work package, with their status (draft, submitted, approved).
- Each ITP names its verifying documents: the ITR or checksheet template for each activity, and the intervention points for each party. We cover this relationship in ITP vs ITR vs checksheet.
- Each template is controlled, with a number, a revision and an owner.
- Templates are allocated to tags or items, using the tag register, so you can list every record the project must produce.
- Completed records roll up by system or area into certificates and the handover dossier.
Once that chain exists, the quality plan becomes auditable: pick any requirement, and you can follow it down to a signed record.
For the discipline content of the checksheets themselves, detailed ITRs and inspection checklists are available at checksheets.com.
Hold points and the quality plan
The quality plan should set the rules for intervention points: which parties can impose hold points, how much notice is required, who is authorised to release them and what happens if one is missed. The ITPs then apply those rules line by line. See hold points and witness points for the practical detail.
Roles and responsibilities that people can act on
A responsibilities section that says "the Project Manager is responsible for quality" is true but useless. Write it so a new starter knows what to do. As a minimum, cover:
- Project quality manager: owns the plan, runs audits, reports quality performance, and has direct access to senior management independent of the construction line.
- QC inspectors (by discipline): carry out and sign inspections, release contractor hold points, raise NCRs.
- Construction supervisors: plan work to allow for hold and witness points, give notice, ensure records are completed at the time.
- Completions or document control: control templates and records, compile dossiers.
- Subcontractor quality leads: submit their own ITPs and records, respond to NCRs.
State plainly who has authority to stop work for quality reasons. If nobody knows, nobody will.
The NCR process in the quality plan
The quality plan should define when a finding becomes a non-conformance rather than a punch item, how NCRs are raised, who can disposition them (use as is, repair, rework, reject), when client approval is needed, and how root cause and corrective action are tracked. Many projects also keep a separate route for concessions and deviations requested before work is done. Keep the process in a procedure and summarise it in the plan, so the two can't drift apart.
Audits: planned, not reactive
Include an audit schedule that covers the project's own processes and its key subcontractors and suppliers. Typical topics are document control, calibration, welding and NDT records, material traceability and completion records. Each audit should produce findings with owners and dates, and the plan should say how overdue findings are escalated.
Early audits are the most valuable. An audit of the first ten completed ITRs will tell you more about your record quality than an audit of ten thousand at handover.
Making the quality plan live rather than shelf-ware
A quality plan that is written to get a contract milestone signed off and then filed is common. The signs are familiar: it references procedures that were superseded, names people who left, and describes a process nobody follows. To keep it live:
- Keep the body short. Put volatile content in registers (ITP register, procedure list, calibration register) that are maintained day to day.
- Brief it. Walk supervisors and subcontractor leads through the parts that affect them at mobilisation, not just the quality team.
- Measure against it. Report a small set of quality KPIs monthly, such as ITPs approved versus required, records completed versus planned, open NCRs by age, and audit findings overdue.
- Revise it on triggers. New phase, new major subcontractor, change of key personnel or a significant audit finding should all prompt a review.
- Make the records the evidence. If the plan's requirements are enforced by the system people use to record work (templates, witness requirements, sign-offs), compliance stops depending on people remembering the document.
That last point is the biggest difference between a plan that works and one that doesn't. Procedures written in isolation drift; records captured in a structured system either meet the requirement or visibly don't. If your team also needs help writing the underlying procedures, workprocedures.com covers SOP writing in depth.
Common mistakes
- Copying the last project's plan without updating specifications, client requirements and roles.
- Listing ITPs that don't exist or have never been submitted.
- No link between the plan's inspection regime and the completions records the client expects at handover. See what goes in a handover dossier.
- An NCR process that nobody uses because defects are quietly logged as punch items instead.
- An audit schedule that is written and never carried out.
Putting the quality plan to work in Accord and Checksheets
Accord turns the plan's inspection regime into enforced workflow: Inspection and Test Records against the system and tag hierarchy, a witnessing workflow, NCRs and punch items with Category A/B/C criticality in one issue register, revision-controlled documents and forms, and an immutable audit trail. Real-time dashboards report completion and readiness.
Checksheets helps QA/QC teams build the ITR and checksheet templates the ITPs call for, with named revisions and reusable templates, and on the Enterprise plan a company knowledge base so new sheets follow your house style.
Frequently asked questions
What is the difference between a quality plan and an ITP?
The quality plan describes how quality is managed on the whole project, including organisation, procedures, NCRs and audits. An ITP is a narrower document for a specific discipline or scope, listing the inspections and tests to be done, acceptance criteria and intervention points. The quality plan normally lists the ITPs the project will use.
Who writes the construction quality plan?
Usually the contractor's project quality manager, with input from construction, engineering and completions leads. It is typically submitted to the client for review and approval early in the contract. Subcontractors may be required to produce their own plans that align with it.
How long should a project quality plan be?
Long enough to cover the contract's requirements and no longer. Keep the main body focused on how things work, and move lists such as procedures, forms and ITPs into appendices or registers. A plan that nobody reads because of its length has failed, whatever its page count.
Is a construction quality plan required by ISO 9001?
ISO 9001 requires an organisation to plan and control its operations, and many certified contractors meet that for projects through a project quality plan. Whether a formal quality plan is required, and what it must contain, is usually set by the contract and client specifications. Check the contract rather than relying on the standard alone.
How often should a quality plan be updated?
Review it at defined triggers, such as a new project phase, a major new subcontractor, key personnel changes or significant audit findings, as well as at any interval your contract sets. Keep volatile information in registers so the plan itself doesn't need reissuing every time a form or procedure changes.
