What a permit to work system actually has to cover

CDM 2015 (SI 2015/51) places the general duty on the principal contractor, under regulation 13, to plan, manage, monitor and coordinate construction work for the whole of the construction phase. A permit to work system is one of the mechanisms that duty gets discharged through on the activities where getting it wrong kills people quickly: fire, asphyxiation or collapse. Nothing requires every site activity to carry a permit; a permit earns its place where a missed check or a changed condition turns into a fatality rather than a near miss. Hot works, confined space entry and excavation are the three that appear on almost every site permit register, and each is governed by its own regulations rather than by CDM alone.

What ties the three together is the shape of the control, not the hazard. A permit to work system that is actually working has four things in place regardless of which activity it covers: a named issuer who is not the person doing the work, a defined set of checks completed and recorded before the permit is signed, a stated validity period after which the permit lapses and has to be reissued, and a formal close-out that records the work finished and the area was left safe. A site that has the forms but not those four features has paperwork, not a permit system, and that is usually what a careful review finds first.

Hot work permits: the fire watch is the control, not the form

The Joint Code of Practice for fire prevention on construction sites, now at its 10th edition incorporating Amendments 1 and 2, is the industry document the insurance market and most client fire safety plans are built around, and it is where the detail behind a hot works permit comes from. HSE's own guidance, HSG168 Fire safety in construction, 3rd edition, sits alongside it as the document an inspector is most likely to be working from. Neither is a statutory instrument; the legal hook is CDM 2015's planning duty.

The permit itself exists to force a sequence, not to record one after the fact: combustible material cleared or protected within the working radius, a fire extinguisher at the point of work rather than at the nearest store, and a fire watch kept during the work and for a stated period afterwards, because the material that starts smouldering during a hot work task often does not catch until the operative has moved on. The commonest gap on a hot works register is not a missing permit; it is a permit correctly issued and then nobody owning the post-work watch, because the form treats the watch as a box rather than a named person's job with a time it ends.

Confined space entry permits: what the regulations actually ask for

The Confined Spaces Regulations 1997 (SI 1997/1713) set a narrower and more direct duty than CDM. Regulation 4 requires that entry into a confined space is avoided so far as is reasonably practicable; where entry cannot reasonably be avoided, the work must be carried out under a safe system of work that makes it reasonably practicable to do it without entering. Regulation 5 then requires suitable and sufficient arrangements for the rescue of a person in the confined space to be in place before entry starts, not improvised once something has gone wrong. HSE's L101, Safe work in confined spaces, 3rd edition 2014, is the Approved Code of Practice and guidance that sets out what those arrangements have to look like in practice: atmosphere testing before entry and, where the risk assessment calls for it, continuous monitoring throughout; a means of communication between the entrant and a dedicated attendant; and a rescue plan with the equipment to carry it out on site, checked and ready, rather than described in the method statement and assumed achievable if needed.

The permit's job is to be the point at which someone checks that regulation 5's rescue arrangements actually exist before authorising entry, not a record that a risk assessment was written earlier. A confined space entry permit signed without a rescue team, a tripod and winch or equivalent, and a tested means of raising the alarm already on site has not discharged regulation 5, whatever the risk assessment says is required.

Excavation permits: the permit to dig and the services check

CDM 2015's general requirements for construction sites cover excavations specifically at regulation 22, energy distribution installations, which is where the duty to locate and protect buried and overhead services sits, at regulation 25, and the duty to produce reports of inspection at regulation 24, with Schedule 3 setting out the particulars those reports have to contain. HSE's HSG47, Avoiding danger from underground services, 3rd edition 2014, and HSG150, Health and safety in construction, 3rd edition 2006, are the guidance documents reviewers and inspectors measure a dig against in practice.

A permit to dig earns its place by forcing three checks before the first bucket goes in the ground: the services drawing has been checked against the work, a cable avoidance tool and signal generator scan has actually been carried out and recorded rather than assumed from the drawing alone, and the excavation method has been agreed against the ground conditions found, not those assumed at tender. The inspection duty under regulation 24 and Schedule 3 then continues for as long as the excavation is open: at the start of every shift, and again after any event liable to affect its stability, such as a fall of material, damage to support, or a change in groundwater. A permit signed once at the start and never reissued against a changed condition is not evidence that regulation 24 was met on day four.

The register that proves the system is working, not just that forms exist

A permit register that lists every permit by number, shows which are open and which are closed, and is reviewed on a stated interval rather than only when someone remembers to, is what turns three separate forms into a system an auditor can trust. The review is where a permit left open on a finished job, or a pattern of permits issued without the independent check they should carry, gets caught before an incident investigation asks why nobody noticed.

What we would put in place before the next audit

The fix is rarely a new form. It is making sure the four features of a working permit to work system are present on the ones already in use: an independent issuer, a checklist that cannot be signed off blank, a validity period that expires, and a close-out someone has to complete. The Site Health & Safety Pack carries a full suite of permits, including the hot works permit, a confined space entry permit and a permit register with its own monthly review tab, and the Excavations & Confined Spaces Pack carries the permit to dig with its services drawing and CAT and genny record alongside the confined space entry permit, gas monitoring log and rescue plan it depends on. The free ITP is the lowest-risk way to see how we cite a current-edition standard before looking at either pack in full.

Where the duty sits

CDM 2015 places the plan itself squarely with the principal contractor. Regulation 12 is the duty to draw up a construction phase plan, and then to implement it and keep it reviewed and revised as the project moves, rather than treating it as fixed on day one. The same regulation carries the client's side of the bargain: the client must not allow the construction phase to start until a suitable plan is in place and the welfare facilities a project needs are arranged. That is the mechanism that makes "before work starts" a legal gate rather than a target. If the plan is not ready, the client should not be letting the principal contractor mobilise, whatever the programme says.

Regulation 13 then covers what the principal contractor has to do with the plan once the phase begins: plan, manage, monitor and coordinate construction work for the whole of that phase, not just write a document and move on. That includes making sure every contractor on site has been given the site induction and the parts of the plan relevant to their work, keeping unauthorised people off site, and seeing that contractors cooperate and coordinate with each other rather than working to separate, unreconciled plans of their own. Welfare facilities have to be in place for the whole of the construction phase, not just available to inspect on the first morning.

Our records show CDM 2015 unchanged since its last consolidating amendment, dated 1 January 2018 on the legislation.gov.uk record, with no outstanding effects as at our last check. HSE's own guidance on the regulations is set out in L153, Managing health and safety in construction, which is the document most principal contractors and inspectors measure a plan against in practice.

What the plan has to show

CDM 2015 does not ask for a fixed-length document; it asks for a plan proportionate to the risk on the project, and in practice reviewers and inspectors look for the same handful of things whatever the size of job. A description of the project and the work involved. The management structure for the construction phase: who is in charge, who deputises, and how contractors report into it. The site rules, and how they will be communicated and enforced, not just listed. The arrangements for worker consultation and engagement, so the workforce has a route to raise a concern. Welfare facilities and where they sit on site. The arrangements for site security and for controlling who can get in. And, specific to the risks the project actually carries: traffic and pedestrian routes, work near existing services, storage and use of hazardous substances, the stability of structures during the works, and the emergency and fire procedures that apply.

The common failure is not a missing section. It is a plan that copies all of this in generic language from a template and never gets reworked against the actual site: a traffic management paragraph that does not name the gate the project is using, an emergency procedure that gives a muster point that does not exist on this site, a site rules section that reads the same on every job the company runs. A reviewer who has seen a hundred of these spots a generic plan in the first page, and an inspector asking a site manager to point to the muster point named in the plan finds out fast whether it was ever read.

Before work starts: the test that actually matters

"Before work starts" is tested less by the date on the plan's cover sheet than by what can be shown to have happened before the first operative arrived. Three things in particular:

• The plan was issued, not just drafted. A dated record of the plan being issued to the client, the principal designer where one is appointed, and the contractors due to start, ahead of mobilisation.
• Welfare was arranged, not promised. Toilets, washing and rest facilities ordered and installed, or a written arrangement for interim facilities, before the first shift, not scheduled for "week two" once the compound is finished.
• The site induction was built around this plan, not a stock one. An induction record naming the project-specific rules, hazards and emergency arrangements the plan describes, delivered to every contractor before they started work, with signatures and a date that precedes the work, not follows it.

Any of these missing is a plan that existed on paper on day one and in practice some days or weeks later. Most disputes about whether CDM 2015 was complied with on a given site turn on exactly this gap.

Where it slips after the start

Regulation 12's review duty is often the weakest part of the file. A plan written for the mobilisation stage, covering groundworks and enabling works, is rarely revisited once the project moves into structure, fit-out or commissioning, even though the significant risks, the contractors on site and the site rules have all changed by then. We see three recurring patterns:

1. The plan is reviewed on a fixed date in the programme rather than against a trigger, so a new high-risk activity starting mid-project, a new subcontractor with its own plant, or a change in site layout, goes unreflected for months.
2. Later contractors are given the original issue of the plan and the original induction, because document control was never told a revision had happened.
3. The health and safety file information the principal contractor owes the principal designer under regulation 12 is left to the last fortnight of the project, when the people who actually did the relevant work have mostly left site.

The record that proves it was in place in time

When a plan's timing is challenged, by an inspector, an auditor or a client, the file has to answer from dated records rather than a manager's recollection.

A site that can produce all four inside a few minutes has a plan that was genuinely in place, not one that merely existed. A site that cannot is relying on the plan having been correct in principle and hoping nobody asks when.

What we would put in place before the next mobilisation

Three things cover most of the gap we find. Build the construction phase plan against this project's traffic routes, services, rules and emergency arrangements rather than a previous one, even where the structure of the document is reused. Tie the plan's review to events on the programme, not a calendar date, so a genuine change in risk triggers a revision. And make the site induction the moment the plan actually reaches the workforce, with a record that ties the two together. Our construction phase plan template is built to regulation 12 with a worked example completed end to end, and the wider Site Management, Planning & Records Pack carries it alongside the daily records, inductions and registers that show the plan was followed once the work began, not just written before it.

What suitable and sufficient actually means

The legal anchor for the risk assessment is regulation 3 of the Management of Health and Safety at Work Regulations 1999, which requires every employer to make a suitable and sufficient assessment of the risks to workers and to anyone else who might be affected. Suitable and sufficient is the test a reviewer is applying, whether they name it or not. It means the assessment is proportionate to the risk, that it identifies the significant hazards rather than listing every conceivable one, and that it leads to real control measures rather than a note to take care.

HSE now frames the assessment as a short sequence: identify the hazards, decide who might be harmed and how, evaluate the risk and decide on controls, record the significant findings, and review when something changes. A generic template fails at the middle steps, because the people and the controls are the parts that only make sense once you know the task and the location. A reviewer can tell in under a minute whether those steps were done for the job in front of them or lifted from the last one.

Why method statements get sent back

The method statement is the safe system of work written down. It is not named in a single regulation, but the duty to provide one flows from section 2 of the Health and Safety at Work etc Act 1974 and, on construction, from the Construction (Design and Management) Regulations 2015, which require the work to be planned, managed and monitored. The common failings are easy to list and easy to fix:

• It describes the activity in general terms and never sets out the sequence of operations in the order they will happen.
• The hazards from the risk assessment are not carried through, so the controls in the method statement do not match the risks that were identified.
• Responsibilities are vague. A reviewer wants to see who supervises, who is competent to do what, and who can stop the job if conditions change.
• Plant, access and materials are assumed rather than stated, so there is no way to check that the method is actually workable.
• Emergency and rescue arrangements are missing, which is the first thing a reviewer looks for on higher risk tasks such as confined spaces, lifting and work at height.
• It still carries the name of another site or another contractor, which tells the reviewer it was never written for this job.

Use the hierarchy of control, in order

Schedule 1 to the Management Regulations sets out the principles of prevention, and they are an order, not a menu. A method statement that reaches straight for personal protective equipment as the main control is one of the clearest reasons a RAMS is rejected. The reviewer wants to see the question asked in sequence: can the hazard be removed, can a less hazardous method or material be substituted, can it be engineered out or guarded, can it be controlled by how and when the work is organised, and only then what protective equipment is needed to deal with the risk that is left. Showing that reasoning is what turns a list of hazards into a controlled task.

Make it specific to this task on this site

The single habit that gets a RAMS accepted first time is specificity. Name the actual location and the actual activity, not a category. Reference the drawings, the permit, the temporary works design or the lifting plan that the method depends on, so the reader can see the controls are real. Where the risk assessment identifies a significant hazard, the method statement should answer it in plain terms a supervisor can brief on site. If the task interfaces with others, say so, because simultaneous operations, shared access and overhead work are where incidents cluster, and a reviewer will look for them.

Briefing and sign-off, the step that gets skipped

A RAMS that has not been briefed to the people doing the work is just paper, and a reviewer increasingly asks for the evidence that it was. The record that the operatives were briefed, understood the sequence and the controls, and signed to that effect is part of the safe system of work, not an afterthought. It is also the record that protects everyone if something goes wrong, because it shows the plan reached the point of work. Keep the briefing record with the RAMS and the toolbox talk that supports it, and make sure the version briefed is the version that was approved.

A quick pre-submission check

Before a RAMS goes in for approval, read it as the reviewer will:

• Does it name this site, this task and this date, with no leftovers from another job?
• Do the controls in the method statement answer every significant hazard in the risk assessment?
• Is the sequence of work set out step by step, with the plant, access and materials each step needs?
• Are the competent and responsible persons named, including who can stop the work?
• Are emergency and rescue arrangements stated for the higher risk elements?
• Is there a place to record the briefing and the sign-off, and a trigger to review if conditions change?

What good looks like

A RAMS that stands up is specific, sequenced and honest about the risk that is left once the controls are in place. The risk assessment identifies the significant hazards and follows the hierarchy of control to real measures. The method statement turns those measures into an ordered plan a supervisor can brief and follow, names who is responsible, and sets out what happens in an emergency. It references the drawings, permits and designs it relies on, and it carries a briefing record so there is proof the plan reached the people doing the work. None of that adds length for its own sake. It is the difference between a document that describes a task and one that controls it, and it is what gets the work approved the first time it is read.

This is general guidance based on the regulations and HSE guidance current at the time of writing. It is not a substitute for the regulations, the relevant Approved Codes of Practice or professional advice, and it is written with Great Britain in mind.

A code insurers wrote, not a regulation

The Joint Code of Practice is not a statutory instrument. It is industry guidance, published by the Fire Protection Association with the Construction Leadership Council, now at its 10th edition incorporating Amendments 1 and 2, and it carries weight because the insurance market built its construction-phase cover around it. Most contract works policies require compliance with the Code as a condition of cover, and most main contractor and client requirements documents require the same by reference, so a plan that does not follow its structure is one the broker and the client's adviser will both query. Alongside it sits HSE's HSG168, Fire safety in construction, now in its 3rd edition: the regulator's own guidance, and the document an HSE inspector is most likely to have in mind on a site visit. Neither replaces the legal duty: CDM 2015 (SI 2015/51) requires the principal contractor to prepare a construction phase plan, under regulation 12, setting out site rules and arrangements for managing the significant risks of the work, and fire is one of those risks on any site with hot works, temporary electrics, combustible insulation or timber frame. The two codes are how that duty gets written up in enough detail to be checked.

Where part of a building is occupied while construction continues elsewhere, a phased school, hospital or retail scheme being the common case, the Regulatory Reform (Fire Safety) Order 2005 also applies, to the occupied part and its own responsible person. The construction phase plan then has to show how the site's arrangements interface with that responsible person's: whose alarm the site reports to, whose evacuation routes the hoarding does not block, and who tells whom when a hot works permit is issued near the shared wall. A plan that treats the whole project as one undifferentiated construction site when half of it is occupied is the first thing a careful reviewer will pick up.

What the plan has to contain

• A named fire safety coordinator, appointed in writing, with the authority to stop work and a briefing record, not just a title added to an existing role.
• A site-specific fire risk assessment that changes as the building does. The escape route past one completed staircase is not the escape route once a second is usable, and an assessment written at mobilisation and never revisited describes a site that no longer exists.
• Means of escape and travel distances for the construction phase, on a site plan reissued as access routes, hoarding and staircases change, not left as the tender-stage drawing.
• A hot works procedure and permit register, with the fire watch during and after the work and the extinguisher at the point of work, not at the store.
• Compartmentation and fire-stopping sequencing against the programme, so the plan states when temporary fire stopping is needed at a penetration awaiting its permanent treatment.
• Control of flammable materials, LPG and temporary heating, with a register of what is stored where, in what quantity, and how far from the boundary and any occupied space.
• Site security against arson: perimeter security, lighting, skip and waste storage away from the structure, and out-of-hours checks.
• Liaison with the fire and rescue service: a site plan held at the gate showing access, water supplies and commissioned fire systems, kept current as the layout changes.
• Fire point and extinguisher provision matched to the hazards present, checked and recorded, not installed once at mobilisation.
• Training and drills, recorded, briefed to every new starter and repeated at a stated frequency.

The sections reviewers open first

Where it gets missed on real sites

A fire safety plan is rarely abandoned outright. It drifts, in a handful of ordinary ways.

1. The coordinator is named but never briefed. The role sits with the site manager by default, nobody tells them what the appointment actually requires, and the first they hear of it is when an auditor asks to see the briefing record.
2. The escape plan is the tender drawing. The staircases, hoarding and access roads have all moved since the plan was issued, and the document in the site office describes a building that no longer matches the one standing.
3. The hot works permit is issued, but the fire watch is not kept on afterwards. The work finishes, the operative moves to the next task, and the smouldering material that starts a fire two hours later is exactly what the post-work watch exists to catch.
4. Fire stopping is treated as snagging. A service penetration is left open "to come back to" once first fix is complete, the compartment line is broken for weeks, and nobody has recorded that a temporary measure was needed in the meantime.
5. The liaison pack is not updated. The road the fire service would use is now the site compound, the plan at the gate still shows the old access, and nobody has told the local fire station the layout has changed.
6. Training happens at induction and nowhere else. New subcontractors joining mid-programme never get the briefing, and the drill record shows one entry from eighteen months ago.

None of these is a decision to ignore fire safety. They are what happens when the plan is written once, filed, and left to describe a site that keeps moving without it.

Keeping the plan alive

The plan needs a stated review trigger, not just a review date. A change in building height or occupied status, a new staircase or escape route becoming usable, a change to the construction programme that moves hot works or fire stopping, a new subcontractor bringing flammable materials onto site, or any incident or near miss, should each trigger a review of the sections that change: the escape plan, the liaison pack, the materials register. Reviewed on a fixed six-monthly date and nothing else, the plan will always be behind the site it describes.

Where this sits in our library

The Construction Site Fire Safety Pack carries the construction phase fire safety plan as a full worked example cited to the JCoP 10th edition with Amendments 1 and 2 and HSG168, with the coordinator appointment, hot works procedure and register, compartmentation tracker, flammables and LPG register, arson checklist, drill record and fire service liaison pack behind it, plus the Regulation 38 handover schedule that carries the fire safety information forward at completion. The RAMS Library and the toolbox talk libraries supply the hot works method statement and the induction and drill briefings that sit alongside the plan. If you want to see how our documents are cited and cross-referenced before buying anything, the free ITP is the place to start.

What Gateway 3 actually decides

The completion certificate is applied for under the Building (Higher-Risk Buildings Procedures) (England) Regulations 2023, SI 2023/909, regulations 40 to 45. The principal contractor and principal designer each sign a declaration that, so far as they are aware, the building work complies with all applicable requirements of the Building Regulations, and the client applies to the Building Safety Regulator for the certificate. The regulator decides whether it is satisfied the work complies, and it can ask for more information before it does. Section 76 of the Building Safety Act 2022 is the sanction that makes this gateway real: a higher-risk building, or a part of one, cannot be occupied until the completion certificate for it has been issued. A handover date that assumes the certificate is the difference between a programme that lands and one that slips into dispute.

The record is the application

A declaration that the work complies is only worth the evidence behind it. The golden thread, kept to regulation 31 of the Building Regulations 2010, is where that evidence lives: the information that shows how the building was designed and built to comply, held digitally, kept current and handed over. Gateway 3 reads the as-built version of it. The approved design from Gateway 2 is the baseline; the completion evidence has to show what was actually installed, where it departs from that baseline, and why each departure is still compliant. Underneath the declarations sit the records that prove the point one element at a time: the inspection and test plans with their hold points signed off, the regulation 7 record that the materials and workmanship were adequate and that materials were as specified, and the regulation 38 fire safety information that passes to the responsible person at completion. The application is not a new document you write at the end. It is the filing system you either kept or did not.

Why the record usually has to be rebuilt

On a project that reaches an advanced stage without a structured quality regime, the record is rarely complete, and the problem is worst exactly where it matters most. Work has been covered: risers closed, ceilings boarded, shafts lined, with no inspection evidence captured before it disappeared. Installations have been changed on site to suit a clash or a late substitution, and the change never reached the designer. Subcontractors have certified their own work in formats that do not tie back to a drawing or a compartment line. None of that is unusual, and none of it is fatal, but it does mean the honest first step is not to write the completion pack. It is to find out what can still be evidenced, what has to be re-inspected, and what has to be opened up to be verified at all. A gap assessment that sizes the recoverable and the unrecoverable is worth more at that point than any template.

As-built verification and design reconciliation

As-built verification is the discipline of recording what was actually constructed and reconciling it against the approved design, element by element and system by system. Where the installed condition matches the design, the evidence is captured and the line is closed. Where it does not, the departure is not quietly redrawn; it is assessed as a change. Under SI 2023/909 regulations 18 to 26 a change to the approved design is at least recordable, a notifiable change is notified before it is carried out, and a major change is applied for and not carried out until approved. A departure discovered during as-built verification is caught by the same classification: the designer reviews it, decides whether the as-built condition is acceptable or has to be remedied, updates the design where it is accepted, and the verification then confirms the final position. Done properly it is an iterative loop, design to site to design, and the as-built information and the supporting design end up saying the same thing. Done badly it is a set of red-pen mark-ups nobody signed.

The fire-critical evidence comes first

Not all of the record carries the same weight, and a sensible recovery strategy triages it. Compartmentation, passive fire protection, cavity barriers, fire-stopping at service penetrations, fire doors and the life-safety installations are where the regulator's attention is, because they are what the higher-risk regime exists to control. For these elements the evidence has to be specific: the product actually installed, its assessed classification for the construction it sits in, the inspection that confirmed it was installed to that assessment, and a photograph or a record taken before it was concealed. "Fire-stopping by specialist, certificate to follow" is not evidence; the product substituted for the one assessed is a change, not a detail. Where fire-critical work has already been closed without that evidence, targeted intrusive verification, opening up a representative sample and inspecting it, is usually faster and more credible than arguing that the absence of a record is the same as compliance.

How to structure it so it survives the reading

A completion evidence register that a regulator can follow is structured the way the building is: by building, by floor, by location and by system, with every record traceable to the relevant building element, the drawing and its revision, and the applicable requirement. That structure is what lets a reviewer pull any thread, a compartment line, a riser, a plant room, and find the inspection, the as-built confirmation, the materials record and the design reference without being handed a folder and a wish of luck. It is also what lets the contractor see the gaps while there is still time to close them, because an empty cell in a register organised by location is a site instruction, not a surprise at the gateway. Inspection apps such as Field View hold this well when they are set up to that structure from the start, with the controlled output feeding the document management system the application is assembled from.

Where this leaves you

If you are approaching Gateway 3 on a higher-risk building and the record is not what it should be, the recoverable position is almost always better than it feels, but only if the recovery is run as a process rather than a scramble. Establish the framework and the registers, size the gap, triage the fire-critical evidence, verify the as-built against the approved design, reconcile the departures through change control, and recover or re-create the inspection evidence element by element. That is the work. The completion certificate is what falls out of it.

England only; Wales, Scotland and Northern Ireland have different regimes. This is a summary of the regulations as read on 16 September 2026 and is not legal advice; the Building Safety Regulator's current guidance and the text of the regulations govern.

Two documents, two different jobs

The Lifting Operations and Lifting Equipment Regulations 1998 set the legal baseline at regulation 8(1): every lifting operation involving lifting equipment must be properly planned by a competent person, appropriately supervised, and carried out in a safe manner. Regulation 8(2) defines a lifting operation broadly, as an operation concerned with the lifting or lowering of a load. Nothing in LOLER says that plan has to be a single document, and in practice it never is. A lifting method statement describes the task around the lift: access, sequence, isolations, environment, the trades on site and the PPE they wear. A lift plan is the engineering of the lift itself: the load, the radius, the ground, the rigging, the exclusion zone and the crane's rated capacity at that configuration. One is a RAMS. The other is a calculation with a drawing attached. Treating them as interchangeable is how a plan ends up with an access route described twice and a sling angle never checked at all.

What BS 7121 actually asks for

BS 7121-1:2016, the general code of practice for the safe use of cranes, is where the lift plan's content comes from. It categorises lifts as basic, standard or complex, and the category decision drives who is competent to plan and sign the lift: a basic lift with established ground conditions and a crane working well within its chart is a different proposition from a complex lift with a shared radius, a tandem lift or a load approaching the crane's limit. The general code sits alongside part-specific codes for each type of crane: BS 7121-3:2017+A1:2019 for mobile cranes, BS 7121-4:2010 for lorry loaders, and BS 7121-5:2019 for tower cranes. A second series of parts covers inspection, maintenance and thorough examination by crane type: BS 7121-2-1:2012 (general), BS 7121-2-3:2012 (mobile cranes), BS 7121-2-4:2025 (loader cranes) and BS 7121-2-5:2012 (tower cranes). Citing "BS 7121" on an ITP or a plan without the part number is the single most common gap we see when we review one; the part tells a reader which code's categorisation and examination regime actually applies.

Who owns the plan

LOLER's "competent person" is given a job title by the industry rather than by the regulations themselves. The CPA Standard Terms and Conditions for Contract Lifting Services 2021 define the Appointed Person at clause 1.6.1 as the person with sufficient technical knowledge and experience to plan the lift and direct its execution, and the Crane Supervisor at clause 1.6.2 as the person who controls the lift on the ground against that plan. Where the work is placed as a contract lift rather than a crane hire, CPA CIG 2308 sets out which route applies and, critically, confirms that ground conditions remain the crane user's responsibility even under a contract lift, unless the contract says otherwise in writing. A plan with no named Appointed Person, or one that names a company rather than a person, has not discharged regulation 8(1) whatever else it contains.

The six things a lift plan has to show

Working from BS 7121-1's categorisation and the planning guidance in HSE's L113, Safe Use of Lifting Equipment, a lift plan that will survive review needs:

• The load: weight, centre of gravity, dimensions and how they were established, not assumed.
• The crane and configuration: radius, boom length, counterweight and the rated capacity taken from the actual chart, with the utilisation shown as a percentage, not just a pass or fail.
• The ground: bearing capacity under the outriggers or tracks, and how that was checked against the load path.
• The rigging: sling or chain type, rated capacity, angle and the mode factor that angle applies, not a generic "certified slings to be used" line.
• The exclusion zone and any overhead line proximity, set against HSE's GS6 distances where lines are present.
• Weather limits and what happens if they are reached mid-lift, including who calls the hold.

L113 paragraphs 221 to 224 distinguish a routine or generic lift plan, used for repeated lifts of the same type under the same conditions, from a plan written for a specific lift; paragraph 226 points back to BS 7121 for the detail. A generic plan used for a lift it was never written for is the gap that review usually finds, because the ground, the radius or the load has moved and nobody re-checked the chart against it.

Keeping the equipment current

A correct plan still fails if the crane or the accessories are not in date. LOLER regulation 9(3) sets the examination intervals: six months for lifting accessories and equipment used to lift people, twelve months for other lifting equipment, or whatever shorter interval an examination scheme sets, plus examination after any exceptional circumstance liable to affect its safety. Regulation 10 requires the examining body to notify the employer forthwith of any defect involving existing or imminent risk of serious injury, and to send a copy to the enforcing authority; the equipment must not be used until the defect is rectified. Regulation 11 sets retention periods for the reports, and Schedule 1 lists the eleven items a report of thorough examination has to contain. An equipment register that tracks the next-due date against each item, and flags anything overdue before it reaches site, is the record that turns these regulations from a filing duty into something that actually stops a defective sling going out again.

When it goes wrong

RIDDOR 2013, Schedule 2, makes the collapse, overturning or failure of load-bearing parts of lifting equipment reportable, other than an accessory on its own, and separately makes contact between any part of a crane or its load and an overhead line carrying more than 200 volts reportable regardless of injury. Both are the kind of event a well-run lift plan is specifically trying to prevent: the first through the ground, rigging and chart checks above, the second through the exclusion zone set against GS6. A near miss on either should be treated as seriously as a reportable one, because the gap between them is often the load swinging a few degrees differently on the day.

Keep the two documents separate, and cross-referenced

The practical fix is not to merge the lift plan and the lifting method statement into one document; it is to keep each doing its own job and link them by number. The RAMS references the lift plan number for the engineering detail and does not repeat the chart figures; the lift plan references the RAMS for access, sequence and the wider site controls and does not repeat the PPE list. Reviewers read both, and a reviewer who finds the rigging calculation buried in paragraph nine of a method statement, with no lift plan to check it against, treats that as a sign the lift was not planned by a competent person at all - whatever the paperwork says. The Lifting Operations Pack keeps that separation built in: the procedure and Appointed Person appointment, four worked lift plans against BS 7121 and LOLER, a separate lifting method statement template, the calculators behind the rigging and ground-bearing figures, and the equipment register with its examination scheme. The free ITP is the lowest-risk way to see how we write a current-edition citation before looking at anything else.

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.

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.

What has happened

ISO released the 2026 edition and BSI has adopted it as the British Standard, BS EN ISO 9001:2026, superseding BS EN ISO 9001:2015+A1:2024, which is now withdrawn. It followed the same path as ISO 14001:2026 earlier this year, released by ISO on 15 April 2026 and adopted as BS EN ISO 14001:2026, superseding its 2015+A1:2024 edition. The text is now something you can buy and read, rather than something to speculate about, and that changes how you should treat it.

What has changed, in headline terms

We have not yet walked the 2026 text clause by clause against the 2015 edition, and we will not pretend a summary is the same thing as that review. But BSI's own guidance sets out the main changes, and these are the headlines worth knowing:

• More emphasis on quality culture and ethical behaviour, and on leadership genuinely owning quality rather than signing the policy, reflected in clauses 5.1.1 and 7.3.
• A clearer distinction in clause 6.1 between managing risk and pursuing opportunity, so that planning has to be deliberate about both rather than treating risk as a box to tick.
• For the first time, an annex of supplementary guidance, Annex A, running to around 15 pages, that explains the structure, terminology and intent behind the requirements. For a smaller contractor implementing without a consultant, that annex is the single most useful addition.

None of that changes the shape of a good system. It sharpens what a good system was always meant to do: leadership that owns quality, planning that takes risk and opportunity seriously, and requirements people can actually understand.

Your certificate is not affected today

A certificate to ISO 9001:2015 does not expire because a new edition has been published. When ISO issues a revision of a management system standard, the International Accreditation Forum sets a transition period during which certificates to the old edition remain valid and certification bodies move their clients across at surveillance or recertification audits. For the 2015 edition that period was three years from publication. Three years is the usual pattern for ISO management system revisions, but it is set case by case, so confirm the arrangements for this revision with your own certification body rather than relying on the pattern.

What that means practically: your next surveillance audit will be to the edition on your certificate unless your certification body tells you otherwise. Ask them in writing, now, what their transition plan is and when they will offer transition audits. Get the answer into your management review minutes so there is a record that the business knew and planned.

What to do now

1. Do not rewrite anything yet. A QMS that works, with records behind it, is worth more at your next audit than a hastily renumbered one. The transition period exists so that you do not have to rush.
2. Buy the UK text now that it is published, BS EN ISO 9001:2026, not a summary of it. The cost of the standard is trivial against the cost of a major nonconformity for a requirement you did not know existed, and Annex A now comes with it.
3. Walk the clause map. Take your quality manual's clause cross-reference, or your gap analysis tool, and go through the 2026 text clause by clause against it. Record one of three things for each: unchanged, renumbered, or new or changed requirement. Only the third category needs work.
4. Put the gap on your corrective action register as a planned change under clause 6.3, with an owner and a date inside the transition window. Auditors like to see a revision planned rather than discovered.
5. Book the transition audit to coincide with a surveillance or recertification visit. Most certification bodies will combine them; a separate visit costs more.

How the StructAssure QMS handles it

The ISO 9001 Construction QMS is written to the 2015+A1:2024 clause structure. On 17 September we added an edition note to the quality manual (QM-001, section 1) and to the implementation plan (IMP-001): it records that ISO 9001:2026 has been published, that the pack follows the 2015+A1:2024 clause numbering pending review, and that the transition period is to be confirmed with the certification body. The note is there so that an auditor opening the manual sees that the business knows, which is itself evidence of clause 4.1 working.

Now that BS EN ISO 9001:2026 is available, that review is the next job. The clause map inside the QMS has 66 rows, and the gap analysis tool (TOOL-001) follows the same numbering. We are walking both against the 2026 text and will revise every procedure, form and register that the review touches. Buyers get the revision through their existing Payhip download link, at no extra cost; the revision table in each document will show what changed and why. If nothing changed in a clause, we will say so rather than issuing a new revision for the sake of it.

We are taking the same line with ISO 14001:2026, which is already published and already cited in the Construction EMS, and with ISO 19011:2026 for the audit pack. The auditing standard is covered in a separate post.

The honest summary

A new edition of ISO 9001 is news for consultants and certification bodies. For a contractor with a certificate, it is a diary entry: ask the certification body about transition, buy the text when the UK adoption appears, walk the clauses, plan the change. If your quality system is built on evidence, hold points signed, NCRs closed with root cause, audits done and reviewed, the edition on the cover matters less than the auditor's ability to find that evidence. That is what we would spend the next three months on.

Clause 6.1.3: compliance obligations, not "the law"

ISO 14001:2015 does not use the phrase "legal register". Clause 6.1.3 asks the organisation to determine and have access to the compliance obligations related to its environmental aspects, to determine how those obligations apply, and to take them into account when planning the management system. Compliance obligations means more than statute: it includes the conditions on a planning consent, the requirements a client has written into a contract, and any voluntary scheme the company has signed up to, alongside the Acts, regulations and consents that apply regardless. In practice, for a construction SME, this becomes one document: a register with one line per instrument, what it requires of this company on this kind of site, how the company meets it, the evidence, and the date it was last checked. The compliance obligations register is the document an auditor asks for on day one of a site visit, and it is also the document most likely to have been written once and left.

What is actually on a construction site's register

The list is longer than most contractors expect, because ordinary site activities each trigger their own instrument. The core group rarely changes: the Environmental Protection Act 1990, section 34, the duty of care for anyone who produces, keeps or disposes of waste; the Waste (England and Wales) Regulations 2011, which govern waste transfer notes and the waste hierarchy; the Environmental Permitting (England and Wales) Regulations 2016, for any activity that needs an exemption or a permit, from a mobile plant registration to a groundwater activity; the Hazardous Waste (England and Wales) Regulations 2005, for anything from asbestos to waste oil; and the Control of Pollution (Oil Storage) (England) Regulations 2001, for every bunded fuel tank on site. Alongside these sit the instruments that only bite on certain jobs: the Control of Pollution Act 1974, section 61, for a prior consent on noisy works; the Wildlife and Countryside Act 1981, the Conservation of Habitats and Species Regulations 2017 and the Protection of Badgers Act 1992, wherever a survey has found a protected species nearby; and the Environment Act 2021, now that biodiversity net gain is a planning condition on most sites rather than an aspiration. None of this is exotic. It is the ordinary paperwork of a site that stores fuel, produces skips and sits near a hedge, and every line of it belongs on the register, not in a consultant's head.

What changes on 1 October 2026

The Digital Waste Tracking (England) Regulations 2026, SI 2026/729, make electronic recording of waste movements mandatory for waste receivers from 1 October 2026, with carriers and brokers following in a second phase from spring 2027. For a contractor this reaches further than the waste transfer note in the site cabin. It changes how the skip company, the muck-away haulier and the recycling facility record what they took off site, and a compliance obligations register written before this year will not mention it. This is the clearest example we can point to right now of why the register has to be a living document rather than a start-up artefact: the duty exists whether or not it is written down, and a contractor who cannot show it has been considered has already failed clause 6.1.3, regardless of whether it has failed the duty itself.

The entries that quietly go stale

Two things make an environmental register drift out of date. The first is revocation. The Environmental Protection (Duty of Care) Regulations 1991 were revoked for England and Wales by the Waste (England and Wales) Regulations 2011, which now carry the duty of care requirement at regulation 35; a register that still cites the 1991 Regulations is citing a dead instrument for a live duty. The Site Waste Management Plans Regulations 2008 were revoked in England in December 2013, so an SWMP is no longer a legal requirement there, only a contract requirement where one is specified, and a register that lists it as statutory overstates the position. The second is the management-system standard itself. ISO 14001:2015 was amended in 2024 to add climate change as a relevant issue, and has since been superseded by a fourth edition, BS EN ISO 14001:2026. None of that changes what the law requires. It does mean a manual that still names the 2015 text on its cover is a housekeeping problem an auditor will raise, and a prompt to check what else on the same page has moved on with it.

The columns that keep it current

A register that survives contact with an auditor has the same shape as any other control document: an identity for each obligation, what it requires, and evidence that keeps the date visible.

The last column is the one that does the work. Without a checking date, an auditor cannot tell a register that is current from one that is coincidentally still correct, and neither can the company.

Evaluating compliance, not just listing it

Clause 9.1.2 asks for periodic evaluation of compliance with the obligations determined at 6.1.3, with results kept as evidence. This is where most small contractors' systems are thinnest. Listing the duty of care is not the same as showing that every waste transfer note this quarter was completed correctly, or that the fuel bund was inspected. The evaluation record does not need to be elaborate. It needs to say, obligation by obligation, what was checked, when, and what was found, with a corrective action raised against anything not being met. A register with a compliance evaluation column, reviewed at the same frequency as the legal update check, answers clause 9.1.2 and clause 6.1.3 from the same document.

Where the register sits in the wider system

The compliance obligations register does not stand alone. It is fed by the environmental aspects and impacts register, which identifies what the company's activities actually do to air, water, land and neighbours, and it feeds the construction environmental management plan for each site, which turns the obligations into site-specific controls, monitoring and named responsibilities. A contractor that keeps these three documents cross-referenced, rather than as separate exercises done for the audit, ends up with a system that answers the standard and matches what is actually happening on site.

Our ISO 14001 Construction EMS carries the compliance obligations register pre-populated with the instruments named above, dated at the edition current when the pack was last rebuilt, alongside the environmental policy, aspects register and the evaluation-of-compliance record clause 9.1.2 asks for. The Environmental & Sustainability Site Pack sits underneath it with the site-level CEMP, waste registers built for the Digital Waste Tracking change, and the spill, monitoring and complaint records the register points to as evidence. Certification is granted only by an accredited certification body after audit; the documents shorten the road, they do not remove it. If you want to see the standard of the documents before buying either pack, start with the free ITP.

What ISO 19011 is, and is not

ISO 19011 is guidance. It is not a requirements standard and nobody is certified to it. ISO 9001:2015 does not even list it as a normative reference; it appears in the bibliography. The requirement to audit comes from clause 9.2 of ISO 9001, and its equivalents in ISO 45001 and ISO 14001: plan an audit programme, define criteria and scope, select auditors who are objective and impartial, report to management, correct what is found, keep the records. ISO 19011 tells you how to do those things well. So a change to ISO 19011 changes the advice, not the obligation.

What we have and have not checked

We have verified that the 2026 edition is current and that the 2018 edition is withdrawn, on the NBS Publication Index and against the release dates on en-standard.eu. We have not yet walked the 2026 text against the 2018 text line by line, and until we have we are not going to tell you which clauses moved or what new guidance was added. The 2018 edition set out seven principles of auditing (integrity, fair presentation, due professional care, confidentiality, independence, the evidence-based approach and, new in 2018, the risk-based approach), a clause on managing the audit programme, one on conducting an audit and one on auditor competence. Whether the 2026 text keeps that shape we cannot say yet. When we have read it, we will say so here.

In the meantime we have changed the citations. The internal audit procedure in the Quality Audit & Reporting Pack (QA-201) and the audit checklist Read Me in the ISO 45001 Construction OHSMS now cite ISO 19011:2026, with a note that the checklist questions were written to the 2018 process and have not yet been checked against the 2026 text. A note that admits what has not been done is worth more to an auditor than a citation that pretends.

The audit programme steps that do not depend on the text

These are the things that make an internal audit programme work on a construction contractor, and none of them will be changed by a revision of the guidance, because they come from the requirements standards and from what auditors actually find.

1. Plan by risk, not by calendar. An audit programme that visits every clause once a year in alphabetical order is a calendar, not a programme. Weight it towards the processes where failure costs most: hold points, subcontractor control, calibration, nonconformance, and the trade with the most NCRs last quarter. Record the reasoning on the programme so an external auditor can see it.
2. Write the criteria before the audit. Every checklist question names the requirement and where it comes from: the ITP line, the specification clause, the standard and its clause at the current edition. A question that does not cite its source cannot be failed fairly.
3. Audit evidence, not opinion. Each finding records the objective evidence: the document number, the location, the photograph, the name of the person interviewed. "Housekeeping poor" is an opinion. "Cable drums stored on bare ground at grid C4, contrary to the materials control plan section 5, photograph 12" is a finding.
4. Independence. The person who runs a process does not audit it. On a small contractor that means the site manager audits the office, the QS audits the site, and the director audits neither. If there is genuinely nobody independent, a half-day from an external auditor once a year is cheaper than a major nonconformity.
5. Grade findings consistently. Major, minor, observation, with the definitions written on the checklist. A major is a requirement absent or broken down; a minor is an isolated lapse in a process that otherwise works; an observation conforms but carries a risk.
6. Root cause before close-out. An NCR closed with "operative reminded" will reopen. Ask why until the answer is a process, a resource or a decision, and correct that.
7. Report upwards and prove it. Audit results are a required input to management review. Take the findings, the trends and the overdue actions into the review and minute what was decided.
8. Auditor competence on record. A training record, a witnessed audit, or a lead auditor certificate. The auditor's competence is one of the first things a certification body checks.

What to do this month

Change the citation in your internal audit procedure to ISO 19011:2026, add a note that the process has not yet been reviewed against the new text, and put the review on your document register as a planned change with a date. Buy the standard when your budget allows; it is guidance, so nobody will fail you for not owning it, but you cannot check your procedure against text you have not read. Then keep auditing. A programme with completed audits, findings closed at root cause and results in management review satisfies clause 9.2 whatever edition of the guidance is on the shelf.

ISO 9001 itself has also been revised this month. That one does carry obligations, and it has its own post.

The fourteen

1. BS EN 166 is withdrawn. Eye protection is now specified to BS EN ISO 16321-1:2022+A1:2025, with BS EN ISO 16321-3 for the mesh and welding parts. Every RAMS, COSHH assessment and PPE matrix that says "safety glasses to EN 166" is citing a dead standard, though the stock in your stores still carries the EN 166 marks and will for years. We name ISO 16321-1 and keep the legacy mark in brackets. Bites: the Site Health & Safety Pack (done) and the RAMS worked examples (next).
2. BS 5975:2019 became two parts. BS 5975-1:2024 covers procedures and BS 5975-2:2024 falsework design; the single 2019 document was withdrawn on 18 December 2024. A temporary works procedure citing "BS 5975:2019" is out of date, and a register that does not distinguish the procedural part from the design part will confuse a temporary works coordinator. Bites: the Temporary Works Control Pack and the formwork and falsework lines in the civils ITP library.
3. BS 7671:2018+A4:2026. The fourth amendment to the Wiring Regulations is current, and the packs record A3:2024 as ceasing to be current on 15 October 2026. Every electrical ITP, check sheet and test record cites it. Bites: the free ITP, the ITP Starter Pack (M&E), the Commissioning & Test Plan Pack and the Construction Records Library.
4. BS 5839-1:2025. The fire detection and alarm code of practice for non-domestic premises was reissued on 30 April 2025 and the clauses were renumbered; the FIA's guide to the changes sets out where. A fire alarm ITP that cites the 2017 clause for commissioning now points at certification, and the cause-and-effect matrix is expected in the handover documentation. Bites: the fire alarm ITP in the M&E pack, the commissioning pack and the Handover & Close-Out Pack.
5. BS 5266-1:2025 with BS EN 1838:2024. Emergency lighting: the escape route illuminance criterion moved from the centre line to across the width of the route (not less than 1 lux, excluding the outer 0.5 m each side), with 0.5 lux for open areas. A commissioning check that measures the centre line only is measuring the wrong thing. Bites: the emergency lighting ITP, the commissioning check sheets and the test records.
6. BESA TR/19 is withdrawn. Ductwork cleanliness is now TR19 Air, Version 2 (2026), and kitchen extract is TR19 Grease (the August 2020 issue). A cleanliness certificate citing "TR/19 3rd edition" cites a withdrawn document. Bites: the ductwork cleanliness record in the Records Library and the kitchen extract ITP in ITP Library Volume 3.
7. BS 8300 split. BS 8300-1:2018 covers the external environment and BS 8300-2:2018 buildings; the undivided 2009 edition is withdrawn. Accessibility lines in a handover deliverables schedule need the right part. Bites: the Handover & Close-Out Pack and the accessible-installation notes in the M&E ITPs.
8. BS 7976 to BS EN 16165:2021. The pendulum slip test is now specified in the European standard; BS 7976 parts 1 to 3 are withdrawn. Floor finish handover evidence should cite the 2021 method. Bites: the Handover & Close-Out Pack.
9. BS 1377-4:1990 to BS 1377-2:2022. Compaction testing for earthworks moved parts when BS 1377 was reorganised. A compaction record citing Part 4 is citing a withdrawn document. Bites: the earthworks compaction record in the Records Library.
10. BS 8212:1995 to BS 8000-8:2023. Dry lining and gypsum board workmanship now sits in the BS 8000 workmanship series. Bites: the plot completion checklist in the Housing & Fit-Out Completion Pack and the dry lining ITP notes.
11. BS EN 124 is a series. Gully tops and manhole tops are covered by BS EN 124 Parts 1 to 6:2015, with the classes in Part 1 and the material-specific parts after it; the undivided 1994 document is withdrawn. Bites: the drainage ITP in the civils library and the drainage checklist in the Quality Audit & Reporting Pack.
12. BS EN 10025 is a series. Structural steel is BS EN 10025 Part 2:2019 for the non-alloy grades S275 and S355, with the later parts for the fine-grain and weathering grades. A materials approval schedule citing "BS EN 10025" without the part is not wrong, but a mill certificate is checked against the part. Bites: the structural steel ITP, the Materials & Procurement Control Pack and the steelwork audit checklist.
13. CIBSE Guide M, 3rd edition, 2023. Maintenance engineering and management, the reference for O&M manual structure and maintenance schedules at handover. The NBS index still carries only the withdrawn 2008 and 2014 rows; the current edition is on cibse.org. Bites: the mechanical and electrical O&M lines in the Handover Pack deliverables schedule.
14. BS EN 16282-1:2026. Commercial kitchen ventilation. The 2017 edition's own index page records it as superseded by the 2026 text, even though the 2026 row had not reached the index list on the day we checked. Bites: the kitchen extract ITP in ITP Library Volume 3.

Also moved this year

Three management system standards have new editions: ISO 14001:2026 (adopted as BS EN ISO 14001:2026 on 15 April), ISO 19011:2026 (BS EN adoption 9 June) and ISO 9001:2026 (published 16 September, UK adoption pending). BS 8214:2026 for fire door installation, BS EN 206-1:2026 and 206-2:2026 for concrete, BS EN 12845:2015+A2:2026 for sprinklers, BS 7273-4:2015+A2:2023 for fire door release and BS EN 15978:2026 for whole-life carbon assessment have all superseded the editions many documents still cite. Each has its own pack note, and the two ISO revisions have their own posts.

How to find yours

Take every standard cited in your quality plan, ITPs and RAMS and put them in one list with the edition as written. Check each one against a primary index: the NBS Publication Index carries the supersession history for British Standards; en-standard.eu gives release dates; cibse.org, hse.gov.uk and legislation.gov.uk for their own publications. Two traps we fell into. A base standard that has become a multi-part series shows as withdrawn when only the pre-series base document is, and the index list can lag a new edition that its own detail page already names. Write the check date on the list. Then do it again before every tender submission, because the reviewer on the other side has a list too.

The frame

The application is made under the Building (Higher-Risk Buildings Procedures) (England) Regulations 2023, SI 2023/909, regulation 4 and Schedule 1. The regulator, a standalone body sponsored by the Ministry of Housing, Communities and Local Government since 27 January 2026, works to a determination period of 12 weeks for a new higher-risk building and 8 weeks for work to an existing one, extendable by agreement. It may approve, approve with requirements, or reject. Our Gateway 2 guide sets out the full checklist; this post is about the order the evidence is read in and what makes each item survive the reading.

1. The building regulations compliance statement

This is opened first, and it is where most rejections originate. The team is looking for a strategy: how the design meets each applicable requirement of Schedule 1 to the Building Regulations, and where and why it departs from Approved Document guidance. A statement that lists the Approved Documents and says the design complies with each is not a compliance statement; it is a table of contents. Write it requirement by requirement, cross-referenced to the drawing or calculation that demonstrates the point, and make the departures explicit with the justification and the alternative evidence. A reviewer who finds the fire strategy, the structural strategy and the departures in the first ten pages reads the rest with confidence.

2. The drawings, at the right level

The drawings are read against the statement. They must demonstrate compliance, not describe a planning scheme with a note that details will follow. If the compliance statement says cavity barriers are provided at every compartment line, the reviewer expects to find them on a drawing with the product and its assessed classification, not "cavity barriers by specialist". The set that goes in is the set the approval attaches to, and every change to it afterwards is at least a recordable change.

3. The construction control plan

This is the principal contractor's document, and the team reads it to decide whether the people building the design will be able to prove they built it. It describes how the work will be planned, managed and monitored so that it complies: the inspection regime, the hold points, the records at each, the interface with the principal designer when the design changes, and how compliance will be evidenced at completion. The test a reviewer applies is whether the plan could be audited. A plan that says "inspections will be carried out in accordance with the quality management system" cannot. A plan that lists the inspection and test plans by element, marks the hold points, names the record for each and says who signs it can.

4. The change control plan

Read together with the control plan. Every change to the approved design during construction is at least recordable under regulations 18 to 26; a notifiable change is notified before it is carried out; a major change is applied for and not carried out until approved, and the regulator has six weeks to determine it. The plan has to show the classification method, the log, who classifies, and how a change discovered on site reaches the principal designer before the concrete is poured. A reviewer who sees a classification guide, a log template and a named owner believes the process exists. One who sees a paragraph does not.

5. The mandatory occurrence reporting plan

The system for identifying, reporting and recording safety occurrences under regulations 32 to 37, in place before construction begins. A safety occurrence meets the risk condition in regulation 35: it could cause a significant risk to life if it were not remedied. A notice goes to the regulator by the quickest practicable means and a report follows within ten days. The plan needs the definition, the workforce briefing, the internal reporting route and the form. Cross-reference it to change control, because an occurrence such as a cavity barrier that is not the product assessed is also a change.

6. Competence and the dutyholder appointments

Part 2A of the Building Regulations 2010 requires the client to appoint the principal designer and principal contractor in writing and to take reasonable steps to satisfy itself of their competence, including organisational capability and any serious sanctions. The application carries declarations to that effect. The evidence behind them is a record: the appointment letters, the competence assessment, the organisational capability evidence and the sanctions check. Reviewers do not read this first, but they read it, and a declaration with nothing behind it is the easiest requirement to attach to an approval.

7. The rest, and what happens after

The fire and emergency file, the partial completion strategy where the building will be handed over in parts, the planning statement and the higher-risk determination itself complete the set. Confirm each against the current text of Schedule 1 and the regulator's guidance on the application, which was updated on 1 April 2026.

Approval starts the clock, not the close-out. Work must commence within three years or the approval lapses under section 32 of the Building Act 1984, and for higher-risk building work regulation 46A of the Building Regulations 2010 treats the work as commenced when the client's statement confirms that 15 per cent of it has been done. From the first day the principal contractor is audited against the plans in the application: the change log open, the occurrence reporting system briefed, the golden thread kept to the standards in regulation 31, the Regulation 7 record for materials, and the ITPs with the hold points the control plan promised. Every declaration in the Gateway 3 completion certificate application under regulations 40 to 45 depends on those records, and under section 76 of the Building Safety Act 2022 the building cannot be occupied until the certificate is issued. A contractor who assembles the Gateway 2 pack in the order above has, without noticing, also built the filing system for Gateway 3.

England only; Wales, Scotland and Northern Ireland have different regimes. This is a summary of the regulations as read on 16 September 2026 and is not legal advice; the Building Safety Regulator's current guidance and the text of the regulations govern.

First, what certification is

A UKAS-accredited certification body audits your business in two stages. Stage 1 is a readiness review: does the documented system cover the standard, is it in use, is there enough evidence for a full audit to be worth doing. Stage 2 is the audit proper: the auditor samples your records against the standard and your own procedures. If there are no major nonconformities, or they are closed, a certificate follows, valid for three years with surveillance audits between. Buying documents does not get you a certificate; the audit does. The documents are what make the audit about your business rather than about your paperwork.

The minimum document set

ISO 9001:2015 does not prescribe a quality manual or a list of procedures. It requires documented information where the standard says so and wherever you need it for the process to work. For a contractor of five to fifty people, our minimum is this:

1. A top-level description of the system, mapped clause by clause to the standard, with the scope of certification written down. Call it a quality manual if you like; the auditor uses it to find things.
2. The quality policy, signed by whoever runs the business, and quality objectives that can be measured: right-first-time at hold points, NCRs closed within a stated period, audits completed to programme.
3. Procedures for the processes that carry risk: document control, tender and contract review, supplier and subcontractor approval, materials control, planning and control of the works, inspection and test, nonconformance and corrective action, calibration, competence and training, internal audit, management review. If you design nothing, say so in the scope and leave design out.
4. The forms those procedures produce: the NCR, the corrective action request, the inspection and test record, the concession, the goods receipt check, the audit checklist, the management review agenda and minutes.
5. The registers that hold the evidence: documents and standards, ITPs, NCRs and corrective actions, approved suppliers, calibration, training, the audit programme, risks and opportunities.
6. A project quality plan for at least one live job, with its inspection and test plans and the signed check sheets behind them. This is the evidence the Stage 2 auditor spends most of the day on.
7. One completed internal audit against the programme, with findings recorded and closed, and one management review with minutes showing the inputs the standard lists and the decisions taken.

That is the whole list. Everything else in a full QMS is there because it makes the system easier to run at scale, not because the auditor will fail you without it.

A realistic timeline

Ninety days is achievable for a contractor with no full-time quality manager if someone owns it and the documents are not being written from a blank page. The roadmap we build into the QMS runs roughly like this:

• Weeks one and two: brand and tailor. Put your name on the documents, delete the procedures that do not apply, fix the scope, sign the policy, set the objectives. Do not add anything yet.
• Weeks three to eight: run it on a live job. Issue the project quality plan, get the ITPs approved, sign the check sheets, raise the first NCR and close it properly, log the calibration certificates, approve the subcontractors you already use with the evidence you already hold. This is where a system either becomes real or stays a folder.
• Weeks nine to twelve: audit and review. Do the internal audit, close the findings at root cause, hold the management review, and only then book the certification body. Booking earlier is the commonest mistake: a Stage 1 with no records behind it is a paid rehearsal.

Certification bodies need lead time for Stage 1 and Stage 2, so speak to two or three early, ask what their diary looks like, and compare the day rates and the scope wording rather than only the price. Tell them you intend to be ready in a stated month and ask them to hold it.

What goes wrong

Three things, in our experience of taking a contractor through it and of auditing the ones that struggled. First, the system was written by someone who does not work in the business, so nobody on site recognises it. Second, procedures promise records that do not exist: a procedure says "the site manager completes form F-12" and there is no F-12. Third, the audit and the review were done the week before Stage 1 with nothing behind them, and the auditor could tell. The fix for all three is the same: use the documents on a live job before anyone external looks at them.

What it costs, honestly

We will not quote you a figure for certification, because it depends on your headcount, your sites and the certification body's day rate, and anyone who quotes a number without knowing those is guessing. What we can say is that the document set above, done properly, is the smaller part of the cost. The larger part is the time of the person who runs it for ninety days. Budget for that person, or for a consultant to stand in for them, and the certificate follows.

One more thing. ISO 9001:2026 was published on 16 September 2026. If you are starting now, build to the edition your certification body will audit you against, which for the moment is 2015; this post explains why that is not a reason to wait.

Why it came back

An ITP has one job: to tell everyone, before the work starts, what will be inspected, against what, by whom, and what record will prove it. A reviewer working for the principal contractor or the client reads it with three questions in mind. Can I measure this? Can I find the clause it came from? Will I be there when it matters? An ITP that fails any of those questions is returned, usually with a comment such as "acceptance criteria to be developed" that tells you nothing about how to fix it. We set out the five reasons in the ITP guide; this post is the fix.

Minutes one to three: the acceptance criterion

Read every acceptance criterion and ask whether two competent people could disagree about whether it was met. "Installed to a satisfactory standard in accordance with the specification" fails: satisfactory to whom? Replace it with the value and the method. For a distribution board: "terminals torqued to the manufacturer's value with a calibrated tool and torque-marked; no exposed copper outside the terminal; conductors identified to Regulation 514". For a pour: "slump within the specified range at delivery, cubes taken at the frequency in the specification, cover checked with a spacer gauge before the pour is released". The criterion should read like the instruction to the person holding the clipboard, because it is.

Minutes four and five: the citation, at the current edition

Every line cites the clause it is checked against, and the edition matters. An electrical ITP citing BS 7671:2018+A2:2022 in September 2026 tells the reviewer that the plan was copied from an older job and nobody checked it. The current edition is BS 7671:2018+A4:2026, and the packs we build record that A3:2024 ceases to be current on 15 October 2026. Fire alarm ITPs citing BS 5839-1:2017 clause numbers are worse, because the 2025 edition renumbered the clauses; a line that says "commissioning to clause 39" now points at certification. Check every cited standard against a current index before you issue. It takes minutes and it is the single most visible sign of a plan that was actually thought about.

Minutes six and seven: the hold points

A hold point means work stops until the named party has attended and signed. A witness point means the party is invited, and if they do not turn up within the notice period the work proceeds and the contractor signs. Surveillance means they may turn up unannounced. Review means they look at the document afterwards. Most rejected ITPs mark everything as a hold point for every party, which is not a plan, it is a way of never getting the client's engineer to site. Choose the genuine holds: the pre-pour, the pre-close-up of a service void, the pre-energisation, the pressure test. Everything else is witness or surveillance, and the notice period, typically 24 or 48 hours, is written on the ITP so it cannot be argued later. Then agree the holds with the reviewer before you issue, so the approval is a formality.

Minute eight: the verifying record

Each line names the document that proves it happened: the check sheet number, the test certificate, the delivery ticket, the calibration record, the photograph log. "Inspection record" is not a name. "Activity check sheet E-014, board serial number recorded" is. If the line has no record, it has no evidence, and an auditor will find that a year later when a defect appears and the site team has moved on.

Minutes nine and ten: the sign-off columns

Three parties, three columns, before the plan is issued: the contractor, the principal contractor, and the client or their engineer, each with name, signature and date. Add a fourth for a third party where the contract has one, such as a building control inspector or a warranty surveyor. A plan that has to be redrawn to add a column after the client asks where their signature goes has lost the reviewer's confidence for the rest of the job. The check sheet that sits behind each line carries the same three columns, so a signed sheet and a signed ITP line say the same thing.

Then the frequency, and the resubmission

Every line states how often: every board, every pour, one in ten, one per batch. "As required" is not a frequency. When the pass is done, issue at the next revision number with a short covering note that says what changed against the reviewer's comments, line by line. Reviewers approve plans that answer their comments; they return plans that make them look for the changes.

What this looks like done

The free ITP for LV distribution boards is a worked example of the whole pass: 26 lines, every criterion measurable, every citation at the current edition, hold and witness points chosen rather than sprayed, a named record on every line and three sign-off columns. Compare it with the plan you have just had returned. If yours is already at that standard, the rejection was about something else and you should ask the reviewer directly; if it is not, you now know what to fix.

Clause 4.1: the issues, on one page

The standard asks the organisation to determine the external and internal issues that affect its ability to achieve what the system is for. On site that means writing down what makes health and safety harder or easier for this company in particular. Externally: the type of work and its hazards, deep excavations and buried services for a groundworker, work at height and hot works for a roofer; the clients it works for and what they demand at prequalification; how much of the workforce is agency or self-employed. Internally: the age of the workforce, the turnover of supervisors, the plant it owns and hires, the languages spoken on site, and how far the directors are from the work. The 2024 amendment added one line here, that the organisation determines whether climate change is a relevant issue; for a contractor it usually is, through heat, flooding and ground conditions. The output is a page, reviewed at management review, that an auditor reads to understand what the rest of the system is for. It does not need a framework. It needs to be true.

Clause 4.2: interested parties, as a table

Who, besides the workers, has an interest in the company's health and safety performance, and what do they need? For a construction SME the list is short and the table is the document: the workforce, including agency and self-employed operatives, who are workers under the standard whether or not they are employees; the clients and principal contractors; the Health and Safety Executive; the insurers; the neighbours and the public around each site; the supply chain; and the certification body. Against each, what they require and where in the system it is met. A principal contractor requires reviewed RAMS, inductions and competence cards: met in the RAMS procedure, the induction record and the competence matrix.

Clause 4.3: the scope, and the two hats

The scope statement says what the system covers, and the trap is to write one that covers only the office. It has to cover the work: the activities, the sites and the workers, wherever they are. It also has to say which hats the company wears. A contractor who is sometimes the principal contractor on a small job and sometimes a subcontractor on a large one has two operating contexts with different CDM 2015 duties, and the scope should say so. ISO 45001 permits no exclusions, so the scope is a description of the business rather than a list of things left out. Three or four sentences on the front of the manual.

Clause 4.4: the system is the joins

Clause 4.4 asks for a management system to be established, implemented, maintained and improved. In a small contractor that is not a new set of documents. It is the statement of how the pieces that already exist connect: the policy leads to the risk process, the risk process produces the RAMS, the RAMS are briefed and the briefing is recorded, the site inspections feed the corrective actions, the corrective actions and the incident investigations feed the management review. The finding that catches most first-time contractors is the missing join: a good RAMS with no process that says how RAMS are produced, or an investigated accident that changed nothing at company level. HSG65, third edition 2013, describes the same plan, do, check, act loop, and a contractor who can draw that loop on one page with its own document codes on it has met clause 4.4.

Clause 5.1: what the director does, not signs

Leadership in the standard is a list of things top management does: takes overall responsibility, sets the policy and objectives, integrates the system into the way the business is run, provides the resources, protects workers from reprisals when they report, and supports consultation. For a small contractor that is the director, and the auditor will ask them, not the safety adviser, how they do it. The evidence is behaviour with a record: site visits with the observations written down, management review minutes with the director's decisions in them, and the stop-work that was backed rather than overruled. A policy signed by someone who cannot describe the company's worst hazards is the finding an auditor writes first.

Clauses 5.2 and 5.3: the policy and the roles

The Health and Safety at Work etc. Act 1974 already requires, at section 2(3), a written policy with the organisation and arrangements for carrying it out. That document can be the ISO 45001 policy as long as it carries the commitments clause 5.2 requires, including eliminating hazards and reducing risks, and consulting and involving workers. Clause 5.3 asks for roles, responsibilities and authorities to be assigned and communicated. In construction the roles are the CDM ones as much as the company ones: who is the contractor under regulation 15 on each project, who is the principal contractor under regulation 13 when the company holds that appointment, and who has the authority to stop the work. The roles are written against names on each project's setup record.

Clause 5.4: consultation is not a toolbox talk

This is the clause that separates ISO 45001 from every system a contractor has had before. Workers must be consulted on a listed set of topics, including the policy, the roles, how legal requirements are met and the objectives; and they must participate in a further set, including hazard identification, the choice of controls, incident investigation and the audit programme. A toolbox talk is communication, one way. Consultation is two way and it changes something. The record is what an auditor opens: site meeting minutes with a standing item, the near-miss cards and what was done about them, the RAMS review where an operative's comment altered the method. CDM 2015 already requires the principal contractor to consult and engage with workers under regulation 14; the standard adds only that it be planned, recorded and free of reprisal.

The legal register, and the link to CDM 2015

Clause 6.1.3 asks for the legal and other requirements to be determined, kept up to date and taken into account. For a UK contractor that is a register: each instrument, what it requires of this company, how the company complies, the evidence, and the date it was last checked. The 1974 Act; the Management of Health and Safety at Work Regulations 1999, with the risk assessment duty at regulation 3; CDM 2015 under each hat; the work at height, lifting, COSHH, noise, vibration and RIDDOR instruments as the work requires; and the client requirements the company has agreed to. Most small contractors hold this in the consultant's head. The standard wants it written down, reviewed and, at clause 9, evaluated: not "does this apply to us" but "are we complying, and how do we know".

CDM 2015 is where the register meets the site. The general duties under regulation 8, to have the skills, knowledge and experience for the work, are the competence process. The construction phase plan under regulation 12 is the operational planning the standard asks for at clause 8. Regulation 13 is coordination with subcontractors, regulation 14 is clause 5.4, and regulation 15, the contractor's duties on every job, is the day-to-day system. A contractor that writes its ISO 45001 procedures as descriptions of how it discharges those regulations ends up with one system that a client's auditor and a certification auditor both recognise.

Our ISO 45001 Construction OHSMS is written on that basis: manual, policy, procedures, pre-populated legal register and consultation records, pointing by code at the RAMS, permits and inspection registers in the Site Health & Safety Pack rather than duplicating them. Certification is granted only by an accredited certification body after audit; the documents shorten the road, they do not remove it.

Where the inspection comes from

The New Homes Quality Code is administered by the New Homes Quality Board and applies to developers registered with it. Version 2 was published in March 2026 and applies to homes reserved from 2 March 2026; the first version, from October 2023, governs earlier reservations, so a site with plots reserved either side of that date is running both. Part 2 of the Code covers the period up to completion, and the customer's right to inspect sits there, under clause 2.8: after the developer has given notice that the home is ready to complete, and before legal completion, the customer may inspect the home themselves or appoint a suitably qualified inspector to do it. The developer cannot refuse, cannot restrict the visit to a token walk-round, and has to give a notice period long enough for the inspection to happen, usually at least fourteen calendar days. The inspection is carried out against the NHQB's own pre-completion inspection checklist, not the inspector's, and that is the detail that decides how the day goes.

What the checklist covers

The NHQB checklist is public, and a developer's own quality team should know it better than the inspector does. It is organised the way a plot is walked, room by room and element by element, with guidance on what is and is not a defect. Broadly, the inspector is looking at four things.

• Finishes. Plaster and paint, ceilings, skirtings and architraves, tiling, flooring, kitchen units and worktops, sanitaryware, glazing and ironmongery. The guidance sets viewing distances and conditions, for instance internal surfaces viewed in daylight from two metres and external finishes from ten, with small marks below a stated size accepted. An item passed at arm's length under a torch may fail at two metres in daylight, and vice versa; the criteria are the ones that count.
• Operation. Doors and windows opening, closing, locking and sealing; taps, wastes, WCs and showers running and draining; the heating and hot water firing; extract fans running; sockets and switches live; smoke and heat alarms sounding on test; appliances working. The inspector operates things, so the plot has to be live, filled, vented and commissioned before the notice to complete is served, not after.
• External and plot. Brickwork and pointing, render, roof coverings and flashings visible from the ground, rainwater goods, driveways, paths, fencing, gates, garden levels and gullies, meter boxes and external taps. The external works are where incomplete items are most often found, because they depend on the adjacent plot.
• Safety and compliance items. Glazing markings where required, balustrade heights, the consumer unit labelled, the gas appliances labelled and fire door closers working where the home has them. The checklist directs attention to the items a customer would not know to look at.

The output is a list of items the inspector considers defects against the checklist guidance. The developer reviews each one, accepts it as a snag or records why it is not a defect, and the agreed list goes on the plot snagging register with its source recorded as the customer's inspection.

Snag or defect

The two words are used loosely on site and precisely by an ombudsman. A snag is an item, usually cosmetic or a matter of adjustment, that can be put right quickly without affecting whether the home is complete: a paint run, a door needing easing, a mastic bead to redo. A defect is a failure to meet the building regulations, the warranty provider's technical standard or the specification the home was sold against: a bathroom floor that holds water, a missing cavity tray. The Code's glossary and the checklist guidance govern how an item is classified, and the classification matters because the consequences differ. A snag found before completion is put right, where possible, before the keys are handed over, or within thirty days; a defect is a breach of the warranty standard, NHBC Standards 2026 for homes whose foundations began on or after 1 January 2026, that the developer has to remedy under the warranty and the Code's after-sales provisions. A developer who argues that a defect is a snag will find the ombudsman reading the checklist guidance more carefully than it did.

The inspection that has to come first

The Code does not, in terms, require the developer to inspect its own plot. Arithmetic does. Every item the customer's inspector finds is an item the developer's inspection missed, and each becomes a customer communication, a register line and a thirty-day clock. So the developer's plot completion inspection has to be at least as thorough as the customer's, has to use the same or tighter criteria, and has to happen before the notice to complete is served. The checklist we use runs to over two hundred lines for a three-bedroom house, structured as the plot is walked, room by room, then loft, garage, envelope, plot, whole-house services and certificates. Each line carries the item, the acceptance standard, a pass, snag or not-applicable result and the snag reference. The length is the point: the inspector will look at everything, so the developer must already have looked at everything.

The register the checklist feeds needs three things the usual site snag list lacks: a source for each item, so that customer-found items can be counted separately; an owner and a target date; and a flag for whether the customer can see the item. The notice to complete is not served until the register shows the plot clear or the remaining items agreed with the customer in writing, with a date, as clause 2.10 allows where something genuinely cannot be finished.

The records that show the home was ready

The Code asks the developer to prove that the home was inspected and finished before the customer was asked to complete, that the customer was given the information and the demonstration, and that anything reported afterwards was handled in time. Each is a record, per plot.

• The developer's plot completion checklist, signed and dated before the notice to complete, with every line answered.
• The plot snagging register, showing the items found, their source, their close-out date and the sign-off, with the customer's inspection items identifiable.
• The pre-completion inspection record itself: who inspected, when, the list received, the developer's response item by item and the agreed outcome.
• The plot certificate schedule, completed plot by plot: the building control completion certificate under regulation 17 of the Building Regulations 2010; the Electrical Installation Certificate to BS 7671:2018+A4:2026 and the Part P notification; the gas notification and the heating commissioning certificates; the energy performance certificate and the air tightness result where one was required; the ventilation commissioning record; the water regulations notification; the warranty documentation; and the manufacturer warranties, registered where registration is a condition. A missing certificate is a completion that cannot happen on the date.
• The home demonstration record under clause 2.11: the systems shown, the questions asked, the follow-ups, and the customer's signature.
• The handover certificate and key release, with the schedule of incomplete work, short and signed by both parties.

After the keys, Part 3 of the Code runs the clocks: thirty days for snags, a defined complaint process with dates, and referral to the New Homes Ombudsman Service where the developer has not resolved matters in time. Those dates are only manageable from a log that calculates them.

Our Housing & Fit-Out Completion Pack carries the plot completion checklist, the pre-completion inspection record, the certificate schedule, the snagging register and the customer care log written to Version 2 of the Code; the Activity Check Sheet Library holds the trade check sheets that sit behind the plot inspection. The Code and the NHQB checklist belong to the New Homes Quality Board, and their text governs where this summary is briefer.

What contemporaneous means, and why it matters

A contemporaneous record is one made at the time by someone who was there, for the purpose of recording what happened rather than for the purpose of the dispute. That definition is the whole value of the diary. A witness statement written after the claim has been notified is memory shaped by the argument; a programme analysis is only as good as the facts it is built on; correspondence is the parties talking to each other with an eye on the file. The diary, if it was written on the day and never altered, is none of those things. It is what the person in charge of the site believed had happened before anyone knew it would matter.

Adjudication makes this sharper than litigation does. The adjudicator has weeks, not months, to reach a decision, and will not hear from everyone who was on site. The party whose records let the adjudicator reconstruct the day in question from one folder starts ahead. The party whose case rests on what the site manager now recalls does not.

The entry, heading by heading

One page per day, completed at the end of the shift by the person in charge of the site, signed, never altered. The headings are not optional, and each one is there because a dispute will ask for it.

• Header. Project, date and day, project week and day number, site hours, and who completed the page. A diary that cannot be tied to a programme week needs a translation exercise before it can be used.
• Weather and ground conditions. Morning and afternoon separately: conditions, temperature, wind, ground state, and, above all, the hours lost and which operatives were affected. "Wet" is a weather note. "Rain 09:40 to 11:10, external drainage D4 to D7 stopped, eleven operatives, 1.5 hours" is a delay record, and only the second kind supports an extension of time.
• Labour on site. By company and trade, with numbers, the split where a gang was divided, the location and the activity, and a total. This is the entry that proves, or disproves, resource levels a year later, and it is checked against timesheets and subcontractor returns. Round numbers every day are a sign the page was filled in from habit.
• Plant. Each item with its reference, hire reference, hours worked, hours standing and the reason for standing. Standing plant with a reason is a disruption record in its own right.
• Deliveries. Time, supplier, material, quantity, the goods received note reference and the condition on arrival. A rejected delivery with a photograph reference and a nonconformance number is worth more than the exchange of emails that follows it.
• Visitors. Name, company, role, purpose, outcome, time in and out. When the client later says nobody from their side agreed to the change, the diary entry recording the visit and the conversation is the reply.
• Instructions and information received. From whom, the reference, the subject and the action taken. A verbal instruction goes in the diary on the day and is confirmed in writing under the contract's procedure; the diary is the evidence of when it was given, the confirmation is the evidence of what it said.
• Delays, disruption and events affecting progress. Cause, area, operatives affected, duration, what was done about it, who was told, and the cross-reference to the early warning, the notice or the nonconformance. This is the section a claim or a defence stands on, and it is the one most often left blank on the days that turn out to matter.
• Inspections, hold points and nonconformities. The ITP line, the level, who attended, the result and the record reference. An entry that says a hold point was witnessed and passed, with the check sheet number, ends most arguments about whether an inspection took place.
• Health and safety observations, photographs taken, and the plan for tomorrow. Each cross-referenced to the register it belongs in.

Consistency with everything else

A diary does not stand alone, and an adjudicator will not read it alone. The labour figures are compared with the timesheets and the subcontractor's own daily returns. The plant hours are compared with the hire invoices. The weather is compared with the nearest station's published data. The instruction recorded on Tuesday is compared with the confirmation of verbal instruction dated Thursday. The delay entry is compared with the early warning register and the programme update issued that month. Where they agree, each record makes the others stronger. Where they disagree, the diary is the record that loses credibility first, because it was the one written by the party relying on it.

The practical answer is to make the diary the index and the registers the detail. The diary entry says the pour to slab B2 was held for a rebar cover failure and cites the nonconformance number; the nonconformance report carries the detail, the photograph and the close-out; the photograph log gives the photograph a number the diary can quote. A site whose registers cross-reference each other can answer a question about any day on the job in minutes. A site whose registers were written separately will spend a fortnight reconciling them and the result will still be open to challenge.

How a diary is read in a dispute

Some general principles, which we set out without reference to any particular decision, apply across adjudication, arbitration and the courts. A record made at the time is given more weight than a recollection. A record made in the ordinary course of business is given more weight than one made for the dispute. A record that is specific, with times, locations, numbers and names, is given more weight than a general one. A record that the other party had the opportunity to see and did not challenge at the time is stronger than one produced for the first time in the referral. And a record that has been altered, or that was plainly written up in one sitting for a week, is given little weight at all, and may take the rest of the contractor's evidence down with it.

Two consequences follow. The first is that opinion has no place on the page. "Client's team unhelpful" proves nothing; "client's representative attended 10:00 to 12:00, verbal instruction to add two double sockets in room G14, confirmed by CVI-011 at 15:00" proves something. The second is that the quiet days matter as much as the eventful ones. "No delays, full resource, dry" on the Monday is the entry that makes the delay on the Wednesday credible. A diary with entries only on bad days looks like what it is.

Paper, Word or Excel

Any of the three works if the site will actually complete it before leaving. A bound book is hard to alter and easy to lose. A Word page per day suits a site that keeps its records in a folder and signs them. A workbook with one tab per week and a column per day suits a site that lives at a laptop, and it makes the labour and hours-lost totals add up. Whatever the medium: the same headings, the same day, a signature, and a weekly review by the person the site manager reports to, which is the step that catches the missing days and moves a recorded delay to the person who has to give the contractual notice under NEC4 or JCT before the time for doing so runs out.

Our Site Management, Planning & Records Pack carries the diary in both forms with a fully completed worked day, alongside the labour, plant, delivery and weather records and the photograph log it cross-references; the Construction Records Library holds the inspection records the diary points to. Neither will make a site keep its diary; they only make the page worth keeping when it does.

Five stages, not one

The words move around between specifications, and the first job of the plan is to define them for the project. We use five: static completion, pre-commissioning, commissioning, witnessing and seasonal or proving commissioning. CIBSE Commissioning Code M (2022) is the reference for how the whole process is managed, and BSRIA BG 8/2009 gives the model plan; between them they settle the structure of the document. What they cannot settle is the sequence on a particular job, because that is fixed by dependency. No fan runs before the ductwork leakage test and the fire damper drop tests; no pump runs before the pressure test and the water quality certificate; no board is energised before initial verification. The plan sets the stages out as a table of activities, each with what it depends on, the ITP or form that releases it, the planned date and the witness required. A programme bar chart with a paragraph underneath does not do that, and a client's consultant will say so at the first witness visit.

Stage 1: static completion

Static completion means the installation is physically finished and its static tests have been passed. For pipework that is the pressure test to the value and duration in the specification; for ductwork the leakage test to the class specified, with the record to BS EN 12599:2012 or the specification's own method; for the electrical installation the dead tests of initial verification under BS 7671:2018+A4:2026 with the schedule of test results filled in. The entry condition for everything that follows is that the installation ITPs for the system are signed, including the hold points that were witnessed when the work was still visible: the containment before the ceiling closed, the insulation before the cladding went on, the pipework before the screed. A commissioning plan that starts at the pumps has skipped the stage that decides whether the pumps can run.

Stage 2: pre-commissioning

Pre-commissioning is the set of checks that prove a system is clean, safe and ready to start. For heating and chilled water it is the pre-commission cleaning to BSRIA BG 29/2021, with the flushing velocities, the water samples and the laboratory results on file before any circulating pump runs for balancing. For air systems it is the checklist route in BSRIA BG 49/2024: plant secured, filters fitted, dampers free and marked, drives aligned, rotation checked at a bump start. For the electrical installation it is the Electrical Installation Certificate and its schedules for every board that feeds the system; nothing is energised on a verbal assurance. The plan also lists the instruments here, with serial numbers, calibration due dates and the register reference, because a balancing result from an instrument that was out of calibration is a result the client is entitled to reject. Permits, isolations, commissioning method statements and task briefings sit in this stage too, and a reviewer will look for them.

Stage 3: commissioning

Commissioning proper is setting each system to work and adjusting it to the design values. The acceptance basis is well established and the plan cites it at the current edition: air distribution to CIBSE Commissioning Code A (2024) and BSRIA BG 49/2024; water distribution to CIBSE Commissioning Code W (2025), which replaced the 2010 edition, with BSRIA BG 2/2010 alongside it; heating systems to BS EN 14336:2025; controls to CIBSE Commissioning Code C (2001); fire detection and alarm to BS 5839-1:2025; emergency lighting to BS 5266-1:2025. The tolerances themselves are project values. A specification that asks for terminal flow rates within a stated percentage of design has set the acceptance criterion, and the plan says so rather than quoting a guide that may say something different. The record form for each test carries the design value, the tolerance and the measured value on the same line, so that pass or fail is decided on the sheet and not argued afterwards.

Stage 4: witnessing, and who witnesses what

Witnessing is where most disputes start, because the plan did not say who was expected, at what notice, and what happened if they did not come. The four levels are the same as on any ITP. A hold point stops work until the named party has attended and signed. A witness point invites the named party and proceeds after the notice period, usually 24 or 48 hours under the contract, if they do not attend, with the non-attendance recorded. Surveillance is unannounced. Review is the document only. The plan states the level for each test, and the pattern on most commercial projects looks like this.

The contract governs, and the plan should say where it departs from that pattern. What it must not do is mark every line as a hold point for every party. That is not a plan; it is a way of never getting the consultant to site. The witness notice and the witness test record are one form in our packs so that the notice, the attendance and the result sit on the same page.

Stage 5: seasonal and proving commissioning

A heating system commissioned in July has not been proved at design conditions, and a chiller commissioned in January has not either. The plan says which systems are deferred to seasonal commissioning, the month it will happen, who attends and what record is produced, and it says so before practical completion so that the retention and the defects period take account of it. Proving runs for the BMS, the sequence of operation under real load, and the repeat of any test that the client's consultant witnessed only as a sample belong here too. If the plan is silent, the client will assume the systems were fully proved at handover and the first cold week will be a defect notice.

The records that close a system

A system is closed when the following exist, are signed by the person who did the work, and are indexed against the ITP line: the installation ITPs and check sheets; the static test certificates; the pre-commissioning checklists and the water quality results; the Electrical Installation Certificate and schedules; the balancing records with design, tolerance and measured values; the controls point-to-point and loop tuning records; the fire alarm commissioning certificate and cause-and-effect record; the emergency lighting test records; the witness notices and the witnessed results; the nonconformity reports and their close-out; and the training record and the O&M content to BSRIA BG 79/2020. The plan lists every one of those record types in a table with the form, who produces it, who reviews it and where it is filed. If a record is not on that table, it will not be produced, and the gap will be found at handover.

Our Commissioning & Test Plan Pack is built on this structure: a plan template to Code M and BG 8 with a completed worked example, eight commissioning ITPs and eleven test records with the limits printed on the sheet. The Commissioning Check Sheet Library carries the same lines onto printable sheets for the engineers doing the tests. The free ITP for LV distribution boards shows the same pattern before you buy anything.

Three sources of the requirement

The specification names a standard for every material and usually the evidence required: a certificate of conformity, a mill certificate, third-party certification, a sample or a test. That is the requirement the certificate has to meet, and a certificate citing a different standard or grade does not meet it. The law sits behind it: regulation 7 of the Building Regulations 2010 requires building work to be carried out with adequate and proper materials, and the Construction Products Regulations 2013, SI 2013/1387, carry the construction products regime into UK law, so that a product covered by a designated standard has a Declaration of Performance and carries the mark. On the mark itself, the government confirmed in a ministerial statement on 2 September 2024 that CE marking continues to be recognised for construction products in Great Britain with no end date, alongside the UKCA route; in Northern Ireland products are CE marked, or CE plus UK(NI) marked where a UK body did the assessment. The quality system is the third source. ISO 9001:2015 requires control of externally provided products, identification and traceability where traceability is a requirement, and evidence of conformity before release. The tracker is how a contractor shows all three.

Which document proves what

• Certificate of conformity. The supplier's or manufacturer's statement that what was supplied conforms to a named specification, standard or order. It proves the supplier says so. Its value depends on who signed it, what it cites, and whether the batch on the certificate is the batch that arrived.
• Declaration of Performance. The manufacturer's legal declaration of the product's performance against the essential characteristics in its designated standard, with the assessment system, the body number where one is involved, and the declared values. It proves the product is what the manufacturer says it is. It does not prove the product is right for the specification; that check is specified characteristic against declared characteristic, line by line.
• Inspection documents for metals. BS EN 10204:2004 defines the types. A type 3.1 certificate reports the results of tests on the product supplied, validated by the manufacturer's inspection department independent of production. A type 2.2 reports non-specific results; a type 2.1 is a statement of compliance without results. Order the type the specification calls for and check the heat or cast number against the material.
• Third-party product certification. Reinforcement from a CARES-approved supplier carries the certificate for the producer and the fabricator, with a tag on every bundle, against BS 4449:2005+A3:2016. Kitemark, BBA and similar certificates prove a scheme has assessed the product; each has a scope and an expiry, and both need checking.
• Concrete. The delivery ticket records the mix, the batch, the time and any water added; conformity to BS 8500-1:2023 and BS 8500-2:2023 is evidenced by the supplier's third-party certification and the site's own identity testing and cube register.
• Chain of custody and factory acceptance tests. FSC or PEFC claims on the invoice and delivery note for timber; the FAT record for switchboards, air handling units, precast and fabricated steel.

What a certificate must match

A certificate on its own is a piece of paper. It becomes evidence when it matches three other things. The specification: the standard, grade, class or classification the clause asks for, compared with what the certificate declares. The delivery: the batch, heat, cast, drum or roll number on the certificate against the number on the delivery note and on the material itself, recorded at the delivery inspection while the label is still legible. The location used: the pour, the riser, the elevation, the fire compartment line, recorded in a traceability log as the material goes in. Break any of the three links and the certificate proves something about a product, but not about your building. The mistake we see most is a folder of certificates that were collected but never compared: the Declaration of Performance is valid, the product does not meet the specified classification, and nobody noticed because the certificate arrived and was filed.

The tracker columns

One row per material or product, set up from the specification and the approval schedule before the first delivery, not from the pile of paper after the last. Material, specification clause and standard. Supplier and approval status, with the submittal reference. Certification required, which may be more than one of the types above. Certification received: date, reference, and the batch or heat numbers it covers. The DoP and marking check: designated standard, assessment system, marking route, body number, and the specified-against-declared result of accept, query or reject. Validity, where a third-party certificate expires. Chase: the date requested, the deadline given and the consequence stated. Status, with colour, so the outstanding rows can be seen from across the cabin. And links: the delivery inspection record, the traceability log entries, the nonconformity where one was raised, and the handover file location. Our certificate of conformity guide takes the columns in turn. The chase column does the most work: a written request with a five-working-day deadline and a stated hold on installation is the difference between a certificate that turns up and one that does not.

What happens at practical completion when they are missing

The certificate and warranty register is a fixed item on the handover checklist, and the client's completion inspection goes through it line by line, because the client's own advisers will ask for it before they accept the building. When a certificate is missing there are, in practice, four outcomes, in descending order of comfort.

1. The supplier can still produce it, because the delivery note carried the batch number and the supplier's records are good. This takes days if the tracker recorded the batch and weeks if it did not.
2. The supplier can produce a certificate for the product line but cannot tie it to your batch. The client may accept it with a note, or may not; for fire-rated products and structural materials they usually will not.
3. The material can be tested or inspected in place to demonstrate the property the specification cares about. That costs money, delays completion and does not always answer the question: an insulation resistance test proves the cable is sound, not that it is the cable that was specified.
4. The material is removed and replaced, or accepted against a deduction and an indemnity. This is where the missing certificate for a cavity barrier or a structural fixing ends up.

Every one of those outcomes is a completion certificate delayed, a retention held, or a defect that the client's lawyers will remember, and every one of them was a five-minute check at the delivery gate that did not happen. The handover checklist guide shows where the register sits in the file; a tracker kept from the first delivery produces it by filtering, and a project without one produces it by searching.

Start the tracker on day one

The materials control plan should name the tracker, the delivery inspection checklist for each material type and the traceability log, and should say who updates them and when. The Materials & Procurement Control Pack has that set: the control plan with a worked example, the approval schedule, the certificate of conformity tracker with the DoP and marking check, delivery inspection checklists for ten material types, the shelf-life register and the traceability log; the Construction Records Library carries the pour, cable and fixing records the log points at.

Updated 17 September 2026: ISO 9001:2026 was published in September 2026. At the date of this update the British Standard listed as current remains BS EN ISO 9001:2015+A1:2024, certificates to the 2015 edition are unaffected, and the requirements on externally provided products, traceability and release referred to above are from the 2015 text.

Why the questionnaire is your evidence

CDM 2015 regulation 8 requires anyone appointing a contractor to take reasonable steps to satisfy themselves that the appointee has the skills, knowledge, experience and organisational capability to do the work safely, and regulation 15 requires a contractor not to appoint anyone without them. The PQQ is the record that the reasonable steps were taken, and a questionnaire that was never scored is not evidence that anything was assessed. ISO 9001:2015 asks the same question from the quality side: externally provided processes and products are controlled, and providers are evaluated, selected and monitored against criteria the organisation has written down. Upstream, the question set clients use on main contractors is the Common Assessment Standard, owned by Build UK and delivered through seven recognised assessment bodies; PAS 91, the BSI question set that many older PQQ templates were built on, is no longer listed as a current product on BSI's site. A subcontractor holding a current Common Assessment Standard certificate has already answered the generic areas, and the PQQ can accept the certificate for those and concentrate on what a certificate cannot tell you, which is most of the list below.

The twelve questions

1. Which trades do you carry out with your own directly employed labour, and which do you sublet? The single most predictive question on the form. A subcontractor who sublets the package is a layer of margin between you and the people doing the work, and their PQQ has to reach the next tier or it has assessed nobody.
2. Employers' liability and public liability: insurer, policy number, limit of indemnity, expiry date, and the certificate. Employers' liability is compulsory for almost every employer under the Employers' Liability (Compulsory Insurance) Act 1969. It is the easiest thing on the form to check and the one most often found lapsed on site. Add professional indemnity where the package carries design.
3. Who provides your competent health and safety advice, and how often are they on your sites? The Management of Health and Safety at Work Regulations 1999 regulation 7 requires it. A name and a retainer letter is one answer; a consultant who has never visited a site is another, and the difference shows in the RAMS.
4. Enforcement action and RIDDOR-reportable incidents in the last three years, and what you changed afterwards. The incidents matter less than the last clause. A subcontractor who can describe what changed has a system; one who reports nil for three years across a large workforce may have a reporting problem rather than a safety record.
5. Three comparable projects in the last five years, with a client contact we may approach. Then approach them. Ask the referee two things: would you use them again, and did they finish with their own people. The second answer is usually the more revealing.
6. The named supervisors and operatives for this package, with their cards. CSCS, CPCS or NPORS for plant, ECS, CISRS, IPAF, PASMA, Gas Safe, SSSTS or SMSTS, first aid, and the package-specific training. Ask for the register with expiry dates, not the assurance that everyone is carded.
7. Send us a completed inspection record from a recent job. Not the quality policy and not the ISO certificate. A subcontractor who can produce a filled-in check sheet from last month has a working quality system, whatever it is called. One who sends the certificate has a certificate.
8. Describe how you dealt with your last nonconformity. Everyone has them. The answer tells you whether they are recorded and closed or argued about and hidden, and it is the best predictor of how the snagging list will go.
9. Who writes your RAMS, and send us the last one you wrote for similar work. A generic method statement with the client's name changed is the most common finding at RAMS review, and it is cheaper to find at PQQ than at pre-start.
10. Turnover for the last three years and the value of the largest contract undertaken. Set beside the package value. A package worth half the company's annual turnover is a risk to both parties, and a subcontractor growing fast is a subcontractor whose supervision is being stretched.
11. How many people will you have on this package, in which weeks, and what else are they committed to? Resource is the question the PQQ template never asks and the programme always does.
12. How is your labour engaged, and how do you check right to work? Directly employed, self-employed under the Construction Industry Scheme, or agency; and the process for checking right to work for every person. The answers decide which tax and employment regimes apply and who carries the risk if they are applied wrongly, and the civil penalty for employing an illegal worker can reach £60,000 per worker.

Scoring: gates first, then weights

A PQQ that produces one overall mark hides the fact that some questions have only one acceptable answer. Separate them. The gates are pass or fail and any failure ends the assessment: employers' liability and public liability current and at the required limit; no undisclosed insolvency; competent health and safety advice in place; no unresolved enforcement action relevant to the package; a right-to-work process; and any statutory registration the package needs, such as Gas Safe or a waste carrier licence. Everything else is a weighted criterion, scored 0 to 5 against a scale written down before the scoring starts: what a 5 looks like, what a 0 looks like. Weight the criteria for the package, so that competence of the named team and resource carry more on a labour-heavy trade and quality records carry more on a finish-critical one. The weighted percentage ranks the tenderers; a threshold turns the rank into approve, approve with conditions, or decline. Score competing subcontractors side by side on the same sheet, record who scored and when, and keep it. That sheet is what you produce when the declined subcontractor asks why, and when the client's auditor asks how the supply chain was selected.

What approval does not do

A PQQ approved in March is not evidence of anything in September. Three sets of checks follow it. Every insurance, certificate and registration on the form has a date, and the register that holds them should calculate the days remaining and warn at 60 days. Onboarding verifies the named people card by card, reviews the RAMS against a written checklist, minutes the pre-start meeting with the hold points and interfaces agreed, and confirms right to work for each person given site access. Monitoring records labour against plan, progress, quality and safety weekly, with an improvement notice process that escalates in stages and a scorecard that feeds an annual panel review. The PQQ guide sets out the full question set by area and the scoring method in more detail.

The test of a good PQQ

Take the last subcontractor who went badly and read their PQQ. The warning is usually there: the sublet trade, the referee who was never called, the resource question that was not asked. The twelve questions above are the ones that would have caught it. The Subcontractor Management Pack carries the PQQ and scoring sheet, the expiry tracker, the onboarding and RAMS review checklists and the monitoring records built to this method, and the Bid & Tender Pack is the same exercise seen from the other side, with model answers under each Common Assessment Standard area for when a client sends the questionnaire to you.

Updated 17 September 2026: ISO 9001:2026 was published in September 2026. At the date of this update the British Standard listed as current remains BS EN ISO 9001:2015+A1:2024, certificates to the 2015 edition are unaffected, and the requirement to evaluate, select and monitor external providers referred to above is from the 2015 text.

What the record is evidence of

No regulation mentions toolbox talks. The duties they discharge are in the Management of Health and Safety at Work Regulations 1999, which require an employer to give employees comprehensible and relevant information on the risks to their health and safety and the preventive measures, and to provide adequate training, repeated periodically where appropriate; and in CDM 2015, which requires every contractor to give each worker under its control the supervision, instructions and information needed to carry out the work without risk, and requires the principal contractor to ensure that workers receive a suitable site induction and any further information and training they need. A toolbox talk is the practical mechanism for "further information" and "repeated periodically". The record is the evidence that the duty was discharged on a given day to named people. It also feeds the competence and awareness records that a management system certified to ISO 9001:2015 or ISO 45001 (adopted in the UK as BS EN ISO 45001:2023) has to keep. The record has to show what was said, why, to whom, and that it landed.

The six things the record must show

1. The topic and the content. Not the title: the content. The key points that were briefed, in the words they were briefed in, filed with the attendance sheet. An attendance sheet headed "Working at height" with nothing behind it cannot tell an inspector whether the crew heard the hierarchy of control or two minutes about ladders.
2. The law and guidance the talk is based on. The regulation and the HSE guidance the content came from, at the edition current on the day. The crew do not need the citation; the deliverer and the auditor do. Talks are written once and reused for years, and a talk that cites withdrawn guidance is a talk that nobody has read since it was written.
3. The site-specific points. The two or three things that apply to this site this week: the area, the live permit, the near miss on Tuesday, the delivery that changes the traffic route. This is what separates relevant information from generic information, and relevance is what the regulations ask for.
4. The questions asked, and the answers. Two or three open questions put to the crew, with a note of how they responded. Signatures prove attendance. Questions are the only evidence of understanding. "What is the heaviest thing you will handle today, and how are you moving it?" is a question. "Any questions?" is not.
5. Attendance, by name and company. Every attendee's name, employer and signature; the deliverer's name and signature; date, location and duration. The employer column matters more than it looks. CDM 2015 puts the duty on each contractor for the workers under its control and on the principal contractor for the site, and a file that shows talks delivered to direct employees while the subcontract crews got nothing is evidence of a gap, not of compliance.
6. The declaration. A sentence above the signatures that says the signatory attended, understood, and raised anything they disagreed with before signing. That turns a signature from a formality into a statement, and it is the sentence an inspector reads first.

The link to the RAMS and the task briefing

A toolbox talk is a briefing aid, and it sits below the documents that govern the work. The risk assessment and method statement set the controls for the task; the permits and the site rules apply on top; the task briefing is where the crew doing a specific task on a specific day are taken through the method, the hold points and their own competence for it. The toolbox talk is the periodic, hazard-based reminder that keeps the general controls fresh. The record has to show that hierarchy in two ways. First, the talk itself should say that the site risk assessment, method statement and permits take precedence where anything differs. Second, the training register should let an auditor trace from a RAMS to the crew who were briefed on it and to the talks they have had on the hazards it identifies. When a roofing RAMS names work at height, fragile surfaces and manual handling as its principal hazards, the register should show that the roofing crew had those three talks, with dates, before or during the work. The RAMS guide covers the briefing record on the method statement side; the two records should agree on who was there.

What an inspector or auditor looks for

The questions are much the same whoever is asking.

• Which talk did the injured person, or the crew on the task being audited, last have on the hazard in question, and when? A register listing talk reference, date, deliverer and attendee count answers that from one sheet. A folder of loose sheets does not.
• What did the talk say? The content is filed, and it matches the guidance it cites.
• Was it relevant to that site and that phase? Excavation talks during fit-out and electrical safety talks during groundworks tell the reader that the programme of talks was a calendar, not a plan. The site-specific section shows that someone thought about that week.
• Is there evidence anyone understood it? The questions section, with the responses noted.
• Were the subcontractors covered? The employer column, checked against the site's daily labour return.
• Was the record made on the day? A week of talks signed in the same pen on Friday afternoon is reconstructed evidence, and an inspector will treat it as such. Sign on the day, file the same day.

A programme, not a pile

The talks a site needs across a year are predictable. A library of twenty, delivered one a week with the site-specific section rewritten each time, covers the core hazards and then repeats. Front-load the talks that match the phase: excavations, underground services and temporary works during groundworks; work at height, lifting and slinging during frame; electrical safety, dust, COSHH and abrasive wheels during services and fit-out; fire prevention and hot works throughout. Manual handling, slips and trips, PPE, and fatigue and mental health apply at every stage. Add the talk that almost never appears in a downloaded library, on quality: why the site inspects, what a hold point means, and how to raise a nonconformity without getting anyone into trouble. Deliver it in the first week of every new trade on site.

The ten-minute check on your own file

Take the last five talks from the file and, for each, ask: is the content filed with the sheet; does the law and guidance box cite the current edition; is the site-specific section written in; are the questions and the responses recorded; do the attendees' employers appear; and is there a register entry. Five that pass all six are a file that will stand up. Five that fail the same one or two are a template problem, which is the cheapest kind to fix. The Toolbox Talk Library and its second volume are written to that shape, with the law and guidance box, the site-specific section, the questions and the attendance declaration on every talk, and the Task Briefing Sheets are the document that ties the method statement and the ITP hold points to the crew on the day.

Updated 17 September 2026: ISO 9001:2026 was published in September 2026. At the date of this update the British Standard listed as current remains BS EN ISO 9001:2015+A1:2024 and certificates to the 2015 edition are unaffected. We have not yet compared the 2026 text clause by clause and will say what changed for competence records when we have.

Where the duty sits

The legal duty is in CDM 2015. Regulation 19 requires all practicable steps to be taken to prevent danger from any structure in an unstable or temporary state of weakness, and requires any buttress, temporary support or temporary structure to be designed, installed and maintained so that it withstands any foreseeable loads and is used only for the purpose it was designed for. Regulation 22 covers excavations: supports or battering to prevent collapse, and inspection by a competent person at the start of every shift and after any event likely to affect strength or stability. The coordinator, the register and the permits come from BS 5975-1:2024, Temporary works. Management procedures for the control of temporary works. Code of practice, which with BS 5975-2:2024 on falsework replaced the single-part BS 5975:2019 in December 2024. Part 1 is the procedural code HSE points to and the one an auditor or inspector measures the site against.

The appointments that make the register mean something

BS 5975-1:2024 describes three roles. The designated individual is the person at organisation level who owns the temporary works procedure and appoints the coordinators. The temporary works coordinator is appointed in writing for the project, with the authority to stop work, and is responsible for the register, the design briefs, the checks and the permits. The temporary works supervisor is the person on site who supervises an item day to day and reports to the coordinator. The appointment letters are the first thing we look for, because a register kept by someone who was never appointed and has no authority to refuse a permit is a list, not a control. The letters name the project, the scope and the authority to stop work, and are signed and dated before the first item goes up.

Design check categories, and who assigns them

Every item on the register carries a design check category, from category 0 for a standard solution that needs no bespoke design, through the categories that require the design to be checked by someone independent of the designer, to the highest category where the check is by a separate organisation. The category is assigned by the coordinator from an assessment of complexity and consequence of failure, and the assessment is recorded. The commonest failure we find is not the wrong category; it is every item at category 1 because that is what the template said, with nothing on file to show that anyone thought about it. A scaffold within a standard TG20:21 configuration is a category 0 item and still belongs on the register, because it still needs inspection at intervals not exceeding seven days under regulation 12 of the Work at Height Regulations 2005. A scaffold outside TG20:21 needs a design, a check at the category assigned, and a check certificate before it is loaded.

Permit to load, permit to strike

The permit to load is the coordinator's written confirmation that an item has been erected in accordance with the checked design, inspected, and may now carry the load it was designed for. The permit to strike is the written confirmation that the load has been taken by the permanent works, or that the condition for removal in the design has been met, and the item may be taken down. Both are numbered, dated, signed and cross-referenced on the register. On the sites we audit, falsework nearly always has a permit to load. Far fewer items have a permit to strike, because striking feels like the end of the risk when it is often the start of it: the slab that is loaded early, the back-propping removed before the pour above has gained strength, the excavation support pulled with people still working at the toe.

The items that never make the register

These are the items we find missing most often, and each one is temporary works under BS 5975-1:2024 as much as a falsework tower is.

• Edge protection. Proprietary barriers, timber guardrails fixed to the structure, and the temporary balustrade on a stair or a slab edge. Each is a structure that has to resist a load, is installed by a trade that did not design it, and is routinely modified when a delivery needs to come through. It needs an item reference, a design or a standard solution, a supervisor, an inspection interval and a note of every alteration.
• Hoardings and fencing. The timber hoarding on the public frontage is a wind-loaded structure that the public walks past. It is designed for the site's wind conditions, it has a check, and it has an inspection interval that shortens when the weather turns. It is also the item most likely to be extended or cut for a gate after the design was done.
• Excavation support. Trench boxes, sheet piles, hydraulic frames and battered faces. Regulation 22 requires the start-of-shift inspection; BS 5975-1:2024 requires the design, the category and the permits. A trench box used outside its manufacturer's rated depth, or with a service crossing that was not in the brief, is a design change, and the register should show it.
• Propping and needling. Back-propping under freshly poured slabs, props to a retained facade, needles through a wall being opened up. Back-propping is assumed by the falsework design above it and is the item the register is most likely to have missed altogether, because it was installed by the same gang as the falsework and nobody raised a separate brief for it.
• Crane bases, piling platforms and temporary roads. The working platform certificate is a design record and belongs on the register with the rest.
• The temporary condition of the permanent works. A steel frame before its bracing is complete, a masonry wall before the floor that restrains it is built, a precast unit before its grout has cured.

What the register needs to show

A register that works has three groups of columns. Identity: the item reference, a description with location and gridline, the category and the assessment behind it, and the supervisor. Design and check: the brief reference and date, the designer and design revision, the checker, the check category and the certificate reference. On site: a status on a ladder that runs from identified through brief issued, design received, check complete, erected, inspected, permit to load, in use, permit to strike, struck and closed; the inspection interval with the last and next-due dates; the permit numbers; and an action flag that turns red when anything is overdue. Our temporary works register guide goes through the columns one by one. Sorted on the flag each morning, it shows which design is out of date, which inspection is late and which item has gone without a permit to strike.

The audit questions we ask

1. Show us the coordinator's appointment letter, signed and dated before the first temporary works item.
2. Pick any hoarding, edge protection or propping on the site and find it on the register.
3. For that item, show the category assessment, the design or standard solution, the check certificate at the category required, and the last inspection record.
4. Show the permit to load and the permit to strike for the last item struck.
5. Show one design change on site and the revised design, re-check and updated register entry that followed it.

A site that can answer all five from the register in ten minutes has a control. A site that answers from a supervisor's memory does not. The Temporary Works Control Pack is the document set we use for the audit above: the procedure to BS 5975-1:2024, the appointment letters, the category assessment tool, the register with the status ladder and the due-date formulas, and the permits to load and strike with worked examples.

Agree the list at mobilisation, not at completion

The lesson from every close-out review we have been part of is the same. The subcontract said "O&M manuals", the actual list was agreed with the main contractor in the last three months, and it added certificates nobody had priced or asked their suppliers for. The fix is a handover deliverables schedule issued with the project quality plan: every document by discipline, the standard it is issued to, the format, who produces it, who signs it and when it is due. Once that exists it is a register to be maintained, not a surprise at practical completion.

The O&M manual: what "complete" means

Where the client or principal contractor mandates a template, use it. Where they do not, BSRIA BG 79/2020 is the reference for how a building services O&M manual is structured, and a reviewer will recognise it. Whatever the structure, the content a reviewer checks is this:

• A system description and operating instructions for every system, written for the people who will run the building rather than for the people who built it.
• Maintenance schedules with frequencies, and the manufacturers' literature for the installed equipment, not the catalogue range it was chosen from.
• The asset schedule and the spares list, cross-referenced to the as-built drawings.
• Commissioning results incorporated in the manual, not referenced to a folder on a shared drive that will not survive the project team leaving.
• Warranties and guarantees, each with its start date, its duration, its conditions and the maintenance obligations that keep it valid. A warranty that lapses because nobody told the client to service the unit annually is a defect the client will attribute to you.
• Training records for the client's facilities team, by system, with attendance signed. Someone who was not in the room for the BMS session is not signed off for the BMS.

A draft at 80 per cent, issued for comment four weeks before completion, is what turns a manual from a delivery into a conversation. The final issue then answers comments rather than opening them.

The health and safety file: whose it is and what goes in it

CDM 2015 regulation 12 requires the principal designer to prepare the health and safety file, and requires the principal contractor and every contractor to provide the information needed for it. Where the principal designer's appointment ends before the project does, the principal contractor takes the file on. So the file is not the contractor's document, but the contractor's contribution to it is, and it is usually the part that is missing. HSE's guidance L153 sets out at Appendix 4 the eight headings the file should be structured on:

1. A brief description of the work carried out.
2. Residual hazards and how they have been dealt with.
3. Key structural principles, including safe working loads on floors and roofs.
4. Hazardous materials used.
5. Information on the removal or dismantling of installed plant and equipment.
6. Health and safety information about equipment provided for cleaning or maintaining the structure.
7. The nature, location and markings of significant services.
8. Information and as-built drawings of the building, its plant and equipment.

Assemble your contribution against those headings, not as a box of certificates with a covering letter. The heading that is most often empty is the second. "No residual hazards" is almost never true of a services installation: there are isolation points, pressurised systems, refrigerant charges, fragile ceilings above plant and access hatches that need a ladder. Write them down, say what was done to reduce them, and say what the building's operator has to do about what remains. That page is the one the file exists for.

Regulation 38: the fire information

Building Regulations 2010 regulation 38 requires fire safety information to be given to the responsible person under the Regulatory Reform (Fire Safety) Order 2005 no later than completion or occupation. Approved Document B describes what that information should cover. In practice it is the as-built fire strategy, the fire detection and alarm design, installation and commissioning certificates to BS 5839-1:2025 with the cause-and-effect test record, the emergency lighting completion certificate to BS 5266-1:2025, the fire damper schedule with drop-test records, and the fire-stopping register with photographs of every sealed penetration. Regulation 38 information is regularly the last thing to arrive and the first thing a fire risk assessor asks for. Put it in its own tab of the deliverables schedule and track it separately, because it has a different recipient from the rest of the pack.

Two neighbours of regulation 38 are worth knowing. Regulation 40 requires information about the use of fuel and power, which in practice is the building log book content for the installed plant. Regulation 44 requires a notice to building control confirming that fixed building services have been commissioned, and your commissioning records are the evidence behind that notice.

The certificates that get returned

Three certificate faults account for most of the rejections we see. The Electrical Installation Certificate does not state which amendment of BS 7671 it is issued to: Amendment 4 was published on 15 April 2026 and Amendment 3 may be used only for installations designed before 15 October 2026, so say which. The fire alarm certificates cite the 2017 clause numbering when the 2025 edition of BS 5839-1 renumbered most of it. And the emergency lighting certificate is a single sheet where BS 5266-1:2025 expects separate design, installation and verification declarations. Each of these is a ten-minute fix at the time and a fortnight's delay at final account.

Higher-risk buildings in England: the golden thread

If the building is a higher-risk building under Part 4 of the Building Safety Act 2022, the handover pack above is necessary but not sufficient. The Building (Higher-Risk Buildings Procedures) (England) Regulations 2023 add the completion certificate application to the Building Safety Regulator, and that application includes confirmation that the golden thread information has been handed over to the accountable person. The golden thread is not a separate document set; it is the as-built information, the fire and structural safety information and the change control record, kept in a form the accountable person can find things in and keep current. The practical consequence for a contractor is that the deliverables schedule for a higher-risk building has to be agreed with the client's golden thread structure at the start, and every change made during construction has to be traceable in it. If you learn that at completion, retention is the least of the problem.

The countdown

A workable programme for a services package, in weeks before practical completion: minus 12, deliverables schedule agreed; minus 8, as-built drawing register frozen; minus 4, O&M draft at 80 per cent issued and certificates to date placed in the register; minus 2, client training and the second snagging round; minus 1, joint pre-completion inspection; week 0, handover certificate, keys, spares and log books; plus 2, final O&M, as-builts and the health and safety file contribution; plus 3, lessons learned. Deliver everything by transmittal and get the receipt acknowledged, because "we sent it" is not a defence at final account.

The Handover & Close-Out Pack is that schedule built as registers: a deliverables schedule by discipline with the governing standard on each line, the certificate and warranty register, and a health and safety file contents checklist structured on the eight L153 headings with regulation 38 and 40 tabs. The forms of record behind the certificates, from fire-stopping to cable terminations, are in the Construction Records Library. The full handover checklist, discipline by discipline, is on the site if you want the long version.

The four codes, and what each one commits you to

The code is set per party, not per line. A pre-pour inspection is commonly H for the contractor's own engineer, W for the principal contractor and S for the client. Each party's code is that party's decision, agreed before the plan is approved, and it is the reason we tell contractors to negotiate the codes before they issue an ITP rather than after: a plan that marks everything H for everyone is not thorough, it is a programme lever handed to the client.

Who owns a hold

A hold point belongs to the party whose letter it is. If the principal contractor's column says H at pre-energisation, then the principal contractor's named representative releases it, by attending and signing, and nobody else can do so on their behalf. The contractor's site manager cannot release it because the inspector was late. The client's engineer cannot release the principal contractor's hold, though they may hold their own. This sounds obvious written down and it is the thing most often fudged on site, usually by phone: "can we go ahead and you sign it Monday?" A signature on Monday for a hold released on Friday is a record of a hold that was not held, and an auditor reading the dates will see it.

ISO 9001:2015 clause 8.6 is the requirement behind all of this: planned arrangements to verify that requirements have been met, evidence of conformity, and traceability to the person who authorised release. The hold point is the planned arrangement, the signature is the authorisation, and the record is the evidence. Remove any one and the clause is not met.

Notice periods

The notice period is written on the ITP, typically 24 or 48 hours, and it cuts both ways. The contractor must give it, in a form that can be shown later: an email, an entry on a shared inspection request log, a numbered notice. In return the party holding the point must attend within it, or for a witness point, lose the right to complain that they were not there. Where the notice is given verbally, or given late, the protection disappears in both directions: the contractor cannot prove the invitation, and the client cannot prove they were denied it. We keep a single inspection request register per project, with the notice number, the ITP line, the date and time issued, the date and time the point was attended or the period expired, and the outcome. It is the record that settles most of the arguments before they start.

The holds that actually matter

Most packages have two or three genuine holds, and the rest are witness or surveillance. On a reinforced concrete element it is the pre-pour inspection, because once the concrete is placed the reinforcement can never be inspected again. On a distribution board it is the pre-energisation inspection and the test results before the board is put into service. On a service void it is the pre-close-up, before the ceiling or the boxing goes on. On temporary works it is the permit to load and the permit to strike, which under BS 5975-1:2024 are the temporary works coordinator's to issue and nobody else's. Choose those, defend them, and let the rest be witness points with a notice period. A plan with fourteen holds gets bypassed precisely because nobody can honour fourteen.

How holds get missed

In our experience they are rarely ignored outright. They are missed in one of a handful of ordinary ways.

1. The notice was never issued. The engineer meant to email on Wednesday, the pour was booked for Friday, and by Thursday it was too late to give 48 hours. The point quietly becomes a witness point that nobody witnessed.
2. The hold is on the ITP but not on the programme. The planner has the pour on Friday morning; the ITP needs an inspection on Thursday afternoon that is on nobody's programme. The two documents were never reconciled.
3. The subcontractor does not hold the approved ITP. They are working to their own check sheet, which has no hold point on it, because the approved plan is in the contractor's document control and never reached the gang.
4. The check sheet is signed after the event. The work was covered, the sheet was filled in from memory, the photographs are of the finished surface. The record exists; the inspection did not.
5. The permit is treated as paperwork. The falsework is loaded before the permit to load is signed because the coordinator is on another site and the crane is booked. The permit is signed later "to tidy up".
6. The wrong party releases it. The site manager signs the client's column, or the client's inspector releases a point the contractor's own engineer should have signed first, so the order of checks is reversed.

None of these is a decision to skip an inspection. They are what happens when the plan lives in an office, the programme lives on site and nobody has put the two together.

The record that proves a hold was held

When the question is asked months later, by an auditor, a client's engineer or a claims consultant, the answer has to come from records that agree with each other. We look for five.

• The inspection request, numbered and dated, issued within the notice period, naming the ITP line.
• The check sheet for that line, with measured values rather than ticks, signed by the party whose hold it was, with the time as well as the date.
• The ITP line itself signed in the right column, so the plan and the sheet say the same thing.
• A photograph taken at the point of the inspection, before the work was covered, with its reference on the check sheet.
• The site diary entry for the day, which puts the inspection in sequence with the pour, the energisation or the close-up that followed it.

The sequence is the proof. If the pour record shows concrete placed at 09:00 and the pre-pour check sheet is signed at 14:00 the same day, the dates have answered the question and no explanation will help. If the request went out on Tuesday, the sheet was signed Thursday morning with the cover readings written in, the photograph shows the reinforcement and the diary says the pour started at 13:30, nobody needs to remember anything.

What we would change on most sites

Three things. Put every hold and witness point on the construction programme as an activity with a duration, so the planner sees it. Give the approved ITP and its check sheets to the subcontractor's supervisor, not just to document control, and brief the holds at the pre-start. Keep one inspection request register and make it the first thing the quality manager looks at each morning. The ITP templates in our M&E and civils libraries carry the four codes per party on every line with the notice period in the header, and the Activity Check Sheets behind them ask for measured values and the time of inspection, which is what makes the sequence provable. If you want to see how a plan reads with the holds chosen rather than sprayed, the ITP guide walks through a worked line.

Why six, and why in this order

BS EN ISO 10005:2018, Quality management - Guidelines for quality plans, is the document a reviewer has in mind whether or not they name it. It is a guideline rather than a requirements standard, so nobody is certified to it, but clause 6 lists what a quality plan is expected to cover, from scope and inputs through responsibilities, documented information, externally provided products, production, identification and traceability, to inspection and release. ISO 9001:2015 clause 8.1 is where the requirement to plan the work comes from. The reviewer's job is to check that your plan applies your system to their contract, and the six pages below are where that is either demonstrated or not. Everything else in the plan is supporting material.

Page one: scope

The first page has to prove that the plan was written for this contract. It names the contract, the package, the physical extent, the sections or phases, and what is excluded. It cites the client's quality requirements document by reference and revision, and if the client has mandated their own plan format it says so and cross-references it. A reviewer reads the scope looking for one thing: evidence that the document in front of them is not the company quality manual with a different cover. Fifteen pages describing the document control procedure is the sign that it is. "Document control is to our procedure PR-001; the project document register is Appendix D" is the sign that it is not.

Page two: contract documents and standards

The table of documents that set the requirements: the contract form, the employer's requirements, the specification sections that apply to your package, the drawing register, and the standards that govern the work with their editions. This page has to prove that the standards are current, because it is the easiest place on the whole plan to find a fault. An electrical package plan issued this month that lists BS 7671:2018+A2:2022 tells the reviewer it was copied from an old job; Amendment 4 was published on 15 April 2026. A fire detection plan citing BS 5839-1:2017 is worse, because the 2025 edition renumbered the clauses and every clause reference downstream in the ITPs is now wrong. Check every line of this table against a current index before you issue, and put the date you checked at the foot of it.

Page three: organisation and authority

Named people, not job titles, for the project manager, quality manager, site managers by discipline, document controller, commissioning manager and the specialist subcontractors, with the organisation chart in an appendix. The page has to prove two things. First, that the people exist and the reviewer can find out whether they are competent, which is why "the Quality Manager will" without a name is returned. Second, who is allowed to sign what: who can sign each type of record, who can release a hold point, who can grant a concession, and who can stop work. If those authorities are not written down here, they will be argued about on the day a pour is waiting.

Page four: construction control and the ITP register

This is the page the reviewer spends longest on, and it is the one most plans get wrong. It has to prove that you know what will be inspected before you start. That means the inspection and test plan register for the package, listing every ITP, its revision and its approval status, as a live appendix rather than a table pasted in once. It means the definitions of hold, witness, surveillance and review as they will be applied on this contract, with the notice periods agreed with the client written down, typically 24 or 48 hours. It means the check sheets that record each ITP line, the method statement and briefing regime, and the calibration register for the instruments that will be used. A plan that says "inspections will be carried out to approved ITPs" and does not say which ITPs exist, or whether any are approved, has made a promise the reviewer cannot check.

Page five: nonconformity, concessions and corrective action

The page has to prove that when something goes wrong it will be recorded, contained and decided by the right person. How a nonconformity is raised and numbered, how the work or material is quarantined, the five dispositions and who can authorise each, and the rule that only the party whose requirement it is can grant a concession. Then how the cause is recorded and how corrective action is verified after an interval. Reviewers read this page with a particular fear in mind: the departure from specification that the site manager accepted on the contractor's behalf and that the client discovers at handover. If the plan says in plain words that the site manager cannot do that, the fear goes away.

Page six: records and handover deliverables

The last page the reviewer reads is the one about the end of the job. It has to prove that the argument about deliverables will not happen at practical completion. It lists the records the contract will produce, where they are filed and how long they are kept, and it lists the handover deliverables agreed with the principal contractor: certificates by discipline and the standard each is issued to, as-built drawings and their format, O&M manuals, the health and safety file contribution and client training. A plan that leaves this to "O&M manuals will be provided" has not defined the deliverables, and the reviewer knows from experience what that costs in the last three months.

What the reviewer does next

If the six pages hold up, the reviewer samples the rest: an ITP from the register against the acceptance criteria in the specification, a name from the organisation chart against the competence records, a standard from the table against the ITP that cites it. If the six pages do not hold up, the plan is returned with comments on those pages and the rest is not read. That is why the effort belongs on these six. A plan with a beautiful design control section and an ITP register that says "to follow" is a returned plan.

Keeping it alive

One more thing reviewers notice, later rather than sooner. A PQP still at revision 01 nine months into a contract has not been maintained. The ITP register grows, people change, standards move, and the plan is re-issued when they do, with a revision line that says what changed. The monthly review of the plan itself belongs in the audit and review section, and it belongs in the diary.

Our Project Quality Plan is the template with guidance in every section alongside a fully completed worked example for an M&E package, structured to ISO 10005:2018, with the six pages above written the way a Tier 1 reviewer expects to find them and the appendices set up as registers. It cross-references the procedures in the ISO 9001 Construction QMS so that the plan, the procedures and the forms say the same thing. If you are writing a plan from a blank page this week, read the full section-by-section guide first; it will save you a round with the reviewer.

Updated 17 September 2026: ISO 9001:2026 was published on 16 September 2026. At the date of this update the UK designation on the published index remains BS EN ISO 9001:2015+A1:2024 and BS EN ISO 10005:2018 is unchanged; the clause 8.1 reference above is to the 2015 edition.

What "closed" means to the person signing

ISO 9001:2015 sets the test. Clause 8.7 requires nonconforming output to be identified and controlled so that it is not used or delivered by mistake, and it requires a record of what was wrong, what was done about it, any concession obtained and who had the authority to decide. Clause 10.2 then requires the organisation to react to the nonconformity, to evaluate whether action is needed to eliminate the cause so that it does not recur, to implement that action, to review whether it worked, and to update risks and the system where necessary. A reviewer with that clause in their head is looking for five things on your form: what the requirement was, what was found against it, what was done to contain it, what was done to correct it, and whether anyone asked why. An NCR that answers all five closes. One that answers two of them starts a conversation.

Symptom or cause

The commonest reason an NCR comes back is that the "cause" box describes the symptom again in different words. "Cover to reinforcement below specification" is the nonconformity. "Insufficient cover" is not the cause; it is the same sentence. "Spacers not fitted to the bottom mat because the cage was fixed on the ground and lifted in, and the pre-pour check was signed before the cage was placed" is a cause, and it tells the client three things at once: how it happened, why the inspection did not catch it, and what has to change. You do not need a formal root cause method for every NCR. You need the discipline of asking "why" until the answer is something that can be changed, and then writing that down.

Be honest about scale. Not every NCR needs a corrective action. A single under-supported cable tray is corrected, re-inspected and closed. A pattern of them, a repeat of something already corrected, anything the client found rather than you, or anything over the cost threshold your procedure sets, should trigger a corrective action request with its own number. The NCR then records that reference and the client can see that the cause is being handled somewhere, even if it is not handled on this form.

Three actions, three different words

Reviewers are precise about the vocabulary, so use it the way the standard does.

• Containment is what stopped the problem spreading on the day: work stopped, the area quarantined, the material segregated and labelled, the client told where the contract requires it. It is written in the past tense with a date, because it has already happened by the time the form is issued.
• Correction is what was done to this instance: the rework, the repair, the replacement, or the concession that accepted it as it is. It is the disposition, and it is decided by the party whose requirement it is, which is not always the contractor.
• Corrective action is what was changed so it does not happen again: the amended check sheet, the extra hold point, the supplier taken off the approved list, the briefing with a signed attendance record. It has an owner, a date and an effectiveness check some weeks later.

An NCR that puts "rework completed" in all three boxes will be returned, because rework is a correction and nothing else. An NCR that says "toolbox talk given" as the corrective action will be returned too, unless it also says how you will know the talk worked.

Quote the requirement, then measure against it

The requirement box is the one that stops arguments. "Poor workmanship" invites the subcontractor to ask "compared with what?" and the reply takes a week. "Cover to reinforcement 40 mm, specification clause E10, BS EN 13670" does not. Then the finding is measured, not described: the reading, the number of locations, the photograph reference, the check sheet number it was found on, and who found it. The "detected by" field matters: a register in which the client finds most of the nonconformities says something about your inspections, and a reviewer who sees you recording that honestly trusts the rest of the form.

The disposition, and who is allowed to sign it

Every nonconformity ends one of five ways: rework to the original requirement, repair by a method that does not restore it, accept as is under concession, reject and replace, or regrade and use elsewhere. The question the reviewer asks is not which one you chose but whether the right person agreed. Rework can be authorised by your own quality manager. Repair changes the product, so the designer and usually the client accept the method before it is done. Accept-as-is is a concession, and only the party whose requirement it is can waive it. An NCR closed "accepted by site manager" for a departure from the specification is the fastest way we know to lose a client's confidence, because it is a concession nobody had the authority to give. Put the concession reference on the NCR and do not close the NCR until the concession is granted in writing.

Evidence of closure

The NCR does not close when the subcontractor says the work is done. It closes when the work has been re-inspected against the original acceptance criterion and the record of that re-inspection exists with a number. The close-out section therefore carries the check sheet reference for the re-inspection, the date, and the name of the person who verified it, who is not the person who did the work. Reference the photograph taken after, alongside the one taken before, from the same position where possible. If the disposition was a concession, the reference is the concession number and the date it was granted. If it was reject and replace, the reference is the delivery ticket and receipt inspection for the replacement.

One more link the reviewer will check: the original inspection record for that element. If the pre-pour card still shows a pass and the NCR says the cover was wrong, the two records disagree and both are suspect. Every form of record that can produce a fail should carry an NCR reference box, and the NCR should cite the record it came from.

The shape of a form that closes first time

What this looks like in practice

The NCR form and the corrective action request in our ISO 9001 Construction QMS are laid out in exactly that order, with separate registers for NCRs, corrective actions and concessions so that one does not wait on the other. The forms of record in the Construction Records Library each carry the NCR reference box that closes the loop from the other end, and every worked example includes at least one fail so you can see the nonconformity recorded and corrected rather than just the pass. It is the standard's own sequence, written on a form so that the person who did not write it can sign it.

Updated 17 September 2026: ISO 9001:2026 was published on 16 September 2026. At the date of this update the UK designation on the published index remains BS EN ISO 9001:2015+A1:2024, and the clause 8.7 and 10.2 references above are to the 2015 edition; we will revise them when the British Standard adoption is listed.