What a scaffold inspection report should record

Most inspection records prove that somebody attended. Fewer prove that anything was examined, and that difference only becomes visible when a record is read by someone who was not there — an auditor, a client, or an investigator after something has gone wrong.

Recording what was fine, not only what was not

A report that lists only defects cannot later demonstrate that anything else was looked at. If a tie fails three weeks after an inspection that found nothing, the record showing no defects is ambiguous: it might mean the ties were checked and were sound, or that they were not checked. A report that records what was examined resolves that.

This is also what makes a clean inspection meaningful rather than empty. On a well-built structure most inspections should find nothing, and a record showing a thorough check that found nothing is a genuinely useful document.

Identifying the structure precisely

On a site with several structures, a report has to say unambiguously which one it covers. "Rear elevation" is the kind of description that is perfectly clear on the day and useless eighteen months later, particularly once the structure has been adapted or partially struck. Referencing the structure the same way the handover record and tag do keeps the documents in step.

What belongs in the record

• –Which structure, identified the same way as its handover record and tag
• –Who inspected, and what made them appropriate for that structure
• –The date and time, not just the date
• –What was examined, including the areas found satisfactory
• –Any defect, described specifically enough to be acted on by someone who was not present
• –What was done immediately, and what was raised as work with an owner and a date
• –Whether the structure was left available for use, restricted, or taken out of use

The photograph problem

Photographs help and are frequently taken badly — wide shots of a whole elevation that show nothing specific. A photograph is useful when it shows the particular thing being described, close enough to be legible later, and it is close to useless as a general record that an inspection happened.

Common mistakes

• –Recording defects only, so nothing shows what else was examined
• –Structure descriptions that make sense on the day and not afterwards
• –No time recorded, only a date
• –Defects described too vaguely for someone else to act on
• –No statement of whether the structure was left usable
• –Records held on paper at site with no copy held centrally

In practice: a record that answered the question

A tie pulled out of a substrate eleven days after an inspection. The question that followed was whether the ties had been examined, and the firm's record showed that they had — with the areas checked listed, a note that the substrate had been sound at three sample points, and the inspector named.

That did not prevent the failure and it completely changed the conversation. The alternative record, listing only that no defects were found, would have left the firm asserting that ties were checked with nothing to show it. Same inspection, same inspector, same day — the difference was entirely in what was written down.

Free text is where reports quietly fail

Reports written as prose tend to be inconsistent between inspectors and impossible to compare across visits. One person writes three lines, another writes a page, and neither can be searched later for whether a particular area has recurring problems.

A structured record — the same fields, every time, with free text for the specifics — produces something that accumulates into a history rather than a folder of individual accounts. It also makes it far more obvious when an inspection has skipped something, because the field is empty rather than merely unmentioned.

Worth knowing: the record has to outlive the job

Inspection records are frequently needed long after a structure has come down and the job has closed — for a client query, an insurance matter, or an investigation. Records kept in a job folder that gets archived, or on paper that stays with a site file, are the ones that cannot be found when that happens.

• –Store centrally, not only in the job folder
• –Keep records for as long as they could conceivably be needed, not as long as the job runs
• –Make sure they are searchable by structure as well as by date

Where this connects: structured fields beat free text

Reports written as prose vary by inspector and cannot be compared. One writes three lines, another a page, and neither can be searched later for whether a particular area has recurring problems. That is fine for a single report and useless as a body of evidence, which is what a firm actually needs when a question arrives eighteen months later.

The same fields every time, with free text for the specifics, produces something that accumulates into a history. It also makes omissions visible: an empty field is obvious in a way an unmentioned topic in prose never is, which means the format itself catches inspections that skipped something.

• –Use the same fields every time, with free text only for specifics
• –An empty field is visible; an unmentioned topic in prose is not
• –Make reports searchable by structure, not only by date
• –Record what was examined and found satisfactory, not only defects
• –Store centrally so a report outlives the job folder
• –Photograph the specific thing described, not the elevation