A Google Drive folder structure for small teams that does not rot
A simple Google Drive folder structure for small teams: three levels, one naming rule, shortcuts for overlap and tags for status, so the structure stays usable as the team grows.
6 min read
Small teams rarely fail at Drive because of a bad first structure. They fail because the structure has no rules, so each person adds their own. Google's guidance is to start simple and adjust, with folders inside folders and clear names.[1] Here is a concrete version for teams of two to fifteen people.
Use three levels, no more
Team Drive (or shared drive) ├── 01 Clients │ ├── Acme │ │ ├── 2026-Website-Redesign │ │ └── 2026-Brand-Guidelines │ └── Birch ├── 02 Internal │ ├── Finance │ └── Hiring ├── 03 Templates └── 99 Archive
The first level is by function, the second by client or area, the third by project. Numeric prefixes keep the order stable. Deeper levels are where files get lost, so keep working files at level three and use naming for anything finer.
Decide who owns the files
On Google Workspace, a shared drive keeps files with the team instead of an individual, so files stay in place when someone leaves.[2] Google's shared drive guide lists a Google Workspace account as a requirement, so on a personal Gmail account choose one person to own the top folder and share it with the rest, and write down who that is.
One naming rule
Drive's help suggests short, meaningful names that can include dates and project names, with a date format such as year-month-day.[1] Pick one pattern and write it at the top of the structure: YYYY-MM-DD_Client_Document_vN. Dates in that order sort chronologically on their own.
Handle overlap with shortcuts, not copies
When a file belongs in two places, add a shortcut rather than a duplicate. A shortcut is a link to the original, and deleting it does not delete the file.[1] Copies drift apart; shortcuts do not.
Keep status out of the folders
"Draft", "In review" and "Approved" change weekly. Putting them in folder names forces a move on every change and breaks links people saved. Track status with a different mechanism: Drive Labels if your edition has them and an admin sets them up,[3] or a tagging layer. FolderPls lets each person tag the files they choose with their own status tags without moving anything. Tags live in FolderPls, not in Drive, and the free plan covers personal Google accounts only, while Workspace accounts need a paid plan (pricing).
A 20-minute setup checklist
- Create the top-level folders and number them.
- Write the naming rule in a short document at the top of the structure.
- Name one owner for each top-level folder.
- Move only the active projects in; archive the rest into 99 Archive.
- Choose how you will track status, and write it down too.
Related: organize Google Drive files by tags and Drive Labels alternatives.
Frequently asked questions
- How many folder levels should a small team use?
- Three is a practical limit: function, then client or area, then project. Deeper nesting makes files harder to find, so use file names for finer detail.
- Should status like Draft or Approved be a folder?
- Usually not. Status changes often, and moving files between folders breaks saved links. Track it with Drive Labels where available, or with tags.
- What is the difference between a shared drive and a shared folder?
- Per Google, unlike files in My Drive, files in a shared drive belong to the team instead of an individual, so they stay in place when members leave. Google's shared drive guide lists a Google Workspace account as a requirement.
Sources
- [1] Google Drive Help: Organize your files in Google Drive(opens in a new tab) — read on 2026-10-16
- [3] Google Workspace Admin Help: Get started as a classification labels admin(opens in a new tab) — read on 2026-10-16