A Rename Log for Shared Files: Change a Filename Without Breaking the Links Your Team Already Sent

Renaming a file looks harmless. Then a customer says the link in last month's email no longer works, or a page shows a missing image. This article proposes a small rename log: a short routine you complete before changing a name, so you know where the old name is used. It is a process option, and the details will depend on the tools you use.

The inputs you need

Before renaming anything, write down:

The current name and the proposed name.
Why the change is wanted, in one line.
Where the file is known to be referenced: web pages, emails, documents, spreadsheets, printed material.
Whether the file was ever shared outside the team.
Who owns the file and who must approve the change.
The date and the person making the change.

The branching decisions

After filling in the log, choose the path.

The file is internal only and nothing references it: rename it, record the new name, finish.

The file is referenced in places you control: rename it, then update each reference, and open every one afterwards to confirm it works.

The file was shared outside the team: do not rename it. Instead, create a new correctly named copy, keep the old one in place, and decide whether the old one should show a note pointing to the new one or simply be retired later.

You cannot find all references: treat it as shared outside. Keep the old file.

The reason for renaming is cosmetic: ask whether it is worth the risk at all. A slightly untidy name that works is often better than a tidy one that breaks something.

A hypothetical worked example

Imagine a small training business with a file named "price-list-final-v2". The owner wants to call it "course-prices-2027". The log shows it is linked from two web pages and was attached to several emails sent to customers. Because it went outside the team, the owner does not rename it. They save a copy as the new name, update the two web pages to point to it, and leave the old file in place with a short line at the top saying the current list is the newer file. Three months later they review whether anyone still opens the old one, and only then decide whether to remove it.

Stop conditions

Stop and ask the owner if the file is part of a signed agreement, an invoice, or anything a customer might need to find later. Stop if you are unsure who has copies. Stop if the rename would be done in bulk across many files at once; do one first, check the results, then continue in small batches.

Small acceptance checks

After any rename or copy, confirm:

Each known reference opens the file when clicked.
The old name, if kept, either still works or clearly points onward.
The log records old name, new name, reason, date and person.
A colleague can find the file using only the new name.
Nothing was deleted in the same step as the rename.

Keep the log in one place the whole team can reach, even if it is only a simple table. The value is not the table itself but the pause it forces. If the pause feels too heavy for small internal files, restrict the log to files that have ever left the team, and rename the rest freely.