Quick answer
If several pages deliberately link to the same document, replacing that one file updates all of them at once. For a current form, handbook, policy or guide, that is exactly what you want.
The risk is that the same file is also used somewhere you did not mean to touch.
So before replacing a shared document, find out what else points at it, and whether all of it should change. If one page needs to keep the old version, that replacement should stop until you have sorted it out.
Why it happens
WordPress makes reusing a file easy, and everybody does it.
A single PDF can be linked from several pages, from posts, from custom fields, from a resource index, from the footer, from a page-builder module, from the navigation, and from emails and other websites you have no control over.
Which is efficient. It also means “replace the file on this page” quite often means “replace the file everywhere”.
When that is the point
A site has one current membership application, linked from the Join page, the Membership page, the FAQ, the Resources page and the footer.
All five are meant to show the same current form.
Replacing the shared file is the best possible outcome — one change, five pages correct, nothing to keep in step.
When it is a problem
Now a policy PDF is linked from the Current Policies page and from the 2025 Archive.
The current page should change. The archive should not.
Technically those two situations are identical: two pages, one file. What differs is what you meant, and nothing about the link itself can tell a plugin which one you are in.
Where to look
Checking properly means looking beyond the page you have open: the page content, block attributes, stored references to the Media Library entry, direct URLs pasted into a page, custom fields, plugin data and page-builder structures.
Which of those apply depends on the site. It is why the “Attached to” column is never the whole answer.
Why “outside the batch” is the important line
Say your batch has 100 intended replacements, and one of the files is also used by a page that is not in the batch at all.
That outside page matters because it proves the job you approved does not describe everything the job will do.
Which is worth stopping for:
This row will not run until you decide about the other page.
A small warning next to a destructive action is not the same thing. In a list of 100 rows, nobody reads it.
What you can do about it
Include the other pages on purpose. If they should get the new file too, say so and let it run.
Give one of them its own copy. The archive page keeps the old file; the current page gets the new one.
Send the new file somewhere else. Sometimes the match was simply wrong.
Skip it. Leave the existing file alone for now.
Publish it as a new document. If what arrived is a new edition rather than a correction, replacing was never the right action.
Example: a benefits guide on 12 pages
An employer publishes one annual benefits guide, linked from 12 department pages.
The new year’s guide is approved and should replace it everywhere. Twelve references, and the replacement is still exactly right, because all twelve were meant to be the same thing.
Now add an archived “2025 Benefits” page pointing at the same file.
That single page changes the decision. The current document and the archive need their own copies before anything is replaced.
Check again before the write
Somebody can add a link between you reviewing the batch and the batch running.
For anything destructive, the check is worth repeating immediately before the write rather than only when the batch was first built.
Summary
Shared files are not dangerous. Shared files nobody checked are dangerous.
Before replacing, answer one question: what else uses this, and should all of it change?
If you are not sure, stop until somebody decides.
Related: Shared media files · Check where a file is used · Replace PDF without breaking links