Organise your shared drive: a folder and file-naming system that scales

Every office loses hours to the same question: "Where is the latest version?" The fix isn't a new tool. It's a few agreed rules that everyone follows, whether you use Microsoft 365 (OneDrive and SharePoint), Google Workspace (Google Drive) or a shared network folder.

1. Use a shallow, predictable folder structure

Deep folder trees hide files. Aim for no more than three levels:

Team Drive/
├── 01_Admin/          (policies, contacts, templates)
├── 02_Clients/
│   └── ClientName/    (one folder per client)
├── 03_Projects/
│   └── 2026_ProjectName/
├── 04_Finance/
└── 99_Archive/        (finished work, read-only)

Numbering the top folders keeps them in the same order for everyone.

2. Agree one file-naming rule

YYYY-MM-DD_Client-or-Project_Document-type_v01

For example 2026-10-20_Acme_Proposal_v03.docx. Dates written year-first sort correctly, and the version number removes "final_FINAL_2" chaos. Avoid spaces and special characters such as / \ : * ? " < > |, which can break links and syncing.

3. Let the system keep versions for you

OneDrive, SharePoint and Google Drive keep version history automatically. Instead of saving copies, edit the same file and use Version history to go back. Keep the _v01 numbering only for files you send outside the team.

4. Share links, not attachments

• Send a link to the file so everyone works on one copy.
• Give the least access needed: "view" for most people, "edit" only for contributors.
• Review "anyone with the link" shares every quarter and switch off ones you no longer need.

5. Make it a 10-minute monthly habit

Once a month, move finished work to 99_Archive, delete duplicates and check sharing. Add it to your weekly review on the last Friday of the month.