The temporary works register is the project’s controlled list of every temporary works item, and the status of each one as it moves through design, checking, installation, use and removal. It is the spine of temporary works management: nothing else in the process works properly if the register is incomplete.
It is also the first document an auditor asks for, and the speed with which a project can produce a current one tells you almost everything about how well temporary works are being controlled there.
What each entry should record
A register is not just a list of items. Each entry needs to carry enough status information that someone can look at it and know exactly where that item has got to, without having to ask anyone.
Per-item fields
- Unique reference number for the item
- Description and precise location
- Design category
- Who the designer is, and whether the design has been issued
- Design reference and current revision
- Who the design checker is, and whether the check is complete
- Required date, and the programme activity that drives it
- Permit to load status and date
- Inspection regime and the date of the last inspection
- The person responsible for the item on site
- Any outstanding actions against it
- Removal, strike and close-out status
Who owns it
The Temporary Works Co-ordinator owns the register. That ownership needs to be real: someone whose job it is to chase the missing check certificate, to add the item that appeared on site without going through the process, and to close out the entries for temporary works that were removed two months ago.
Where a project has multiple subcontractors each running their own temporary works, the registers need consolidating into a single project view. Several parallel registers with no consolidated picture is functionally the same as having none, because nobody can answer the question "what temporary works are live on this site today".
Why registers stop being useful
Almost every project starts with a well-structured register. The failure is rarely at mobilisation; it is at week eight, when the site gets busy and updating a spreadsheet stops feeling urgent.
The specific ways it degrades are predictable.
How registers decay
- Populated at mobilisation from the programme, then never updated as reality diverges
- Items appear on site that were never added — usually subcontractor-provided temporary works nobody classified as temporary works
- Design revisions move but the register still shows the original revision
- Status columns show "in progress" for items that were completed and removed months ago
- Permit and inspection columns left blank because the evidence lives in a different folder
- Multiple versions of the register circulating by email with no single controlled copy
- No close-out, so at handover nobody can demonstrate that temporary works were removed safely
Keeping it current
The practical fixes are unglamorous and they work. Put register status on the agenda of an existing recurring meeting rather than creating a new one. Keep one controlled copy and make everyone work from it. Make adding an item to the register a precondition of ordering or mobilising it, not an afterthought.
The most useful discipline is a standing review of two specific things: items whose required date is approaching but whose design or check is not complete, and items showing as live whose work has actually finished. The first list is where risk is accumulating; the second is where the register is lying to you.
A register that is 80% accurate is more dangerous than no register at all, because people trust it.
Register, schedule and programme
These get conflated. The register is the controlled list of items and their status. The programme tells you when the associated construction activity happens. A temporary works schedule, where one is used, sets out the planned design and delivery dates for the items on the register.
The register is the one that has to be right, because it is the record that everything else — permits, inspections, audits, handover — refers back to.
What an audit does with it
An auditor will take the register and sample from it. They will pick a handful of items and ask to see the design brief, the design, the check certificate, the permit and the inspection records for each one, then check that those documents are consistent with each other and with what is physically on site.
That is the whole test, and it is why register accuracy matters more than register formatting. A register that lists twelve items when there are nineteen on site does not fail because of the paperwork; it fails because seven temporary works items are being used without anyone tracking whether they were designed, checked or inspected.