An inspection record can show what was checked. It cannot, by itself, show that the right requirement reached the team before the work began.
That is the distinction we suggest putting at the centre of a construction quality system: make the work ready to meet the requirement, then verify the result. A large folder of completed forms is not the same as a dependable process.
Assurance and control do different jobs
ASQ describes quality assurance as the planned, systematic arrangements that provide confidence in meeting quality requirements. It distinguishes this from quality control, which focuses on fulfilling those requirements, including examination and inspection. The two support each other, but they are not interchangeable. Source: ASQ, Quality Assurance vs. Quality Control.
Applied to a work package, we use that distinction this way: assurance establishes the requirement, method, competence, responsibilities and evidence route. Control checks the delivered result. Both need to connect to the same approved information.
Begin with the requirement, not the form
Our suggested starting exercise is to choose one upcoming activity and trace each acceptance requirement to its approved source. That might be a drawing, specification, material approval or agreed method. Record the revision and the relevant location.
Then ask what evidence would establish conformity. A photograph may show an installed arrangement, but not a hidden material property. A delivery document may identify a product, but not confirm that the correct item was installed in the correct place. Choose evidence for the question being answered rather than collecting documents indiscriminately.
If the acceptance criterion is unclear, resolve it through the authorised project functions before presenting the inspection plan as complete.
Make the inspection and test plan usable
A practical inspection and test plan can be structured around the following questions. The actual checks, frequencies and release points must come from the project’s requirements; the table is a working framework, not a universal specification.
| Question | What the plan should make clear |
|---|---|
| What is being checked? | The activity, location and requirement reference |
| How will it be checked? | The examination, measurement, test or document review |
| When does it happen? | The agreed stage, frequency and any hold or witness point |
| Who acts? | The performer, reviewer and authorised release function |
| What proves the result? | The record, result, acceptance and linked supporting evidence |
A hold point should mean what the agreed plan says it means. Do not invent a client approval requirement for every task; equally, do not let an important release depend on an informal assumption that someone else has checked it.
An illustrative pre-pour conversation
For a concrete work package, we suggest a short readiness discussion around the approved design and method: is the relevant information available, have the required checks been completed, is the testing arrangement understood, and is the evidence linked to the pour location?
The National Ready Mixed Concrete Association’s pre-construction conference guidance emphasises establishing responsibilities and communication between the parties before concrete work starts. It is a useful reminder that quality preparation includes coordination, not only testing. Source: NRMCA, CIP 32: Concrete Pre-Construction Conference.
This article does not prescribe reinforcement cover, concrete properties, test frequencies or formwork-release criteria. Those are project-specific matters for the applicable requirements and responsible specialists. The example concerns how the agreed checks are organised and recorded.
Keep the evidence chain intact
We recommend a simple traceability chain:
Location → requirement and revision → inspection or test → result → acceptance or non-conformance → close-out.
Every link should be understandable to somebody who was not present when the work took place. Use consistent location references, keep superseded documents identifiable, and distinguish a submitted record from an accepted result.
A useful weekly review asks which activities have incomplete evidence, not merely how many files were uploaded. Give each gap an owner and a recovery action. The objective is a reliable account of the work, not a higher document count.
Use non-conformances to improve the system
Our suggested close-out review asks two different questions: has the affected work been appropriately addressed, and what needs to change to reduce recurrence? A corrected installation does not necessarily resolve an unclear instruction or an ineffective release check.
Record the agreed disposition, authorised decisions, implementation evidence and verification. Where the proposed response changes the design or acceptance basis, obtain the appropriate approval rather than closing the record on the strength of a photograph alone.
Recurring issues should feed back into preparation: clarify the requirement, update the method, improve the handover or change the check. This makes the non-conformance register part of assurance rather than a disconnected list of defects.
A useful first improvement
Choose one package and test whether a reviewer can follow its evidence chain without asking the original inspector to explain every file. Fix the missing links, then reuse the structure.
Good assurance makes the next correct action clear before the inspection takes place.
Related reading: Concrete cracks: observe, record, assess.
