Organizing a shared drive

TL;DR:

• Organize by how people look for things, with a few top-level folders that never change.

• Give access to groups or roles, not one person at a time, and keep edit rights narrower than view rights.

• Move finished work into an archive folder instead of deleting it, and review the drive on a fixed day each quarter.

A shared drive starts tidy and rots slowly. Someone saves a file to the top level "just for now", another person makes a second folder for the same client, and a year later nobody can say which version of the price list is the real one. Fixing this is less about clever software and more about a few decisions made once and written down.

This guide walks through those decisions for a small team, using any shared drive or shared network folder. The exact buttons differ between apps, so the steps below describe the job, and you can find the matching option in your app by looking for terms like "share", "members" or "access".

When a shared drive needs a clean-up

Signs it is time: people ask in chat where a file lives, the same document exists in three places, new joiners cannot find anything without a guided tour, or someone has edit access to files they never touch. Any one of these is enough. You do not need a crisis first.

Before you move a single file

Do these three things first, because moving files before you have a plan only creates a second mess.

1. Write down who uses the drive and what each person needs to do with it: read, add files, or change and delete files.

2. List the five or six kinds of work the team really does, such as clients, finance, marketing and internal admin.

3. Tell the team a date and a short reason, so nobody is surprised when a link they had bookmarked moves.

Make sure you can undo: Before reorganizing, ask your app whether it keeps a version history or a trash. If it does, you can undo a mistake. If you are not sure, copy a small test folder first and check that the copy opens.

Step by step

1. Pick a few top-level folders: Aim for roughly four to eight. Name them after the kind of work, not after people or years. If a folder name needs an explanation, it is the wrong name.

2. Number them so the order stays fixed: Start folder names with 01, 02, 03 so they sort the same way for everyone, instead of alphabetically jumbling.

3. Decide how deep to go: Two or three levels is usually enough. If you find yourself at level five, the files are probably better found by search and a good file name.

4. Set access on the top-level folders: Share each top-level folder with a group or role, and let the folders inside inherit that, unless there is a real reason to change it.

5. Create the archive: Add one folder for finished work and one rule: nothing is deleted in the first pass, it is moved to the archive.

6. Move, then tell people: Move files in batches, check that links still work, and send one short message saying where things are now.

Worked example: folder structure for a small team

Say a team of six runs a small design studio: two designers, an account manager, a bookkeeper, an office manager and the owner. Their drive has 300 loose files at the top. Here is the structure they choose.

01 Admin
02 Clients
   Client name
      01 Brief and contract
      02 Work in progress
      03 Delivered
03 Finance
04 Marketing
05 Templates
99 Archive
   2025
   2026

There are six top-level folders. Client work is the one that grows, so each client gets the same three inner folders. A new designer who has used one client folder can find things in all of them.

Permissions for this team

Notice that only one folder is restricted from viewing: finance. Everything else is open to read, which keeps the team helpful, and edit rights stay narrow so a stray click cannot overwrite the template. Create four groups once, then add people to groups. When the bookkeeper leaves, you change one membership, not forty folders.

Counting the result

Before: 300 loose files and no structure. Suppose that after sorting, 180 files belong to current clients, 40 to finance, 30 to marketing, 20 to templates and 10 to admin, with 20 old files left over. Check: 180 + 40 + 30 + 20 + 10 + 20 = 300. Those 20 leftovers go to 99 Archive/2025 rather than being deleted, so every file is accounted for.

Mistakes to avoid

• Sharing a folder with individuals one at a time. It works on day one and becomes impossible to audit later.

• Making a folder for every person. People change roles, the work does not.

• Giving everyone edit rights "to keep things simple". One accidental drag can move a folder that dozens of links point to.

• Deleting old files in the same pass as reorganizing. Archive first, delete later, when you are sure.

• Skipping the announcement. A silent move looks like lost files.

Watch out: Be careful with anything holding personal or financial details, such as payroll or contracts. Restrict those folders from the start, and check with your company's IT or legal contact about how long records must be kept before deleting anything.

Keeping it tidy afterwards

Pick one recurring day each quarter. Spend twenty minutes: move finished projects to the archive, check that the members of each group are still correct, and look for files stranded at the top level. Put the structure itself in a short note called "How this drive works" in 01 Admin, so new people read it first.

If you want help while you do the clean-up, DuckyHelper can see your screen and answer out loud as you work through the folder list. Press fn on a Mac, or Ctrl+Shift+Space on Windows and Linux, and ask which folder a file belongs in.

Frequently asked questions

How many top-level folders is too many?

If people have to scroll to see them, there are too many. Four to eight is a good range, and anything rare can live inside a broader folder.

Should I organize by year or by project?

By project or kind of work at the top, with years used only inside the archive. Years at the top force people to guess when something happened.

What if people keep saving files in the wrong place?

Say where the right place is in one note, and make the right place easier than the wrong one, for example by putting a template in each client folder.