How to organize client files in Google Drive
By The Onbo team · Updated
Short answer
Use one top-level folder per client, a subfolder per project, and the same small set of subfolders inside every project: admin, client uploads, working files, deliverables and archive. Name everything with one consistent pattern, share only the folders clients need, and keep the structure in a shared drive if more than one person works on it.
Google Drive gets messy one shortcut at a time: a file saved to the wrong folder, a second “Final” version, a client upload left in Downloads. A simple structure set up once, and repeated for every client, keeps it tidy as you grow.
Why does client Drive organisation fall apart?
- No fixed structure. Each project gets a slightly different set of folders.
- Uploads land anywhere. Files from clients arrive by email and get saved wherever is quickest.
- Versions multiply. “Logo final”, “Logo final v2”, “Logo FINAL use this”.
- Personal ownership. Files live in one person’s account, so access breaks when they leave.
- Over-sharing. Clients get edit access to folders full of internal working files.
What folder structure works for client work?
Use the same structure for every client and project. Copy it as a template folder and duplicate it each time:
Clients/
Client name/
Project name - YYYY/
01 Admin/ agreement, invoices, brief
02 Client uploads/ everything the client sends
03 Working files/ drafts, sources, internal notes
04 Deliverables/ final files for the client
05 Archive/ superseded versions
| Folder | What goes in it | Shared with client? |
|---|---|---|
| 01 Admin | Accepted agreement, invoices, hand-off brief | No |
| 02 Client uploads | Logos, content, photos, documents from the client | Upload only, if needed |
| 03 Working files | Drafts, source files, internal notes | No |
| 04 Deliverables | Final approved files | Yes, view only |
| 05 Archive | Older versions you might need again | No |
Numbering the folders keeps them in the same order everywhere.
How should you name files?
Pick one pattern and stick to it. For example:
client-project-item-v02-2026-11-18
- Client and project first, so a file makes sense if it’s moved or downloaded.
- Version numbers with a leading zero, so v10 sorts after v09.
- Dates as year-month-day, so they sort correctly.
- No “final” in file names; use the Deliverables folder for that.
For example, a three-person design studio might adopt this structure for every new client. When a designer is off sick, a colleague opens the client folder, finds the latest working file by its version number and the client’s photos in “02 Client uploads”, and carries on the same day.
How do you fix an existing mess?
Don’t reorganise everything at once. Create the new structure, use it for every new project from today, and move old projects across only when you next work on them. For files you can’t place, make one “To sort” folder per client and empty it in short sessions. Search helps here: Drive can find files by name, owner and type, which makes it quicker to gather a client’s scattered files into their folder.
Write the structure and naming pattern down in one short document and link to it from the Clients folder. New team members, contractors and your future self will follow a written rule far more reliably than a remembered one.
What should clients be able to see?
Share as little as the work needs:
- Deliverables: view access, so clients can download final files.
- Client uploads: a way to add files, ideally without browsing your other folders. An upload link that saves into this folder is cleaner than edit access; see how to let clients upload files to your Google Drive.
- Everything else: private to your team.
If several people work on client files, keep the Clients folder in a shared drive so files belong to the team, not to whoever created them.
When should you review the structure?
Look at it once a quarter, or whenever someone on the team saves a file in the wrong place twice. Recurring mistakes usually mean a folder name is unclear or a folder is missing, not that people are careless.
A Drive organisation checklist
- One template folder to duplicate for each project
- One top-level folder per client
- The same numbered subfolders in every project
- One file naming pattern, written down
- Client uploads always land in “02 Client uploads”
- Final files only in “04 Deliverables”
- Old versions moved to “05 Archive”
- Clients see deliverables only, view access
- Shared drive used for team-owned files
- Access reviewed when a project ends
Getting files from clients into the right folder is half the job; see how to stop chasing clients for files and how to request brand assets from clients.
Where Onbo fits
Onbo fills the client uploads folder for you. Its file collection uploads straight from the client’s browser into your own Google Drive, creating a folder for each client, using only the drive.file permission. Clients upload as part of one onboarding link, after accepting your agreement and paying, and reminders follow up on anything missing. Try it free for 30 days; see pricing.
Questions
How should I organise client folders in Google Drive?
One folder per client, a folder per project inside it, and the same fixed subfolders in every project, such as admin, client uploads, working files, deliverables and archive.
Should client files go in a shared drive or My Drive?
If more than one person works on client files, a shared drive keeps files owned by the team rather than by one person's account.
How should I name client files?
Pick one pattern and use it everywhere, for example client, project, item, version and date. Consistency matters more than the exact format.