Cheat sheet
Quality control: hold point, NCR, RFI to taking-over
Every rule of the course on one page: how each figure is built, the mistake people usually make, and where it comes up at work. Print it or keep it open while you work.
- Rule
- A hold point is released before the work hides it. No release, no pour: the concrete is stood down.
- How it is built
- Concrete stood down = Bay B area − Core opening × Slab thickness
- Usual mistake
- The core opening is in. No concrete goes into it; deduct it from the bay.
- At work
- The quality manager records the fail at once and the site manager calls the plant before the cut-off.
- Rule
- A nonconformity costs the repair, the time the site waits, and the client's repeat check. All of it goes on the NCR.
- How it is built
- NCR-001 cost impact = Rework + Concrete cancelled + Pump cancelled + Site overheads × days + Repeat inspection
- Usual mistake
- The site overheads are missing. The frame is critical, so every working day the pour moved cost the site.
- At work
- The NCR goes into the monthly quality report with its cost and the corrective action for the next pour.
- Rule
- An RFI carries a date and its answer carries a price. The change is valued on what it adds.
- How it is built
- RFI-001 cost impact = Separating walls per level × Flat levels × Insulation rate
- Usual mistake
- Walls inside a flat are in. The answer covers walls between flats and to the corridor.
- At work
- The quality manager keeps the RFI log; the quantity surveyor values the answer as a Variation.
- Rule
- Taking-over waits for safe use, not for a zero list. Safety and water first; the rest is listed.
- How it is built
- Rework before taking-over = Critical snags + High snags
- Usual mistake
- All open items are in. Low and medium ones go on the certificate's list.
- At work
- The Engineer and the contractor walk the building together and agree the list before the application.
- Rule
- Delivered means verified. A file nobody has checked is not yet evidence of quality.
- How it is built
- Completeness = Verified slots ÷ Required slots
- Usual mistake
- Bound but unverified documents are counted. Only verified evidence counts.
- At work
- The quality manager binds and checks the records; the Engineer reviews the package with the taking-over application.