Skip to content
Proof on Demand

The whole world asks for proof. Rosie answers them all.

GCs, owners, COR auditors, WorkSafeBC, insurers, and executives all ask for proof — but the evidence lives in binders, PDFs, photos, and inboxes, when it exists at all. SALUS captures crew-level facts with full context, and Rosie assembles them into packets, dashboards, and live portals in minutes.

Your daily work is the proof — operational safety means the evidence exists because the field used the tool, not because someone built a binder.

Live board

Who's asking for proof · This week

Asked
COR auditor 🍁 / CNESST mutuelle ⚜️A year of evidence · binder, 2 days
WorkSafeBCHazard-comm records · filing cabinet
GCSub compliance · emailed PDFs
InsurerClaims & indicators · reconstructed
OwnerLive program proof · a deck, maybe
CEO“Are safe sites more profitable?” · a week
  1. Proof is a byproduct of the work

  2. Crew-level facts with full context

  3. Rosie assembles each package

  4. Packets, dashboards, live portals

  5. LMS · any job's proof on demand

The problem

Everyone asks for proof; the evidence is everywhere and nowhere.

A COR auditor needs a year of organized evidence. A GC needs sub compliance before mobilization. An insurer wants claims handling and leading indicators. WorkSafeBC asks about hazard communication. An owner wants live program proof. Each request sends the safety team into binders, PDFs, photos, and inboxes — assembling, by hand, evidence the company already generated but never organized.

01
Request arrives
From an auditor, GC, or insurer
clock starts
02
Hunt
Binders and inboxes
hours
03
Reconstruct
What was never organized
gaps
04
Compile by hand
A packet, manually
a day
05
Hope
It's accurate
risk
06
Repeat
For the next requester
again
The solution

Turn daily field activity into proof anyone can verify.

Tap a requester to see the package assemble — every fact carries its crew-level context.

Proof isn't produced by compiling a binder — it's produced the moment the field acts.

See where proof comes from
Way 01 · Capture the factProof reconstructed laterA fact the moment it happens

The proof exists because the field used the tool.

Every QR scan, form, and inspection creates a timestamped, GPS-tagged, worker-identified fact — no separate reporting step.

01

Forms

Each form carries its context — who, where, when — the moment it's completed.

A completed field form is stored as a timestamped fact tagged with worker, site, and time
02

Scans

Every QR scan is timestamped and located — a verifiable event, not a memory.

A QR scan at a site gate records a timestamped, GPS-located access event
03

Inspections

Inspection evidence is captured in-flow — findings and photos attached to the record.

An inspection record with attached photos and findings captured during the walk
04

Incidents

Incidents are documented at the scene, offline, with the full chain preserved.

An incident documented at the scene with photos, location, and a timestamped chain of events
Evidence · a second job → a byproduct Audit trail · assembled → generated
Way 02 · Assemble on demandDays in bindersMinutes with Rosie

Ask, and the package builds itself.

Rosie pulls any element, any job, any date — mapped to whatever standard the requester uses — in seconds.

01

COR evidence

Rosie assembles the audit package element by element, mapped to the standard.

Rosie assembles a COR audit package element by element, each item mapped to the standard's requirements
02

GC compliance

Per-sub compliance assembled on demand — current, not reconstructed.

A per-subcontractor compliance summary assembled on demand for a general contractor
03

Insurer packets

Claims handling and leading indicators packaged for underwriting.

An insurer evidence packet with claims handling, corrective-action velocity, and leading indicators
04

Any job, any date

Pull the proof for any job and any date range in seconds.

Rosie retrieves the full evidence record for any selected job and date range in seconds
LMS · 2 days → 1h45m Any job's proof · binder → on demand
Way 03 · Share liveA static PDFA live portal

Not a PDF — a live link.

The Trust Portal shows current training, certs, forms, and corrective-action closure to any GC, owner, or auditor; even those not on SALUS can verify you.

01

One link

One link, always current — no version to email, no PDF to age.

A Trust Portal share link showing live, always-current compliance status
02

GCs verify

GCs verify your compliance before you mobilize, on their own time.

A general contractor opens the Trust Portal link and verifies a sub's compliance before mobilization
03

Owners see proof

Owners see live program proof — current training, certs, and closure.

A project owner views live program proof in the Trust Portal — training, certs, and corrective-action closure
04

No account

Even those not on SALUS can verify you — no account required.

A reviewer without a SALUS account verifies current compliance through a public Trust Portal link
Proof · email attachments → one live link GC chasing · eliminated
Way 04 · Answer the hard questionA week of spreadsheetson demand

The CEO's question, answered before the meeting.

Rosie correlates form completion with incident rates, engagement with margin — the analysis that took a week arrives in seconds.

01

Engagement vs. outcomes

Rosie correlates field engagement against incident and outcome rates.

A chart correlating field-tool engagement against incident and outcome rates across sites
02

Safety vs. profitability

The safety-versus-margin question answered with the company's own data.

A correlation view answering whether safer sites run more profitably, from the company's own data
03

Site vs. portfolio

Any site benchmarked against the portfolio in a click.

A single site's safety metrics benchmarked against the portfolio average
04

One chart

Exported as one chart, board-ready, before the meeting.

A board-ready chart exported from Rosie summarizing the correlation in one view
“Are safe sites more profitable?” · a week → 4 minutes Drill-down · 3 clicks
Who gets it

Proof for every role.

01 ·

Safety leaders

Gets · Proof without the binder hunt

Any requester's evidence assembled on demand from daily activity.

02 ·

Executives

Gets · Answers for the board and the owner

Correlations and live proof that win trust and contracts.

03 ·

Field supervisors

Gets · No more chasing docs

Sub and crew compliance visible without end-of-day paper runs.

04 ·

Workers

Gets · Work that counts as proof

The forms they complete become the company's evidence, automatically.

Both outcomes

Prove the program to anyone, in minutes.

The proof and the protection are the same artifact. Every fact the field captures is evidence the moment it's created — assembled for whoever asks, without a binder hunt. 🍁 Across the rest of Canada, whoever asks is often a COR auditor or a provincial OHS inspector, and the assembled record is the due-diligence evidence — the 'every reasonable precaution' standard under Bill C-45 / Westray. ⚜️ In Québec, it's a CNESST inspector, and the same evidence is produced in French, on demand.

Proof outcomes

  • COR/audit packets in minutes
  • Live Trust Portal sharing
  • Insurer-ready evidence
  • Board-level correlations
  • No binder hunts

Safety & compliance outcomes

  • Crew-level facts with context
  • Timestamped audit trails
  • Verified sub compliance
  • Consistent hazard-comm records
  • Bill C-45 due-diligence evidence

Rest of Canada🍁

  • COR audit-ready kits
  • WCB / WSIB claims-and-leading-indicator evidence

Québec⚜️

  • Kits ready for the mutuelle and a CNESST inspection
Related use cases

Keep exploring the work SALUS gives back.

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

Prove it

Make proof a byproduct of the work not a project.

Bring your next audit or GC request to a 15-minute demo and watch the package assemble.

Capture the fact · Assemble on demand · Share live · Answer the hard question