Our complete guide to the WSIB Health & Safety Excellence Program covers the mechanics: the levels, the topics, the band-table rebate, how to apply. This piece answers the next question a safety lead asks — okay, so where does a tool like ours actually fit?
Every topic runs on Plan-Do-Check-Act. Dashpot touches two of the four.
To complete any HSEp topic, WSIB expects evidence across the full cycle: a written standard (Plan — the policy your company commits to), implementation and training (Do), a formal evaluation of whether it worked (Check), and — where the evaluation turns up gaps — a documented fix (Act). Your business has to develop, approve, sign and date the written standard — your WSIB-approved provider or a consultant can guide that work, but it isn't theirs to hand you finished. Do and Check are where action plans stall — and Act still needs someone to look at the results and decide what to change. WSIB built the program to pay for demonstrated implementation, not binders, so on validation day the question is always the same: can you show this was real, and that you checked it stuck?
Dashpot generates evidence for the Do step, and — because it runs every day — the raw material for Check. We produce a per-worker, per-hazard record of verified comprehension — a three-minute matched video and a two-minute guided dialogue with each worker each morning, five minutes in total, prompted by the Job Safety Plan your crew already fills out, transcribed and dated. That's dated proof training happened, and because the daily rotation is built to resurface hazards it's already covered — oldest-verified first — the same hazard typically gets re-checked weeks or months later, a real second touchpoint rather than a theoretical one. What it doesn't do on its own is the judgment call: comparing this test to the last one and deciding whether a gap is real is still the safety lead's job. We don't draft your standards, we don't run that evaluation, we don't "complete" topics for you, and no one can promise WSIB pays a rebate. What we supply is the piece that's hardest to reconstruct after the fact: a dated record, attributed to the worker, that the message landed.
The three closest evidence fits
Across the program's 41 topics, there are three where a dated, per-worker comprehension record is the closest fit — strong, specific support for a slice of what the topic asks you to prove, even on the two where it isn't the whole file:
| Topic | Level | What the record evidences |
|---|---|---|
| Health & safety training | Intermediate | The standard demands delivery plus assessment, evaluation and monitoring. Per-worker comprehension records dated to real work are the training-effectiveness proof a sign-in sheet can't supply. The strongest single match. |
| Competency | Intermediate | One input among several. The standard also wants per-position task-competency expectations, certification/licence tracking, and a training-needs analysis for each role — a comprehension record supports the training-effectiveness slice, not the whole competency file. |
| Control of hazards | Foundation | Evidences the "people were educated and understood the controls" element specifically. The standard also wants hierarchy-of-controls selection with rationale, implementation via policy or procedure, and effectiveness monitoring — those are the employer's or provider's to build. |
Why these records are the kind validators accept
Two specifics matter more than the general fit.
First, this evidence is on WSIB's own list of examples. WSIB's evidence-story template lists "documentation that confirms employees understood the training information" and "results of assessment" among the kinds of proof that could support the Do step. A comprehension record is that kind of artifact — not a guarantee a validator accepts it, but not an adjacent proxy either.
Second — and this is the one most tools miss — the program wants two touchpoints, not one. A quiz right after training evidences that you did the training (the "Do" step). The "Check" step asks for a formal evaluation of whether it stuck, done after time passes — WSIB's guidance is on the order of two to three months later. A one-shot quiz at the end of a course doesn't produce that second touchpoint by itself — it can be followed by a separately scheduled quiz, interview or observation months later, but that follow-up has to be planned and run as its own step. Dashpot's daily rotation produces that follow-up as a byproduct of how it already operates: hazards it's covered get resurfaced and re-tested on their own schedule, oldest first, so you get longitudinal, per-hazard evidence without a separate round to plan.
Where it helps but can't carry the topic
Several other topics benefit from comprehension data but are the member's to own.
- Health & safety communication (Foundation) — the daily dialogue is real two-way, audience-appropriate communication, documented per worker. But the topic also wants defined communication channels and a way to collect employee feedback and suggestions, so the record is strong support, not the whole standard.
- Hazard identification (Foundation) — the daily JSP can feed and supplement your hazard registry, and the record shows which workers engaged with which hazards on a given day. But the topic asks for a maintained written registry of all workplace hazards — routine and non-routine work, everyone on site, remote locations included — and that structure, review cadence and assessment methodology are yours to build; our evidence rides alongside, it doesn't carry the topic.
- Monitoring, measurement & analysis (Advanced) — a daily comprehension score is a genuine leading indicator, and almost no contractor has one. But the topic covers the whole measurement system.
- Health & safety participation and hazard reporting (Foundation) — daily per-worker engagement records help; the joint-committee involvement and reporting workflows are yours.
- Control of documents / control of records (Intermediate) — our records natively meet retention and legibility requirements, but only for their own slice.
- Contractor management and review of trends — comprehension data contributes; the topic scope is bigger.
Useful, but don't build an action plan expecting these to complete on our evidence alone.
One thing to check before you build a plan
A topic whose written standard is already signed and approved is ineligible — the program is for new implementation, not re-banking work you've finished ("continuous improvement" is the reason WSIB gives). Interestingly, a standard you've drafted but never had approved is fine; WSIB's own worked example resumes exactly that. So before you pencil in the topics you're counting on us for, confirm none of them is already an approved standard on your shelf. Discovering that at the provider call is an avoidable way to lose a topic.
The honest limits
- We're an evidence engine, not a turnkey action plan. The written standard for every topic is still your business's to develop and approve — your provider or consultant guides it, not drafts it for you.
- No one can guarantee the rebate. It rides on your evidence passing validation, and validators can ask for more or interview your workers.
- Verify the requirements. WSIB updates topics and rules; confirm the current topic-requirements list before you commit a plan.
If you want to see what a day of that evidence looks like on your own site, talk to us — we're onboarding a small number of Ontario pilot contractors.
Sources: WSIB Health & Safety Excellence Program topic requirements and 2025 Program Manual (evidence-story template, Do/Check requirement, newness rule), verified July 2026 — confirm against WSIB's current published requirements before relying on them. Companion to the program explainer. Dashpot Safety supplies the implementation-evidence half of HSEp topics — per-worker, per-hazard verified comprehension records — and never drafts standards or guarantees a rebate.
Fall 2026 · GTA & Hamilton
See your crew's comprehension, not their signatures.
Dashpot runs a five-minute verified-comprehension dialogue with every worker, every morning — built on the JSP your site already produces. We're onboarding a small number of Ontario pilot contractors.
Request a pilot conversation