Quick answer
Policy documents need three things kept apart: getting the document approved, replacing the file on the site, and keeping the previous versions.
If a page represents the current policy, replace the file behind it and every link keeps working.
If previous versions have to stay available, publish them deliberately as their own items.
Undo in WP Bulk Replace is there for when you replace the wrong file. It is not a compliance archive, and it should never be treated as one.
Current policy, or policy history?
Replace: the current privacy policy, the current safety policy, the current employee policy manual. The page means “whatever the policy is now”.
Publish as new: “Policy effective January 2025” and “Policy effective January 2026” are two documents, and both need to exist.
Approval comes first
A policy update may need legal sign-off, board approval, a compliance review, an effective date, an accessibility check or a translation.
None of that is the plugin’s job, and it should not be able to bypass any of it. Its job starts when the approved file is ready to go on the site.
Policies linked from many pages
Policies get linked from everywhere — the footer, the employee portal, the careers page, the contact page.
If all of those should show the current version, one replacement handles it. If one page has to keep an older version, separate them before you replace anything.
Keeping the link stable
A stable current-policy URL means fewer broken references in emails, staff portals, public resource pages and printed material — the places you cannot easily go back and edit.
Example: a policy refresh
An organization receives:
- 12 revised current policies
- 5 policies that have never been published
- 3 historical amendments.
A safe run: upload everything, map the 12 replacements, set up the 5 new ones, publish the amendments separately as history, check anything shared, replace what you approved, and verify.
What undo is and is not
Undo helps when the wrong file was uploaded, approval changed at the last minute, or the replacement was simply a mistake.
It cannot tell you which version was legally in force on a given date. If you need to be able to answer that, you need a records system, not a backup.
Effective dates
A policy is often approved today and effective next month.
Nothing about a file tells a plugin when it should go live, and it should not guess. The approved file and the date it goes public both come from your own governance process.
A pattern that works
Publish one current policy on the public site, and keep the signed and approved historical versions in whatever records system you actually use.
That keeps the public links simple and stops anyone mistaking a replacement backup for a retention record.
Example: a 20-policy annual review
After legal review:
- 12 policies changed
- 5 are unchanged
- 2 are new
- 1 has been retired.
So the batch replaces 12, publishes 2 as new, leaves 5 alone, and removes or redirects the public route for the retired one.
Twenty files in the folder does not mean twenty overwrites, and a tool that assumes it does is the problem.
The failure nobody notices
A replacement can pass every technical check and still be the wrong revision of the right policy.
For anything sensitive, make “open it and check the effective date” part of the process rather than trusting that the file with the right name was the right file.
Policies marked superseded
Some organizations need an old policy to stay public but clearly labeled as superseded, with a link to the current one.
That is not a replacement — it is a page in its own right, and a backup of a replaced file is no substitute for it.
A folder is not all one thing
A policy refresh usually arrives as one folder containing revised policies, unchanged policies, retired policies and new ones.
Those are four different actions. A file being in the folder is not, by itself, an instruction to overwrite anything.
Check the page, not just the file
After publishing, check the title, the effective date, the revision number, the public URL — and the page copy around the link.
A correct PDF sitting under a paragraph that still describes last year’s policy is still wrong.
Policies come in families
A policy is often a main document plus an appendix, a procedure and a related form.
If the appendix changes, that does not mean the whole family should be replaced. Keep each one distinct so a revised appendix cannot overwrite the policy it belongs to.
Summary
Use WP Bulk Replace as what it is: a careful way to replace files.
It is not a policy management system, it does not approve anything, and its backups are not a retention record.
Related: SDS document updates · Annual reports · Employee handbook updates