NEWScaffEngine — the 3D builder. Model the scaffold before anyone leaves the yard
ScaffoldOptixScaffolding software
Operations28 April 2026 · 4 min read · Updated 27 September 2026

Scaffolding insurance: what the cover actually turns on

Scaffolding firms hold public liability, employers' liability and usually contract works cover, and all of it is in place. Where claims become difficult is not the existence of a policy but the conditions inside it — and those tend to describe exactly the record-keeping a busy firm lets slide.

Conditions that look like admin until they matter

Policies commonly assume inspections happen at stated intervals and are recorded, that people working are appropriately trained and carded, that subcontract labour is verified, and that the work is within the described activities. Each of those is a normal operating expectation. Each becomes a question at claim time, answered from records rather than from practice.

Which means the inspection record and the competence evidence for subcontract labour are not only compliance artefacts. They are what a claim is defended with.

Activities are more specific than firms assume

Cover is written against described activities, and scaffolding firms drift into adjacent work — a temporary roof, a suspended access job, something at a height or a complexity beyond what was described at renewal. The drift is commercial and gradual and nobody re-reads the schedule.

Worth checking at renewal, in both directions: what you are doing that the schedule does not describe, and what it describes that you no longer do.

In practice: the claim that turned on a folder

A minor injury claim arrives eighteen months after a job finished. The firm's position is straightforward and the structure was sound. What it needs to produce is the inspection history for that structure across the period, and the records are on paper, in a job folder, archived — incomplete for the weeks that matter.

The claim was defensible. Defending it cost considerably more than it should have, because the evidence had to be reconstructed rather than retrieved.

Common mistakes

  • Assuming the policy's existence is the protection, rather than its conditions
  • Drifting into activities the schedule does not describe
  • Inspection records held only on site and archived with the job
  • No verification evidence for subcontract labour
  • Not telling insurers about a material change in work type
  • Retaining records for less time than a claim can realistically take to arrive

Claims arrive late

The gap between an incident and a claim can be considerable, and it is routinely longer than a firm's instinct about how long to keep job records. Retention driven by how long a job runs, rather than by how long a claim can take to arrive, is how firms end up defending a position from memory.

Which makes retention a commercial decision rather than an administrative one, and it is worth setting deliberately rather than by whatever a filing system happens to do.

Getting this right

The records a claim needs are the ones a firm already produces: the inspection history for the structure, the competence evidence for whoever worked on it, the design basis and the handover. The failure is almost never that they were not created — it is that they cannot be retrieved years later.

  • Set retention by how long a claim can take, not how long the job ran
  • Hold records centrally rather than in archived job folders
  • Re-read the policy schedule at renewal, in both directions
  • Tell insurers about a material change in the work you take on
  • Keep verification evidence for subcontract labour with the job
  • Make sure records can be retrieved by structure, not only by contract

Where this connects: retention is a commercial decision

The gap between an incident and a claim is routinely longer than a firm's instinct about how long to keep job records. Retention driven by how long a job runs, rather than by how long a claim can take to arrive, is how firms end up defending a defensible position from memory and paying considerably more to do it.

Which makes retention worth setting deliberately rather than by whatever a filing system happens to do. The records a claim needs are ones the firm already produces — the inspection history, the competence evidence, the design basis, the handover. The failure is almost never that they were not created.

  • Set retention by how long a claim can take, not how long the job ran
  • Hold records centrally rather than in archived job folders
  • Make records retrievable by structure, not only by contract
  • Re-read the policy schedule at renewal, in both directions
  • Tell insurers about a material change in the work you take on
  • Keep subcontract verification evidence with the job

Key takeaways

  • Claims turn on policy conditions, not on whether a policy exists.
  • Inspection and competence records are what a claim is defended with.
  • Cover is written against described activities, and firms drift out of them gradually.
  • Re-read the schedule at renewal, in both directions.
  • Keep records for as long as a claim could take to arrive, not as long as the job ran.

The ScaffoldOptix team

Written by people who work daily with principal contractors on CDM design, inspection and the records that hold up when a client asks.