Safety packs from one row of a sheet
I’m David McMillan, a forward deployed engineer. For a UK fit-out contractor, I built a generator that turns one row of their project sheet into a full RAMS pack, the risk assessments and method statements a site team works to. It started as a demo in November 2025 and ran as a pilot from July to September 2026.
was Copied by hand from the project sheet now Generated by ticking one row of the Smartsheet
- Sector
- Commercial fit-out, including bank branches
- When
- November 2025, then July to September 2026
- Systems
- Smartsheet, Word, PDF
- Status
- Prototype
- Rev
- B · 14.10.2026
The work
The contractor fits out bank branches for tier-one UK banks, among other work. Every site gets its own RAMS pack. The details for each site were already in a project sheet, and the teams copied them into the pack by hand.
Constraints
Every pack is marked DRAFT, not for issue, until the contractor names a competent person to approve it, and that approval step is not built yet.
What I found
In November 2025 I went through the documents the teams produce and ranked twelve things to automate. RAMS packs, site posters and weekly reports made the first group, high impact and low complexity, and RAMS came first, with the data already in the sheet. Operations manuals and legal documents were near the end of the list.
What I built
A tick on a row of the sheet sends one webhook. The generator assembles the pack from a library of the contractor’s own approved content: 12 risk assessments, 12 method statements and about 20 policy and compliance sections. It adds the site’s details, a contents page, and the nearest A&E, fire station and police station. Word and PDF come from the same section model, so the two match. A repeated webhook is dropped, and each job writes a document record and an audit log row.
The first version used a language model to draft the method statements. In July 2026 I replaced it with the contractor’s own approved wording, because the packs carry the banks’ site details. No model call is now in the path that makes a pack.
What happened
The contractor generated two packs themselves from the demo, on 31 July and 4 August 2026, from rows they entered for two of their sites: 63 pages each, DRAFT throughout.
Checking those packs against the contractor’s own, I found the hospital lookup had named a minor injuries unit for one site, where their own pack for that site named a major A&E. On 6 August I changed the lookup so that a unit known to have no A&E is never named, even when the map marks it as one.
Next for the same contractor, agreed but not yet built: an intranet hub and a filing service in their own Microsoft tenant.
Start with a call
The call takes 30 minutes. I ask how the work moves today, not which tools you use.
I’m based in Lisbon, Portugal, and work UK hours. I’ll be on site anywhere in the UK and Europe, with travel inside every fixed price.
bigbadbird.ai/work/site-safety-packs · dm@bigbadbird.ai · Built 15.10.2026