Quick answer
Universities and colleges update handbooks, course documents, program guides, forms and departmental PDFs on a schedule — usually all at once, usually around the same few weeks of the year.
Uploading them is not the hard part. Working out which one replaces which is.
The file you have been sent uses a department code, an academic year and an internal abbreviation. The page on your site is called something a student would understand. A safe workflow puts the new files somewhere harmless first, suggests where each one goes, keeps the uncertain ones aside for you, separates revisions from genuinely new documents, and lets you check the result afterwards.
If the same departments send you files every year, it is worth having something that remembers their abbreviations so you are not explaining them again next September.
Why higher-ed batches are so messy
A university site usually has several naming systems running at once:
- the public page titles
- department abbreviations
- course codes
- program codes
- academic years
- campus names
- whatever the admin team calls things internally.
So a file called:
BUS-UG-Handbook-26-FINAL.pdf
belongs on a page called:
Undergraduate Business Student Handbook
Anyone who works there sees that instantly. Nothing matching on filenames alone ever will.
When it happens
Document refreshes cluster around:
- the start of the academic year
- the start of each semester
- admissions cycles
- policy revisions
- accreditation reviews
- catalog updates
- orientation
- financial aid changes.
Which means the web team often gets several departmental folders in the same week.
Current document, or historical record?
Usually a replacement: the current student handbook, the current program guide, the current application form, the current departmental policy, the current syllabus template.
Usually a new publication: annual reports, archived catalogs, meeting minutes, accreditation reports tied to a specific review.
One folder often contains both, and nothing in the filenames will tell you which is which. That decision is yours, and a good batch makes you make it rather than guessing on your behalf.
Department abbreviations
Higher-ed filenames are full of shorthand:
- BUS = Business
- ENG = English
- SCI = Sciences
- UG = Undergraduate
- GR = Graduate
These are specific to your institution — “ENG” is English at one university and Engineering at another. That is exactly why they are worth teaching the plugin once rather than having it assume.
The year in the filename
Years are the tricky one.
If the page is “Current Student Handbook”, the year in the filename is noise and matching on it will only get in the way.
If the page is “2025–26 Student Handbook”, the year is the entire point.
There is no universal “ignore dates” rule that gets both of those right.
Documents that have never existed before
New courses, programs, centers and certificates appear every cycle.
A file with nowhere to go is not a failure. If you know where it belongs and there is simply nothing there yet, it should be added as a new document in the same run — and you should be able to say so on the row rather than pulling it out into a separate job.
Central forms used by every department
One central form is often linked from dozens of department pages:
- the FERPA form
- the graduation application
- the general petition form
- a central policy.
If every department should get the new version, that shared use is doing its job.
If one department needs its own variant, you have to separate them before replacing anything — otherwise one replacement changes all of them.
Getting departments to check their own rows
The person who knows whether BUS-UG-Handbook-26 is the right file is rarely a WordPress administrator.
You can export the batch, send a department the rows that concern them, and let them confirm where each file goes, which to skip, and which are new — without giving them access to the site.
When the spreadsheet comes back, everything in it is checked again before it changes anything. A spreadsheet is a way of moving decisions around, not a license to overwrite.
Example: the autumn refresh
A university receives:
- 45 program handbooks
- 30 departmental forms
- 12 policy PDFs
- 18 documents for new courses.
A safe run:
- upload all 105
- let the obvious departments match themselves
- check the programs that have been renamed
- mark the 18 new-course files as new documents
- look at the central shared forms before touching them
- back up and replace the current documents you approved
- publish the new ones
- open a few department and program pages and check.
Where Pro helps
Institutional vocabulary is the same every year, which is exactly what makes it worth remembering.
Pro remembers your department abbreviations, ignores “FINAL” and the approval dates on the end of every filename, keeps the corrections you already made, and holds all of it against that site — so next September’s batch starts with less to fix than this one did.
The free plugin will get the same batch done. It just will not remember any of it next time.
What this does not do
WP Bulk Replace replaces files. It does not certify PDF accessibility, confirm that a document has been academically approved, check policy compliance, or manage records retention. Those stay with the institution.
Accreditation and catalog cycles
Some documents are tied to an accreditation period or a catalog year, and need to stay available as that edition even after a newer one exists.
The pattern that works is a stable “current handbook” page plus a separate archive, updated deliberately rather than as a side effect of a batch.
More than one campus
Multi-campus institutions often have near-identical handbooks with campus-specific differences.
Make sure the campus is part of what you are matching on. A shared “student-handbook” in the filename should not be allowed to override which campus it belongs to.
Summary
Higher education is a strong case for batch replacement because the pages are stable and the filenames are not.
The pattern: upload → match on department and program → check the exceptions → handle the new documents → look at the shared forms → replace → verify.
Related: School district document updates · Bulk replace PDFs · Association document updates