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.
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.
Key takeaways
- Certificates and tags are practice, not statute — which is why their quality varies so much between firms.
- Certificate, tag and inspection should be three views of one structure record.
- Most mismatches trace back to an adaptation that was never written down.
- Raising the certificate from the design removes a whole class of transcription error.
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.