Construction Quality Control Software: ITPs and NCRs

Most construction quality control software is sold on features. It is better bought on process. Your QC plan already specifies what gets inspected, at which stage, by whom, and what evidence gets retained — and the only useful question about any system is whether it can follow that sequence without you bending the plan to fit the software.

This guide works through construction QC as it is actually practised, and what each stage demands from a system.

Start with the inspection and test plan

The ITP is the backbone. It sets out each activity, the applicable specification, the inspection type, the responsible party and the acceptance criteria. If your software cannot represent an ITP faithfully, everything downstream degrades into a generic checklist.

What to check for:

Activity-level structure that mirrors your ITP rows, not a flat list of questions
Reference to the governing specification or drawing, including revision
Named responsibility per line — contractor, consultant, client, third party
Acceptance criteria captured as values and tolerances where relevant

Hold points and witness points are the hard part

This is where most general inspection tools fall down. A hold point stops work until an inspection is signed off. A witness point requires notification but does not stop work if the party declines to attend.

Software that treats both as ordinary checklist items loses the distinction that matters commercially. Look for the ability to mark an activity as a hold, block downstream sign-off until it clears, log the notification that was issued, and record who attended or waived. When a delay claim turns on whether notice was given, that log is the evidence.

Non-conformance handling

A failed inspection is not a note. It is an obligation with a lifecycle: raise, categorise, assign, propose corrective action, implement, re-inspect, close. Good QC software makes each of those a tracked state with a timestamp and an owner.

Two things to insist on. First, an NCR should carry its own reference number and remain traceable after close-out — not disappear once the item goes green. Second, re-inspection should link back to the original failure, so the record shows the full history rather than a final pass with no context.

Evidence and the handover pack

The end product of QC is usually a handover or O&M pack that somebody has to assemble. If your software stores evidence but cannot export it in a structured, navigable form, you have moved the assembly problem rather than solved it.

Ask specifically how the system produces a compiled quality record: whether photographs retain their metadata, whether certificates and test results can be attached against the relevant ITP line, and whether the export is organised by work package or dumped chronologically.

Where general inspection apps are genuinely fine

Not every project needs this. On fit-out, refurbishment, residential and much subcontract work, QC is closer to structured snagging: check the work, photograph defects, assign them, close them out. A general inspection or snagging app handles that well and rolls out in an afternoon.

The threshold is roughly this — if your contract names an ITP, specifies hold points, or requires an NCR procedure, you need QC-specific tooling. If it does not, a lighter tool is proportionate and far more likely to be used.

Questions to ask on a demo

Can we build an ITP structure, or only flat checklists?
How are hold points enforced, and can they block downstream sign-off?
Does the system log notification of a witness point and any waiver?
Does an NCR get its own reference and remain traceable after close-out?
Can test certificates be attached against a specific ITP line?
What does the compiled handover pack look like on export?
How does sign-off work for parties who are not licensed users?

The adoption problem

QC software fails on site more often than it fails on capability. The engineers filling it in are doing so between other tasks, frequently with poor signal and gloves on. Offline capture is not a bonus feature here, it is the difference between records made at the point of inspection and records reconstructed in the site office that evening — which is precisely the failure mode the software was bought to eliminate.

Weight your evaluation accordingly. Speed of capture on a phone, in the rain, matters more than the sophistication of the dashboard.

Where SiteAudit fits

SiteAudit handles structured quality control without enterprise overhead: templates built to your own acceptance criteria, photo evidence against each line item, full offline capture, assignment and close-out tracking, and clean exportable records. For teams whose QC is rigorous but whose budget and timeline will not stretch to a full QMS implementation, it covers the ground that matters.

Construction Quality Control Software