The hold point that wasn't held
Work carries on past a failed hold point because nobody who could stop it was told in time.
Run ITP and ITR inspections with hold and witness points and geotagged photos, see an NCR raised the moment a material is rejected, and close punch items only once they have been verified. Every NCR, submittal and walkdown keeps its own sign-off rules and audit trail.
Paper checklists and spreadsheets record what happened. They don't stop what shouldn't.
Work carries on past a failed hold point because nobody who could stop it was told in time.
A rejected delivery is noted, then used — because the rejection never became an NCR anyone had to close.
When the person who raised an NCR can also close it, 'closed' stops meaning 'fixed'.
Create the inspection from a built-in checklist.
Start it, mark each line and take geotagged photos.
A failed hold point notifies the inspector at once.
Pass, conditional pass or fail — then print the ITR.
A rejected material raises its NCR automatically.
Someone other than the raiser closes it, with the corrective action.
The broadest HSE toolset on the platform, with TRIR, LTIFR and severity rate worked out from man-hours.
SourcingRequisition to goods receipt — sealed bids, scored vendors and budget-checked POs.
HandoverBring the project to a clean, documented finish.
Not by itself: the inspector raises the NCR in one step from the inspection. What BuildCore raises automatically is the NCR for a rejected material — at a site or pre-dispatch material inspection, or at goods receipt.
No — someone else has to (administrators are exempt). Once closed, the NCR is locked, and every change along the way is in its log.
Twenty-one: eleven for work, from excavation and pour cards to rebar, formwork, blockwork, plaster, waterproofing, tiling, conduit and plumbing, and ten for materials. Lines can be added on each inspection.
Yes. Inspection photos are taken with the device camera and geotagged, and NCRs can also be captured offline in Field Capture and synced later.
Tell us about your project and we'll shape the demo around Quality (QC) and the modules it connects to.