A good company folder structure splits at the top level by access boundary (a department or a project), goes no more than three or four levels deep and gives every type of document exactly one right home. Folders named after people, version suffixes such as "final" or "v2", and permissions scattered across subfolders are where most structures fall apart.
Key takeaways
- The top level should mark who can see what; lower levels reflect how work is organised.
- Name folders after departments, processes, projects or clients, never after individual employees.
- Write your naming convention down: dates as YYYY-MM-DD, and versions tracked by the system rather than in file names.
- Atlassian's State of Teams 2025 survey found that teams waste 25% of their time just searching for answers.
- Before migrating an existing shared drive, map what is there and who can access it, then move.
What does a messy folder structure actually cost?
Most companies never design their folder structure; it simply accumulates. "Accounts" becomes "Accounts New", then "Tom - Invoices", and a few years later there are four copies of the same contract and "Old" folders nobody dares delete.
The first cost is time. Atlassian's State of Teams 2025 survey of 12,000 knowledge workers and 200 executives found that teams waste 25% of their time just searching for answers. According to Microsoft's 2023 Work Trend Index, 62% of respondents struggle with too much time spent searching for information during their workday.
The second cost is security: messy folders mean messy permissions, and a personnel file can sit forgotten in a "Shared" folder anyone can open. Türkiye's data protection authority received 328 data breach notifications in 2025, according to the KVKK 2025 Annual Report. Personal data sitting in the wrong folder is exactly how such a notification can start.
What principles make a folder structure work?
A folder structure is as much a permissions plan as a filing plan. These principles hold at any company size.
- The top level is the access boundary: Folders such as Finance, HR and Sales are split according to who should see them. Permissions are set at this level; anything below is an exception.
- No folders named after people: "Sarah's Files" is orphaned the day Sarah leaves; file by process, project or client instead. We cover that risk in what happens to company files when an employee leaves.
- Depth is limited: If a document takes more than three or four clicks to reach, people start keeping their own copies.
- Each document lives in one place: If a contract sits in both Legal and Sales, one copy will go stale; use a link or read access instead.
- Versions do not belong in file names: "Quote_final_FINAL.docx" is not a system; it is a sign version tracking is missing. Our guide to document version control goes into this in detail.
Department, project or client: which layout suits you?
There is no single correct template; the right layout depends on how the business actually runs. Most organisations end up with a hybrid: departments at the top, processes or clients underneath.
| Layout | Best suited to | Strength | Watch out for |
|---|---|---|---|
| By department | Manufacturers, traders and service firms with stable teams | Easy permissions that mirror the org chart | Cross-department work needs its own shared area |
| By project | Architecture, engineering, software and contracting firms | Everyone on the project works in one place | Needs a rule for archiving and closing access at the end |
| By client or matter | Law firms, accountancy practices, agencies | Client-level confidentiality is straightforward | Naming standards matter as clients grow |
| By process | Quality records, procurement, HR processes | Documents are quick to find during audits | Folders drift without a clear process owner |
One question settles most debates: "Who decides who can access this document?" A department head means a department area; a project manager means a project area.
What does a sample company folder template look like?
The template below suits a trading or manufacturing business with roughly 20 to 200 staff. Top-level folders mark access boundaries and subfolders follow processes.
`` 01-Company-Wide/ (everyone reads: policies, templates, notices) 02-Finance/ (finance team) Invoices/2026/ Bank-Reconciliation/ Supplier-Contracts/ 03-HR/ (HR only) Personnel-Files/<Surname-Firstname>/ Payroll/2026/ 04-Sales/ (sales team) Clients/<Client-Name>/Quotes, Contracts, Correspondence 05-Procurement/ 06-Projects/<Year-ProjectCode-Name>/ 99-Archive/ (read-only) ``
Number prefixes keep folders in a fixed order. "99-Archive" is read-only; set how long things stay there using our guide to company document retention periods in Türkiye.
How should you name files and folders?
If the naming convention is not written down, everyone follows their own. Put it on a single page and store it under "01-Company-Wide" where everyone can find it.
| Rule | Poor example | Better example |
|---|---|---|
| Date first, as YYYY-MM-DD | invoice 3 march.pdf | 2026-03-03_Invoice_Supplier-A.pdf |
| Document type and party are clear | contract new.docx | Contract_Client-B_Maintenance.docx |
| No version suffix | quote_v3_final.xlsx | Quote_Client-C_Project-12.xlsx |
| Hyphens instead of spaces and special characters | Client Meeting Notes!.docx | Client-Meeting-Notes.docx |
| A person's name only when they are the subject | Mark's file.pdf | Personnel_Smith-Mark_Employment-Contract.pdf |
Avoiding spaces and special characters is optional, but it reduces breakage in older systems and attachments. What matters is one company-wide convention.
How do you design folders and permissions together?
Design folders and permissions together, or both break down. Give every top-level folder an owner and a simple table: who reads, who uploads, who deletes. The principle of least privilege says everyone should have only the access their job requires.
Granting access to a department rather than to individuals means it updates automatically when someone moves team or leaves. Needs such as "can upload but not delete" should be met by separating permission types, not by duplicating folders. For a practical permission matrix, see our guide to file sharing permissions.
How do you move a messy shared drive into the new structure?
Designing the structure on paper is easy; moving years of shared-drive clutter without stopping work is not. This sequence keeps migration controlled.
- Take an inventory: List top-level folders, total size and areas untouched for a year.
- Map current access: Write down who can see which folder today. Most companies find surprises at this stage.
- Agree the target structure and naming rules: Department heads design their own subfolders.
- Clear out duplicates and expired files: Merge copies and handle anything past its retention period in line with your data retention and disposal policy.
- Start with a pilot department: Move one team, run it for two weeks and adjust.
- Move everyone else and make the old drive read-only: That stops saving to the old location out of habit.
- Review every quarter: Check new folders and exception permissions.
The infrastructure side of the move, including cloud options, is covered in replacing an on-premise file server.
How does SmartFiles put this structure into practice?
SmartFiles is the business file management service in the Smart360 family, developed by Digital Bridge. It mirrors the principles above: department-based storage areas at the top, folders of unlimited depth inside. Folders are for organising; the storage area is the access boundary, and each area has its own permission matrix, colour and tags.
Take a manufacturer that opens five storage areas: Finance, HR, Procurement, Projects and Company-wide. Departments are defined once in Smart360, so permissions go straight to the department, and eight separate rights (read, write, edit, delete, create folder and more) are switched on or off independently. The accounts trainee can upload invoices but cannot delete them, and anyone who changes department has their access updated automatically.
Uploading a file with the same name in the same folder creates a new version, so nobody needs to add "final" to a file name. HR applies a checklist to the personnel folder to see which documents are missing for each employee, and folders can carry a retention period of 1 to 30 years, with expired documents listed for the owner rather than deleted. Whole folders migrate with their hierarchy intact, and file migration and expert onboarding support are included in the package.
For incoming documents, AI suggests the most suitable folder with its reasoning, but nothing moves without approval. Search covers document content as well as file names. For a broader comparison, read Google Drive vs business file management.
How can Digital Bridge help with document organisation projects?
Some organisations need more than tidy folders: correspondence registers, approval workflows or formal document processes. In those cases Digital Bridge builds a process-led setup with its document management system solutions.
The first step in such a project is to map the current folder inventory, the access picture and the target structure together. For organisations that want file management and email under one identity and one console, the Smart360 family is a good fit: there is no server to install, and initial configuration is guided by our team. For background, see our guide to business document management and the glossary entry on file versioning.
What is the next step towards a better folder structure?
Do one thing this week: list your shared drive's top-level folders, with the owner and who can see each one. That list is the first draft of your new structure. More articles on the subject are collected on the business email and files topic page.
If you want to build the structure straight onto department-based areas, explore SmartFiles on the product page and get started from the SmartFiles purchase page. To talk through a migration plan or a wider document management need, get in touch via our contact page or call +90 850 346 41 09.