Brief the workforce and send the pack out
Version-anchored briefings with signatures — plus client issue by link, and the review queue for packs contractors send you.
6 min read · Last reviewed 18 August 2026
Brief the gang
- 1
From the issued pack, record a briefing: who was briefed, when, with signatures captured on the device.
- 2
Brief a whole gang in one batch — each person signs against the exact pack version they were briefed on.
- 3
On site without signal, briefings queue offline and sync later. A sync failure is surfaced loudly, never silently lost.
Note: Briefings are append-only and version-anchored — after a re-issue you are warned that existing briefings cover the old version, and the old records stay intact as evidence of what was briefed on the day.
Issue to a client
- 1
Send the pack to a client on a share link — they read it without an account.
- 2
Their acceptance decision is recorded against the exact version they read, on your record.
- 3
Re-issuing generates the next version to send; the link history keeps who accepted what.
Review packs contractors send you
- 1
Incoming RAMS from your contractors land in RAMS → Reviews, attached to the contractor’s record.
- 2
Review against the checklist — assessments present, method adequate, competence stated — and record the outcome.
- 3
An in-date accepted review can satisfy a permit type that requires RAMS, so the permit gate and the review queue speak to each other.
Tip: Review the method against your site’s reality, not just its grammar. The checklist keeps the review honest; your local knowledge makes it useful.