What Quality Assurance Means in Construction
QA operates at the system level: plans, procedures, training, scheduled inspections and records. It answers the question “how will we know the work is right?” before the work starts. Quality control operates at the product level: measuring, inspecting and testing the work itself. QA makes QC happen at the right time, against the right requirement, by the right person.
The standard the work is judged against comes from the contract, drawings, specification, manufacturer data and applicable standards — not from a vague idea of what looks good. QA checks conformity to that agreed requirement, and it records the result so the decision is traceable.
QA vs QC: The System and the Checks
| Quality assurance (QA) | Quality control (QC) | |
|---|---|---|
| Level | System and process | Product and workmanship |
| What it does | Plans checks, assigns roles, records results | Inspects, measures and tests the work |
| Ceiling example | The inspection and test plan schedules a pre-lining hold point | At that hold point, lining flatness, joint finish and lighting alignment are checked |
| Effect | Prevents defects by controlling the process | Finds defects that have already occurred |
The two work together: a QA plan that schedules checks poorly produces QC that happens too late, and QC without records produces checks that cannot be proven. Both are required for a defensible project.
How a QA Plan Works on a Ceiling and Wall Project
A QA plan for a ceiling and wall package starts with an inspection and test plan (ITP): a list of activities, the checks applied to each, the hold or witness points where work stops for inspection, and the records produced. Typical hold points in ceiling work include before lining close-up, after framing and before finish acceptance — but the plan is written for the specific project, not copied from a template.
The ITP is usually written by the contractor at the start of the package and agreed with the head contractor and consultant before work begins, so everyone signs up to the same checks. It is a live document: when a service or condition changes, the plan is updated and the change is recorded. A plan that sits in a folder until a dispute is not a QA system — it is paperwork that failed its purpose.
When a check fails, the result is a non-conformance report (NCR): what is wrong, what correction is proposed, and how the re-check is done. The NCR log is part of the handover record. Roles are assigned in the plan: the contractor self-checks, the supervisor reviews, the client or consultant witnesses key hold points, and a third-party inspector performs specified testing where the contract requires it.
Why QA Matters Today
Modern projects run on records. Digital inspection logs, photos, signed checklists and test certificates make the quality trail traceable from first fix to handover, which settles the “who approved what” arguments that used to drag on. QA also reduces rework: a check at the right time costs minutes; a lining that must be removed to fix a service behind it costs days. And QA clarifies responsibility — the records show what was checked, when, and against what requirement, which protects every party with a clear scope.
The records also feed the maintenance phase: a facility team that knows where access panels are, what was inspected and when the last acceptance happened can plan its inspections instead of discovering conditions by accident. Quality assurance today is therefore not only about the construction phase — it is the bridge between construction and the building’s life.
QA is a contract requirement, not an optional extra. The level of the system scales with the project — a small fit-out needs a proportionate plan, not a corporate manual — but the principle is constant: checks are planned, someone owns them, and results are recorded.
The QA Responsibilities Matrix
| Role | QA task | Record produced |
|---|---|---|
| Project manager / contractor | Write the QA plan, schedule hold points, manage the NCR log | QA plan, inspection and test plan |
| Site supervisor | Run inspections, sign off checklists, witness work | Signed checklists, photos |
| Ceiling/wall subcontractor | Self-check before requesting inspection | Self-inspection records |
| Client / consultant | Witness hold points, review NCRs, accept the work | Inspection reports, acceptance records |
| Third-party inspector (where specified) | Perform specified testing | Test certificates |
Every QA plan should state four things: what is checked, when it is checked, who checks it, and where the record lives. If any of the four is missing, the plan has a gap that will be found on site.
Frequently Asked Questions
What should I ask a contractor about its QA system?
Ask what the inspection and test plan covers, who runs the checks, which hold points require you or your consultant to attend, and how results are recorded. If a contractor cannot answer those four questions, the QA plan is not real.
Can a contractor change its QA plan mid-project?
Yes, when conditions change — but the change is agreed with the same parties and recorded, not made silently. The revised plan still states what is checked, when, by whom and where the record lives, so the approval trail stays intact.
Who is responsible for QA on site?
The contractor leading the package runs its QA plan; the head contractor coordinates across packages; and the client or consultant witnesses key hold points. The responsibilities are defined in the contract, and the commercial ceiling project delivery guide sets out how the delivery and QA framework works for ceiling work.
To build QA into a ceiling and wall package from the start, define the checks and records before work begins and contact CeilingPro with your project documents for an inspection assessment and quote.
