Safety

Incidents, SWMS and safety paperwork on a job.

Safety

What it is

What workers reported from site, and whether anybody went to it; the job's compliance registers as controlled documents; the forms asked at the gate; the SWMS and other safety paperwork on file; and which subcontractors have supplied their SWMS. The page leads with the reports nobody has been to, because a notification that was missed is indistinguishable from an incident that never happened, and "what did you do when it was reported" is the question that gets asked afterwards.

Before you start

  • Nothing to switch on; the page is on every job.
  • Reports come from the site QR: workers raise an incident or an issue when they sign out. The QR needs to be at the gate (see Crew and timesheets on a job).
  • Gate forms and registers are set up when a job is won and goes to site; a job that predates them has a Set up registers button.

How to

Deal with what was reported

  1. The banner says how many reports nobody has been to. Reported from site lists every one, open first: an incident or an issue raised, who reported it, the date and how many photos.
  2. On an open one, press Mark as dealt with. Write what was done about it (optional, but it is the bit that matters later) and press Record.
  3. The report shows seen with the date, your note underneath, and drops out of the count.

Keep the registers

  1. Registers lists the Site sign-in register, Induction register, SWMS register and Incident register, each with its current revision and status.
  2. PDF downloads the current revision. Regenerate now produces a new revision from the site record; if nothing it records has changed, it says so and offers to produce one anyway. Finalise locks the current revision so it can no longer be changed or deleted.
  3. Earlier revisions are listed under each register, kept exactly as issued, each with its own PDF.

Set what the gate asks

  1. Gate forms shows the switch (on by itself when the job is won and goes to site, or by hand) and the list of forms asked at sign-in: the daily pre-start and fit-for-work, a visitor declaration, a sign-out form.
  2. A job follows the company defaults (edited under Forms) until you press Customise for this project, which copies them here to change. Add a form from the templates with its audience, timing and whether it is required; Go back to the organisation defaults drops the job's own list.
  3. Switch off stops the gate asking anything on this job.

Read the paperwork

Safety documents lists the SWMS, incident reports and toolbox talks filed on the job. Subcontractor SWMS lists each sub's SWMS with its expiry, red when expired or missing.

What happens on its own

  • Registers update at the end of each site day; the incident register within the hour. Never on every sign-in.
  • Subcontractors are asked for their SWMS when a trade is awarded; what they upload lands here.
  • Documents the assistant generates (ask it for a SWMS, an incident report or a toolbox talk) file here automatically.
  • A worker who declares not fit for work at the gate is still let in; the shift records it and the supervisor is told.

Things that surprise people

  • An incident used to produce one notification and nothing that outlived it. Marking it dealt with, with a note, is what makes the record.
  • Finalising a register locks that revision only. The next regeneration makes a new one; the finalised one is kept as issued.
  • A sub with no SWMS on file is flagged at the gate when their workers sign in; this page is where you see who still owes one.
  • Forms for the company's default gate forms and incident form.
  • Site diary for where the day's safety notes are recorded.