What a WSIB “Evidence Story” Actually Looks Like (With Example)

If you've joined the WSIB Health & Safety Excellence Program (HSEp), the word you'll hear at validation isn't policy — it's evidence story. This is a plain-language WSIB evidence story example: what the document is, the difference between documents and records that decides whether a topic passes, and a full worked sample for the Health and Safety Training topic. WSIB defines an evidence story as "a detailed description of a member's activities and actions to develop and implement a topic in the workplace and their journey to meet the topic requirements." In other words: not what you say you'll do — what you actually did, and how you know it worked.

The evidence story is one half of an evidence package

Every topic you complete needs exactly one evidence package, and WSIB is precise about what's in it: "the combination of a member's evidence story and evidence supporting materials." The evidence story is your written summary — the narrative. The supporting materials are the proof you attach to back it up. Per the 2025 Program Manual, you can attach up to five files (50 MB each) per topic, in supported formats such as PDFs, spreadsheets, photos, video, and audio.

So a passing topic is two things working together: a short story that says "here's what we did and how we checked it," and a handful of dated files that prove the story is true.

Documents vs. records — the distinction that decides validations

This is where most action plans lose time, so it's worth getting exact. WSIB's own definition of supporting materials splits them cleanly:

• Documents — "policies, safe operating procedures, etc." These state what you intend to do.
• Records — "training, pre-use inspections, minutes of meetings, signoffs, etc." These prove you did it.

A document is a promise. A record is a receipt. You need both, but validators lean on the records, because a binder full of well-written policies proves only that someone can write policies. It's the same logic as a concrete pour: you don't sign off a slab because the mix design looked good on paper — you break a test cylinder to prove the concrete actually reached strength. The written standard is your mix design. The records are your broken cylinder.

The bar isn't "do you have a policy." It's "living and breathing."

That's WSIB's own phrase. Its HSEp program guidelines are blunt about what validation checks: they exist to "make sure [your topics are] complete and are living and breathing in your workplace" — a topic is living and breathing, in WSIB's words, once it "has become a part of your day-to-day business activities." The 2025 Program Manual echoes it: health and safety has to be "embedded in day-to-day work," and validation confirms a topic is "fully implemented in a workplace" — not filed. The evidence story template walks you through a Plan-Do-Check-Act structure, and it's the Check step that catches people. WSIB wants you to show "how you checked (evaluated) that your topic is being practiced/is understood," and it sets a specific timing rule:

"you allowed sufficient time (generally 2 to 3 months) after you delivered training in your workplace before you did your evaluation."

What WSIB asks for is a documented formal evaluation, generally 2 to 3 months after training — and that evaluation can take whatever form fits the work: follow-up quizzes, interviews, observations on the job, or a mix. It isn't a mandated re-test of every hazard; it's proof that you deliberately went back and checked whether the training stuck. That's why a sign-in sheet from training day can't carry a topic on its own. A signature collected the morning of the session is a Do record — it shows the training happened. The formal evaluation comes later, and one piece of paper can't be both.

Desk validation and onsite validation

Once your provider submits the package, every topic goes through online validation — and some members get an onsite visit on top of it.

• Online (desk) validation. A WSIB validator reviews your package through the digital tool. WSIB aims to return an online decision within 14 business days.
• Onsite validation. In addition to the online review, some members are selected for a visit. Per the manual, "onsite validation of a single location will require two to four hours," and the validator's job is "reviewing documents and records" and "interviewing employees" — i.e. asking your crew, directly, whether the thing on paper is real. WSIB aims to return the onsite decision within five business days of the visit.

If a topic comes back Additional Evidence Required (AER), you're not sunk — you have 60 calendar days from the notice to submit what's missing (and that window includes the time your provider needs to review it). Miss the 60 days and the topic goes incomplete. Plan for onsite: the manual's own advice is to prepare "as though all your topic(s) will be selected."

A worked WSIB evidence story example: Health and Safety Training

Here's a full, fictional example for the Health and Safety Training topic (Intermediate level). Details invented; the structure mirrors the manual's template.

The business. ABC Mechanical — a 34-worker plumbing and HVAC contractor. Action plan approved by its provider on March 3, 2026. (Timing matters: the topic has to be new work. Because ABC's written standard was still to be developed when the plan was approved — it was signed a week later, on March 10 — the topic is eligible. A standard already signed and approved before the plan would make it ineligible.)

The written standard (Plan / the document). ABC's Health and Safety Training standard does more than name a few hazards. Following the topic's requirements, it sets out how training is given and managed; how it's assessed, evaluated, monitored and updated (including refresher training as required); and a requirement that a competent person handles all of it. It also spells out the minimum training content every worker receives — the training prescribed by legislation, plus roles, responsibilities and rights, the purpose of the health and safety management system, and the consequences of noncompliance. On top of that baseline it commits that task-specific training is tied to the actual hazards of each assigned job; that every session is assessed for understanding, not just attendance; and that understanding is formally evaluated after a set interval, with gaps corrected and re-verified.

The evidence story (the narrative ABC writes):

• Plan. "We signed our training standard on March 10, setting out how training is delivered and managed, how we assess and update it, the minimum content every worker gets, and who our competent person is. We identified our three highest-risk tasks — silica cutting, lockout/tagout, and work at heights — and defined who delivers each briefing, how we assess understanding, and when we evaluate it."
• Do. "From mid-March to May 2026 we delivered task-specific briefings before each affected job. For every worker we logged who was trained, on what hazard, and on what date. We kept the completed assessments, not just the sign-in sheets."
• Check. "In June 2026 — about three months after the first briefings — we ran a formal evaluation of comprehension on the trained tasks, using short quizzes plus on-the-job observation. It surfaced a gap: four of 34 workers were fuzzy on the LOTO isolation sequence."
• Act. "We treated that gap as a documented corrective action. In late June we retrained the four workers on the LOTO isolation sequence, re-evaluated them, and recorded the result — logged with dates in a short corrective-action note. Gap found, gap closed, verified."

The five supporting files (the records):

1. Health-and-safety-training written standard, signed and dated March 10, 2026 — covering how training is given, managed, assessed and updated, the competent-person requirement, and the minimum training content. (A document.)
2. Per-worker training log, March–May 2026 — worker, hazard, date. (A record.)
3. Comprehension assessment results, April 2026 — the initial understanding check. (A record.)
4. Formal evaluation results, June 2026 — the 2-to-3-month evaluation (quizzes plus observation), with the LOTO gap flagged. (A record — and the Check step.)
5. Corrective-action note plus photos — the dated late-June retraining and re-evaluation of the four workers (the Act step), alongside photos of posted safe-work procedures and a dated toolbox-talk sign-off. (Records.)

Notice what files 2 through 5 are. They're exactly what the manual's template names as accepted proof: "documentation that confirms employees understood the training information, results of assessment (e.g., tests, quizzes)." File 4 — the June evaluation — is the Step-4 evaluation the "2 to 3 months" rule asks for, and file 5 carries the Act step: the dated corrective action that closed the gap it found. That package tells a complete story: planned, delivered, checked, corrected, verified.

Why a daily comprehension record is an evidence story's strongest exhibit

Here's where the day-to-day tool matters. Everything above — the per-worker record, the dated proof of understanding, the second touchpoint months later — is hard to reconstruct the week before validation. It's easy if your everyday workflow produces it automatically.

That's where Dashpot helps. Each morning, the Job Safety Plan your crew already fills out triggers a short per-worker check on that day's hazards — producing a per-worker, per-hazard record of verified comprehension that's dated, attributable, and exportable. That record is, almost word for word, the evidence WSIB's template calls "documentation that confirms employees understood the training information." That's your Do evidence. And because the daily rotation is built to resurface hazards it's already covered, the same hazard is likely to come back around weeks later — giving you the dated raw material for a later Check, rather than a paper trail staged the week before validation.

What Dashpot doesn't do is the rest of the cycle for you. It doesn't perform the formal evaluation, it doesn't make the judgment call about whether a gap is real, and it doesn't carry out the Act — comparing this check to the last one and deciding what to change is still your safety lead's job. It can't guarantee a given hazard will reappear on any schedule, and it doesn't "complete" a topic. The written standard is your business's to develop and approve — your WSIB-approved provider can guide it, but it isn't theirs to hand you finished. And Dashpot complements your toolbox talks, it doesn't replace them.

For a sense of what a completed action plan is worth, the WSIB rebate calculator estimates your per-topic rebate from your premium band, and the full HSEp guide walks the program end to end.

Frequently asked questions

What is a WSIB evidence story?

A WSIB evidence story is the written summary you submit for each Health & Safety Excellence Program topic. WSIB defines it as "a detailed description of a member's activities and actions to develop and implement a topic in the workplace and their journey to meet the topic requirements." It travels with your supporting files as an "evidence package," and every topic in your action plan needs exactly one.

What's the difference between a document and a record in HSEp?

A document states what you intend to do — WSIB's examples are "policies, safe operating procedures." A record proves you actually did it — "training, pre-use inspections, minutes of meetings, signoffs." Validation leans on records, because a policy on paper proves only that a policy was written. You submit both, but the records are what confirm the topic is being practiced, not just planned.

How long does WSIB validation take?

WSIB aims to return an online (desk) validation decision within 14 business days of your provider submitting the package, and within five business days of an onsite validation visit. If a topic is returned as "additional evidence required," you have 60 calendar days from the notice to submit what's missing before the topic is marked incomplete.

What happens during a WSIB onsite validation?

According to the 2025 Program Manual, an onsite validation of a single location typically takes two to four hours. The validator reviews your documents and records and interviews employees — checking that the written standard on paper matches what workers actually know and do. Some topics are selected for onsite review; WSIB advises preparing as though all of yours will be.

Do attendance sign-in sheets count as WSIB evidence?

A sign-in sheet is a record — but only of attendance. It shows a worker was present, not that they understood. The evidence template asks for "documentation that confirms employees understood the training information, results of assessment," and it wants a documented formal evaluation generally 2 to 3 months after delivery — which can be quizzes, interviews, observations, or a mix, not necessarily a re-test of every hazard. A sign-in sheet can support the "Do" step; on its own it can't satisfy the "Check."

---

Dashpot Safety complements legislated certification training such as Working at Heights and WHMIS — it never replaces it. Nothing here is legal advice; confirm program requirements with your WSIB-approved provider.

Sources: WSIB Health & Safety Excellence Program — Program Manual 2025 (evidence story, evidence package, documents vs. records, the Plan-Do-Check-Act template, onsite duration, the "2 to 3 months" re-evaluation rule), frequently asked questions (14-business-day and 5-business-day decision targets, 60-day additional-evidence window), and topic requirements. The "living and breathing" validation standard is from WSIB's HSEp program guidelines (July 2023, p.18) and IHSA's validation guide for employers. Verified July 2026 — confirm current details with WSIB.