Map the incoming files
A document can arrive by email, land in Downloads and end up on the desktop. Sorting everything by topic immediately can leave three copies and no obvious original. Choose one inbox folder as a temporary stop, not a permanent home.
When sorting, give each file a role: source material, work in progress, finished output or reference copy. Do not begin with a separate folder for every extension. A text, a spreadsheet and a picture often belong to the same project and are more useful together.
- Collect new files in one place.
- Separate your own work from material received from elsewhere.
- Before moving a file, check whether another document or application refers to its path.
A small project structure
A one-off project usually needs four things: what came in, what you are editing, what you will deliver, and a note explaining the work. Numbered names keep the order predictable in different file managers.
reading-room/ README.txt 01_source/ 02_work/ 03_export/
Keep unchanged inputs in 01_source, editable files in 02_work, and outputs that open without the working application in 03_export. In the README, explain the aim, name the main working file and describe how to produce the result. Do not repeat this structure inside every small folder. Empty levels only make paths longer.
Separate work from an archive
An archive is a completed set you intend to keep, not everything you have not opened recently. Move a whole project there once the outputs are checked and nothing still relies on the old path.
Do not move databases, application directories or sync folders as if they were ordinary documents. First establish what reads them and where updates are written. A copy of a changing file may be incomplete even when the copy operation reports success.
Sort without bulk deletion
Start with a single project. Keep a short move list: old name, new name and reason. Make a separate copy of important material before sorting. Copy first, inspect the result, and only then decide what can be removed.
Matching names do not prove that files are duplicates. Compare size and contents; a hash is useful for exact byte comparisons. Keep both versions if they differ. A modification time is not necessarily the date a document was created.
A quick check
Open an input, a working file and an export from the new structure. Try finding the final result without a hint. If that requires remembering the project history, add two lines to the README rather than three more folders.
An example you can adapt
The pack below contains a teaching project with short texts and an inventory. It has no personal data or programs. Extract it into a separate folder, rename it and remove any levels you do not need. For a personal book collection, arranging files by author may be more useful than arranging them by workflow.
Download folder example · ZIPOriginal educational pack, CC0. It runs no commands and does not modify your files.