Quick answer
Before you update an annual report, decide what the page actually means:
- “our current annual report”, or
- “the 2025 annual report”.
If it is a single “Current Annual Report” link, replace the file behind it and every existing link keeps working.
If the site keeps a year-by-year archive, publish the new report as a new item and leave the previous years exactly where they are.
If you are dealing with reports from a dozen departments at once, a batch makes it manageable: it maps the filenames, gets the department and year right, and lets you check the result.
The two publishing models
One stable “current report” link
The page says:
Download our current annual report.
The link means “whatever the newest approved report is”. Replacing the file is exactly right.
A year-by-year archive
The page lists:
- 2024 Annual Report
- 2025 Annual Report
- 2026 Annual Report
Each one exists in its own right. The 2026 report must not overwrite 2025.
Both at once
Plenty of organizations want a stable current link and a full archive.
That means the new report needs two separate things done: published into the archive as 2026, and set as the file behind the current-report link. Do them deliberately — it is not one action.
Reports from different departments
A university, charity or public body might publish:
- a finance report
- a foundation report
- an athletics report
- individual department reports
- a compliance report.
The year on its own does not identify any of them. Matching has to take the department or report title into account as well, or annual-report-2026.pdf could land almost anywhere.
Links that live outside your site
Annual reports get linked from press releases, donor emails, board pages, other people’s websites and people’s bookmarks.
For a stable current-report page, keeping the URL the same saves you chasing all of those every year.
Undo is not an archive
Undo is there for when you replace the wrong file. It puts it back.
It is not how you keep last year’s report available to the public. If history matters, publish the old editions on purpose.
Example: 35 departmental reports
A university receives 35 reports.
A safe run:
- upload them
- match on department and report type, not just the year
- check the departments that have been renamed
- work out which are current-report links and which are archive entries
- replace the current ones
- publish the year-specific ones into the archive
- check both.
Check the cache
If the current-report URL has not changed, anything caching it may still be handing out last year’s report. Purge that URL and confirm.
Decide before you start
| Question | If yes | If no |
|---|---|---|
| Should last year’s report stay public? | Publish as new | Replacing is probably right |
| Does an external link mean “the current report”? | Keep the same URL | A new URL is fine |
| Is the year part of what the document is? | Treat the year as identity | The year is just filename noise |
| Is the report linked from several pages? | Check all of them first | Normal review is enough |
| Does a department keep its own archive? | Publish into that archive | Use the central current link |
Running through that turns an ambiguous folder into a set of decisions you have already made.
Where this goes wrong
Overwriting last year’s archive. Something matches on “Annual Report” and ignores the year. The replacement succeeds perfectly and destroys a year of history.
Uploading a new file for a current link. The 2026 report is on the site and looks right, while the “Current Annual Report” page and every emailed link still serve 2025.
Departments that got renamed. “Advancement” became “Development”; the foundation changed its public name. That is worth teaching the plugin once rather than guessing at every year.
A stale CDN copy. The file is replaced correctly and donors still download last year’s report because something in front of your site never noticed.
Worth recording
For each report, keep enough to answer: which page, which report, which year, replacement or new publication, what happened, the public URL, and whether you can still undo it.
Next year’s cycle is much easier when last year’s is written down.
Several audiences, one title
Some organizations publish different annual reports for donors, regulators, the board, the public and regional programs.
They all have “Annual Report” in the title, so the audience has to be part of what you match on. A file called annual-report-final.pdf is genuinely dangerous when five different reports could claim it.
Timing
A report is often approved well before it is meant to go live.
A replacement tool has no idea about your embargo date and should not pretend to. When it goes public is your publishing process, not the plugin’s.
Check what search engines see
Annual reports get indexed directly, so afterwards confirm that the current-report URL serves the new file, the archive pages still point at the right years, and no old direct URL has been quietly repointed at something else.
Summary
Annual reports are a publishing decision before they are a file operation.
Ask whether the page means “current” or means a particular year, and replace or publish accordingly.
Related: Replace vs re-upload · Bulk replace PDFs · Policy document updates