๐พ Castle Rock Kennels
A staff waiver is the wrong tool โ here's what actually protects the kennel
We have a customer waiver. The natural next thought is "we should have a staff waiver too." But under BC law a staff waiver is the wrong instrument entirely. This is a side-by-side of what a staff waiver would (not) do, versus the Staff Agreement & Onboarding Acknowledgement that animal-care employers actually use.
The short version. A "staff waiver" โ a document where a worker agrees not to hold the kennel responsible if they're hurt at work โ is void and unenforceable in British Columbia. The Workers Compensation Act says every agreement to waive WorkSafeBC benefits is void, and it bars an employer from making a worker indemnify it. Worse than useless: it gives the kennel paper that does nothing, and demanding it can itself be treated as bad faith.
What actually protects the kennel is a different kind of document โ a Staff Agreement & Onboarding Acknowledgement. Its protective value isn't a release; it's a written record that the worker was informed of the real hazards, received safety training, and agreed to confidentiality, systems rules, and an animal-welfare code of conduct. That record โ paired with dated training logs โ is what holds up.
The category error
A customer waiver and a staff waiver are not the same kind of document.
They feel parallel โ both are "people who interact with the kennel sign something." But they aren't. A customer is a counterparty: they legally can release the kennel from liability for their own dog, and BC case law tells us exactly how to word that so it holds.
An employee cannot do the same thing. The Workers Compensation Act makes any agreement to waive workers' compensation benefits void โ full stop. So the staff document can't be a waiver at all. It has to be a different instrument: an acknowledgement-and-agreement that documents informed risk, training, and conduct. Same goal (protect the kennel), completely different tool.
Side by side
The same seven questions, asked of each instrument.
โ The wrong tool
A "Staff Liability Waiver"
Legally enforceable in BCโ Void
Protects if a worker is injuredโ Nothing
Risk it createsโ Bad-faith exposure
Customer-data confidentialityโ Not covered
Systems / PIN misuseโ Not covered
Animal-welfare conductโ Not covered
What it actually deliversโ False security
โ The right tool
Staff Agreement & Onboarding Acknowledgement
Legally enforceable in BCโ Yes
Protects if a worker is injuredโ Documents OHS duty met
Risk it createsโ None
Customer-data confidentialityโ Explicit (PIPA)
Systems / PIN misuseโ Explicit acceptable-use
Animal-welfare conductโ Explicit code of conduct
What it actually deliversโ Real, defensible record
What you might assume โ and what's actually true
For each thing people expect a "staff waiver" to do: why it doesn't, and what the Staff Agreement does in its place. Clause references (ยง) point into the canonical document.
1"If a worker is bitten, a waiver means they can't come after us."
Why that's wrongA worker's WorkSafeBC benefits cannot be waived โ the Workers Compensation Act makes "every agreement to that end void." A signed waiver changes nothing about an injured worker's entitlements.
What actually protects the kennelยง2The Staff Agreement records that the worker was informed of the hazards (bites, knockdowns, zoonotic disease) and received safety training. That record is what shows the kennel met its legal duty if WorkSafeBC ever looks.
2"Signing a waiver shifts the risk onto the worker."
Why that's wrongAn employer cannot make a worker indemnify it for workers'-compensation liability โ the Workers Compensation Act expressly prohibits it. The risk legally cannot be shifted this way.
What actually protects the kennelRisk is managed the way the law intends: through WorkSafeBC coverage plus the documented training and supervision the kennel is already required to provide. The Agreement is the proof that happened.
3"A waiver covers us if a worker leaks customer data."
Why that's wrongA liability waiver is silent on confidentiality entirely โ it's about injury claims, not information handling. Staff see customer names, addresses, payment info, dog records, the whole database.
What actually protects the kennelยง3An explicit confidentiality clause: customer personal information and business data are kept confidential, used only for work, never copied or retained โ and it survives the end of employment. The kennel's PIPA obligations flow down to staff in writing.
4"A waiver stops a worker from sharing their PIN or altering records."
Why that's wrongNot addressed at all. A waiver has nothing to say about staff PINs, the staff app, the till, or who can change a booking or a payment record.
What actually protects the kennelยง4An acceptable-use clause: credentials are personal and not shared, records may not be altered or falsified outside normal duties, and customer/business data is accessed for work purposes only.
5"A waiver protects the animals in our care."
Why that's wrongA liability waiver says nothing about how animals are handled โ it's the kennel disclaiming responsibility, not the worker committing to a standard of care.
What actually protects the kennelยง5An explicit animal-welfare code of conduct: humane handling only, no abuse or neglect, follow each dog's care/feeding/medication instructions, and a duty to report suspected mistreatment (including to the BC SPCA).
6"A waiver makes sure they follow our procedures."
Why that's wrongA generic waiver doesn't reference the kennel's actual operations at all โ it can't bind a worker to procedures it never names.
What actually protects the kennelยง8A policy-acknowledgement clause ties the worker to the kennel's written shift manuals and policies โ the morning/afternoon/night procedures that actually run the business โ and to following the current version as they're updated.
7"A waiver gets our keys and devices back when someone leaves."
Why that's wrongNot addressed. Nothing in a liability waiver speaks to kennel property, keys, fobs, or access credentials.
What actually protects the kennelยง6A property clause: keys, devices, uniforms, and materials remain the kennel's, and all of them โ plus all access credentials โ are returned and stopped on separation.
8"Existing staff are already covered โ they've worked here for years."
Why that's wrongLongevity isn't a record. Right now there is no signed acknowledgement on file for anyone โ new or existing. If a question ever arises, "they've been here a long time" proves nothing.
What actually protects the kennelยง4 (rollout)The rollout has every existing staff member sign once as a back-fill, and every new hire at onboarding, before working unsupervised โ so the record exists for the whole team.
9"Once it's signed, that's the protection."
Why that's wrongEven the right document, signed, is only half of it. A signature that the safety training "happened" is weak if there's no record the training actually happened.
What actually protects the kennelยง4 (rollout)The Agreement is paired with dated training records โ who was trained, on what, when. The signed Agreement plus the training log together are the protective package; the signature alone is not.
โ One honest caveat โ carried over from the canonical document
Employment documents are more legally sensitive than the customer waiver was โ they engage the Employment Standards Act, the Workers Compensation Act, the Human Rights Code, and PIPA. The Staff Agreement is drafted to a defensible standard, but it carries a stronger recommendation: have it reviewed by a BC employment-law practitioner before anyone signs.
- Confirm each worker's actual employee vs. independent-contractor status โ the whole "no waiver" reframe assumes employees.
- Confirm the business's WorkSafeBC registration is current โ the entire approach assumes that coverage is in force.
The honest bottom line
A staff waiver isn't a weaker version of the right document โ it's the wrong document. It would hand the kennel paper that does nothing and could backfire.
The Staff Agreement & Onboarding Acknowledgement is what animal-care employers actually use, and what actually holds up: it documents informed risk, real training, confidentiality, systems use, and an animal-welfare code of conduct โ a genuine, defensible record. Pair it with dated training logs, get one round of BC employment-law review, and have every current and future staff member sign it.