Document control
One library for every record a site raises
Every form a site raises — RAMS, toolbox talks, inspections, permits — is built, submitted and stored in one library, with drafts tracked separately from submissions so a record half-finished on a phone is never mistaken for one that exists.
Document control on a construction site usually means a shared drive and a naming convention that survived about three weeks. The failure is not storage. It is that there is no difference, to the filesystem, between a document somebody started and a document that was actually submitted.
So drafts and submissions are tracked as different things. A form in progress belongs to the person filling it in. A submitted one belongs to the record, is timestamped, and is what an audit sees. That distinction is most of what a document controller does, held in the structure rather than in somebody's discipline.
The form builder exists so the records match how you already work. An inspection sheet that mirrors your existing one gets filled in properly; a generic template gets worked around, and the workaround is where the real record ends up.
Everything submitted lands in one searchable library, tied to the site, subcontractor or worker it concerns. That is what makes assembling a health and safety file at handover a matter of filtering rather than remembering.
What it does
Forms that match your paperwork
A drag-and-drop builder for RAMS, toolbox talks, inspections and permits, so the digital record is the one people actually fill in.
Drafts separated from submissions
In-progress records tracked apart from submitted ones, so nothing half-finished is counted as evidence and nothing finished goes missing.
One searchable library
Every form ever submitted, searchable and filterable, tied to the site, subcontractor or worker it was raised against.
A handover file that assembles itself
Because records are already attached to the right site, producing the documentation a project owes at the end is a filter rather than an excavation.
What goes wrong without it
- The shared drive has a naming convention that three people follow and nine ignore
- A PDF is emailed out, edited by the recipient, and sent back as a new version under the same filename
- Nobody can say which version of a document is current without asking the person who wrote it
- The health and safety file is assembled in the last fortnight of a job, out of whatever can still be found
Further reading
The Health and Safety File: what it must contain, and who's actually responsible for it
The health and safety file gets assembled during a project most people never think about again — until someone renovating the building years later needs to know exactly what's behind a wall they're about to open up.
What actually belongs in a daily site diary
A site diary that just says who turned up is a missed opportunity — it's often the single most useful record when a dispute, delay claim or incident needs reconstructing months later.
What site inspection records actually need to show
A record that says an inspection happened is weaker than one that shows what was found — and what was found is what actually protects you if something goes wrong later.
Terms on this page
Next to this
- RAMS & method statements
Built, reviewed and versioned against the firm that wrote them
- HSE reporting
Roll-ups across every site, built from records already entered
One licence, every site you run.
All eight modules are included on every licence — this one is not sold separately, and there is no per-user charge on top of it.