Treadstone Associates
Article · 9 min read

Contractor safety prequalification packages

A contractor's prequalification file gets built around price and past projects, and the safety section gets treated as a formality — right up until it's the section that fails the submission.

Treadstone Associates · Updated 2026

Key takeaways

  • • CCDC 11, the Contractor's Qualification Statement, “offers a standard format for contractors to provide information about their company, capacity, skill, and experience” — safety record is one named component, not a separate document.
  • • COR®'s scoring rule is fixed nationally: a minimum 65% on every individual audit element and 80% overall, so one weak element fails an otherwise strong audit — the average across elements isn't what's tested.
  • • IHSA is the authority having jurisdiction to grant COR® in Ontario, and the certificate is explicitly “a pre-qualification requirement for many contractors working in and out of the province.”
  • • No published source gives a COR® fee or renewal cycle — IHSA's own page directs cost questions to the certifying body directly rather than publishing a figure.
  • • A prequalification failure isn't always about missing paperwork — a growing firm can fail on headcount alone, the moment it crosses a threshold like Ontario's 20-worker JHSC trigger, without anyone connecting the dots to why the file suddenly reads differently.

Two different kinds of evidence go into a construction prequalification package, and they get reviewed differently. One is financial and experiential — can this firm actually deliver the work. The other is safety-specific — does this firm run a compliant site — and it has its own standard form, its own scoring rule, and its own way of quietly failing a growing firm.

What CCDC 11 actually asks for

CCDC 11 is the standard Canadian disclosure form, and its own description is direct: it “offers a standard format for contractors to provide information about their company, capacity, skill, and experience”. In practice that means company detail (legal structure, financial and insurance references, health and safety record, and the value of work completed in the current and past four years), the key office and site personnel proposed for the project, and a project list demonstrating relevant experience.

CCDC 29 exists on the other side of the same process — it's written for the procurement authority (owner, consultant, construction manager or design-builder) rather than the contractor, and explains how to determine whether pre-qualification is necessary in the first place, compares pre-qualification types, and sets out best practices for Requests for Qualifications — including how CCDC 11 fits into that process.

The safety-specific evidence inside the broader file

Within CCDC 11's health-and-safety component, the concrete evidence a reviewer is actually looking for is: current COR® status and score if the firm holds one, a current WSIB or WorkSafeBC clearance certificate, and the claims-cost and injury-frequency history behind how those claims actually feed a firm's premium rate. A file that states “strong safety record” without any of these three is making a claim the reviewer has no way to verify against the standard form's own structure.

COR: what the score actually gates

IHSA's COR page states the scoring rule without qualification: “with one common audit instrument utilized across Canada, the national standard is clear: minimum 65% in each element and an overall audit score of 80%”. That dual test means an otherwise excellent audit — strong on eight of nine elements — still fails if the ninth element scores below 65%, because the pass condition is both thresholds together, not an average across elements.

The same page states plainly that COR® “is currently being used across Canada and is a pre-qualification requirement for many contractors working in and out of the province and on public- and private-sector projects” — which is the reason a GC's prequalification package asks for it at all: it's not a nice-to-have credential, it's frequently the gate itself. For the certification's own history and how the 65/80 rule became the national standard, the glossary entry on COR covers the definition.

Why a strong file still gets refused

Headcount, not paperwork quality, is the failure mode one case worth reading in full walked through: a growing Ontario electrical trade contractor kept failing prequalification for the same reason twice, before anyone connected it to the fact the firm had crossed from 14 to 27 regularly-employed workers over eighteen months — passing through Ontario's 20-worker JHSC threshold along the way. A firm that grows past that line without standing up a compliant committee has a real, checkable gap in its file, regardless of how complete every other section reads.

There's a size exception worth knowing on the construction side specifically: OHSA s.9(1)(a) exempts a constructor at a project expected to last less than three months from the joint committee requirement altogether, whatever the constructor's regular headcount. The case above turned on the firm's own regular workforce crossing 20 workers, not on any single short job — the two triggers are different, and a reviewer checking a file needs to know which one actually applies.

That's the structural risk in treating prequalification as a one-time submission rather than a file that has to stay accurate as the firm itself changes — the safety section can go stale even when nothing about the firm's actual safety practice has gotten worse.

What you genuinely cannot find published

IHSA's own COR page gives the scoring thresholds and states pre-payment is required for an audit review, but “for information regarding costs, contact cor@ihsa.ca” is the extent of the published guidance. Don't quote a renewal cycle or a fee figure to a client or a reviewer — direct the question to the certifying body (cor@ihsa.ca) rather than inferring one from adjacent programmes or other provinces.

Worked example: a COR audit that fails on one element

Say a firm's COR audit scores 91% on management leadership, 88% on hazard assessment, 84% on training, 79% on inspection, and 62% on incident investigation — five elements, an unweighted average around 81%. On the average alone, this reads as a pass against the 80% overall threshold. Applying the actual dual test: the 62% on incident investigation falls below the 65% per-element floor, which fails the audit outright regardless of the 81% average or the 80%-plus overall score the other four elements would otherwise support.

The fix isn't distributed effort across all five elements — it's targeted at the one element below 65%, since raising a 91% to a 95% does nothing for a failing audit while the 62% sits uncorrected.

Common questions

Is a COR® certificate mandatory to bid on public construction work?

IHSA's page confirms COR® functions as “a pre-qualification requirement for many contractors working in and out of the province and on public- and private-sector projects,” but doesn't state it's universally mandatory on every public contract. Confirm the specific requirement in the tender or RFQ document rather than assuming COR® is always a hard gate.

Does a firm need to disclose a past OHSA conviction on CCDC 11?

CCDC 11's own description names health and safety record as a required component of the standard disclosure, without publishing the specific fields required for a conviction disclosure — the actual CCDC 11 form text is the authoritative source for exactly what's asked, since CCDC's general conditions and forms are sold rather than published free.

How is COR® different from a WSIB or WorkSafeBC clearance certificate?

They test different things. COR® is a safety-management-system audit against a national scoring standard; a clearance certificate is an insurance-standing document confirming the firm is registered and in good standing. A firm can hold a valid clearance without ever having pursued COR®, and a lapsed clearance doesn't affect an existing COR® score.

See where AI pays off first in your business.

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