Digital Skills Hub
Menu

How to Create a File Naming System a Small Team Can Follow

Person typing on a laptop at a wooden desk
Photo via Pexels

Create a file naming convention that makes project documents easier to sort, identify and hand over.

Start with how people search

Ask a colleague to find the last approved workshop agenda with only the shared folder and two minutes. Notice which information they use first: the event date, the project name or the document type. Make that the first field of your naming convention.

Choose a consistent pattern

For date-first work, use 2026-11-14_workshop_agenda_v03.docx. The four-digit year and two-digit month and day let ordinary alphabetical sorting follow the dates. For multiple projects in the same location, put the project first if people search by project most often.

Separate working versions from published copies

Number exported snapshots only when other people receive them or need to cite them. If a shared editor already preserves version history, keep one clearly named working file. When the agenda is approved, save a copy in the approved folder and record the approval date wherever your team tracks decisions. Avoid filenames such as agenda-final-final-new.docx.

Pilot the convention before renaming an archive

Try the pattern on five new documents and ask someone else to find two of them. Keep a one-paragraph note in the top-level folder with the pattern and a good example. Rename older documents gradually and check dependent links and spreadsheet references before moving or renaming shared files.