How to organize shared files without duplicate folders

Use a few top-level folders based on real work: active projects, operations, clients, resources and archive. Avoid classifying the same file by person, date and format at once.

Archive completed work rather than leaving it beside active files. The current workspace stays useful without losing history.

A useful name includes the subject, state and date when the date matters. Avoid ‘final’ or ‘final-final’; those names only make sense to the person who created them.

If there is one editable source, make its location clear instead of relying on file names to signal approval.

• Use one shared source for editable work.
• Use dates only where chronology matters.
• Archive rather than duplicate completed files.

Ten minutes each month is enough to archive closed work, remove obvious copies and repair broken links. A large annual cleanup tends to happen when nobody is sure what can be touched.

For a fictional project called Harbour, keep the editable proposal in ‘Harbour/work’ and the approved export in ‘Harbour/deliveries’. Name the export ‘Harbour-proposal-v03-2026-09-13.pdf’. A delivery note records who received that version. The latest editable document can change without rewriting the record of what the client actually received.

Link to the master from other folders rather than creating competing editable copies. Before removing an apparent duplicate, compare content, ownership, permissions and incoming links; matching filenames are not enough. Trial a new structure on one closed project before moving active work. Ask someone to find both the sent proposal and the editable version. If three files appear equally authoritative, fix the status convention before adding more folders.

Fictional small consultancy: one proposal has an editable source, an approved PDF and a newer draft. A folder cleanup should preserve those different meanings. Ask a teammate who did not design the folders to retrieve each item with their own authorized account.

Record whether the reader found the right item, not just whether they found any similarly named file. When a test fails, change one convention and repeat the same retrieval task. A shortcut or index may solve the problem without moving every folder. Before a migration, list dependent links and test the storage provider’s actual move behavior.

Scroll the table to see every column.

Retention obligations and client agreements can override a cleanup preference. Do not delete historical versions simply because current work no longer needs them. This exercise does not define a legal retention schedule.

• The editable source and delivered snapshot remain distinguishable.
• External recipients retain only the access they need.
• Potential duplicates are reviewed before deletion, with a recoverable copy where appropriate.