FlowmatixGuide · Induction & SWMS
What makes a site induction defensible?
Most sites can produce a form with a signature on it. Far fewer can produce evidence. The difference is four things — and it's the difference between a record that answers the question after an incident and one that just raises more.
The question you'll actually be asked
It's rarely "did they sign something?" It's more specific, and it usually comes months later:
"Can you prove this contractor was inducted — and that they accepted the version of the site rules that applied on the day they were here?"
A signed piece of paper struggles with that question, because it can't tell you what the induction said at the time, whether it was actually read, or whether the wording has changed since. Four properties fix that.
1. It's versioned
Your site rules and SWMS change over time. If all you have is "signed the induction," you can't show which induction. A defensible record ties the acceptance to a specific version of the wording — and when you change that wording, the version increments and people re-accept. A signature against text you've since edited proves nothing; a signature against a known version proves a lot.
2. It's enforced, not optional
A tick-box in a browser can be skipped with a back button or a script. If your induction can be bypassed, then "they signed it" doesn't mean "they did it." Enforcement on the server side — where the worker genuinely can't reach the sign-in without completing the steps — is what lets you say: if they're on site, they completed it.
3. It carries a signature and a timestamp
Evidence is specific: this person, this acceptance, at this moment. A typed signature bound to the record and stamped with the time turns "sometime around then" into "at 7:42am on the 3rd." Small detail; large difference when it's examined.
4. It fits the worker
An electrician and a courier don't need the same induction. Per-type forms mean the screened contractor gets the full briefing and the delivery driver gets three questions — so the evidence is proportionate and people actually complete it rather than clicking through a wall of irrelevant fields.
The test: produce it in under a minute
Here's the honest benchmark. Pick a contractor who was on your site eleven months ago. Can you produce, in under a minute: who they are, which induction they received, which version of the SWMS they accepted, their signature, the timestamp — and every change to that wording since?
If that's a folder-and-a-prayer exercise, the record isn't defensible yet. If it's one screen, it is.
Flowmatix Visitor Management is built around exactly those four properties — versioned acceptance, server-side enforcement, signature and timestamp, per-type forms — so that last test is a non-event. If you want a process checklist to audit your current setup, the contractor induction checklist walks the whole flow — and the same logic applied to SWMS sign-off covers the other half of the paperwork.
Make the induction the evidence.
Versioned, enforced, signed and timestamped — by default.