Safety
Report incidents, near misses and unsafe acts, investigate the serious ones, raise and verify corrective actions, and close the event as a permanent record.
The Safety tab is the project's incident register. Anyone on site with safety access can report an event; the Safety Officer or Project Manager investigates it, raises actions and closes it. Events are never deleted.
📷 Screenshot spot — the Safety tab with the Days since last LTI tile, the events list with one critical row flagged in red, and an event's detail panel showing its actions
Save as static/img/screenshots/site-safety.png and replace this box with 
Report an event
- Open the project and go to the Safety tab.
- Click Report event.
- Pick the Type and the Severity (see the tables below).
- Set the Date (not in the future) and Time, and pick the Location.
- Write What happened (required) and the Immediate action taken.
- Enter Days lost — working days the injured person could not work.
- Under Persons involved, click Add person for each one: name, role or trade, and injury if any.
- Click File report.
The event is numbered for the project (…/SFT/001), starts as Reported and opens in the side panel.
Report near misses and unsafe acts as well as injuries. The ones that are reported are the ones that do not become injuries.
Types and severity
| Type | Use it for |
|---|---|
| Near miss | Something that nearly hurt someone |
| Unsafe act | A person working unsafely — no harness, no helmet |
| Unsafe condition | A hazard on site — open shaft, loose railing, exposed wiring |
| First aid | Injury treated on site |
| Medical treatment | Injury needing a doctor |
| Lost time injury | Injury that kept someone off work |
| Fatality | A death on site |
| Property damage, Environmental, Fire | As named |
Severity is low, medium, high or critical.
A fatality is always critical, and a lost time injury is at least high — the form greys out the lower choices. Both are marked reportable to the authority, and the event cannot be closed until the authority report is recorded. Both also reset the Days since last LTI count.
Investigate
The Safety Officer, Project Manager or Company Admin opens the event and:
- Clicks Start investigation. The status becomes Under investigation.
- Writes the Root cause and Investigation notes, then clicks Record findings. This can be revised later.
- Adds actions: choose Corrective or Preventive, set the Target date, describe the Action ("Fit toe boards on every scaffold lift"), pick who is Responsible, and click Add action.
Once the event has a root cause and at least one action, its status moves to Actions pending on its own.
For a reportable event, enter the inspectorate's acknowledgement number under Authority reference and click Record report.
Work the actions
- Click Start when work on the action begins.
- Click Mark complete when it is done.
- Someone with closing rights who did not complete it clicks Verify.
An action past its target date shows overdue with a red border, and counts in Overdue actions at the top.
Close the event
Click Close event. If the event cannot close yet, the panel lists why above the button, and the button stays greyed out:
- N action(s) are not yet completed. An incident is closed when its fixes are done, not when they are raised.
- A HIGH event needs a recorded root cause before it can be closed. (Same for critical.)
- This event is reportable to the authority and the report has not been recorded.
A low or medium event with no actions — an unsafe act corrected on the spot — can be closed straight from Reported, without an investigation.
Once closed, an event cannot be edited, reopened or deleted. Check the root cause, the actions and the authority reference before you close it.
The screen has no edit form for a filed event. If a report was filed with the wrong type, severity or date, record the correction in the investigation notes before closing.
Who can do what
| Job | Who |
|---|---|
| Report an event | Site Engineer, Store Keeper, Safety Officer, QA/QC Engineer, Project Manager, Company Admin |
| Investigate, record findings and the authority report, raise and complete actions | Safety Officer, Project Manager, Company Admin |
| Verify actions, close events | Safety Officer, Project Manager, Company Admin |
The person who completes an action cannot verify it — You completed this action, so somebody else must verify it.
The numbers at the top
Days since last LTI (counted from the last lost time injury or fatality, or from the project start if there has been none — red under 30), Open events, Critical open, Overdue actions, and This month with the days lost. Critical events that are still open are also flagged with a red mark on their row. Use Open only / All events to filter the list.
Toolbox talks and permits
The Safety tab records events and their actions. It has no toolbox-talk register or permit-to-work form. Keep signed toolbox-talk sheets and work permits on the project's Documents tab (category Permit or Minutes) — see Documents and photos.
Quality, Snag & Safety Watch ranks open safety events and actions by severity and age with snags and NCRs. The Assistant can draft a near miss, unsafe act or unsafe condition report for you to confirm; injuries, fires and damage are reported by a person on this screen.
Related
- Quality — inspections and NCRs.
- Snags — a hazard found at handover can be a snag in the safety category too.
- Daily progress reports — mention the day's safety events under issues faced.