File organisation at scale with Claude Cowork

TL;DR. Take a folder with thousands of misnamed, undated, half-duplicated files and turn it into a structure a team can navigate — without losing anything. 1–2 days saved on a 5,000-file shared drive. The "copy never move" rule is the most important one; reversibility is what makes the workflow safe enough to ship.

Job to be done#

Take a chaotic source folder and produce a navigable target structure with a complete index from old paths to new.

Who runs it#

Operations, the IT-adjacent ops associate who inherits "the shared drive problem," EAs reorganising an executive's archive.

Inputs (inbox/)#

• The chaotic source folder (read-only, ideally)
• A target taxonomy — or "ask Cowork to propose one"
• Naming convention (or "use the company convention from CLAUDE.md")
• Backup of the source

Outputs (output/)#

• A new folder structure in /output/organized/
• INDEX.md mapping old → new for every original file
• duplicates/ folder for what Cowork classified as redundant
• low-confidence/ folder for items it wasn't sure about

Prompt seed#

Read /inbox/source-folder/ recursively.
Plan a taxonomy first; show it to me before moving anything.
After approval, copy (do not move) files to /output/organized/
following the taxonomy.
Standard naming: YYYY-MM-DD_description.ext.
Detect duplicates by content hash; place duplicates in /output/duplicates/.
For ambiguous classifications, place in /output/low-confidence/.
Produce /output/organized/INDEX.md mapping every original path to
its new path.
NEVER delete; copy only.

Quality bar#

• Copy, never move. Reversibility is the point.
• Confidence flagging is honest — the ambiguous bucket is large in week one and that is fine.
• Index is comprehensive — every original file accounted for.
• Common trip-up: aggressive de-duplication of similar-but-different files. Set similarity thresholds in CLAUDE.md.

Time saved (typical)#

1–2 days for a 5,000-file shared drive. Spread across multiple sessions — this workflow rewards iteration.

Upgrade path#

• Schedule a daily inbox-sweep task once the structure is stable.
• Convert to a function-specific skill — client-folder-organise, legal-matter-archive.

Tinkso's take#

The "copy never move" rule is the most important one. The first run is always partly wrong; reversibility is what makes the workflow safe enough to ship to a non-technical operator. The second-most-important rule is plan the taxonomy first — Cowork moving files into a bad taxonomy is harder to recover from than not moving them at all.