Give a shared file a name that carries context

A shared filename should carry the context that disappears when the file leaves its folder. Give the next person enough information to recognise the work without opening several candidates.

Choose a small set of meaningful parts: project, document purpose and a date or agreed version. Use an unambiguous date order consistently. Avoid adding private client or personal information when a file may circulate beyond the team. Check the systems involved for naming restrictions before adopting unusual punctuation.

Name the decision, not the mood

“Final final new” describes frustration rather than status. Use a clear version and keep approval status in the agreed location. If a file is an alternative proposal, name the alternative rather than pretending it is a later revision of the same idea.

Try the filename in a crowded downloads folder. Can someone distinguish it from last week's file? Is the most useful part still visible in a narrow list? Long descriptive sentences can hide the distinguishing word at the far end.

Agree on the convention with the people exchanging files. Renaming only your own copies can create confusion if others still refer to an earlier name. Preserve references when changing an established set. The best convention is small enough to use consistently and specific enough to survive outside its original folder.