Quick answer
Public-sector sites handle large recurring sets of forms, policies, notices, agendas, reports and guides — usually from several departments at once.
A safer way to update them: upload the files without touching anything live, let the plugin suggest where each one goes, keep the uncertain ones aside, check anything used on more than one page, back up before replacing, record what happened, and keep undo available for individual files.
That saves publishing time. It does not do accessibility review, records retention, legal approval or any other compliance process, and it should not be presented as though it does.
The documents this covers
Permit forms, public notices, agendas, policy documents, application packs, annual reports, program guides, departmental publications.
Why replacing blindly is risky here
Public documents tend to have direct external links, bookmarks, references in print, retention requirements, effective dates and accessibility obligations.
One wrong match does not affect one page. It affects everyone who had the link.
Current, or a dated record?
Replace: the current permit form, the current policy, the current application.
Publish as new: board minutes, a dated notice, an annual report, an ordinance.
A single batch routinely contains both, and the workflow has to handle both without you splitting the folder in two.
Department naming
What a department calls itself internally is rarely what the public page calls it.
Those abbreviations are worth teaching the plugin once, because the same eight departments will send you files again next year.
Central forms
One central form is often linked across many department pages.
If every department should get the new version, that shared use is doing its job. If one needs its own variant, split them before replacing.
Example: an annual public-document refresh
An agency uploads:
- 40 current forms
- 12 policy updates
- 8 new publications
- 20 historical meeting documents.
The important part is that those four are separated before anything runs, not discovered afterwards.
What this does not certify
WP Bulk Replace does not check WCAG or PDF accessibility, legal sufficiency, records retention, or procurement and security compliance. Those stay where they already are.
Decide what each document is, first
Before the batch runs, every file should be one of:
- a current form or policy
- a dated public record
- something published for the first time
- a document being retired.
That decision matters far more than how similar two filenames look.
Old links live a very long time
Government PDFs get indexed directly, and people find them through search years after the page linking to them changed.
Where a URL is meant to be “the current form”, keeping it stable is what stops people downloading a 2019 permit from a search result.
Where a URL is a dated public record, keeping the old content exactly as it is is the correct behavior.
Example: eight departments, ninety files
A public agency receives 90 files from 8 departments. A useful outcome:
- 48 current forms replaced
- 22 new dated records published
- 10 documents published for the first time
- 6 unchanged
- 4 held back because the file is shared or the match is unclear.
That is a great deal more useful than “86 uploaded”.
Keeping a record
For public-sector work it should be easy to see what changed, when, which document, what the result was, and whether undo is still available.
That is an operational log. It is not a records-management system and should not be counted as one.
Give each department its own queue
When several departments contribute to one batch, group the exceptions by department.
Planning checks the planning forms. Parks checks the recreation forms. The clerk checks the public records. That is much safer than one site administrator guessing at ninety filenames from eight departments they do not work in.
New programs, new documents
A new program produces documents that have never existed on the site.
Those should show up as “this is new, where does it go?” rather than as failed matches — and you should be able to place them without inventing a fake replacement.
Corrections that need to be visible
Some public records require a published correction notice rather than a quiet replacement.
That is a decision for your publishing policy. The plugin can make the file change easy; it should not imply that changing it quietly is always the right thing to do.
Documents in more than one language
Agencies often publish the same form or notice in several languages.
Language has to be part of what identifies the document. A Spanish form must never be matched onto the English page just because the form number is the same.
For multilingual sets, check the language, the form number, the department and the effective date together.
Check the important links afterwards
After a big batch, a short check on the high-traffic forms catches stale caches, broken direct links, a form that landed on the wrong department’s page, and accidental 404s.
That is an operational check, not formal QA.
Summary
Make the technical work reviewable, and keep the governance where it belongs — outside the plugin.
Related: Municipal permit forms · Policy documents · Board meeting documents