Do Employees Need to Re-Sign a Policy After an Update, or Every Year? (US and Canada)
Short answer: most laws require you to give employees the current policy, not to collect a new signature for every update. Ask for one anyway when a change matters: a new rule, a changed procedure, a new person to report to. Typo fixes don't need one. A few rules set a schedule, such as New Jersey's yearly Gender Equity Notice acknowledgment.
Free policy version log
A spreadsheet with one row per policy version: what changed, whether it needs new signatures, who must sign, when it went out, how many have signed, and where the old version is kept. It flags overdue sign-offs and gives each version a review date. Blank log, filled-in example and a how-to tab. No email needed.
Download the log (.xlsx)This page is part of our guide to employee handbook and policy acknowledgments. It is general information, not legal advice.
When an update needs new signatures
A signed acknowledgment proves that a person received one version of a policy. Once the text changes in a way that matters, that signature no longer covers what the policy says. A simple test: would an employee have to do anything differently, or could they now be disciplined for something the old version allowed?
- Ask for new signatures: a new rule or a rule removed, a changed procedure (how to report a problem, who to report to, deadlines), new consequences, a new benefit or eligibility rule, or a policy that now covers people it didn't before.
- No new signatures needed: typos, formatting, a new logo, a corrected phone number or address. Post the new version, say what changed, and note the decision in your version log so you can explain later why nobody re-signed.
- Only some people: if the change affects one group, such as people who work remotely or drive company vehicles, you can ask only them. Record who was asked and why.
Give every version its own number and effective date, printed on the policy itself, and keep the old versions. A signature on "the harassment policy" with no version proves much less than a signature on "version 3.0, effective January 5".
Every year, or only when it changes?
Outside the rules below, a yearly re-sign is your choice. Many employers collect a fresh acknowledgment of their core policies (harassment, safety, code of conduct) once a year, often with the annual training, because it gives every current employee a recent, dated record without anyone having to work out who signed which version. Others re-sign only when a policy changes. Either works if you can show who received which version and when.
United States: rules that set a schedule
- No federal law requires employees to re-sign policies. The reason to keep acknowledgments current comes from harassment law: an employer's defense to some harassment claims depends on showing it took reasonable care to prevent harassment, and in Faragher v. City of Boca Raton, 524 U.S. 775 (1998), the city lost partly because it had failed to disseminate its policy to the employees involved. Proof that each person received the current version is part of that showing.
- New York requires every employer to give employees its sexual harassment prevention policy at hire and at every annual training (Labor Law §201-g). Handing out the current version with each year's training covers both.
- Massachusetts requires employers with six or more employees to give each employee an individual written copy of the sexual harassment policy at hire and every year (G.L. c. 151B, §3A).
- New Jersey employers with 50 or more employees must give the Gender Equity Notice at hire, every year by December 31 and on request, and get each employee's written or electronic acknowledgment that they received and read it within 30 days (N.J.S.A. 34:11-56.12). Every employer also gives each employee a copy of the Law Against Discrimination poster every year by December 31, and employers with 30 or more employees worldwide the Family Leave Act poster (N.J.A.C. 13:8-1.2 and 13:8-2.2). See our New Jersey December 31 notices guide.
- Healthcare (HIPAA). When a covered entity makes a material change to its privacy policies or procedures, it must train each workforce member whose functions are affected within a reasonable period after the change takes effect, and document that training (45 CFR 164.530(b)(2)). Policies and that documentation are kept for six years from when they were created or last in effect, whichever is later (45 CFR 164.530(j)(2)).
Ontario and federally regulated employers in Canada
- Workplace violence and harassment policies must be reviewed as often as necessary, and at least once a year (Ontario OHSA s. 32.0.1(1)(c)). The Act doesn't ask workers to sign them; it requires the employer to give each worker information and instruction on the contents of the policies and programs (ss. 32.0.5(2) and 32.0.8). When a review changes the policy, handing out the new version and recording that you did is how you show workers have the current contents. The written health and safety policy is also reviewed at least once a year (s. 25(2)(j)).
- Disconnecting from work and electronic monitoring policies. Employers with 25 or more employees on January 1 must have both written policies, each showing the date it was prepared and the date of any change. When an existing policy changes, each employee must get a copy within 30 days of the change (Employment Standards Act, ss. 21.1.2(2) and 41.1.1(3)). Keep a copy of every version for three years after it stops being in effect (s. 15(8.1) and (8.2)).
- Federally regulated employers (those covered by the Canada Labour Code) must review their workplace harassment and violence prevention policy at least once every three years and after any change to one of its elements, and make it available to all employees. Employees take the harassment and violence training within three months of starting, at least every three years after that, and again after the training is updated (Work Place Harassment and Violence Prevention Regulations, SOR/2020-130, ss. 10(3), 10(4) and 12(4)).
What to keep as proof
- Every version of each policy, with its version number and effective date. Don't overwrite the old file: it's the text earlier signatures refer to.
- A one-line note of what changed in each version, and whether you asked for new signatures.
- For each person: which version they received, when and how, and their signed acknowledgment of that version.
- For people who haven't signed yet: when the new version was sent to them, and your reminders.
How long to keep signed policy acknowledgments. Need the sign-off wording? Our policy acknowledgment form has a line for the version and effective date.
Where doing it by hand breaks
The first round of signatures is the easy part to organise. Updates are where paper and spreadsheets fall behind:
- Mixed versions. After two updates, some people have signed version 1, some version 2, a few version 3, and the tracker only says "signed".
- The old text disappears. Someone saves the new policy over the old file on the shared drive, and you can no longer show what an employee signed in 2025.
- New hires get the wrong one. The onboarding packet still has last year's PDF.
- Chasing. Re-sign rounds go to everyone at once, and following up with the last few people takes longer than sending the policy did.
If someone won't sign the new version, record that instead: what to do when an employee refuses to sign.
Updating a policy in Ethica
Upload the new PDF to the policy and give it a new version number and effective date; once anyone has signed the current version, Ethica asks for a new number before it accepts a new file. Everyone who already signed keeps their record of the earlier version, including a copy of the exact file they signed. Anyone who hasn't signed yet, and every renewal, gets the new version. For a policy that doesn't repeat, assign it again to the people who signed the old version and each gets an email with the new one; for a policy set to repeat every year, the next round goes out with the new version.
Employees read the policy in their browser and sign with one click, with no account. Ethica reminds anyone who hasn't signed, and the record shows which version each person signed and when. The activity log shows who changed the version and when, and the spreadsheet export lists the version next to each acknowledgment. Each employee needs an email address. Replacing the file removes its Spanish and French versions, so upload the new translations at the same time.