Site Safety

The safety documents workers must read and acknowledge — inductions, RAMS, risk assessments, COSHH, procedures, the safety policy and toolbox talks — with who still owes an acknowledgement on each; a builder for risk assessments scored on your matrix, with a template library a new account starts with; toolbox talks and in-person inductions recorded against whoever was on the register that day; the induction record; and the accident book with the RIDDOR deadline worked out for each incident. Status everywhere is a dated acknowledgement, a published version or a recorded session — never a tick.

You enter

A document: its kind, title, the project it belongs to or company-wide, the text the worker reads on their phone or the file (a RAMS is usually a PDF), who it applies to, whether it needs a signature, and for an induction how often it must be refreshed.
A risk assessment: each hazard with who is at risk and the existing controls, scored likelihood by severity before and after further controls; the actions, their owner and due date; then Publish.
A talk or induction delivered in person: the project, the date, the document and the attendees — those on that day's register are pre-ticked. An incident: four fields on the day, the rest at the desk.

Saral fills in

Who still owes each document, by project, from who is assigned and who has acknowledged the current version; a new version asks everyone again.
The hazard score and band from the group's matrix, the warnings the rules raise, the overdue actions, and the next review date of every document and assessment.
The induction record from every source — signed, delivered in person, paper form read, portal tap — and whether each is current, due a refresher or on an old version.
The RIDDOR category's reporting deadline and urgency from the incident's facts.

It produces

Published risk assessments as safety documents with a PDF per version; the induction record as Excel; the outstanding list per project.
The accident book with each incident's status, days lost, investigation notes and the HSE reference once you have reported it on hse.gov.uk — Saral records the reference, it does not submit the report.

What this page is for

Site safety is a paper trail that has to exist before anyone asks for it: who read the RAMS, who was inducted on this site and when, which risk assessment covers this activity, what happened on the day of the accident and whether it was reported in time. This page keeps that trail as it happens. A document is acknowledged because a named worker did so on a dated version; an induction is current because a recorded session or a signed form says so; an action is done on a date, with evidence. The Outstanding tab is the list of what is owed, the Induction record is the positive record, and together they answer the inspector and the principal contractor without a search.

Documents, versions and acknowledgements

Every document has a kind, an owner, a review cycle and a version. Workers read it on their portal — plain text and bullet points work on a phone, or the attached PDF — and acknowledge it, with a signature where the document requires one. Attaching new bytes or re-issuing bumps the version and asks everyone again; disabling takes it out of circulation without losing its history. Applies to narrows a document to worker types; a project-level document is asked only of that project's people; a RAMS registered on a project's own register is read-only here and follows the project's approval. Owners with a login are reminded on Mondays from 30 days before the review date.

Risk assessments on your matrix

An assessment is built from hazards: each names who is at risk and the existing controls, scores likelihood and severity on the group's matrix to a band, then scores again after the further controls to show the residual risk. The rules warn beside a hazard when the residual risk scores higher than the initial, or when further controls are listed but the residual is not scored; and publishing is blocked while any hazard's residual risk sits in the top band with no further control, or while anything the AI drafted is still unchecked. Every further control becomes an action with an owner and a due date; done is a date, with evidence. Publish freezes a version as a safety document for the right people to acknowledge, and a change after publishing is flagged until the next version. A new account starts with the standard construction templates, each copied into a new assessment and edited there.

Talks, inductions and the accident book

A toolbox talk or an in-person induction is recorded against the live register: pick the project and the date and the people on site that day are already ticked, so the record is who was actually there. An induction delivered this way counts in the induction record alongside a signed induction, a paper form read in the worker's name and a portal tap, ranked in that order, with a refresher falling due after the months set on the induction. The accident book takes an incident in four fields on the day — kind, project, when, what happened — and the rest at the desk. Choosing a RIDDOR category sets the deadline and the urgency, and the pane says when to phone HSE first; the report itself is made on hse.gov.uk and its reference recorded here.

Where the settings live

Site Safety has no separate settings tab: the risk matrix is edited on this page under Risk assessments → Matrix, because it only changes how assessments score; a document's owner, review interval and refresher months are set on the document from its Review cell; who a document applies to is set on the document. Which workers belong to a project — and so who is asked — comes from the site register and assignments. The project-level RAMS register is on the project in Projects.

Next screen: /hr/disciplinary

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.