Policy Version Control in Canada: What Employers Must Do to Prove Which Policies Applied

Most Canadian employers update policies regularly but cannot prove which version was in effect at any given time. Learn what must be tracked to maintain defensible policy records.

Introduction

An employee was hired in 2023. At the time, the company's vacation policy offered two weeks of paid vacation after one year of service. In 2025, the policy was updated to three weeks after two years.

The employee, now past the two-year mark, requests three weeks. The employer believes the original policy applies. The employee believes the updated version does.

Neither side can prove which version was in effect when the employee reached the eligibility threshold. The employer updated the policy — but overwrote the previous version. There is no record of when the change was made, no version history, and no evidence that the employee received or acknowledged either version.

This is not a policy problem. It is a version control problem. And for most small and mid-sized Canadian employers, it is entirely unaddressed.

When This Applies

Policy version control becomes a compliance issue whenever:

If any of these describe your current process, your ability to defend your policy position during a dispute is significantly weakened.

What Must Be Tracked

Maintaining defensible policy records requires tracking the following elements for every policy document:

Without these elements, an employer cannot reliably demonstrate which policy governed a specific situation at a specific time.

Sources

Why This Matters Under Canadian Employment Standards

Canadian employment standards legislation already requires employers to maintain specific records, and these obligations reinforce why version control matters:

While these provisions do not all explicitly require "policy version control," they establish a clear expectation: employers must maintain accurate, retrievable records that can demonstrate what applied and when. An employer who cannot produce the version of a policy that was in effect at a specific time is at a significant disadvantage in any dispute.

Sources

Example: The Vacation Policy Dispute

A small manufacturing company in British Columbia updates its vacation policy annually. Each update is saved over the previous file. The company does not maintain archived copies, does not assign version numbers, and does not track which employees received which version.

An employee hired in 2022 disputes their vacation entitlement after a policy update in 2024. The employer believes the 2022 version applies based on the employee's hire date. The employee argues the 2024 version should apply because it was the most recent policy communicated to them.

Under BC's Employment Standards Act, employers must provide employees with at least 2 weeks of vacation after 12 consecutive months of employment, and at least 3 weeks after 5 consecutive years (section 57). However, the employer's own policy may offer additional entitlements beyond the statutory minimum — and in a dispute about those additional entitlements, the employer's ability to prove which version was in effect is critical.

The employer cannot produce the 2022 version. There is no record of when the 2024 version was distributed. There is no acknowledgment on file for either version.

The employer's position — that the earlier version governs — is effectively unverifiable. Without version records, the dispute becomes a matter of competing claims rather than documented fact.

Sources

What Employers Must Do

To maintain defensible, traceable policy records, employers should implement the following practices:

  1. Assign a version number and effective date to every policy document — even minor updates should be reflected in the version history. This creates a clear timeline of what changed and when.
  2. Maintain archived copies of all previous versions — never overwrite a policy document without preserving the prior version. Employment standards recordkeeping requirements across provinces reinforce the importance of maintaining accessible historical records.
  3. Track distribution — record when each version was sent, shared, or made available to employees, and through which method. This establishes that the employee was informed.
  4. Collect employee acknowledgment — this can be a signature, an electronic confirmation, or a logged acceptance through an internal system. An employer who can show that an employee received and acknowledged a specific version is in a much stronger position than one who cannot.
  5. Document changes between versions — a brief changelog that identifies what was added, removed, or modified provides clarity during reviews or disputes.
  6. Ensure records are retrievable — archived policies, distribution logs, and acknowledgment records must be accessible when needed, not buried in old email threads or deleted shared drives. Under Ontario's ESA, employers must retain required records and make them available for inspection.

Sources

Common Mistakes

The following practices are common among Canadian employers and create significant version control gaps:

Sources

What Is at Risk

When policy version control is absent, employers face the following risks:

A workplace policy must not only exist — it must be provable. Employers must be able to demonstrate which version was in effect, when it took effect, who received it, and who acknowledged it. Without version control, even a well-written policy becomes difficult to enforce and nearly impossible to defend.

Sources

Related Reading

Canada Policy Manual generates province-specific policy manuals with built-in version tracking, so you always know which policies are current and which jurisdiction's rules they reflect. See what is covered for your province at free policies.

Sources

Key Takeaways