Who is actually competent to inspect a scaffold?

Inspection duties get delegated more casually than almost anything else on a site. Someone is available, they have been scaffolding for years, and they are asked to walk the structure and sign the record. That works until somebody asks what made that person competent to inspect this particular structure, and the answer turns out to be seniority rather than anything demonstrable.

Competence is specific, not general

The useful question is never whether someone is competent in the abstract. It is whether they are competent for this structure — its type, its complexity, its loading, and whether it is a standard configuration or something that has moved into bespoke design territory. A person entirely capable of inspecting a straightforward independent tied scaffold may not be the right person for a complex temporary roof or a heavily adapted structure.

That distinction matters because it is the one an inspection record cannot show. A signature proves somebody attended; it does not show that the person signing had the knowledge the structure actually demanded.

Recording why, not just who

The practical improvement is small and almost nobody does it: record what made the inspector appropriate for that structure, not merely their name. Card held and type, relevant experience, and any limits on what they will inspect themselves. It takes a line and it converts an assertion into evidence.

It also surfaces the gap before somebody else does. Firms that write this down tend to discover quite quickly that one or two structure types are being inspected by whoever is nearest, because nobody on site is obviously the right person.

Independence is worth thinking about

There is a second, quieter question: whether the person inspecting is the person who built it. It is common, often unavoidable on a small firm, and it is worth being conscious of — somebody checking their own gang's work is being asked to find their own mistakes. Where it can reasonably be separated, separating it produces better inspections.

Common mistakes

• –Treating competence as a general status rather than specific to the structure
• –Delegating on seniority or availability rather than on demonstrable knowledge
• –Recording who inspected without recording what made them appropriate
• –No stated limits on what an inspector will assess themselves
• –The same person building and inspecting with no acknowledgement of it
• –Not revisiting the arrangement when the firm takes on unfamiliar structure types

In practice: the firm that found its gap on paper

A contractor with four squads wrote down, for the first time, which of its people were competent to inspect which structure types. The exercise took an afternoon and produced an uncomfortable finding: birdcages and temporary roofs were being inspected by whoever was nearest, because the two people with genuine experience of them were both on other sites most weeks.

Nothing had gone wrong. But the firm had been unable to see that a category of structure was effectively uncovered, because the inspection records looked identical to every other week's — signed, dated, nothing found. Writing the competence down made a gap visible that the records never would have.

What to do when the right person is not available

The honest options are narrow: bring in someone competent, restrict the structure until somebody appropriate can attend, or accept that the inspection is being done by someone whose competence for that structure has not been established. Only the first two are defensible, and the third is what happens by default when nobody has named the constraint.

Firms that handle this well tend to have a short list of structure types they will not inspect internally, and an arrangement in place before they need it rather than a phone call on the day.

Worth knowing: review the arrangement, not just the people

Competence arrangements are usually set once and left. They need revisiting whenever the firm's work changes — a first temporary roof, a first job at height beyond the usual, a new client with different expectations — because each of those may put structures into the business that nobody on the books has inspected before.

• –Revisit whenever the firm takes on an unfamiliar structure type
• –Keep a standing arrangement for anything you will not inspect internally
• –Record refusals as well as inspections — a declined inspection is a good sign

Where this connects: what to do when nobody suitable is available

Establishing that competence is structure-specific creates an obvious problem: sooner or later a structure needs inspecting and the right person is on another site. The options at that point are narrow and worth deciding in advance, because deciding under pressure reliably produces the wrong one.

They are: bring in somebody competent, restrict or take the structure out of use until somebody appropriate can attend, or have it inspected by someone whose competence for that type has not been established. Only the first two are defensible, and the third is what happens by default when nobody has named the constraint. Firms that handle this well hold a short list of types they will not inspect internally and an arrangement already in place.

• –Decide in advance what happens when the right person is unavailable
• –Hold a list of structure types you will not inspect internally
• –Arrange external cover before you need it, not on the day
• –Record refusals — a declined inspection is evidence the system works
• –Review the arrangement when the firm takes on unfamiliar work
• –Separate the builder from the inspector where it is practical