Handover certificates and tags: getting the paperwork to match the scaffold

Neither the handover certificate nor the tag is required by name in legislation. Both are industry practice, and both exist for the same reason: the person about to walk onto a scaffold needs to know whether it is finished, what it can carry, and when it was last looked at. None of that is visible from the standards and boards in front of them.

What each one is for

• –The handover certificate is the contractual moment: this structure, at this address, to this loading class, handed to this client on this date, signed.
• –The tag is the on-site status: do not use, incomplete, or safe to use — readable by someone who has never seen the certificate.
• –The inspection record is the ongoing evidence that the status on the tag is still true.

How they drift apart

They drift apart the moment they live in different places. The certificate is in the office, the tag is on the scaffold, and the adaptation that changed the loading happened on a Thursday with neither one updated. Nobody intended it; it is simply what happens when three records of the same structure are kept by three different people.

The remedy is to treat all three as views of one record. Raise the certificate from the design, so the loading class on the certificate is the loading class that was designed. Set the tag status from the same record, so changing one changes what the other should say. Log the adaptation against the structure, so the next inspection starts from what is actually standing.

The tag that stopped describing the structure

A tag reflects the structure at handover. Structures then get altered — a lift added, a section struck, a board removed to get plant through — and unless each alteration triggers a reassessment, the tag keeps saying what it said on day one while the structure underneath it has changed.

This is the most common way a scaffold ends up in use in a condition nobody has assessed. Nobody removed a control; the control simply stopped describing reality. Tying the tag to the adaptation record and to the inspection cycle is what keeps the two in step.

Common mistakes

• –Tags not updated when a structure is altered
• –Handover recorded without identifying precisely which structure it covers
• –No copy of the handover record held anywhere but site
• –Alterations made by another trade with no route back to the scaffolder
• –No record of who handed over and to whom
• –Treating the tag as the whole control rather than as a visible summary of one

Worth knowing: handover is a transfer of responsibility

A handover is not an administrative formality. It is the point at which a structure passes from the people who built it to the people who will use it, and the record of that transfer matters to both sides — particularly where the structure is subsequently altered by somebody other than the scaffolding contractor.

The situation worth planning for is another trade modifying a handed-over structure: removing a board to get plant through, taking off a guardrail, adding a sheet. It happens regularly, the scaffolding contractor is frequently unaware, and the tag continues to describe the structure as handed over. Agreeing explicitly at handover that alterations come back to the scaffolder — and giving the client a quick way to do that — prevents most of it.

• –Say explicitly who may alter the structure after handover, and how they request it
• –Give the client a fast route to ask, or they will do it themselves
• –Re-tag after any alteration rather than relying on the original
• –Keep the handover record centrally, not only on site

Where this connects: what happens after you walk away

Handover transfers a structure to people who will use it for weeks, alter it if they need to, and have no particular reason to tell you. The commonest sequence that ends badly is another trade removing a board or a guardrail to get plant through, doing it competently, and nobody reinstating it because the person who removed it was not the person who finished.

Two things reduce it, and neither is a document. Saying explicitly at handover who may alter the structure and how they request it, and giving the client a route that is faster than doing it themselves. Where requesting a change takes two days and doing it takes ten minutes, the structure will be altered by whoever is standing there.

• –State at handover who may alter the structure, and how they ask
• –Make the request route faster than doing it unilaterally
• –Re-tag after any alteration rather than relying on the original
• –Keep the handover record centrally as well as on site
• –Say what the structure may not be used for, not only what it is
• –Record who handed over and to whom, by name