Most quality systems close a nonconformance report and stop there. The cover was wrong, the rework was done, the re-inspection passed, the NCR is filed. Nobody told the site starting next month that the same fixing method causes the same problem, so it happens again, gets its own NCR number, and gets closed the same way. A quality alert and a lessons learned register are how a contractor breaks that cycle: one defect, properly handled once, becomes a briefing that stops it recurring on every site that comes after it. This post sets out what a quality alert has to contain to be read, when to issue one, and how the register behind it has to work for the loop to actually close.
What the NCR register does not do
An NCR register is built to manage instances. Each entry is one occurrence: what was wrong, what was done about it, who signed it off. That is the right design for its job, and it is also its limit. A register with forty entries for "fire-stopping annular gap not sealed" across six projects tells you, if you sort it, that you have a pattern. It does nothing on its own to stop the forty-first. The pattern has to be noticed, translated into an instruction a site supervisor will actually read, and pushed out before the next project starts the same activity. That translation step is the quality alert; the register that tracks whether it happened is the lessons learned register.
What ISO 9001 actually asks for
This is not an optional extra sitting outside the standard. BS EN ISO 9001:2015+A1:2024 clause 7.1.6 requires an organisation to determine the knowledge necessary for its processes, maintain it, and specifically consider knowledge gained from experience and from lessons learned from failures. Clause 7.4 requires it to decide what to communicate internally, when, to whom, and how. Clause 10.3 requires continual improvement of the system's suitability, adequacy and effectiveness. A lessons file nobody opens satisfies none of the three. A quality alert that reaches the person about to repeat the mistake, with a record that it was read and understood, satisfies all three at once, in one document rather than three separate procedures.
When a nonconformity earns an alert
Not every NCR needs one; most do not. Writing the trigger into the procedure keeps the decision consistent rather than dependent on who happens to notice:
- Recurrence. The same category of defect appears on the NCR register more than a stated number of times, or on more than one project. A simple Pareto of NCR categories, reviewed monthly, is usually where this first shows up.
- Consequence. A single nonconformity that cost more than a set threshold, delayed a handover, failed a third-party inspection, or was found by the client rather than by the contractor's own inspection.
- Latent defect. Something reported during the rectification period that traces back to a workmanship or detailing error that could just as easily be sitting undetected on the project now on site.
- Change in requirement. A new edition of a standard changes an acceptance criterion the sites are still working to. When BS 5975-1:2024, BS 5839-1:2025 or BS 7671:2018+A4:2026 changed something an inspector checks, an alert reaches site faster than waiting for the ITP library to be reissued.
- Handover lessons. The close-out workshop identifies something that should have been known at the start. If the lesson is a quality one, it becomes an alert for the projects now mobilising.
The one-page format, and why it has to stay one page
A quality alert borrows its shape from the safety alert, because the shape works: a site supervisor will read one page with two photographs and will not read a corrective action report. The fields that make it readable and auditable are the same every time.
| Field | What it has to do |
|---|---|
| Reference, date, issuer, trade | Numbered into a library the project quality plan can list by scope |
| Title naming the defect | "Fire-stopping: unfilled annular gaps behind cable trays", not "Fire-stopping quality" |
| What happened | Found, detected, cost or risk; project and subcontractor anonymised |
| Why it matters | Standard, clause or drawing detail not met, at its current edition |
| Right and wrong | Two annotated photographs, side by side; the picture is what gets remembered |
| What to do | Checkable actions, each with an owner and a deadline |
| Briefing record | Who was briefed, when, signatures; without it, a poster, not a record |
If the page runs to two, it has become a corrective action report in disguise, and the supervisor will not read it. Everything beyond that one page belongs in the register and in the procedure it eventually changes.
The register that stops lessons being noted instead of learned
The lessons learned register captures every input and tracks it to the point where something on the ground has actually changed, not just where it was written down. The columns that make that distinction visible are the source (the NCR, audit finding, close-out workshop or external bulletin that produced it), the category (design, procurement, materials, workmanship, inspection, commissioning, handover or subcontractor management, so the register can be sorted for the next quality plan), the lesson itself written as an instruction to a future project rather than a description of what went wrong, the change it caused in a procedure, ITP line, check sheet or supplier approval, the alert reference where one was issued, and the owner, status and date closed. Closed means the change was made and verified, not that the lesson was written down. A column showing which projects have since applied the lesson is evidence against clause 7.1.6 an auditor can see; a lesson with nothing in that column, however old, is a finding.
Keeping the loop moving both ways
The register fills from four places, each with a named owner: the NCR and corrective action process, where every closure is asked whether it needs an alert; internal audit, where a systemic finding goes on the register as well as the findings tracker; the close-out workshop, minuted and transferred by category; and tender feedback, won and lost, on the same register so the bid team and the site team read the same document. Getting lessons out again rests on three mechanisms: the alert itself, for anything sites need to act on now; a section in every new project quality plan listing the lessons and alerts that apply to its scope; and management review, where clause 9.3.2 treats the register as an input and a lesson left open a year with nothing changed becomes a finding of its own.
Starting the library without your own history
A contractor with no register yet need not wait for its own defects to accumulate first. The defects that recur across UK construction are well known: fire-stopping and compartmentation, cavity barriers and trays, cover to reinforcement, screed cracking, roof membrane laps, cladding fixings, cable containment and terminations, commissioning records that do not match what was installed, and handover information that does not exist at all. A starting library built around those, cited at the current edition with a right-and-wrong photograph, gives a year of briefings while the company's own lessons fill the same register behind it.
The check on your own file
Take the last six months of your NCR register and ask three questions. Does any category appear more than twice, and if so, where is the alert. For each alert issued, is there a signed briefing record, and a line in the register showing what procedure or check sheet actually changed. If the third answer is blank against more than one or two alerts, the loop is not closing; it is a folder of good intentions. The Quality Alert and Lessons Learned Library is built to close it: thirty one-page alerts on the defects that recur most, with the register that tracks every one of them from source to change, alongside the lessons learned workshop record in the Handover & Close-Out Pack. If you want to see the standard of the writing before anything else, the free ITP is the same document, at the same level, for no commitment.
Note added 1 October 2026: the clause numbers above are to BS EN ISO 9001:2015+A1:2024. BS EN ISO 9001:2026 was adopted on 30 September 2026 and now supersedes it. We have not yet walked the 2026 text clause by clause and will update the references above once that review is done; certificates to the 2015 edition are unaffected during the transition period.
Where this leaves you
The Quality Alert and Lessons Learned Library has thirty one-page alerts on the defects that recur most across UK construction, each cited to the standard at its current edition, with the register that tracks every one from source to change. It sits alongside the lessons learned workshop record in the Handover & Close-Out Pack. If you want to judge the standard of the writing first, start with the free ITP.
Written by Craig Collier, MCIOB, CQP MCQI, MAPM, Director of StructAssure Ltd. Published 1 October 2026; standards and regulations as read on that date.