How to Build a QA Coverage Analysis for Any Civil Project
Most QA registers on civil projects tell you what inspections have been done. What they rarely tell you is what inspections are missing — the assets, zones, or activities where work has proceeded without any HP or WP being raised.
A QA coverage analysis answers that second question. It maps what’s in your register against what should be in your register, and produces a list of gaps that can be acted on while construction is still live.
This article walks through the methodology, step by step.
The Core Concept
A coverage analysis has three inputs and one output:
Inputs:
1. Your HP/WP register (exported to a structured format)
2. Your asset schedule (pit schedule, structure list, chainage map — whatever defines the inspectable assets on your project)
3. The expected inspection sequence for each asset type (drawn from the governing specifications)
Output:
A coverage map showing, for each asset, which inspection types have been raised and which are missing.
The power is in the comparison. Without the asset schedule, your register is just a list of events. With it, you can see the gaps.
Step 1: Define Your Asset Register
The asset register is the anchor. It defines the universe of things that need to be inspected. On most civil projects this already exists:
- Stormwater drainage: pit schedule from the designer, listing every pit number, type, and connection
- Earthworks: chainage list broken down by side (North/South) and design element (Road, Verge, Shared Path)
- Pavements: lot boundaries from the project quality plan
- Structures: structure schedule listing each foundation member, abutment, headstock, or deck element
- Piling: pile schedule from the structural drawings
If a formal schedule doesn’t exist, create one. A simple spreadsheet with asset ID, type, and location is sufficient. The point is to have a complete list of what needs to be inspected before you start mapping what has been.
Step 2: Define the Expected Inspection Sequence
For each asset type, define what a complete set of QA submissions looks like. This comes from the governing specifications.
Step 3: Map Your Register Against the Schedule
For each asset in your schedule, check which inspection types from the expected sequence have been raised in the register.
The mapping works by extracting asset references from the location codes in your HP/WP entries. Most contractors embed asset identifiers in their submission codes — pit numbers, chainage references, structure IDs. Extract those references, group by asset, and compare against the expected sequence.
The output for each asset is one of three states:
– Complete — all expected inspection types have been raised
– Partial — some inspection types have been raised, others are missing
– None — no HP or WP of any type has been raised
Step 4: Prioritise the Gaps
Not all gaps have equal urgency. Prioritise based on two factors:
Construction stage: Gaps for assets that are already built or being built imminently are urgent. Gaps for assets not yet started can be addressed through the upcoming ITP review and pre-construction briefing process.
Inspection type: Missing foundation HPs are generally the highest priority — once the foundation is buried under blinding concrete, the inspection opportunity is gone. Missing excavation WPs are significant but slightly lower priority. Missing pipework WPs, while still a non-conformance, are less time-critical because the pipes are still accessible.
Step 5: Act on the Gaps
The coverage map generates a prioritised action list:
For assets not yet started: Confirm the relevant HP/WP obligations are in the ITP and the contractor understands the notification sequence before work starts.
For assets under construction now: Issue a site instruction noting the obligation to raise the specified HPs and WPs before proceeding past each activity. Confirm in writing.
For assets already built with no coverage: Issue a formal NCR. Direct the contractor to provide retrospective evidence (test results, inspection photos, survey records) to demonstrate conformance. Reserve the right to direct remediation if evidence is insufficient.
The formal record is important in each case. A verbal conversation about HP obligations is not sufficient — you need written confirmation that the contractor has been notified, and a dated record of the gap.
When to Run the Analysis
Ideally, run a coverage analysis:
- Before construction commences on each work package — as part of ITP review, confirm the HP/WP sequence is captured and the contractor understands their notification obligations
- Monthly during construction — check that register entries are keeping pace with physical progress; gaps found monthly are much easier to address than gaps found at final account
- Before each stage hand-over — before earthworks hand over to pavement, before drainage hand over to pavement, before any stage that buries or covers earlier work
The earlier you find the gap, the more options you have.
stormwater pit QA coverage tracker
earthworks chainage coverage tracker
AI for contract administration
Methodology developed on live civil infrastructure projects. Specification references are to TfNSW B30, B59, B80, R73, and NATSPEC 1112.