Insights

Policy Governance · 12 min read

Show Me the Trail: Version Control for HR Policies

Sid Varma

“Which version did we use last quarter?”

HR policy version control means every change to a policy is kept as a version, with who saved it and when, who approved it and who acknowledged it, so you can answer that question with a link instead of a search through email threads, chat messages and a file called Final-FINAL.pdf.

This post is part of our guide to policy governance, which covers who writes, approves, owns and reviews each policy as a company grows. Auditors and Legal will not accept guesswork, and what they ask for is who changed what, when, plus who approved it and who acknowledged it. This guide shows what that trail looks like in AllyMatter, how to see a policy’s version history, compare two versions, restore an older one, and put the habits in place.

I care about this because of a moment at my last company. Our NDA went through five versions, and which one a person had signed depended on when they joined. An auditor sampled an employee who had not signed it yet, because they had joined while it was being rewritten. A system that can show which version applied on a given day, and who confirmed it, removes that kind of surprise.

Key takeaways

  • Every saved version records who saved it and when, and Admins and the policy’s Editor can open any older version while everyone else sees only the current approved one.
  • Version Compare shows every word added and removed between two versions, so approvers and Legal review the change instead of rereading the whole policy.
  • Restoring puts an older version’s text back as a new version, and that version goes through approval again like any other change.
  • The audit log lists versions, restores, approvals, rejections and each acknowledgment by name, filters by date range or person, and exports as a PDF or CSV.

What does version control for HR policies need to record?

Picture a PTO accrual table that changed mid-quarter while Legal tweaked the harassment language in a chat thread, and now someone asks you to prove which version was in force on March 15, who approved it and whether employees acknowledged it. Without a proper history you are hunting through screenshots, email timestamps and file metadata, which is slow and brittle. Here is the minimum a system should capture on every policy change, and where AllyMatter keeps each item.

What to recordWhere it lives in AllyMatter
Version numberEach saved version gets its own number, and the minor or major choice at Save Version labels how big the change was
Who saved it, and whenThe Version History list shows the person and the date for every version
What changedVersion Compare shows every word added and removed, with a count of each
ApprovalEach approver, each step and the date, plus the reason for any rejection, in the document’s audit log
Who it applies toTags decide who can see the policy and who is asked to acknowledge it
AcknowledgmentName, email, date, time and the version the person confirmed
A way backA Restore button on every older version, which creates a new version that goes through approval

These live with the policy itself, so there is no separate spreadsheet to keep in step. Our guide to policy management software explains how this loop of writing, approving, sending and acknowledging fits together, and this post follows one thread of it, the history.

How do you see a document’s version history and who changed what?

Open the policy, choose the three dots menu and select Version History. You get a list of every saved version with its number, the person who saved it and the date, and the current version is marked Current. Admins and the policy’s Editor can open any older version to read exactly what the policy said at that time, which is what Legal needs for sign-off and what an audit needs when it asks what language was in force on a date.

I have spent more time than I would like in meetings where the first twenty minutes went on establishing which version of a document everyone was looking at. Nobody was debating the content or discussing improvements, we were just working out whether we were all reading the same thing.

The three dots menu on a Remote Work Policy, listing Move, Version History, Download PDF and Delete Document, with Version History highlighted.
Version History sits in the three dots menu of every policy.
The Version History list for a Remote Work Policy, with v1.3 marked Current above v1.2, v1.1 and v1.0, each showing who saved it and the date, and a Restore button on each older version.
The Version History list: each version with who saved it and when, the current one marked, and a Restore button on every older version.

People who work from the policy see only the current approved version. The history is there for the Editor and Admins rather than being the main view, which keeps everyone else from wandering into old text while the complete lineage stays available.

When you save a version you choose minor or major. That choice labels the change for anyone reading the history later, so a typo fix and a change of policy look different, and it never skips approval or acknowledgment.

How do you compare two versions to see what changed?

Version Compare puts two versions side by side and marks every word removed and every word added, with a count of each and the number of sections changed. Approvers can use it before they decide, so they review what moved instead of rereading the whole document, and Legal can do the same when a tweak was made in a hurry.

The Version Compare screen for a Remote Work Policy, comparing version 1.2 with version 1.3 side by side. A summary line reads 13 words added, 13 words removed and 2 sections changed, and a Version History list on the right shows v1.3 as Current above v1.2, which has a Restore button.
Version Compare: two versions side by side, a count of the words added and removed, and the Version History list on the right.

How do you restore a previous version of a policy?

Even careful teams make edits they later reconsider. Open the Version History, find the version you want and select Restore. The text of that version goes back into the document as a new version with its own number, and the version it replaced stays in the history, so nothing is overwritten and the lineage stays intact.

I have watched teams spend an entire afternoon reconstructing a document from memory because someone’s well-intentioned edits made it worse and nobody had a clean copy of the previous version. Putting it back the way it was should have taken seconds.

Because a restored version is a new version, it still goes through approval before anyone sees it, and only once it is approved does it become the version people work from. Restore is switched off while an approval is running, so finish or withdraw that approval first, and nothing goes out to people automatically afterward: the Editor presses Distribute and chooses whether to notify or ask for acknowledgment again.

That is the difference between a controlled restore and the manual kind, where someone pastes in an old copy from a downloads folder and wipes out changes that were correct. Here you go back to an exact, recorded version, and the record of the restore is written to the audit log.

Does every policy change need approval?

Yes. Approval is mandatory for every policy, and every new version goes through it, however small the change, because even a comma can change what a rule means. Email approvals do not age well, since people leave and inboxes get archived, so the approvals belong where the policy lives.

An approval workflow can have several steps in order, the document is locked while it is under review, and a rejection has to carry a reason saying what to fix. Everyone else keeps reading the last approved version in the meantime, and each approver, step and date is recorded in the document’s audit log. Our guide to document approval workflows covers setting these up.

One document, two approvers, in order: the policy is sent, locked while it is in review, and approved step by step.

There is no separate effective-date field. A version takes effect when it is approved, so the approval date is the effective date, and you approve a change on the day you want it to start. Once it is approved and the Editor distributes it, the Editor can ask everyone who holds the policy’s tags to acknowledge the new version, and a pending request on the older version is replaced, so nobody is chased for a version that no longer applies. Our post on re-acknowledgment after a policy update explains why each version needs its own confirmation.

How do you prove which version was in force on a given date?

Start in the Version History and find the version that was approved before that date. Its approval and its date are written to the audit log, and because the approval date is the effective date, that version applied from then until the next approval. Open it to read the full text, then export the document’s audit log as a PDF or CSV to show the approvals and acknowledgments around that date.

The acknowledgment record names the person, with email, date, time and the version they confirmed, and the audit log lists each one as a named line. Between the version, the approval and the acknowledgments you can show what the policy said, who approved it and who was told, and you answer with a link and an export rather than a reconstruction from old emails.

How do you track every change to a policy?

Each policy has its own log, which Editors and Admins open from the log icon in the document’s top menu, and Admins also have a workspace Audit Log that covers every document. The entries cover the document being created, each version saved and each restore, approvals and rejections with their reasons, distributions, each acknowledgment by name, tag changes, folder moves and deletion.

You can filter the log by date range or by person and export it as a PDF or CSV, filtered or in full. Editors and Admins can export a document’s log, and only Admins see the workspace log. That one export is what you hand Legal: what changed, who approved it, who acknowledged it and when.

One document’s audit log, with the date range and person filters and the Export button, showing who did what and when.

How do you put this in place without a reorganization?

You need consistent habits and the right settings, not a reorg.

Put each policy in as its own document. Convert long PDFs and email chains into one document per policy, with a short summary, who it applies to, the details and the exceptions.

Give every policy an Editor and the right tags. The Editor owns the policy and tags decide who can see it, so a new version reaches the same audience without anyone rebuilding a list. Approvers need to hold the policy’s tags too.

Set an approval workflow once. Build it in Administrative Settings and pick it from the dropdown in each policy, for example HR, then Legal, then the head of the department.

Choose minor or major on purpose. Use the label the same way on every policy, so anyone reading a history can tell a wording fix from a change of rule.

Practice a restore. On a test policy, save a version, open the previous one and restore it, then watch the new version go to approval. It shows you how the lineage looks before you need it.

Set review dates. A review date alerts the Editor, and if nothing changed the Editor re-approves the policy, which records that someone judged it still valid and does not ask anyone to acknowledge it again. If something did change, it becomes a new version and goes through approval.

Export the log once. Pick a key policy, such as PTO and sick leave, export its audit log and check that it answers who, what and when before an auditor asks.

Habits that prevent version drift

  • Title and scope lines: name policies plainly and add a line saying who the policy applies to, and keep any rule that differs by state in a clearly labeled addendum that counsel has checked.
  • One source of truth: no policy copies in shared drives; link to the policy instead of attaching a file.
  • No email approvals: approve in the system so names and dates are captured as part of the work.
  • Acknowledgments in the system: track them where the policy lives and export the log when asked, instead of keeping a spreadsheet.

Questions about HR policy version control

Do we need approval for every edit?

Yes. Every new version of a policy goes through approval, however small the change, because even a comma can change what a rule means. The minor or major choice when you save a version is a label that helps people reading the history, and it never skips approval.

Can we keep people from wandering into old versions?

Yes. People who work from a policy see only the current approved version. Admins and the policy’s Editor can open any older version, so the full history is there for governance without being the main view for everyone else.

What is the difference between version history and the audit log?

Version history lists the versions of one policy and lets you read, compare and restore them. The audit log is the wider record of events on the document, including versions saved, restores, approvals, rejections with their reasons, distributions and each acknowledgment as a named line.

What if Legal wants a copy in email anyway?

Export the document’s audit log as a PDF or CSV and send that. It gives Legal a record to keep while the policy itself stays in one place.

How do acknowledgments fit into the trail?

Each acknowledgment records the person’s name, email, date, time and the version they confirmed, and the audit log lists it as a named line. When a new version goes out, a pending request on the older version is replaced, so people only confirm the version that applies.

Can an auditor see the trail without access to everything?

Yes. An auditor can be given Viewer access to the workspace and sees only what their tags allow, and you can hand over an exported audit log for the policies they sample.

Three scenarios

An honest read on whether to put this in place:

If you are under 30 employees and policies rarely change, a Drive folder with strict version naming will hold for a while, and the trail pays off once policies change often or an audit lands.

If you are 30 to 200 employees and you can no longer say quickly who approved the last change to a policy or who acknowledged it, this is the moment, and AllyMatter is what we built for exactly this.

If you are 200 or more employees, work across several locations, or sit in a regulated industry such as healthcare, finance, legal or government contracting, a trail you can export is not optional, and we would start with AllyMatter. Our guide to compliance management software shows where this fits in the wider picture.

Version control is not about tracking changes for the sake of it. It is about having defensible evidence when compliance, Legal or an auditor asks the uncomfortable questions, so that when someone asks which version you used last quarter, you answer with a link.

Setting up AllyMatter takes about half an hour, and on yearly plans our migration service moves a large library for you, usually within a week and often sooner. You can also look around first in our sandbox.

Start your 30-day free trial of AllyMatter. No credit card to start, and a 30-day money-back guarantee if you subscribe and change your mind. Free migration.

Compliance note: This article is informational, not legal advice. Consult your counsel for the requirements that apply to you.

Try AllyMatter free for 30 days

  • No credit card needed
  • 30-day money-back guarantee
  • Free migration on yearly plans