There are two files in the folder: handover-final.pdf and handover-final-2.pdf. The second is newer. That is the only thing its name explains.
It might contain a correction. It might be an abandoned alternative. A person returning to the folder has to open both to find out.
Keep the name small.
A practical file name can carry a project, an object, and a date: handover-introduction-2026-10-14.pdf. It is sortable and tells the reader what to expect. It does not try to carry the review history.
Words such as “approved” are useful only if their meaning is agreed. If two people can approve different parts of a document, the label needs more context than a file name can comfortably hold.
Put the reason beside the file.
A short note does a different job: “Shortened the opening page; moved the references to their own index.” That is enough to distinguish the new version from the previous one.
Keep that note in the project introduction, a change log, or the message that accompanies the file. The location matters less than being able to find it again.
A better name reduces the first guess. A sentence about the change saves the second.