Skip to content
COR Certification

Earn COR. Keep it. Bid more.

Build the evidence COR auditors require — hazard assessments, toolbox talks, training, inspections, corrective actions, management review — as a byproduct of daily work, so the audit takes hours instead of days and the certificate opens provincial, GC, and owner prequalification.

COR should open doors — not consume your safety team.

Live board

COR Maintenance Audit · 6 weeks out · Element readiness

6 weeks out
Hazard assessments (FLHA)Complete
Toolbox talksGaps · 3 crews
Training & certificates2 expired
InspectionsOn paper
Corrective actions4 open · >30 days
Management reviewNot started
  1. Evidence built year-round, not audit week

  2. Gaps visible before the auditor sees them

  3. Every element tied to real field activity

  4. The package assembles itself

  5. LMS: 2 days → 1h 45m of audit review

The problem

COR lives in binders the other 51 weeks of the year.

COR isn't earned in the audit — it's earned in the twelve months before it, in evidence that has to be complete, organized, and provable across every element. But that evidence is scattered: paper FLHAs in trucks, toolbox-talk sign-ins on clipboards, training in a spreadsheet, corrective actions in inboxes, management review written the week before. So audit prep becomes a project — a senior safety professional pulled off the field for days to reconstruct a year of work the company already did.

01
Pull a year of FLHAs
From trucks and binders
+days
02
Toolbox-talk attendance
Reconstructed from sign-in sheets
+hours
03
Training & certificates
Chase current records
+hours
04
Corrective-action closure
Compiled across every site
+hours
05
Management review
Written from memory
+hours
06
Cross-check vs the standard
Against the audit tool
+hours
07
Audit day
— audit day —
The solution

Turn daily field activity into COR evidence.

Tap a card — each COR element builds itself as crews work, leaving an audit-ready record.

The package isn't compiled the week before — it's already built.

See the audit assemble itself
Way 01 · Build continuouslyAudit prep that starts six weeks outEvidence that was never not being built

Audit prep that never starts — because it never stopped.

Every FLHA, toolbox talk, inspection, and corrective action accrues into the COR record as a byproduct of the work. There is no "prep phase" because the evidence is already complete and organized when the auditor arrives.

01

Daily forms become evidence

Every FLHA, FLHA, and inspection a crew completes accrues into the COR record automatically — the hazard-assessment element is built by the work itself, not assembled later.

A field form captured by voice and photo files itself into the COR record, tagged to the hazard-assessment element
02

Logged the moment it happens

Toolbox talks capture timestamped attendance at QR sign-in, and corrective actions close with a photo-verified trail — every element is dated and complete when it's created.

A toolbox talk signed in by QR with timestamped attendance, verified and logged
03

Management review on real data

When review time comes, Rosie draws on a year of captured activity instead of memory — the review becomes evidence, not narrative.

Rosie pulls a year of captured activity into a management review mapped to every COR element
COR prep · days → hours Evidence accuracy · reconstructed → captured at source
Way 02 · See the gapsFinding the hole on audit daySeeing it any day

Find the missing element before the auditor does.

Rosie monitors element readiness continuously — the three crews behind on toolbox talks, the two expired certs, the corrective action open past 30 days — and surfaces the gap while there's still time to close it.

01

Element readiness, live

Rosie tracks every COR element across every site continuously — you see completion by crew and site, not a single number at audit time.

Live COR element readiness by crew and site, gaps flagged six weeks before the audit
02

Flagged before they're findings

Expired credentials and corrective actions aging past 30 days surface while there's still time to close them — an expired cert becomes an eight-minute refresher, not a finding.

Expiring certifications surface on the worker's profile before they become audit findings
03

The hole, visible any day

The three crews behind on toolbox talks appear on the dashboard weeks before an auditor would notice — gap discovery moves from audit day to any day.

Crews behind on toolbox talks appear on the dashboard weeks early, owner assigned
Gap discovery · audit day → any day Expired cert · a finding → an 8-min refresher
Way 03 · Assemble on demandDays compiling the binderRosie builds the package

Rosie builds the package.

Ask for any element's evidence and Rosie assembles it — mapped to the audit standard — in seconds. The two-day documentation review becomes a request you answer before the meeting starts.

01

Ask for any element

Request the evidence for any COR element and Rosie assembles it — mapped to the provincial standard — in seconds.

Rosie assembles the evidence for any COR element, mapped to the provincial standard, in seconds
02

Any job, any date

Pull a specific site, a date range, or a single element; the package is built from the captured record, not a binder hunt.

A COR package built for any site and date range from the captured record
03

One package, many audiences

The same assembled evidence serves the COR auditor, WCB, and your insurer — the two-day review becomes a request you answer before the meeting.

One COR evidence package shared live with the auditor, WCB, and insurer
LMS · 2 days → 1h 45m Evidence pull · binder hunt → on demand
Way 04 · Maintain everywhereA separate binder per provinceOne COR across every jurisdiction

One COR, every province.

Multi-jurisdiction operations maintain COR from one dashboard — the same field activity feeds each provincial audit, so you stop running a separate documentation effort per region.

01

One platform, every province

Multi-jurisdiction operations maintain COR from a single dashboard — the same field activity feeds each provincial audit.

COR maintained for every province from a single dashboard, one activity feeding each audit
02

Remote and northern sites included

Crews in dead zones capture offline and everything syncs when signal returns, so northern and remote work sits in the record like everywhere else.

Crews in dead zones capture offline and everything syncs when signal returns
03

No separate documentation effort

You stop running a documentation project per region — Wildstone maintains COR across BC and the Yukon from one dashboard and eliminated a full-time documentation role.

COR maintained across two provinces from one dashboard, no documentation project per region
Wildstone · 2 provinces, 1 dashboard Full-time COR documentation role → eliminated
Who gets it

COR that earns its keep for every team.

01 ·

Safety leaders

Gets · Audit prep without the binders

Element readiness visible year-round; the package assembles itself instead of consuming days before every audit.

02 ·

Executives

Gets · A certificate that wins work and cuts premiums

COR that clears provincial, GC, and owner prequalification — and secures the WCB rebate — without a growing back-office cost.

03 ·

Field supervisors

Gets · Toolbox talks and sign-in without the clipboard

Rosie writes the talk; QR captures attendance; the evidence is created without leaving the work.

04 ·

Workers

Gets · Forms that count, in their language

The FLHA and orientation they complete on their phone become COR evidence automatically — no extra step.

Both outcomes

Pass the audit and run a stronger program.

This isn't paperwork for the auditor. The same captured activity that makes COR effortless makes the program underneath it measurably stronger.

COR outcomes

  • Faster audits (days → hours)
  • Fewer gaps and findings
  • One COR across provinces
  • WCB rebate secured
  • Provincial, GC, and owner prequalification

Safety & program outcomes

  • Stronger FLHA records
  • Verified training and certificate currency
  • Faster corrective-action closure
  • A management review built on real data
  • Bill C-45 due-diligence evidence
Related use cases

Keep exploring the work SALUS gives back.

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

COR, explained

COR audit & certification software

What does COR mean?
COR stands for Certificate of Recognition. It shows that an employer’s health and safety management system has been evaluated by a qualified auditor and meets the applicable provincial program standards. SALUS COR certification software helps contractors build, track, and prove that program year-round.
Get COR certified

Make COR the certificate that pays for itself.

Bring your last audit to a 15-minute demo and we'll show you the package building itself.

Build continuously · See the gaps · Assemble on demand · Maintain everywhere