WorkSafeBC Training Records: What Sections 3.23–3.25 Require, and Why an Orientation Checklist Isn't Enough

A prevention officer asks to see your training records for a worker who was hurt in his third week. You have the orientation checklist. It's signed and dated, it covers the supervisor's name, WHMIS, PPE, first aid and emergency procedures, and it was completed the morning before he started.

Then the question narrows: what records do you have for the task he was doing when it happened?

That is usually where the file goes quiet. The generic orientation is documented because there's a form for it. The task-specific part is real — someone showed him, he worked alongside a senior for a while — but it lives in people's memory rather than on paper.

The BC Occupational Health and Safety Regulation asks for both.

Who counts as a "young or new worker" in BC?

Both terms are defined in section 3.22, and both are wider than they sound.

A young worker is "any worker who is under 25 years of age." That's the whole test — not a student, not an apprentice, not a summer hire. Twenty-four and in year six of the trade still counts.

A new worker is any worker who is:

• new to the workplace
• returning to a workplace where the hazards in that workplace have changed during the worker's absence
• affected by a change in the hazards of a workplace
• relocated to a new workplace if the hazards in that workplace are different from the hazards in the worker's previous workplace

Read the last three again, because they're the ones that surprise people. A driver back from six months of medical leave, returning to a yard that changed its loading procedure, is a new worker. A crew moved from a residential site to an industrial one is made up of new workers. A shop that introduces a new machine has just converted its existing operators into new workers for that hazard.

The practical consequence: the obligation isn't a hiring event you clear once. It's triggered by a change in hazard exposure, and it can attach to your most experienced people.

What does section 3.23 require before someone starts work?

Section 3.23(1) is unambiguous about timing. The employer "must ensure that before a young or new worker begins work in a workplace, the young or new worker is given health and safety orientation and training specific to that young or new worker's workplace."

Before. Not in week one.

Section 3.23(2) then lists thirteen topics that must be included:

Twelve of those thirteen are informational. You can satisfy them by telling someone something and having them acknowledge it, which is exactly what a checklist is good at.

Paragraph (j) is a different kind of obligation, and it's worth separating out.

Why paragraph (j) is the one that gets missed

"Instruction and demonstration of the young or new worker's work task or work process."

Two things follow from that wording.

First, it is task-specific. Not "an overview of the job" — the worker's task or work process. If someone is going to couple a trailer, transfer product, reposition a client, or commission a rooftop unit, the instruction and demonstration attach to that task. A worker with four tasks has four instances of paragraph (j), not one.

Second, it requires demonstration. Somebody has to show the work being done. Handing over a written procedure and confirming receipt is document distribution; it isn't demonstration.

This matters for how you read the rest of Part 3. It's tempting to treat 3.23 as "the generic orientation" and think of task competence as something that happens afterwards, informally. The Regulation doesn't structure it that way. Task instruction sits inside the pre-work requirement, alongside WHMIS and PPE — and under section 3.25, it's equally recordable.

WorkSafeBC's own guidance on training and orienting workers describes the sequence in plain terms: "Provide an overview of each task, including if there are any safety precautions and safe work procedures. Demonstrate and describe the task, going through the steps slowly. Observe workers on the job and check their progress."

Note where that ends. Not at explaining, and not at demonstrating. At observing.

When does section 3.24 require additional training?

Section 3.24 is short:

An employer must provide a young or new worker with additional orientation and training if (a) workplace observation reveals that the young or new worker is not able to perform work tasks or work processes safely, or (b) requested by the young or new worker.

Trigger (a) carries a quiet assumption. For observation to reveal anything, observation has to be happening. The section doesn't create a separate duty to watch people, but it is written for an employer who does — and an employer who never observes new workers performing their tasks has no mechanism for this section to fire.

Trigger (b) is the one most often left out of internal summaries, and it's the easier one to get right: if a new worker asks for more training, that request creates an obligation. It also creates a record worth keeping, because a documented "asked for more training on X, provided on Y" is strong evidence of a functioning system.

What records does section 3.25 actually require?

An employer must keep records of all orientation and training provided under sections 3.23 and 3.24.

Three things to notice.

"All." Every topic in 3.23(2), including paragraph (j), and everything provided under 3.24.

Both sections. The follow-up training is not an informal correction that happens off the books. If observation revealed a worker couldn't perform a task safely and you retrained them, that's a record.

No specifics. The Regulation does not state what a record must contain, what format it takes, or how long to keep it. WorkSafeBC's guidance says only that "you're responsible for maintaining records of the education, training, and supervision for each worker."

That silence is not permission to keep less. It means the burden of designing a record that would actually answer an officer's question — or an insurer's, or a COR auditor's — sits with you. A record that says "Orientation: complete ✓" is technically a record and practically useless, because it can't distinguish between a worker who watched a video and a worker who was observed performing the task correctly.

If you hold a Certificate of Recognition, the same gap shows up in the audit: see what a COR audit looks at in training.

Does a signed orientation checklist prove competence?

No, and it isn't designed to. It proves that a set of topics was covered with a named person on a named date. That's genuinely valuable, and WorkSafeBC publishes a Young and New Worker Orientation Checklist in modifiable Word format precisely so employers have a defensible artifact for the informational topics.

The limitation is structural. A checklist records delivery. Paragraph (j) and section 3.24 are about performance — whether instruction and demonstration happened for a specific task, and whether observation showed the person could do it safely.

Those produce different evidence:

If your file contains only the first column, the honest answer to "what records do you have for the task he was doing?" is that you don't have any.

What a task-level training record should contain

Since the Regulation doesn't specify, here's a field set that answers the questions people actually ask afterwards:

• Worker name and start date, plus whether they meet the young or new worker definition and which branch of 3.22 applies. The branch matters when the trigger was a hazard change rather than a hire.
• Procedure name and version. If the procedure gets revised, you need to know which version this person was trained on. Without a version, a record ages into ambiguity.
• Who instructed and demonstrated, with the date. This is your paragraph (j) evidence.
• Who observed the worker performing it, with the date, and the outcome. Separating instruction from observation is the single most useful thing you can do to this form, because it forces the observation step to actually occur.
• Whether additional training was provided, why, and when — the 3.24 trail, including worker-initiated requests.
• Re-check date. Not required by 3.23–3.25, but it's how the record stays meaningful for infrequent tasks, and it connects to the ongoing supervision WorkSafeBC describes: "make a point to regularly observe your workers to check that they're still following safe work procedures."

The structural change is small: one record per worker per procedure, rather than one record per worker. A fuel hauler with nine distinct procedures generates nine rows. That feels like more paperwork until the first time someone asks a narrow question, at which point it's the only thing that answers it.

A worked example

A new Class 1 driver joins a fuel distributor. His generic orientation is done on day one and the checklist is signed. Under paragraph (j), his task training covers the procedures he'll actually perform — pre-trip inspection, coupling, product transfer, spill response, winter chain-up.

Product transfer is instructed and demonstrated by the senior driver on day two. On day four, the supervisor observes him perform a transfer start to finish without prompting, and notes that he sequenced the grounding step correctly but needed a reminder on the closing paperwork. Observation revealed a gap that wasn't unsafe, so section 3.24 wasn't triggered — but the note is recorded, and a re-check is set for two weeks out.

Chain-up is a different story. It's demonstrated in October, but he won't perform it under real conditions until the first snow. The record shows instruction and demonstration complete, observation pending, and a flag against the procedure. When someone asks in January whether he's cleared for a mountain run, the file gives an answer instead of a shrug.

Common mistakes

Treating it as a hiring checklist. The 3.22 definition attaches to hazard changes, not just hires. A procedure change, a new machine, a site move or a return from long absence all create new workers.

Signing the checklist but never observing the task. The most common failure, and the one that leaves the biggest hole. Paragraph (j) and section 3.24 both point at watching someone work.

One record for the whole job. A single "trained" flag can't tell you which of nine procedures a person is actually cleared on, which is the question that gets asked.

No procedure version on the record. When the procedure changes, you can no longer tell who was trained on the current version and who wasn't.

Leaving 3.24 undocumented. Retraining after a gap is observed — or after a worker asks — is evidence that your system works. Unrecorded, it looks like nothing happened.

Assuming experienced hires are exempt. Nothing in 3.23 turns on years of experience. A 30-year journeyman new to your workplace is a new worker, and paragraph (j) still applies to your tasks, your equipment and your sites.

Where this fits with Talum

Sections 3.23(2)(j) and 3.24 describe a loop: someone experienced demonstrates the task, the new worker practises it, someone observes, and gaps trigger more training. That loop is the work Talum is built around.

Talum starts from an interview with the person who already does the task well, turns what they know into practice modules with checks, and tracks readiness per procedure rather than per course completion — which produces the per-procedure record that section 3.25 is asking for, including procedure versions and who needs to re-validate when a procedure changes.

If you want to see what that looks like on a real procedure, request a 15-minute call — usually the task where a gap would hurt most.