All articles
Compliance and conflicts6 min read

Policy change management: from approved policy to updated procedures

Policy change management is the process of carrying an approved policy change through to every document that repeats it: procedures, FAQs, onboarding packs, templates and regional versions. Approving the new policy is the easy part. The risk sits in the old wording that stays live elsewhere, because people, and the AI assistants that read your drives, keep finding it.

Anchoris teamNotes from the people building Anchoris

Most organisations have a clear process for writing and approving a policy. Far fewer have one for the step after: making sure nothing else still says the old thing. That gap is where outdated guidance, failed audits and wrong answers come from.

Why approved changes don't reach every document

A policy rarely lives in one file. The travel policy is in the handbook, but it's also summarised in the finance FAQ, quoted in a slide deck for new joiners, adapted in a regional version and pasted into a booking template. When the policy changes, the owner updates the handbook. The other copies were written by other people, at other times, and nobody has a list of them.

The common causes are ordinary:

  • Local copies. A team downloads a policy, adapts it for a project and saves it in its own folder. That copy becomes the team's working guide.
  • Summaries and FAQs. Helpful shortcuts written once and never revisited.
  • Templates. Contract and form templates that embed a figure from the policy, such as a payment term or approval limit.
  • Mergers and acquisitions. Two sets of policies arrive in the same environment, and both stay searchable long after one has been chosen.
  • Filename versions. "Policy_final_v2" and "Policy_final_v3_USE_THIS" sit side by side because nobody was sure which could go.

What happens when the old version stays live

Three things go wrong, in rising order of cost.

People lose time. Someone finds two versions, stops, and asks HR or legal which one applies. Multiply that by every employee who hits the same question.

People act on the wrong version. Not everyone stops to ask. Someone follows the old approval limit or the old safety step in good faith, and the organisation owns the outcome.

Audits find it. An auditor who finds an outdated procedure still in circulation sees a control that isn't working, even if the policy itself was updated correctly.

AI makes all three more likely. An assistant answering from your drives retrieves the passages that best match a question. The old version and the new one can match equally well, and the assistant has no way to tell which is current. It answers from whichever it finds, in the same tone either way. For more on that mechanism, see Why does AI give wrong answers? Often it is the documents.

A policy change management process that reaches every document

1. Record exactly what changed

Write the change as specific facts: "expense claims must be submitted within 30 days (was 60)", "purchases over €5,000 need two approvers (was €10,000)". Specific old values are what you'll search for in the next step. "Updated expenses policy" is not searchable.

2. Find every document that repeats the old version

Search your shared drives for the old values and the key phrases from the old policy, not just the policy's title. Look in FAQs, onboarding material, slide decks, templates and regional folders. Note each document, its location and who can edit it.

3. Decide what happens to each one

For every document you found, choose one action:

  • Update it to the new wording, if it still has a purpose.
  • Replace the copied text with a link to the policy, so it can't drift again.
  • Retire it, by moving it to an archive or to trash, if it no longer serves a purpose.

Linking beats copying. Every pasted copy of a policy is a future conflict.

4. Give each action to a named person, with a date

"Priya, please update the onboarding deck to the 30-day rule by Friday" gets done. "Teams should check their documents" does not. Rank the actions by how many people can open each document, and start at the top.

5. Check again after the change

A few weeks later, search for the old values again. Some copies will have been missed, and some new ones will have appeared because someone copied from an old document. This check is what turns a one-off update into a process that holds.

Make ownership and review dates part of the policy

Two habits stop the next change going the same way. First, every policy names an owner who is responsible for its accuracy and for finding its copies when it changes. If the owner leaves, ownership moves to a named successor rather than lapsing. Second, every policy has a review date. A policy nobody has reviewed in two years may still be right, but nobody can say so with any certainty.

Where Anchoris fits

Anchoris checks your documents in Google Drive and SharePoint for the issues a policy change leaves behind: contradictions between documents, outdated and expired content, people named as owners or contacts who have left, unfinished placeholders, broken links and duplicates. It ranks each issue by how many people can open the document, suggests who should fix it, and fixes it at the source with approved workflows (move, rename or move to trash), with every run logged. You get a quality score from 0 to 10 for your documents, and first results within an hour.

You choose which drives Anchoris can reach, and nothing changes without your approval. It works alongside the assistant you already use, whether that's Copilot, Gemini, Claude or Glean: fix the source once, and every assistant that reads it answers correctly.

See which documents still repeat your old policies.

Book a demo

Frequently asked questions

What is policy change management?

It's the process of carrying an approved policy change through to every document that repeats the policy, including procedures, FAQs, templates and regional versions, so the old wording is updated, replaced with a link or retired.

Why do outdated policy documents create compliance risk?

People can act on the outdated version in good faith, and auditors who find old procedures still in circulation see a control that isn't working. The risk is not that the policy is old, but that nobody can tell which version applies.

How do I find every document affected by a policy change?

Search your drives for the specific old values and phrases, not just the policy title. Check FAQs, onboarding material, slide decks, templates and regional folders, and note who can edit each document you find.

How often should policies be reviewed?

It depends on the policy and your industry. What matters most is that each policy has a named owner and a review date, and that every change triggers a search for the documents that repeat it.

Do we need to move all our policies into one system?

No. What matters is that each policy has one approved version, that other documents link to it rather than copy it, and that copies left over from earlier versions are found and retired.

Next article

AI readiness checklist: 8 signs your company's knowledge is ready for an AI assistant

Read next

More from the blog

Compliance and conflicts
Compliance and conflicts7 min read

Conflicting procedures: how to find documents that disagree

Two procedures, two answers, both official. How conflicting information builds up, where it hides, and a method to find it before your AI assistant does.

Guides
Guides9 min read

How to find duplicate files in Google Drive

Google Drive has no one-click duplicate finder. Four manual methods, where they break down, and what it takes to stop copies coming back.

Guides
Guides11 min read

The anatomy of a documentation audit: what to look for

Most audits end as a 400-row spreadsheet. The four things a useful audit looks for, and how to keep its findings from decaying.