Construction quality control: why QC should gate progress

Why failed quality checks should block the next activity and keep rejected material out of stock, and how to design inspections that work as gates.

Published
Reading time
4 min read

Quality control as paperwork

On many sites, quality control exists mostly on paper. Checklists are filled in, sometimes after the fact, and filed. The next activity starts on schedule whether or not the previous one passed. Delivered material goes into the store and is issued to site while its inspection is still pending.

The problem is not that the checks are wrong. It is that they have no consequence. When a failed check does not stop anything, it becomes a record of a problem rather than a way of preventing one — and in construction, problems that are built over are expensive to find and expensive to fix.

What a QC gate is

A QC gate is a point in the workflow that work or material cannot pass until an inspection has been approved. The gate sits between two steps: between fixing reinforcement and pouring concrete, between receiving cement and adding it to stock, between finishing waterproofing and laying tiles over it.

The principle is simple. If a required check fails, the gate stays closed. The work is corrected and inspected again, and only then does the next step open.

The two things to inspect

Everything that ends up in a building is either work done on site or material delivered to it. Both need gates.

  • Work inspections check what has been built before it is covered or built upon — shuttering and reinforcement before a pour, blockwork before plaster, concealed plumbing and electrical work before walls are closed, waterproofing before tiling.
  • Material inspections check what has been delivered before it is accepted — grade and brand against the purchase order, quantity, physical condition, and test certificates where the specification requires them.

Designing checklists that work as gates

A checklist that gates progress has to be precise enough to fail. Some practical guidelines:

  • Mark which checks are required. Not every item needs to block progress, but the ones that affect safety, structure or waterproofing should.
  • Make each item a clear pass or fail. “Cover blocks placed at the specified spacing” can be judged; “reinforcement OK” cannot.
  • Ask for remarks when something fails, so that the correction is specific.
  • Require a photo where evidence matters, especially for work that will soon be hidden.
  • Keep checklists short enough to be used on site. A long checklist that is skimmed protects less than a short one that is followed.

Why there should be no override

The most important design choice is also the least popular: a failed required check should not be overridable. The moment a manager can approve an inspection despite a failure, the gate becomes a negotiation, and schedule pressure usually wins.

Removing the override does not remove judgement. If a check genuinely does not apply, it should not be marked as required on that checklist. If the work is acceptable after a correction, it should be re-inspected and pass. What goes away is the option to record a failure and carry on anyway.

Connecting QC to the schedule and the store

A gate only works if the rest of the system respects it. That means the schedule and the store both need to know the result of an inspection.

On the schedule side, an activity that depends on another should not be able to start until the earlier activity’s QC has passed. On the store side, delivered material should not become stock — and so cannot be issued to site — until its QC has passed. Purchase approval and payment then follow accepted material rather than delivered material.

Will it slow the site down?

Occasionally, in the short term, yes. A pour may wait while reinforcement is corrected, and a delivery may sit in a holding area until it is inspected. That is the point of a gate.

Over the life of a project, gates tend to save time. Defects found before they are covered are cheaper to fix than defects found afterwards. Rework, disputes with contractors about responsibility, and buyer complaints at handover all shrink when problems are caught at the step where they happen. Site teams also get a clearer rule: the next step opens when the inspection passes, not when someone decides it is probably fine.

How Proprite applies QC gates

In Proprite’s Quality Control module, inspections cover both construction work and delivered material. Each checklist item can require a pass or fail, remarks and a photo as evidence.

If a required check fails, the inspection cannot be approved, and there is no override. In Project Scheduling, the next dependent activity cannot start until the previous QC passes. In Material Inventory, delivered material does not become stock until its QC passes.

See how Proprite fits your project workflow.

Walk through Proprite using the workflows your team already manages — your towers, your payment plans, your approval chain.