Published 5 March 2026 · 6 questions
A UK construction site manager shares their experience using AI to generate compliance documentation. Honest review of what works, what does not, and time saved.
Too much. I estimated about 12-15 hours per week writing RAMS, risk assessments, toolbox talks, and updating the construction phase plan. That is a third of a 45-hour working week spent writing documents instead of managing the site. And the quality was inconsistent — by Friday afternoon, my risk assessments were not as thorough as Monday morning's. It was the part of the job I dreaded most, which meant it often got left until the last minute, which made the quality even worse.
Desperation, honestly. I had a project with 14 different work activities all needing RAMS, and the client wanted them all submitted before work started. That was 14 RAMS to write in a week on top of running the existing site. I had heard about Site Manager AI and thought, 'What is the worst that can happen?' The worst case was that the output was rubbish and I wasted 30 minutes. But the best case was that it saved me days.
The first RAMS I generated genuinely surprised me. It had all the right sections — scope, sequence, hazards, controls, emergency procedures, competency requirements — and it referenced the correct regulations (CDM 2015, WAH 2005, MHSWR 1999). It was not perfect — no AI output is — but it was a solid 80% draft that I could review and customise in 15-20 minutes instead of writing from scratch in 2-3 hours. The regulatory references were actually more comprehensive than what I would have included manually, because I tend to reference the regulations I know off the top of my head and miss some of the peripheral ones.
A few. The first-generation outputs were occasionally too generic — they would include control measures that were not relevant to my specific site conditions. For example, suggesting traffic management controls on a site with no vehicle access. But that is the same problem with any template — you need to review and customise. What AI does is give you a much better starting point than a blank page or a 5-year-old template from a different project. I learned that the more specific I am with my input (describing the site, the access, the adjacent properties, the ground conditions), the more specific and useful the output is.
I have been using it for 4 months now. A RAMS that used to take 2-3 hours now takes 20-25 minutes total (2 minutes for AI generation, 20 minutes for my review and site-specific customisation). Risk assessments that took 45 minutes take 10. Toolbox talks that I used to recycle because I did not have time to write new ones — I now generate fresh topics in seconds. Overall, I estimate I save 8-10 hours per week on documentation. That is 8-10 hours I now spend on actual site management, quality control, and safety observations. The irony is that my documentation quality has improved and I am spending less time on it.
Without hesitation, with one caveat: you must review everything. AI is a drafting tool, not a replacement for your professional judgement. Every document still needs a competent person to review it against the actual site conditions, the actual workforce, and the actual risks. If you treat AI output as a final product and put it in the site file without review, you are setting yourself up for failure. But if you treat it as a very competent first draft that saves you hours of writing, it is genuinely transformative. I cannot imagine going back to writing everything from scratch.