Lab 2 · beginner · About forty-five minutes
Organise a folder of files safely with Claude Cowork
Work on copies, define the boundary, get a plan before any change, review the proposed moves and keep a way back.
You finish with
A folder reorganised by a rule you set, with a log of every change and nothing lost.
Before you start
- Access to Claude Cowork.
- A folder of files.
- Space for a duplicate.
Material: Your own local files. Do not use client or personal data for a first run.
Duplicate the folder
Copy the whole folder and work on the copy. This is not caution about the tool; it is caution about your own instruction, which is where ambiguity lives.
Checkpoint The original is untouched and elsewhere.
Write the rule as an outcome
Describe what should be true when it finishes, with one worked example. "Every invoice named YYYY-MM-DD-supplier.pdf, for example 2026-03-14-hartleys.pdf" beats "tidy up the invoices".
Checkpoint Your rule has an example in it.
Set the boundary explicitly
Name the folder, the file types in scope and what must not be touched. Implicit scope is how a task reaches somewhere you did not intend.
Checkpoint Your brief names a folder and at least one exclusion.
Add the four safety rules
Never delete — move to _needs-review. Never overwrite without stopping. Flag ambiguity rather than guessing. Log every change as from → to.
Checkpoint All four appear in the brief.
Request the plan and read it
Ask for the full list of intended changes before anything happens. This is where you discover the rule matched more than you meant.
Checkpoint You have read every line, not skimmed the summary.
Approve and spot-check
Let it run, then check ten results at random against your rule, and open the _needs-review folder.
Checkpoint Ten correct, and you understand why each review item is there.
Work only inside the folder I have selected. Do not read or modify anything outside it.
Outcome: every PDF is renamed to YYYY-MM-DD-supplier.pdf using the invoice date and supplier name printed on the document. Example: 2026-03-14-hartleys.pdf
Scope: PDF files only. Ignore every other file type and every subfolder named archive.
Rules:
1. Never delete anything. If a file cannot be handled, move it to _needs-review.
2. If a rename would overwrite an existing file, stop and ask me.
3. If the date or supplier is unclear, do not guess — move it to _needs-review.
4. Write changes.log listing every change as: old name → new name.
Before making any change, show me the complete plan.What finished looks like
A renamed set of PDFs, a _needs-review folder holding the genuinely ambiguous ones, and a changes.log you can read end to end. On a folder of fifty invoices expect a handful in review — that is the rule working, not failing.
Test criteria
- File count before equals file count after.
- changes.log line count matches the number of renames.
- Nothing was deleted.
- Ten randomly checked names match the rule.
If it goes wrong
- Too many files in _needs-review.
- Your rule is under-specified for the real variety. Read five of them and add a clause.
- It renamed files outside the intended set.
- The scope was implicit. Name the file types and the exclusions and re-run on a fresh copy.
- Dates read from the wrong place.
- State which source wins — the printed invoice date, not the file metadata.
Privacy and safety
Only point an agent at folders you have the right to share. Client documents, HR records and health information need a specific approval that a general plan does not give you.
Sources2 referenced
- Claude Cowork — product page
Anthropic · official product documentation · link checked 2026-09-06
- Guidance on AI and data protection
Information Commissioner's Office · regulatory guidance · link checked 2026-09-06
Links are checked at build time. If one has moved, tell us.
Read alongside
Claude Cowork: from request to finished files
A different shape of assistant. Instead of a conversation you copy out of, you hand over a task with a scope and get reviewable work back.
Organise files and repeatable workflows safely
File operations are the one place where a mistake is not recoverable by pressing undo. The safety routine is short and worth making automatic.