Start with responsibilities, not file types
A folder called “PDFs” tells you about a format, but little about why you saved anything inside it. Begin instead with the responsibilities or projects you already remember: household administration, equipment, study or a specific repair. File types can remain useful search filters without becoming the main structure.
Keep the first layer broad enough to survive a busy month. Active work, reference and archive are useful distinctions when they match how you retrieve things. They are not compulsory categories. If you always look for material by client or course, that may be a better first division. Choose the logic you can explain without a diagram.
Add a deeper folder only when its contents would otherwise be difficult to distinguish. A single document rarely needs several empty categories around it. Equally, a folder containing hundreds of unrelated records may benefit from a few meaningful subdivisions. Depth should solve a real retrieval problem rather than express an ideal taxonomy.
Personal/
├── 00-Inbox/
├── Active/
│ └── Home-repairs/
│ ├── 2026-03-12_window-repair_quote_v01.pdf
│ └── 2026-03-18_window-repair_approval.pdf
├── Reference/
│ └── Equipment/
└── Archive/
└── 2026/
Name a file for the question you will ask
A useful name usually combines a subject with a distinguishing detail. Add a date when sequence or timing matters, a status when it prevents confusion, and a version when multiple revisions genuinely need to coexist. You do not need every element for every file. Repeating a long folder path inside every filename creates noise.
For dates, the ISO 8601-style year-month-day order, such as 2026-03-12, sorts predictably in many file managers. Decide what the date means: the event, issue date or export date. A consistent meaning matters more than adding dates indiscriminately. A file’s modification timestamp can change during editing or transfer, so it should not replace an important date in the document’s identity.
Use ordinary words, predictable separators and modest name lengths. Avoid characters prohibited by the systems you share with, including slash characters used as path separators. Windows, macOS and cloud services have different restrictions. If a file must cross platforms, test the naming rule with a sample rather than relying on what one computer accepts.
Do not remove or casually change the extension. Renaming “document.docx” to “document.pdf” does not convert it into a PDF. Use the relevant application’s export function and check the result. For archival needs, formats such as PDF/A may be useful, but a label alone does not establish conformity or preserve every interactive feature.
Separate working files from issued records
“Final” becomes confusing as soon as someone requests a change. For a simple local workflow, numbered versions such as v01 and v02 can be enough. For a service with reliable version history, keep one working document and use its history instead of creating unnecessary copies. Understand how long that history remains available.
When a record must represent a particular agreed state, preserve an identifiable issued copy and keep it separate from ongoing edits. A signed document should not be silently replaced by a later draft. If legal, financial or professional retention obligations apply, follow the relevant authoritative requirements rather than this general example.
One home, several routes: use a shortcut, alias, tag or index entry when a document belongs in more than one context. Check whether those references survive a move or export before depending on them.
Make the shared rules explicit
A shared folder needs a named maintainer or a clearly defined responsible role. Agree where the authoritative working copy lives, who can edit it, and who may archive completed work. Before reorganising, ask whether collaborators, scripts or linked documents depend on existing paths. A tidy move can still break a functioning workflow.
Keep permissions separate from naming. A folder called “Private” is not protected simply because of its name. Use the access controls appropriate to your operating system or storage provider, and review who can open shared links. Avoid putting sensitive identifiers into filenames when those names may appear in notifications, search results or exports.
Finish by testing three ordinary searches: a recent document, a completed project record and a reference item. If the same file repeatedly causes hesitation, change its name or the category boundary. Write the few rules that helped in a short readme file. A remembered, maintained map is more useful than an elaborate structure nobody trusts.