How to organise team files so people can actually find them
· 6 min read
Every chaotic shared drive started as somebody's careful folder structure. They do not fail because nobody designed them. They fail because the design assumed everyone would keep filing things correctly forever, and people do not.
So the goal is not a perfect taxonomy. It is a structure that still works when half the files are in roughly the right place.
Make search the primary tool, not the fallback
People do not browse to files. They search for them, and use folders to confirm they found the right one. Once you accept that, a lot follows: names matter more than nesting, and a good name is one you would actually type.
Which means the filename should contain the words someone would search for. Q3-revenue-forecast.xlsx is findable. final_v2 (1).xlsx is not, no matter how beautifully it is filed.
Go shallow
Three levels is usually enough. Past that, two people reliably file the same document in two different places, and both are defensible.
A structure that survives contact with a team usually looks like: a top level by client, project or department; one level inside by year or phase; and files. That is it.
Put the date first, and put it backwards
Where things are dated, lead with YYYY-MM-DD. It sorts chronologically by default in every system, in every locale, with no configuration. 2026-09-16-site-report.pdf sorts correctly next to its siblings forever.
The same logic applies to versions: v01, v02, v10 sort properly, where v1, v2, v10 puts v10 between v1 and v2.
Name the state in the name
DRAFT, FINAL and APPROVED in a filename do more for a team than any folder. People read filenames; they do not read folder conventions.
Better still, keep only one live copy and archive the rest out of the working folder — but if your team is going to make copies anyway, make the copies legible.
Fix permissions at the folder, not the file
Per-file permissions are how a shared drive becomes unauditable. Grant access at the folder that represents a real boundary — a client, a project, a department — and let files inherit it.
It also makes removing access possible. Taking a departing contractor out of three folders is a task; finding every file they were individually granted is an afternoon.
Prune on a schedule
Two habits, once a quarter, keep a drive usable indefinitely: archive projects that finished, and review who still has access to what. Neither takes long. Both are invisible until you skip them for a year.
How to organize team files: the short version
- Name files with the words people will search for.
- Three folder levels, maximum.
YYYY-MM-DDat the front of anything dated. Zero-pad version numbers.- Put the state in the filename, not just the folder.
- Permission folders, not files.
- Archive finished work and review access quarterly.
How search, filters, stars and breadcrumbs work in NevTan Drive is covered in Finding and organizing files, and sharing and permissions covers granting access at the folder rather than the file.
Write the rules down, on one page
A convention that lives in one person’s head is not a convention. Put it in a single document at the top of the drive — half a page is plenty — covering how folders are named, how files are named, where finished work goes, and who to ask. Link it wherever people are onboarded.
Then apply the only rule that makes it stick: when you find a badly named file, rename it rather than complaining about it. A structure survives because a handful of people quietly repair it, not because everyone was told once.
Do not reorganise everything at once
A weekend spent restructuring a shared drive usually produces a week of people unable to find anything, and a quiet drift back to the old habits. Apply the new structure to new work, move a finished project across when you archive it, and let the old mess shrink on its own.
Common questions
How should I structure shared team folders?
Three levels at most: a top level by client, project or department, one level inside by year or phase, then files. Deeper than that and two sensible people will file the same document in two different places.
How should we name files?
With the words somebody would actually type into search, plus YYYY-MM-DD at the front for anything dated and zero-padded version numbers. 2026-09-16-site-report-v02.pdf sorts and searches correctly everywhere, forever.
Should permissions go on folders or on individual files?
Folders, at a boundary that means something — a client, a project, a department. Per-file grants are how a drive becomes unauditable, and how removing someone’s access turns into an afternoon of searching.
Try NevTan Drive freeThe editors, sharing controls and per-file audit log are on every account, free ones included. Only storage is ever paid for.