Quick answer
A board document library is mostly an archive, not a replacement job.
Agendas, minutes, packs, exhibits and reports belong to a particular meeting and should normally be published as new documents. Replacing is right when you are correcting the same meeting’s document — a corrected agenda before the meeting, or draft minutes becoming approved minutes at the same link.
A batch still helps, because one meeting can produce dozens of PDFs. The thing to keep straight is which files are new records and which are revisions of something already posted.
What one meeting produces
An agenda, the board pack, draft minutes, approved minutes, financial statements, staff reports, committee reports, exhibits, public comments, resolutions, presentations and supplementary documents.
Now multiply that by several boards and committees, every quarter.
Why the date is not noise
A meeting is a dated event, and its documents belong to it:
- September 18, 2026 Agenda
- September 18, 2026 Pack
- September 18, 2026 Approved Minutes
None of those should ever be replaced by October’s. The date is not filename clutter to be ignored — it is what the document is.
Where replacing does belong
A corrected agenda. The board posts an agenda, then spots an error before the meeting. The page still means “Agenda for September 18”. Replacing the file there is exactly right.
Draft minutes becoming approved minutes. Some sites deliberately use one page for “Minutes — September 18” and replace the draft with the approved version after the vote. That works if your publication policy says so.
A “current board pack” link. Some sites have one stable link to the latest pack alongside the archive. That gets replaced every meeting while the historical pack is published separately.
The shape of the job
Before the meeting: publish the agenda and the pack, replace corrected versions if you need to, check the links.
After the meeting: publish draft or approved minutes according to your policy, add the new records, and update any “current meeting” link.
Always: leave previous meetings exactly as they are.
Example: 28 files from one meeting
A quarterly board meeting produces an agenda, a pack, 12 department reports, 8 exhibits, 5 committee documents, and draft minutes later.
A useful run:
- upload the 28
- assign all of them to the right meeting
- match the known report pages if the site has meeting fields set up
- publish the new records
- replace only corrected versions of files already posted for that same meeting
- confirm earlier meetings are untouched.
Which is almost the opposite of a monthly report batch, where nearly every row is a replacement.
The filenames are no help at all
They arrive as agenda-final.pdf, packet-v3.pdf, finance.pdf, committeeA.pdf.
Without knowing which meeting they belong to, those names mean nothing. The matching has to use the meeting date, which board or committee it is, what kind of document it is, and where it is going — the filename alone will not get you there.
Public and private materials
Associations and charities often have public board documents and restricted committee materials.
WP Bulk Replace does not manage access. Whatever handles your member area carries on deciding who can see each document.
Undo is not your archive
Meeting records often have retention obligations.
Undo is there for mistakes. Which historical documents stay published is your records policy, and it needs to exist independently of any plugin’s backups.
Draft and approved minutes
Organizations differ on whether draft minutes are published at all.
If your site moves one page from Draft Minutes to Approved Minutes, replacing is right. If both have to stay separately available, publish them separately.
That decision comes from the board’s publication policy, not from how similar two filenames look.
Correcting something already approved
A board may correct minutes that have already been approved and published.
If the corrected version replaces the public copy, decide whether the site should also say it was corrected, and whether the superseded copy stays available.
The plugin handles the file. What you disclose is a policy decision.
What to record against each document
The governing body or committee, the meeting date, the type of document, whether it is draft or approved, and the revision.
Record those and you stop depending on filenames like packet-final2.pdf.
Summary
Board sites should think archive first.
Replace for corrections, for draft-to-final transitions, and for a stable “current pack” link.
Publish new for new meetings, dated minutes, historical packs and meeting-specific exhibits.
A batch helps organise the set. It should never erase meeting history because that was quicker.
Related: HOA documents · Club and nonprofit documents · Replace vs publish new