A Simple Plan for the Files Nobody Owns
May 5th, 2027
Ask three employees where the current version of a contract lives and you may get three different answers. One points to the shared drive. One says it was emailed last month. One opens a folder called "New Folder (3)" and starts scrolling. The file exists. It just does not have a home, an owner, or a rule about which copy counts.
This is one of the most ordinary problems in a growing business, and one of the most expensive. It wastes time, creates errors, and makes it hard to protect information that should not be open to everyone. The good news is that it does not require a massive migration. It requires a small set of decisions and someone willing to enforce them.
Why shared drives become a mess
Most file systems grow one urgent request at a time. A salesperson needs a folder. A project needs a place for drawings. Someone creates a folder for an event in 2019 and nobody deletes it. There is rarely a moment when someone decides the whole structure. It just accumulates, and every new employee learns the mess by copying the habits of the person before them.
Email makes it worse. When a file is sent as an attachment, the shared drive copy and the emailed copy start to diverge. A week later there are two truths, and the one people trust is whichever they saw last.
Start with two questions per folder
For every top-level folder, answer two questions: who owns this, and who needs to see it? Ownership means one person is responsible for the folder's structure and contents. Access means a short list of people or groups who should be able to open it.
If no one can answer the ownership question, that is the first problem to solve. A folder without an owner will either sprawl or become a legal liability. If the access list is "everyone," ask whether that is truly necessary or just the default.
A structure most people can understand
The best folder structure is boring and predictable. It matches how the business thinks about its work, not how a consultant drew it on a whiteboard. Many small businesses do well with a simple arrangement:
- Company for policies, templates, and shared reference material.
- Customers or Projects for active work, one folder per customer or job.
- Finance for invoices, receipts, and records that only a few people should see.
- People for hiring, training, and internal operations.
- Archive for finished work that must be kept but rarely opened.
The names matter less than the consistency. Use the same naming pattern for files and dates, and put the date first if sorting by time is useful. A file named "2027-05 invoice - customer name" is easier to find than "invoice final final v3."
Permissions are not a formality
Access permissions are the part everyone wants to skip. They are also the part that protects the business. Finance records, employee files, customer contracts, and anything with health or payment information should not be open to the whole company by default.
Set permissions by group rather than by individual where possible. That way a new hire gets the right access when they join, and a departure removes it cleanly. Review the list at least twice a year. The most common finding in a file review is a folder that still includes someone who left two years ago.
One current version, and a place for the rest
Version control is a habit, not just a feature. Decide which copy is the working copy and keep it in the shared location. When a file is sent externally, send a link to the shared copy or clearly label the attachment as a snapshot. Use the version history that cloud storage provides instead of creating "final" and "final v2" files.
For documents that go through review, a small workflow helps: draft, review, approved, archived. The labels can be folders, tags, or a note in the file itself. The point is that everyone knows which stage a document is in without opening it and guessing.
Back up what matters, and test the restore
A clean folder structure makes backup easier, but it does not replace it. Confirm that the files people rely on are included in the backup, that the backup is stored somewhere separate from the original, and that someone has tested a restore. A backup that has never been restored is an assumption, not a safety net.
Cloud storage adds its own protection with version history and recycle bins, but it is not unlimited. Check how long deleted files are retained and who can recover them. Then write that down where employees can find it.
A practical cleanup in four steps
- Inventory the top level. List every shared folder and give each one an owner.
- Move, do not copy. Consolidate duplicates into the agreed structure and archive the rest.
- Fix permissions. Remove departed users, limit sensitive folders, and use groups.
- Publish the rules. A one-page guide that explains naming, ownership, and where to save new files.
Expect the cleanup to take longer than one afternoon, and do not let that stop it. A smaller, well-owned structure is better than a perfect plan that never gets applied.
The goal is confidence, not perfection
When files have owners and rules, people stop keeping private copies. They stop asking around for the latest version. They stop saving sensitive documents in places that were never meant to hold them. The business becomes a little calmer, and a little safer.
HTS Voice & Data Systems helps businesses set up managed IT services in San Antonio, including file structure, permissions, and backup reviews. If your shared drive has become a mystery, call (210) 495-5520 or contact us and we will help you sort it out.
Posted in: Managed IT Services
