When must a BC employer answer a joint committee recommendation?
**If a British Columbia joint health and safety committee sends the employer a written recommendation *with a written request for a response*, the employer generally must answer the committee in writing within 21 days of receiving the request.** Workers Compensation Act section 39 says the answer must accept the recommendation or give reasons for not accepting it. If a full response is not reasonably possible in that time, the employer must still send a written explanation of the delay and indicate when it will respond. The law provides routes for a committee co-chair to report rejection or an unreasonable delay to WorkSafeBC.
The trigger is specific. A concern raised verbally in a meeting, an item in ordinary minutes or an informal suggestion may need prompt safety action under other duties, but section 39's formal response process begins when the committee sends a written recommendation accompanied by a written request for response. Do not use that distinction to ignore hazards. Section 39(7) states that the provision does not relieve the employer of other OHS obligations. An immediate unsafe condition needs immediate control, whether or not the committee has sent a formal letter.
The live Canadian joint committee guide covers committee purpose and provincial thresholds. This guide is for the narrower BC workflow often called the “21-day letter”: preparing a clear recommendation, recording the receipt date, responding substantively and escalating a dispute if necessary.
What should the committee send?
Start with the hazard or safety concern, the evidence considered and the control or action the committee recommends. State why the proposed measure is expected to reduce risk. If the committee has already discussed alternatives, record them. Identify the workplace, date, committee and contact co-chairs. Then explicitly request a written response from the employer. Keep proof of when and how the employer received it because the 21-day period runs from receipt, not from a later management meeting or the date someone logged it in a spreadsheet.
A recommendation should be concrete enough that the employer can accept or reject it with reasons. “Improve forklift safety” is less actionable than “install a physical barrier at the marked pedestrian crossing used during loading, and revise the route before the next shift change,” supported by inspection notes and observations. That example is illustrative; the right control depends on the workplace's assessment. A committee does not need to wait for an injury to recommend a safer system.
The committee's own rules of procedure should describe how recommendations are approved, signed, delivered and recorded. Preserve the original letter and any supporting reports. If a workplace has several committees, address the recommendation to the employer responsible for that workplace and identify which committee sent it. The process should be easy enough to use without special legal drafting.
The employer's 21-day response
Under section 39(2), the employer must respond in writing within 21 days by either indicating acceptance or giving reasons for not accepting the recommendation, subject to the delay provisions. An acceptance should identify who will implement it, the interim control, expected timing and how completion will be checked. The statute does not prescribe that project-plan format, but a bare “accepted” with no action owner is weak management practice.
If the employer does not accept it, the response should explain the actual reasons. Perhaps a proposed guard interferes with emergency access, an engineering review finds a different control more effective, or the suggestion cannot address the risk as described. State the evidence and alternative control where one exists. A generic “too expensive” or “not practical” with no analysis is unlikely to help the committee understand how workers remain protected. The committee can then discuss whether the response addresses its concern.
Calendar the response from the received date and give the task to someone who can obtain input from operations, workers and technical advisers. If the employer learns that a full response will not be reasonably possible within 21 days, section 39(4) still requires, within that period, a written explanation of why and an indication of when the answer will be provided. A silent extension is not enough. Record the explanation and the revised response date; keep working on the underlying hazard in the meantime.
No part of this process should postpone a legally required control. If a machine lacks guarding or a worker faces an immediate unsafe condition, the employer must address the risk under its existing OHS duties, regardless of whether the committee recommends a longer-term redesign. Section 39 is a communication and accountability mechanism, not permission to expose workers for 21 days.
What happens if the committee disagrees?
If the employer does not accept the recommendation, a co-chair may report the matter to WorkSafeBC under section 39(3). The Board may investigate and attempt to resolve it. This is a route available to a co-chair, not an automatic enforcement outcome or guarantee that WorkSafeBC will adopt the recommendation.
If the employer sends a delay explanation but the committee is not satisfied that it is reasonable, a co-chair may report that under section 39(5). WorkSafeBC may investigate and, by order, establish a deadline for response. Keep the original recommendation, proof of receipt, delay notice, committee discussion and any communications with the Board. The record makes clear what was requested and when.
A committee can also pursue ordinary discussion before escalation where doing so does not allow an uncontrolled hazard to continue. Ask which facts are disputed, whether a site walk or specialist assessment would help, and what interim measure can protect workers. The statutory route exists to ensure a rejected or deferred recommendation does not disappear into correspondence.
A simple record and decision workflow
- Log the concern and evidence. Keep inspection, incident, worker report or other source information with the recommendation.
- Approve a specific written recommendation. Confirm it represents the committee's decision under its rules of procedure and includes a written request for response.
- Deliver and date it. Record the employer's receipt date and assign the 21-day due date.
- Control immediate risk. Implement necessary interim controls without waiting for the formal response.
- Investigate the proposal. Obtain operations, engineering, worker and supplier input as appropriate. Separate the safety decision from a narrow budget approval.
- Respond in writing. Accept or give reasons for not accepting. If a full response is not reasonably possible, explain the delay in writing within the 21 days and give an expected response date.
- Review and follow up. Put the response on the committee agenda, track actions to completion and keep evidence. If rejected or delayed unreasonably, record whether a co-chair reports it to WorkSafeBC.
This workflow also supports the annual BC joint committee evaluation under Regulation section 3.26, which asks whether the employer met section 39 requirements for written recommendations requesting written responses. A complete recommendation log will make that review evidence-based.
Example: a loading-bay separation concern
At a distribution centre, the committee observes pedestrians crossing a forklift route while loading is underway. It recommends a guarded alternative walkway, revised traffic markings and a temporary marshal until the change is installed. The committee sends a written recommendation and written request for response, and records that the employer received it on 5 October.
Management immediately restricts the crossing while it assesses the engineering proposal. It writes back within 21 days accepting the need for separation but proposing a different barrier location because the original route would obstruct emergency access. The response explains the alternative, assigns an owner and dates the installation. The committee reviews the plan and follows up on the actual control. If management had instead been unable to get an engineer's report in time, it would have needed to send a written delay explanation and expected response date within the 21 days, while maintaining interim protection.
The example distinguishes the statutory response from the underlying OHS duty. A timely letter does not make an unsafe loading bay safe; a safe interim restriction does not remove the obligation to respond to the committee's formal request.
Common mistakes
- Assuming every meeting comment starts a 21-day clock. Section 39 needs a written recommendation and written request for response.
- Using the letter process to defer urgent controls. Other OHS duties continue.
- Counting from an internal forwarding date. Track when the employer received the request.
- Replying verbally. The required response or delay explanation is in writing.
- Rejecting without reasons. The employer must explain why it does not accept the recommendation.
- Sending a silent extension. Explain the delay and indicate when the full response will be provided, within the original 21 days.
- Treating a response as completion. Track the accepted control and test whether it works.
- Assuming WorkSafeBC must adopt the committee position. The Act says the Board may investigate or attempt to resolve the matter.
Where Complys may fit
The verified Complys Canada site describes OHS records. A buyer evaluating Canadian OHS compliance software can ask whether the deployed setup can store recommendations, receipt evidence, response deadlines, written decisions and corrective-action follow-up. This article does not claim Complys automatically calculates a legally binding deadline, sends statutory responses, decides whether a delay is reasonable or resolves a committee dispute. The employer and committee must operate the actual process.
Read the current Workers Compensation Act section 39, agree on a delivery and receipt method, and keep one recommendation log that records both the response and the safety outcome.
For the related Complys product, see Ohs Compliance Software. This guide is general information, not legal advice; verify current requirements against the official sources linked above.