Defect management on traffic signal projects is one of the disciplines most likely to be handled informally until it causes a formal problem. Non-conformance reports (NCRs) pile up in a shared folder, ownership isn't assigned clearly, and by the time the project reaches handover, the register has 40 open items that nobody has touched in three weeks. Getting defect management right requires a defined process that runs continuously from construction through to commissioning, not a cleanup exercise in the final fortnight.
What an NCR actually represents
A non-conformance report documents a specific departure from a stated requirement. That requirement might come from a contract specification, a drawing, an approved ITP (Inspection and Test Plan), an Australian Standard, or a hold point condition. The NCR isn't a fault log or a snag list. It's a formal record that something was done differently from what was approved, and it demands a documented response.
On traffic signal projects, NCRs arise from four common sources: installation workmanship that doesn't meet the specification (incorrect conduit depth, wrong cable type, pole positioning outside tolerance), equipment that arrives or is installed in a non-compliant state, inspection failures at hold points or witness points, and documentation gaps where required sign-offs were skipped. Each category needs a slightly different resolution path, which is why a one-size approach to NCR closeout doesn't work.
Setting up the NCR register before work starts
The register needs to exist before the first NCR is raised, not after. At minimum, it should capture: a unique NCR number, the date raised, the requirement that was not met (with the source document referenced), the specific departure observed, the location on site, the person responsible for resolution, the proposed corrective action, the target closeout date, and the verification method. That last field matters. An NCR isn't closed when the fix is done. It's closed when the fix has been independently verified against the original requirement.
Assign a single NCR controller per project. On a large intersection upgrade with multiple subcontractors, this is typically the principal contractor's quality manager. On smaller projects it can sit with the project engineer, provided that person has enough separation from the day-to-day construction to assess NCRs objectively. Projects that distribute NCR ownership across the whole site team almost always end up with inconsistent closeout standards and disputed records at handover. This connects directly to the broader quality assurance framework that should govern the project from the outset: quality assurance in traffic signal projects sets out how that structure should operate across design, procurement, and construction phases.
Raising NCRs: timing and specificity
NCRs raised late are harder to close. A conduit depth non-conformance raised after backfilling has occurred requires a dig-up to verify the fix. The same NCR raised before backfill gives the crew a chance to correct the work in place with direct visual confirmation. Encourage subcontractors and site supervisors to raise NCRs as soon as the departure is identified, not after it's been buried or built over.
Specificity matters more than volume. An NCR that says "cable installation not compliant" is almost useless. An NCR that says "110 mm PVC conduit installed at 350 mm depth on the southern leg of the intersection, Clause 7.4.2 of AS/NZS 3000 requires minimum 500 mm below finished pavement, confirmed by dig test on 14 July 2026" gives the resolution team exactly what they need. Vague NCRs generate lengthy email chains and delayed closeout. Specific NCRs get resolved in days.
Corrective action vs. concession: knowing the difference
Not every NCR results in a fix. Sometimes the departure is minor enough that the client authority will accept a concession. A concession acknowledges the departure but documents why it's acceptable given the circumstances. The critical rule: the client authority must approve the concession in writing before the NCR can be closed on that basis. A contractor approving their own concession is not a valid closeout.
For traffic signal infrastructure, concessions are appropriate in limited cases. Cosmetic surface finish variations on signal poles are a reasonable candidate. Conduit depth being 20 mm short of specification through an isolated section of hard rock where further excavation would damage adjacent services may be justifiable with engineering sign-off. Incorrect cable type is not a concession candidate. It's a replacement. The project team needs a clear internal rule about which defect categories are eligible for concession requests and which require corrective action regardless of inconvenience.
Tracking closure: the status categories that matter
A well-structured NCR register uses five status categories, not two. Open, in progress, pending verification, closed, and void (raised in error or duplicate). "In progress" and "pending verification" are the two most important, and most teams collapse them into a single status. Separating them makes it possible to see at a glance how many items are waiting on a contractor to act versus how many are waiting on a verifier to inspect. Those are different problems with different actions, and conflating them hides the true state of the register.
Weekly NCR reviews are not optional on any project with more than 10 open items. The review should cover items past their target closeout date, items in "pending verification" for more than 5 business days, and any new NCRs raised since the last review. Keep the review short and action-focused. Each open item leaves the meeting with a named owner and a revised date if the original has passed. This rhythm is also the right context to review hold point compliance, since delayed NCR closeouts often block subsequent hold points from being cleared. The interaction between hold points and quality control mechanisms is worth understanding in detail for any project manager running a concurrent defect and inspection regime.
Commissioning-phase NCRs: a separate category
Defects identified during commissioning need their own sub-register. They're raised later in the project lifecycle, resolution time is compressed, and the consequences of leaving them open are more visible. A controller that fails a functional test raises an NCR that blocks handover. A lamp output failure on a specific signal head needs same-day rectification or a formal concession with the transport authority's sign-off before the intersection can be accepted.
Commissioning NCRs also tend to involve more parties. The equipment supplier, the installing contractor, the programmer, and the client authority's representative may all need to be part of the resolution process. Clarify the escalation path for commissioning-phase NCRs before commissioning starts, not during it. Who approves the fix? Who verifies the retest? Who signs off the updated commissioning record? These questions answered in advance cut resolution time by days.
Closing out the register before handover
The NCR register submitted at handover should have zero open items. This isn't a documentation preference; it's a contractual and operational requirement. An open NCR at handover means an unresolved departure from specification is being transferred to the asset owner. Most transport authorities and local councils won't accept a handover package with outstanding NCRs. Those that do will typically retain a portion of the contract payment until closure is confirmed.
Start the closeout push no later than four weeks before the planned handover date. Audit the register for any items where verification hasn't been completed, any concessions that were actioned without formal client approval, and any items incorrectly marked closed without a verification record. The handover documentation package for a traffic signal project should include the full NCR register with all closure records attached, not a summary or a cover sheet. Reviewers will check individual items, and gaps in the record create delay.
A clean NCR register at handover reflects a project that was managed, not just built. It tells the asset owner that departures were caught, documented, and resolved to a verified standard. That's the record worth leaving behind.