
Valentina Akpan: Founder of Rellatech, providing administrative and operations support to executives, founders, business owners and teams. Her background combines technical support, customer success, administration and operations.
·
Most of the Google Drives I have cleaned up had the same problem. There were too many folders and too many rules, so the people using them could not remember where things went, and files were saved at the root level instead.
This is the structure I start with for a personal Drive or one person's working folders. It uses three folders and a few rules. It is one option among several, and further down I explain when a shared drive or a permission model needs something else.
The 3 folders
- ●01 Active: anything you are working on right now
- ●02 Reference: finished work you might need to look at again
- ●03 Archive: finished, no longer needed, or older than 12 months
Number the folders. Drive sorts alphabetically, so the numbers keep them in the order you want. Inside each folder, you can group files by client, project or year, whichever suits you.
The 3 rules that keep it working
- ●Keep nothing at the root. If a file is at the top of Drive, it has not been filed yet.
- ●When a project ends, move it from Active to Reference the same day.
- ●Once a quarter, move anything in Reference that is older than a year into Archive.
With only three folders, you rarely have to stop and decide where a file belongs.
A simple naming convention
Files are easier to find than folders. If you name files in this format, Drive search will find them for you:
- ●YYYY-MM-DD - Client - Document Type - Short description
- ●Example: 2026-04-23 - Acme - Invoice - April retainer
When three folders is not the right structure
Active, Reference and Archive describe how one person relates to their own files. That is why it works well for a personal Drive and becomes harder to use when more people or more rules are involved. Use a different top level when:
- ●Access is set by client, department or project. Google shares permissions by folder, so the top level has to be whatever you grant access to. A client folder that everyone can see is worse than a slightly messier Drive.
- ●You are on a shared drive with several teams. What is Active for sales is Reference for finance. Group by team or function first, and use Active, Reference and Archive inside each one if it helps.
- ●Files have retention rules. Contracts, financial records and HR files often have to be kept for a set period and then handled in a set way. Those need their own folder and their own rule, not a quarterly sweep into Archive.
- ●A tool already dictates the structure. If your project system, accounting software or CRM files documents into Drive automatically, work with the folders it creates rather than moving them.
In those cases the rules still apply: keep nothing at the root, move things when they are finished, tidy up on a schedule, and name files so search finds them. Only the top-level folders change. The Drive cleanup case study shows the move itself: business files carried from a personal Drive into the business account folder by folder, with each move logged, before setting up a new structure.
What to do with the files you already have
- ●Create the three new folders today
- ●Drag everything currently at root into Archive (yes, all of it)
- ●From now on, only file what you touch into Active or Reference
- ●When you need an old file, you can find it through search
You do not need to go back and organize five years of files. Filing new work in the right place from today is enough to keep Drive tidy from here on.
Work with Rellatech
Google Drive cleanups are a regular part of what I do. I start from this structure, or a permission-led one if that is what your Drive needs, and fit it to how your business works. If this sounds like your Drive, a short call is the quickest way for us to see whether I can help.
Book a free callChoose a time that suits you on the booking page. On the call, tell me what needs attention and which tools you use. Any detailed audit or implementation is scoped separately.
