Treadstone Associates
Case File · Fall & Scaffold Safety

A scaffold inspection log stops a shutdown

Anonymised, illustrative composite. A BC officer asked a prime contractor for ten shifts of scaffold inspection records during a routine visit — and what the log showed, including a documented defect and fix, kept the structure in service.

Treadstone Associates · Updated 2026

At a glance

  • • BC institutional retrofit site; multi-level scaffold serving roughly 34 workers a day across three trades.
  • • OHSR s.13.13: the employer must ensure scaffolds are safe “regardless of who erected” them — a duty independent of the erecting subcontractor.
  • • OHSR s.13.3: inspection required “before use on each shift, and after any modification.”
  • • The prime contractor kept a daily pre-shift log beyond the bare regulatory minimum: inspector, defects found, corrective action, sign-off.
  • • A WorkSafeBC officer requested the past 10 shifts of records; the log showed all 10 inspected and one defect (a missing guardrail pin) fixed same-day, in 25 minutes.

The situation

A scaffold subcontractor erected a multi-level system serving three separate trades on a retrofit project. Under BC's OHS Regulation, erecting the scaffold does not end the prime contractor's own responsibility for it: OHSR s.13.13 states plainly that “the employer must ensure that scaffolds used by workers are in a safe condition and are able to withstand the load, regardless of who erected the scaffold.” The prime contractor treated that duty as active, not delegated, and built a daily pre-shift inspection log — inspector's name, defects found, corrective action, sign-off — well beyond what the bare regulation requires.

The problem

A WorkSafeBC officer on-site for an unrelated site-wide visit asked to see the scaffold's inspection records for the past ten shifts. Without a log, the honest answer would have been that inspections were happening but nothing proved it — exactly the gap that lets an officer treat unverified compliance as no compliance at all.

With the log, the answer was specific: all ten shifts inspected, and on shift six, a missing guardrail pin identified and corrected before any worker used that section. OHSR s.13.3 requires that “any condition that might endanger workers must be remedied before the equipment is used” — the log did not just claim compliance with that rule, it evidenced it.

The numbers

10 shifts logged, 10 inspected. 1 defect found (a missing guardrail pin, shift six). Time from discovery to corrective sign-off: 25 minutes, per the log's own timestamps, before the affected section returned to use. Workers served by the scaffold on a typical shift: roughly 34, across the framing, glazing and mechanical trades sharing it.

The rule that decided it

Section 13.13 is the reason the prime contractor could not simply point at the erecting subcontractor's own records: the safe-condition duty sits with “the employer,” full stop, independent of who built the structure. Section 13.3's before-use, after-modification inspection cycle is what the daily log was actually built to satisfy — and it is worth noting general scaffolds carry no separate statutory logbook requirement in Part 13 itself (that formal record duty applies to elevating platforms and swing stages under s.13.22); this firm's log went further than the regulation strictly demanded, and that margin is what an officer with no other evidence in front of them could actually rely on.

What it would have cost otherwise

Part 13 does not publish a named enforcement instrument for an unverifiable scaffold — this is a reasonable inference from s.13.3's own remedy-before-use duty, not a separately cited figure — but an officer who cannot see evidence of a working inspection system has little reason to take an inspector's word that one exists, and a reasonable response is to require the equipment taken out of service until an inspection can be independently confirmed. On a scaffold serving three trades and roughly 34 workers a day, even a short stand-down ripples across every crew waiting on it.

The outcome

The officer's visit ended in a compliance conversation rather than a stop-use order. The log itself then paid a second dividend: reviewing it as a whole, rather than one shift at a time, showed the same guardrail-pin failure had happened once before, three weeks earlier, on a different level of the same structure — a pattern invisible in any single day's entry.

A documented, dated log is the same underlying fix that mattered in how a contractor passed COR on the second attempt — a different jurisdiction, the same principle: a programme that exists but cannot be shown scores, and is treated, like a programme that does not exist.

The tell

The recurring pin failure traced to one supplier's guardrail-pin design, which vibrated loose under this scaffold's particular loading pattern more than the other hardware on site did. Nobody would have connected the two isolated incidents without the log putting both entries in front of the same person at the same time; the firm swapped that supplier's pins across the whole structure rather than waiting for a third failure to confirm the pattern.

Takeaways

  • • OHSR s.13.13 makes scaffold safety the employer's duty ‘regardless of who erected’ it — a prime contractor cannot delegate this to the erecting subcontractor's own records.
  • • Section 13.3 requires inspection before each shift and after any modification, with remediation before use — a daily log is how a firm proves that happened, not just claims it.
  • • General scaffolds carry no statutory logbook requirement in Part 13 itself; going beyond the bare minimum is what gave the officer something concrete to rely on.
  • • A log's value compounds over time: reviewed as a pattern, not a single entry, it caught a recurring supplier defect a one-off inspection never would have connected.
  • • An officer with no visible evidence of a working inspection system has little basis to trust a verbal assurance — documentation is the actual compliance, not a record of it.

See where AI pays off first in your business.

A 30-minute call is enough to tell you whether AI pays for itself here.