---
title: "Folder structure examples for home and work files"
description: "A useful folder structure gives every file a predictable home without making you navigate a maze. The examples below cover personal documents, shared..."
published: "2026-11-02T15:00:00.000Z"
updated: "2026-11-02T15:00:00.000Z"
url: "https://usedosya.com/folder-structure-examples-for-home-and-work-files"
canonical: "https://usedosya.com/folder-structure-examples-for-home-and-work-files"
site: "Use dosya"
---

# Folder structure examples for home and work files

A useful folder structure gives every file a predictable home without making you navigate a maze. The examples below cover personal documents, shared...

## Key takeaways

- Organize by how you will retrieve files, and start shallow, adding another folder level only when the current one becomes difficult to scan.
- For business files, give departments the recurring records and use a small template inside each client project: Brief, Working, Review, and Deliverables.
- Microsoft recommends avoiding SharePoint folder structures deeper than one or two levels, and suggests columns and views, such as an Awaiting approval view, instead.
- Name files for recognition, such as Kitchen_Quote_SupplierA.pdf instead of scan004.pdf, and use YYYY-MM-DD_Subject only for date-led records.

A useful folder structure gives every file a predictable home without making you navigate a maze. The examples below cover personal documents, shared business files, SharePoint libraries, and Obsidian notes, with practical rules for naming and maintenance. Treat them as starting templates: keep the categories that match your work and remove the rest.

## What makes a folder structure easy to use?

An easy-to-use folder structure groups files by the way you expect to retrieve them: by household responsibility, client, project, or business function. Choose one main organizing principle at each level, then use consistent subfolders where they help. For these templates, start shallow and add another level only when the existing folder becomes difficult to scan.

Before creating folders, finish this sentence: “When I need this document again, I will look under ___.” Your answer should guide the structure more than the file format. For example, keep a renovation spreadsheet beside its quotes and drawings rather than separating everything into “Spreadsheets,” “PDFs,” and “Images.”

## Home folders organized around everyday responsibilities

For personal files, try a structure based on areas of life rather than individual activities. Give ongoing responsibilities a stable home, and reserve project folders for work with a clear finish. You do not need to create every subfolder immediately.

- **Home00_Inbox:** Downloads and scans awaiting filing.
- **Finance:** Annual records, budgets, and purchase receipts.
- **Household:** Property documents, maintenance, utilities, and appliance manuals.
- **Personal:** Education, career documents, and individual records.
- **Projects:** Active efforts such as “Kitchen Renovation” or “Family Reunion.”
- **Archive:** Completed projects and inactive reference material.

Within Finance, use year folders when you naturally retrieve records by year. Within Household, organize appliance manuals by item or room instead; a year may tell you little about where to find the dishwasher instructions.

For a renovation, create subfolders such as “Quotes,” “Plans,” and “Receipts.” Keep the project together while it is active, then move the completed folder into Archive. Decide whether its final documents should remain there or move into Household, and avoid maintaining two competing copies.

Treat the inbox as a temporary landing place. Give yourself a recurring filing appointment, and move each item into its permanent location or delete it when appropriate. If the same category keeps appearing, consider giving it a dedicated folder.

## Business folders built around ownership and delivery

Useful business folder structure examples distinguish ongoing operations from client or project delivery. For this proposed model, departments own recurring business records, while project folders hold the material needed to complete specific work. Avoid mixing these approaches at the same level without clear labels.

- **Business01_Operations:** Procedures, supplier information, and internal templates.
- **02_Finance:** Budgets, invoices, and reporting.
- **03_People:** Hiring, onboarding, and employee documentation.
- **04_Marketing:** Brand assets, campaigns, and published content.
- **05_Clients:** One folder per client, with separate project folders.
- **99_Archive:** Closed projects and inactive operational material.

Inside each client project, reuse a small template:

- **01_Brief:** Scope, requirements, and agreed objectives.
- **02_Working:** Drafts, research, and production files.
- **03_Review:** Material awaiting feedback or approval.
- **04_Deliverables:** Approved outputs intended for handover.

Apply these company folder structure examples to a small pilot before rolling them out. Ask someone who did not design the system to locate a brief, identify the approved deliverable, and save a new draft. Revise labels wherever they hesitate.

Assign a named owner to each shared area. That person should resolve ambiguous filing decisions and maintain the template, not become the only person allowed to organize files. Plan access separately: the “People” label describes content, but should never be treated as proof that sensitive files are protected.

## SharePoint libraries with folders and useful metadata

For SharePoint document libraries, combine a shallow folder layout with columns and views rather than recreating a deeply nested shared drive. Microsoft recommends avoiding folder structures with more than one or two nesting levels because they make content harder to discover. Topic-specific libraries can also provide a clearer starting point than one oversized document library. ([learn.microsoft.com](https://learn.microsoft.com/en-us/sharepoint/information-architecture-modern-experience?source=recommendations))

Consider this proposed setup for a project delivery site:

- **Library: Project DocumentsFolders:** One folder per active project.
- **Columns:** Project, document type, owner, and approval status.
- **Views:** Active projects, awaiting approval, and approved deliverables.
- **Library: Shared TemplatesFolders:** Optional broad categories, such as proposals and reports.
- **Columns:** Template type and responsible team.

SharePoint supports organizing library content through folders, columns, and views. That gives you alternatives to adding another folder whenever users need a different way to browse the same documents. ([support.microsoft.com](https://support.microsoft.com/en-us/sharepoint/libraries/introduction-to-libraries))

For example, propose an “Awaiting approval” view based on a status column rather than requiring everyone to move files into a separate review folder. Agree on a short set of status values and explain who updates them. Otherwise, your carefully designed views may not reflect the actual work.

Keep the first version modest. Test it with real documents and everyday retrieval tasks before adding more columns or libraries. Include the people who upload files, not just those who search for them.

## Obsidian folders that leave room for connections

Obsidian stores notes as Markdown-formatted plain text files inside a vault, which is a folder on your local file system. Your folder layout therefore provides a physical home for notes and supporting material. ([obsidian.md](https://obsidian.md/help/data-storage))

For a starting point, consider these Obsidian folder structure examples as one adaptable template:

- **00_Inbox:** Quick captures awaiting a decision.
- **10_Projects:** Notes tied to active outcomes.
- **20_Areas:** Ongoing responsibilities such as learning or home management.
- **30_Reference:** Reusable explanations, reading notes, and research.
- **90_Archive:** Inactive projects and retired material.
- **Attachments:** Supporting images and other files.

Use folders to answer “Where does this note belong?” and links to express relationships between notes. Obsidian supports internal links, including links to specific headings, so related ideas need not share a folder. ([obsidian.md](https://obsidian.md/help/links))

For example, keep reusable interview guidance in Reference and link to it from a hiring project note. This is preferable to copying the same advice into every project. Start with broad categories; split Reference into topics only when doing so would make your own browsing easier.

## Which folder structure best practices should you apply first?

Apply the rules that remove everyday uncertainty first: choose a clear filing principle, write meaningful names, identify the authoritative copy, and define when work moves to the archive. These folder structure best practices examples are intended as working agreements, not rigid technical standards. Record them in a short readme beside your top-level folders.

- **Name files for recognition.** Prefer Kitchen_Quote_SupplierA.pdf to scan004.pdf. Include the subject and the detail that distinguishes it from similar files.
- **Use dates deliberately.** For date-led records, try YYYY-MM-DD_Subject. Do not add dates to evergreen reference files merely to fill a naming template.
- **Choose a versioning method.** Where SharePoint version history is enabled, use it to track changes rather than automatically creating a new filename for every edit. SharePoint supports version history for library files. ([support.microsoft.com](https://support.microsoft.com/en-us/sharepoint/libraries/work-with-files-in-a-document-library))
- **Define archive triggers.** For example, archive a project after handover and outstanding actions are resolved. Archiving is an organizational decision, not a substitute for an agreed retention policy.
- **Reserve numbering for useful ordering.** Prefixes such as 01_ and 02_ can express a workflow sequence; skip them when alphabetical order is sufficient.

## Introduce the system without reorganizing everything

Start with one household category, team, or active project. Move a representative sample into the proposed folders and test saving, finding, reviewing, and archiving files. Keep a list of ambiguous cases and adjust the rules before expanding.

Then work through the transition:

1. **Map old locations to new ones.** Decide where each major category belongs before moving files.
2. **Identify authoritative copies.** Review apparent duplicates rather than deleting them solely because their names match.
3. **Separate uncertain material.** Use a temporary review area with an owner and review date.
4. **Document the change.** Tell collaborators where active work now lives and which old locations should no longer receive files.

The best folder structure is the one you can explain and maintain. Choose a suitable example, test it against real retrieval tasks, and refine only where confusion appears. Clear ownership and consistent filing decisions matter more than building an elaborate hierarchy.

## Related guides

- [How to recover deleted photos from iCloud](/how-to-recover-deleted-photos-from-icloud)
- [How to edit an MP4 video online for free](/how-to-edit-an-mp4-video-online-for-free)

## Sources

1. [Introduction to SharePoint information architecture - SharePoint in Microsoft 365 | Microsoft Learn](https://learn.microsoft.com/en-us/sharepoint/information-architecture-modern-experience?source=recommendations)
2. [Introduction to libraries | Microsoft Support](https://support.microsoft.com/en-us/sharepoint/libraries/introduction-to-libraries)
3. [How Obsidian stores data - Obsidian Help](https://obsidian.md/help/data-storage)
4. [Internal links - Obsidian Help](https://obsidian.md/help/links)
5. [Work with files in a document library | Microsoft Support](https://support.microsoft.com/en-us/sharepoint/libraries/work-with-files-in-a-document-library)
