Skip to content
Risk Control at Scale

Find the risk. Close the loop. Prove it.

Construction risk assessment software should do more than store an FLHA or JHA. SALUS connects hazard registers, inspections, incidents, and corrective actions; assigns every follow-up to a named owner; and preserves proof of closure while Rosie watches every open loop.

Operational safety isn't more safety — it's the same protection with the risk closed faster, easier, and provable.

Live board

Open risk · Portfolio · 14 sites

Open
Open corrective actions47 · 3 over 48 hrs
Overdue items by trade60% · one framing sub
Near-misses last week3 unreported
Sites missing hazard assessment6 flagged
Incident trendClustering · 1 time of day
Standards deployment2 sites behind
  1. Standards deployed everywhere at once

  2. Field intel multiplied

  3. Corrective actions owned by named people

  4. Rosie watches every open loop

  5. Trends visible before incidents

The problem

Growth makes risk harder to see, not easier.

An FLHA, JHA, or isolated hazard register captures one moment. The field reports and hears nothing back, the office assigns and can't verify, and every new worksite makes the risk picture harder to connect across inspections, incidents, corrective actions, and proof.

01
Hazard reported
On a clipboard
lost
02
Corrective action
Owned by “the company”
ages
03
Closure
Never proven
unprovable
04
Near-miss
Unreported
pattern missed
05
New site
Standards inconsistent
gaps
06
Incident
The cluster was there all along
recordable
The solution

Turn scattered hazards into a closed-loop system.

Tap a signal to see the loop close — every action traces to the form, inspection, or incident that created it.

Risk isn't controlled by reading one report at a time — it's controlled by closing every loop.

See where risk gets controlled
4 waysSALUS + Rosie

Where risk gets controlled.

Way 01 · Deploy everywhereStandards that vary by siteOne standard, every site

Your best practice, on every job.

Procedures, forms, and controls deploy company-wide in one action — your newest apprentice gets the controls your best foreman would write.

01

Forms & SWPs

Procedures, forms, and controls push company-wide in a single action — no site rebuilds the standard.

Rosie deploys a standardized set of forms, SWPs, and controls across all 14 sites in one action, each site confirmed current
02

New sites

A new site inherits the full standard from day one — no weeks of setup, no gaps while it spins up.

A newly added site inherits the company standard — forms, controls, and orientations active from day one
03

Provinces

Ontario, Alberta, BC, and Québec differences are handled centrally, so every site runs the same rigor under the right framework.

SALUS adapts a deployed standard to each province's framework automatically — same rigor, correct regulatory basis per site
04

Apprentices

Your newest apprentice works from the controls your best foreman would write — best practice, not individual memory.

An apprentice opens a task and sees the same expert hazard controls the company's best foreman would specify
Deployment · site-by-site → one action New site · weeks → immediate
Way 02 · See moreThin, late field dataThe signal multiplies

Adoption is the risk multiplier.

QR access and Rosie capture mean crews actually submit hazards, near-misses, and observations — more and better data is the leading indicator.

01

Near-misses

Captured in ~90 seconds from any phone — the leading indicator crews finally have time to report.

A near-miss is captured in about 90 seconds from a phone, with photo and location, no app required
02

Observations

Submitted in any language; Rosie translates so the office reads one clean record.

A worker submits a field observation in their own language and the office sees one readable English record
03

Inspections

Spoken on the walk; Rosie structures the findings and opens the corrective actions.

An inspector speaks findings on the walk and Rosie structures them into a report with corrective actions opened
04

Adoption

Adoption rises from 40% to 80% (Aquicon) — more and better data is the leading indicator.

Field-tool adoption climbs from 40% to 80% at Aquicon, with submitted hazards and near-misses rising in step
Field intel · multiplied Near-miss · unreported → captured
Way 03 · Close the loop“Someone should fix this”A named owner, a proven close

The loop stays open until a specific human closes it.

Corrective actions carry a person's name, a due date, and photo-verified closure — across your whole portfolio, internal and sub.

01

Assigned to people

Every corrective action carries a person's name and a due date — not “the company,” a human.

A corrective action is assigned to a named individual with a due date, not to a company or a crew
02

Tracked to close

Viewed, dispatched, and closed — each transition logged with a timestamp.

A corrective action moves through viewed, dispatched, and closed states, each transition timestamped
03

Photo-verified

Closure requires photo evidence — the fix is shown, not asserted.

A corrective action is closed with a required photo showing the completed fix
04

Escalation

Overdue items escalate automatically and surface by trade, so the lagging sub is visible.

Overdue corrective actions escalate automatically and a dashboard surfaces overdue items grouped by trade
Closure · 7 days → hours Overdue items · invisible → surfaced by trade
Way 04 · PredictReading one report at a timeSeeing the pattern

The patterns become visible before the first incident.

Rosie correlates any field data point against any other — form completion vs. incident rate, training vs. near-misses — across the portfolio.

01

Correlations

Crew, trade, time, and site correlations Rosie computes across the whole portfolio.

Rosie correlates incidents against crew, trade, time of day, and site across the portfolio
02

Leading indicators

The signals that precede recordables — surfaced before they become incidents.

A dashboard surfaces leading indicators that historically precede recordable incidents
03

The declining sub

The subcontractor whose assessments are sliding, caught early instead of after an incident.

A trend view flags a subcontractor whose hazard-assessment completion is declining over recent weeks
04

Portfolio health

Portfolio risk at a glance — every site's open loops and trend in one view.

A portfolio dashboard shows every site's open-loop count and risk trend at a glance
78% of serious incidents · preceded by unreported near-misses Answer · a week of spreadsheets → on demand
Who gets it

Risk control for every role.

01 ·

Safety leaders

Gets · Risk visible before it's an incident

Leading indicators and open loops across every site, without waiting on paperwork.

02 ·

Executives

Gets · A defensible program at scale

Standards deployed everywhere and Bill C-45 due-diligence evidence across the portfolio.

03 ·

Field supervisors

Gets · Closure without chasing

Corrective actions assigned and tracked to a named owner from the field.

04 ·

Workers

Gets · Hazards that actually get fixed

Report in ~90 seconds and see the loop close.

Both outcomes

Control risk across every site without losing visibility.

More sites shouldn't mean less visibility. Every loop Rosie closes leaves a provable record — the risk controlled and the evidence captured at once. 🍁 Across the rest of Canada, that evidence is the due-diligence defence at scale — proof of 'every reasonable precaution' under Bill C-45 / Westray, the same record provincial OHS penalties now turn on. ⚜️ In Québec, it's the documented programme de prévention and the comité de santé et de sécurité record CNESST expects, kept in French across every site.

Risk outcomes

  • Standards deployed company-wide
  • field intelligence multiplied
  • Corrective actions closed in hours
  • Leading indicators before incidents
  • Portfolio-wide visibility

Safety & compliance outcomes

  • Named-owner accountability
  • Provable closure
  • Bill C-45 due-diligence evidence
  • Consistent provincial OHS compliance

Rest of Canada🍁

  • Stronger COR records

Québec⚜️

  • Records supporting the CNESST prevention program and mutuelle
Related use cases

Keep exploring the work SALUS gives back.

These pages use the same field-to-proof system from different operating angles.

Control the risk

Close every open loop across every site.

Bring your portfolio's open corrective actions to a 15-minute demo and we'll show you the patterns.

Deploy everywhere · See more · Close the loop · Predict