Use Claude Cowork to Plan a Folder Cleanup Without Moving Files

A messy project folder creates a small problem that can become a painful one. You know a file belongs to the project, but you do not know whether it is the current brief, an old draft, or the only copy someone still needs.

This is a documentation-based Claude Cowork tutorial with fictional files and an illustrative result. It is not a recorded Cowork run and does not claim that any files were moved.

What you will create

You will create a proposed folder map, a list of uncertain files, and a move plan that waits for your approval. The original files stay in place during this lesson.

Claude Cowork is available on paid plans, with access varying by surface and plan. Current Claude guidance says Cowork can work with files and perform multi-step tasks. The same guidance warns that agentic work has additional risks, so start with a copy of the folder and require a review stop.

Prepare the practice folder

Create this fictional file list in a folder named northstar-pilot:

northstar-pilot/
  brief-v3.docx
  brief-final.docx
  pilot-notes-2026-10-07.txt
  supplier-prices.xlsx
  supplier-prices-old.xlsx
  meeting-recording-link.txt
  readme.txt
  archive/
    brief-v1.docx

Add this text to readme.txt:

Project: Northstar supplier pilot
Owner: Mina
Current review: 2026-10-20
Do not share supplier prices outside the operations team.
The current brief is the version approved by Mina. The filename is not guaranteed to be final.

Do not use customer files, confidential prices, credentials, or a folder that contains unrelated work. A fictional folder is enough to learn the workflow.

Ask for a map first

Open Claude Cowork on an approved desktop, web, or mobile surface. If your account shows the newer unified Claude experience, start from the message box and use the task workflow available there.
Give Claude access only to a copy of northstar-pilot. Do not begin with the parent folder that contains other projects.
Paste the instruction below.
Wait for the proposed map and review it. Do not approve a move yet.

Inspect only the folder northstar-pilot and its archive subfolder. Do not move, rename, delete, edit, or upload any file.

Create a proposed folder map with these columns:
path, proposed destination, reason, confidence, question for the owner.

Rules:
- Preserve every original path in the report.
- Treat filenames as clues, not proof of which brief is current.
- Do not open or quote supplier prices beyond naming the file.
- Do not infer that brief-final.docx is approved.
- Flag files whose destination cannot be decided from the supplied evidence.
- End with a move plan that requires the owner to approve each proposed change.
- Include a recovery plan that says how to return a moved file to its original path.

Illustrative result

A useful result might propose archive/brief-v1.docx for the archive, keep readme.txt at the project root, and flag both brief-v3.docx and brief-final.docx for Mina to resolve. It should also flag the two price files for restricted handling. This is an editor-written example of a checkable result, not output generated by Claude Cowork.

Acceptance checks

Before approving any file operation, check that:

Every input path appears exactly once in the report.
The report does not call a file current, approved, obsolete, or safe to share unless the supplied notes say so.
Both price files carry the restriction from readme.txt.
The two brief candidates remain unresolved.
The move plan names an owner approval stop and a recovery path.
The original folder is still unchanged.

Troubleshooting

Cowork cannot see the folder: check the file access permission and confirm the folder you selected is the copy, not its parent. Claude’s help guidance also recommends checking the output location when files do not appear where expected.
It starts moving files: stop the task and restore the copy. Repeat the instruction with the explicit prohibition on file changes before asking for a proposal.
It picks the newest filename as current: point to the rule that filenames are clues, then require a confidence value and an owner question.

TRY / SKIP / USE: TRY this on a disposable practice folder or an approved copy. SKIP unattended cleanup of confidential or production folders. USE the proposed map as a review document, not as permission to move files.

Sources and next step

If the owner approves a move plan, make one small change at a time and compare the folder with the approved map after each change.