A field guide to cleaning a messy project folder
A good cleanup protects current work, reduces ambiguity, and leaves a structure another person can maintain. The safest sequence is inventory, classify, verify, then remove.
Protect current work before moving anything
Confirm the folder owner, active collaborators, known deadlines, and the current working files. If possible, create a read-only snapshot or use the storage system's version history. A cleanup should never begin with bulk deletion.
Uncertainty is a reason to isolate a file for review, not a reason to guess whether it matters.
Build a lightweight inventory
List top-level folders, obvious file families, large files, recent edits, and repeated names. You do not need a perfect catalog. You need enough evidence to identify the current working set and the areas with the highest risk.
path | modified | size | likely role | owner | action- Mark known current files before sorting.
- Flag shortcuts and linked assets that may break after a move.
- Record files that require a specific application to inspect.
Sort by lifecycle, then by subject
Move files into four broad stages: intake, active, deliver, and archive. Inside active work, use the smallest subject structure that makes retrieval easier. Do not create a folder for a category that has one obvious file.
01_intake/Unprocessed files waiting for a decision.
02_active/The current working set, separated from history.
03_deliver/Approved outputs and their handoff context.
04_archive/Deliberately retained records and references.
Handle duplicates by evidence
Files with similar names are not automatically duplicates. Compare file hashes when available, then inspect modified dates and content. Keep one canonical copy and record why it won. If two files contain different edits, treat them as versions and reconcile them before deleting either.
- Exact duplicates: keep the copy in the correct lifecycle folder.
- Superseded drafts: move temporarily to a review folder.
- Conflicting versions: assign an owner to reconcile them.
- Unknown files: quarantine until the owner decides.
Document the result
Add a project README at the root. State the purpose of the workspace, current working file, owner, folder roles, naming convention, and next review date. A clean tree without context will drift again.
Set a maintenance cadence
Review intake weekly during active work. Review the active folder at each milestone. Build the handoff and archive as part of closing the project, not as an optional task after everyone has moved on.