
Editorial illustration.
A shared drive can hold every project file and still make the team feel as if nothing is organised. The familiar symptoms are easy to spot: final-v3-new, a link sent in an old chat, and two people editing different copies of the same proposal.
This guide is for a small team, club or freelance project that needs a predictable way to store and hand over files. The aim is deliberately modest: a new teammate should be able to find the current working document and understand what can be shared without asking the original author.
Summary
- Organise by project and work stage, not by the person who created each file.
- Keep one clearly identified working copy; use version history or dated snapshots for meaningful milestones.
- Give access to named people and review it when a project ends.
- Agree on a short naming rule and a handover note before the drive grows.
Start with the question someone will ask
Before creating folders, write down the three things a colleague will most often need: the current draft, approved material, and the assets or decisions needed to continue the work. A structure that makes those tasks obvious is better than a tree that mirrors every meeting or role.
For a website launch, a workable starting point might be:
Website-refresh/
01-brief-and-decisions/
02-working/
03-review/
04-approved/
05-handover/
The numbers make the intended order visible in many file browsers. They do not create security boundaries. If the budget or contract is private, use the storage service’s access controls, not a folder name such as PRIVATE as protection.
A small project should not need a separate folder for every week. Add a level only when a person repeatedly cannot find a type of file. Otherwise the extra clicks become their own filing problem.
1. Decide where the source of truth lives
Pick one shared location for active work and tell everyone what it is. A chat attachment, personal desktop, email thread and shared-drive copy are not four equally current sources.
If the team works in collaborative documents, link to the live document rather than downloading and re-uploading it. If the work is a large design, video or spreadsheet file that cannot be edited together, nominate one owner for the working copy and a clear way for others to request changes.
There is a trade-off: a single working copy reduces version confusion but can create a bottleneck. For a time-critical task, assign a backup editor and state how handover works. Do not solve the bottleneck by letting everyone create unnamed copies.
2. Use a filename that answers three questions
A useful filename says what the file is, which project or period it belongs to, and whether a reader should treat it as a draft or approved deliverable. For example:
2026-11-17-homepage-copy-review.docx
2026-11-20-homepage-copy-approved.docx
Use dates in year-month-day order when dates matter; they sort consistently. Avoid final-final, initials that only one person understands, and status words that remain long after a document has changed.
You do not need to repeat the folder name in every file. Website-refresh/04-approved/homepage-copy.docx is already clear. Naming rules should shorten the time to identify a file, not turn every filename into a sentence.
3. Separate working material from approved output
Keep active drafts away from files that have been signed off. When something is approved, either move the chosen deliverable into the approved folder or create a read-only copy there, according to how your tool handles links and permissions.
Do not leave several approved files with the same name and rely on modification time alone. Add the approval date or a short release identifier if several deliverables genuinely need to remain available. Include a one-line note explaining which version was delivered and to whom.
For design or code projects, a final exported file is not necessarily the editable source. Keep both when the next person needs them, and label them plainly: brand-guide-source.fig and brand-guide-export.pdf.
4. Let version history handle ordinary edits
Many cloud services keep a revision history. Use that for normal changes rather than making a duplicate file after every small correction. Before enabling any history or retention feature as a recovery plan, check what the specific service and account actually retain; features vary, and deleted or expired content may not be recoverable indefinitely.
A snapshot is useful at a real milestone: before a client review, before a major rewrite, or when a signed-off deliverable must be preserved. Name that snapshot by event, not by a vague backup label. Keep a separate backup for recovery; a version history inside the same account is not a complete backup if that account becomes inaccessible. The guide Sync Is Not a Backup explains the recovery distinction.
5. Share the smallest useful access
Invite named collaborators with the least permission that lets them do their work. A reviewer may need comment access; a teammate preparing the file may need edit access. “Anyone with the link” is convenient for public handouts but can be a poor default for drafts containing personal, financial or contract information.
Test a share link in a private browser session or ask a colleague with the intended access level to open it. For another practical angle on permissions and sensitive material, see 10 Checks Before Sharing a Work Document Online. This catches the opposite errors too: a document meant for a client that still requires an internal login, or a private document whose link grants broader access than expected.
When work ends, remove people who no longer need access and transfer ownership where the service supports it. A shared folder should have an accountable owner, especially if it contains records that must be kept or deleted on a schedule.
6. Add a handover note, not a maze
For a project that will pass between people, create a short README or handover note at the top level. It should answer:
- Which file is the current working copy?
- What has already been approved or sent?
- What decision is still open, and who owns it?
- Which materials contain sensitive information?
- Who can change access or archive the folder?
Keep it short enough to stay current. A stale document that says a draft is current when it was replaced yesterday is worse than no note. Put a review date beside operational notes and update it when the owner changes.
A quick clean-up for an already messy drive
Do not move hundreds of files in one sweep. Start with one active project:
- Ask the project owner to identify the current source of truth.
- Create the small set of folders people actually use.
- Move only active files and approved deliverables; leave uncertain material in a clearly named
needs-reviewarea temporarily. - Replace links in the main project note or team channel with the canonical links.
- Confirm the intended collaborators can open the right files.
- Assign someone and a date to decide what to archive or delete.
This staged approach matters because moving a file can break links in some tools or leave collaborators looking at a stale shortcut. Verify a few important links before announcing that the clean-up is complete.
Mistakes that bring the clutter back
The most common failure is designing an elaborate hierarchy and never naming an owner. The second is calling everything “final” before someone has approved it. Another is using folder names as a substitute for access control. Finally, do not archive work simply because it is old: first check the team’s retention obligations and whether a client or colleague still depends on it.
If there is an existing team convention that people follow, preserve it and fix the specific confusion. Reorganising for aesthetic neatness can make files harder to find for the people who use them every day.
My Take
A good shared drive is not the one with the cleverest taxonomy. It is the one where a teammate can tell which copy to use, what they are allowed to do with it, and who to ask when the answer is unclear. Start with one active project and let real search friction show you what deserves another folder.
Bottom Line
Choose one source of truth, separate drafts from approved outputs, and use named access with a real owner. Write the naming rule in the handover note, test the links, then apply the pattern to the next project only if it makes work easier.