Working on folders, docs, and spreadsheets

Your Downloads folder has 47 PDFs named Scan_2026-03-12.pdf, three screenshots of receipts from a phone, a voice memo titled “client call rough,” and a half-written notes doc that ends mid-sentence. Chat can summarize one of those files if you upload it. Chat will not turn the pile into a clean expense sheet, a one-page status report, and a short deck for Monday, all saved next to the source material. That is the job Claude Cowork is built for: multi-step work on folders, documents, spreadsheets, and presentations you can open and check.

This is Part 3 of Claude Cowork tutorial. Parts 1 and 2 covered when to pick Cowork versus chat or Claude Code, then setup and a first real file task. Here we stay on the core office loop: organize files, draft docs from messy notes, build sheets with working formulas, and ship PPTX decks from rough inputs. If Claude itself is still new, start with Learn Claude from scratch. For product orientation (what Cowork is versus Code and chat), keep the Claude product map nearby. Software repos and terminals belong in the Claude Code tutorial, not this part.

What you’ll learn

How to treat a working folder as the system of record for a Cowork task
Folder jobs that pay off first: organize, rename, receipts to expense sheet
How to turn notes and transcripts into reports and briefs you can still edit
What “spreadsheet with formulas” and “real PPTX” mean in practice
A five-part task recipe: goal, inputs, constraints, format, done check
Review habits so numbers, names, and file paths do not ship on trust alone
A short practice set you can finish this week without connector sprawl

Product labels, export formats, and UI paths move. Treat this as a durable mental model. Verify live details in Anthropic’s Get started with Claude Cowork guide and related Help Center articles before you write team policy.

Three file jobs, one working folder

Cowork shines when the artifact lives on disk (or in a session file tree you can download), not only as text in a thread. Group the work into three buckets so you stop writing vague prompts like “help with my files.”

Job family	What you want out	Good first ask
Folders	Order you can navigate next week	Sort, rename, archive clutter without deleting secrets
Docs	A report, brief, or status note	From transcripts and scrap notes into one readable file
Sheets and decks	Excel or PPTX you open in real apps	Formulas, tabs, slides with a clear audience

You can chain them. Receipts get renamed, then rolled into expense.xlsx, then summarized in a one-pager for your manager. Say the chain out loud in one task, or run three short tasks if you want tighter review between steps. Either way, name the output files and the folder where they should land.

Rule of thumb: If you cannot point at a folder and a finished filename, you are still in chat mode. Switch to outcome language: “Save Q2-expense-summary.xlsx in this folder.”

Folders: organize, rename, receipts to expense

Folder work is the safest place to build muscle. The blast radius is usually local, reversible if you avoid delete-happy prompts, and easy to audit with Finder or File Explorer. Desktop Cowork is still the strongest path when the source of truth is a local directory.

Organize without a trash fire

Bad prompt: “Clean up my Downloads.” That invites creative interpretation. Better: “In the connected folder ClientX-trip, create subfolders receipts, notes, exports. Move files by content when the name is useless. Do not delete anything. Leave a short README.txt listing what moved.”

Why that works: Claude knows the taxonomy, the no-delete constraint, and the audit artifact. When you come back, you can skim README.txt instead of reconstructing history from vibes.

Rename with a pattern, not poetry

Receipt scans and phone photos often arrive as IMG_4821.jpg. Humans hate that. Machines only care if you give them a pattern.

Example recipe language:

Goal: Rename receipt images and PDFs in /Receipts-raw for expense logging.
Pattern: YYYY-MM-DD_vendor_amount.ext when date/vendor/amount are readable.
If a field is unclear, use unknown and list the file in rename-log.txt.
Constraints: no deletes; no overwrite of existing final names; keep originals only if I say so (default: rename in place).
Done when: every file matches the pattern or is listed in rename-log.txt with a reason.

That log file is not bureaucracy. It is how you catch the hotel bill Claude misread as a coffee shop.

Receipts to expense sheet

This is the classic Cowork demo because it matches real pain. You dump PDFs and photos into a folder. You ask for a spreadsheet. You open Excel and check totals.

Put only this trip’s receipts in a dedicated folder (not your whole home directory).
State columns: date, vendor, amount, currency, category, payment method, notes, source filename.
Ask for working formulas: sum by category, grand total, maybe a simple pivot-friendly flat table.
Require a confidence column or a “needs human check” flag when OCR is fuzzy.
Open the file yourself. Spot-check three line items against the original PDFs.

Sample task you can paste and adapt:

From the connected folder Receipts-March, build expense.xlsx with columns:
date, vendor, amount, currency, category, card_last4, source_file, confidence.
Categories allowed: travel, meals, software, other.
Add a Summary sheet with SUMIF totals by category and a grand total formula.
Do not delete source files.
If amount is unreadable, leave amount blank and set confidence to low.
Done when: expense.xlsx opens, formulas calculate, and every source file appears once in source_file.

Notice what is missing: “be smart,” “use best judgment on categories,” or “email finance when done.” Smart is fine inside the folder. Email and finance systems wait until you intentionally add connectors (Part 4).

Documents: reports from notes and transcripts

Doc work is where people over-trust fluent prose. Claude can stitch a clean narrative from messy inputs. Fluency is not accuracy. Your job is to force structure and a verification pass.

What “from notes” should mean

Inputs might be: bullet notes from a call, a rough transcript, a PDF brief, screenshots of Slack decisions, a previous status doc. Outputs might be: a one-page status, a meeting summary with decisions and owners, a client-facing update, an internal incident writeup.

Spell the audience. “For my manager who has three minutes” produces a different doc than “for legal review” or “for the client without internal slang.”

A solid report brief

Goal: Produce client-status-2026-03-20.docx (or .md if you prefer plain text) from files in /ClientX/notes.
Audience: client sponsor; no internal code names.
Required sections: progress since last update, decisions needed, risks, next 14 days.
Constraints: every risk must cite a source filename; do not invent metrics; if a number is missing, write "not in source materials."
Format: short paragraphs, bullets under each section, max ~600 words.
Done when: file saved in /ClientX/exports and a sources section lists every input file used.

The “not in source materials” line is gold. Without it, models fill gaps with plausible filler. You want empty cells and honest hedges more than a confident fiction.

Transcripts without the novel

Long transcripts tempt “summarize everything.” Prefer task shapes that match how you use meetings:

Decisions only: what was agreed, who owns it, by when
Action list: verbs and owners, no speechifying
Open questions: unresolved items, not closed debate
Quote harvest: pull candidate quotes with timestamps if the transcript has them

If the transcript is wrong (bad speaker labels, missing attendees), say so in constraints. Claude cannot fix a bad recording by sounding sure.

Spreadsheets with formulas (not CSV theater)

A CSV dump is a text file wearing a spreadsheet costume. Cowork’s useful bar is higher: workbooks you open in Excel or Google Sheets with formulas that recalculate, clear sheets, and sometimes light formatting. Anthropic’s Cowork materials call out professional outputs such as Excel with working formulas. Still verify in the real app.

Ask for structure, not only rows

Ask for	Why it helps
Named sheets (Raw, Clean, Summary)	Separates source from analysis
Formulas for totals and rates	You can change an input and watch results move
Data types and date formats	Avoids text that only looks like numbers
A “checks” area	Row counts, null counts, sum control totals
No hidden magic	Prefer visible formulas over opaque scripts you never open

Example: monthly pipeline summary from a CRM export sitting in a folder.

Build pipeline-weekly.xlsx from deals-export.csv in this folder.
Sheets: Raw (unchanged import), Clean (normalized stage names), Summary.
On Summary: count of deals by stage, sum of amount by stage, win rate = Closed Won / (Closed Won + Closed Lost).
Use formulas, not pasted values, for all Summary metrics.
Add a Checks sheet: row count Raw vs Clean, sum of amount Raw vs Clean.
Flag stages not in {Prospect, Qualified, Proposal, Closed Won, Closed Lost} on Clean with a StatusNote column.
Done when: file opens, formulas calculate, Checks shows matching control totals.

If you live in Excel add-ins as well as Cowork, remember the handoff: Cowork can create the workbook; deeper in-grid editing may continue in Claude for Excel depending on your plan and setup. For this tutorial, master the “file appears in the folder and formulas work” loop first.

Presentations: real PPTX, not outline cosplay

People still paste chat bullets into PowerPoint by hand. Cowork can produce an actual .pptx from notes, a report, or a sheet summary. That is useful. It is also how “workslop” decks spread if you never open the slides.

Give the deck a job

Audience: exec skim, team deep-dive, client workshop
Time: 5 minutes vs 30 minutes changes slide count
Claim limit: only numbers present in the source folder
Slide skeleton: title, situation, evidence, options, ask
Visual restraint: prefer simple charts from your sheet over decorative clutter

Sample ask:

Create weekly-status.pptx for a 10-minute team meeting from status-notes.md and pipeline-weekly.xlsx.
Slides: (1) title + week, (2) three outcomes, (3) metric snapshot with numbers only from the sheet, (4) risks, (5) asks.
Max 6 slides. No stock-photo metaphors. One chart max if the sheet supports it.
Save to /exports. List any number you could not source in a final "Gaps" slide instead of inventing it.
Done when: PPTX opens in PowerPoint or Keynote and every metric traces to the sheet.

Then do the human half: fix the one slide that overclaims, delete the cute title nobody needs, and check that the chart matches the Summary sheet. Cowork is a first pass, not the meeting owner.

The task recipe (use this every time)

Most failed Cowork runs are vague goals plus silent constraints. Use the same five fields until they become muscle memory.

Field	Question it answers	Weak	Strong
Goal	What finished work looks like	Help with receipts	Build expense.xlsx for March trip
Inputs	Which folder/files are in scope	My files	Connected folder Receipts-March only
Constraints	What not to do	(none)	No deletes; USD only; flag low confidence
Format	File type and shape	A spreadsheet	xlsx with Data + Summary sheets, SUMIF formulas
Done check	How we know to stop	Looks good	Opens, formulas work, every source_file listed

Pasteable skeleton:

Goal:
Inputs (folder/files):
Constraints (no deletes, privacy, tone, allowed categories):
Output format (filename, sheets/sections, formulas/slides):
Done check (openable file + tests I will run):

Global instructions in Cowork settings can hold standing preferences (tone, default “no deletes,” your name and role). Folder instructions can hold project-specific laws when you attach a local folder on desktop. Session text still carries the goal for this task. Do not bury a one-off deadline only inside global instructions and then wonder why every task sounds like last quarter’s project.

Worked example: one folder, three artifacts

Scenario: you ran a two-day onsite. Folder Onsite-Acme holds receipt images, day1-notes.md, day2-transcript.txt, and a rough agenda.md.

Task A (folders): organize into receipts, notes, exports; rename receipts; write file-map.txt.

Task B (sheet): build exports/expense.xlsx from receipts with formulas and a confidence column.

Task C (doc + deck): from notes and transcript, write exports/onsite-summary.md (decisions, owners, open questions) and exports/onsite-readout.pptx (5 slides for internal leadership). Numbers only from the expense sheet or explicit “n/a.”

Your review checklist after Task C:

Open three random receipts vs expense rows
Confirm no delete of originals
Search the summary for any metric not in the sheet
Read owners aloud: are they real people on the project?
Click through every slide once at presentation zoom

That is a full Cowork day without mail connectors, browser control, or plugin marketplaces. Master it before you add power in Part 4.

Review habits that keep you honest

Agentic file work fails in boring ways: wrong vendor, doubled rows, a slide that invents “up 12%,” a rename that overwrote a final PDF, a report that softens a risk the transcript stated clearly.

Artifact	Minimum human check
Renames	Spot-check 5 files; read the rename log
Expense sheet	3 line items vs source; formula totals vs manual sum
Report	Every number has a source; no silent gap-filling
Deck	Slide-by-slide; delete claims you cannot defend live
Anything deleted	Should have required explicit allow; if not, stop and review settings

Cowork is designed so permanent deletes need your explicit permission in normal flows. Do not “help” it by pre-authorizing destructive habits in Skip modes you do not understand yet. Autonomy modes get their own part later in this series.

If your work touches regulated data, payroll, or customer secrets, re-read your company policy and Anthropic’s safety guidance for Cowork. A tidy folder is not a compliance program.

Common mistakes

Connecting the whole home directory

You wanted receipts. Claude also saw tax PDFs and a personal journal. Use a dedicated working folder. Copy or move inputs in. Export outputs out.

Prompting like a micro-manager, then complaining it is slow

Forty tiny steps with no outcome statement burns usage and patience. State the deliverable and constraints. Intervene when the plan is wrong, not after every file open.

Accepting a “spreadsheet” that is only text

If Summary numbers are pasted values, you cannot safely change inputs. Ask for formulas and re-open the file after a one-cell edit.

Mixing chat memory with Cowork memory expectations

As of Anthropic’s current Help Center notes, chat memory does not fully carry into Cowork the way people hope; project-scoped memory inside Cowork is the more relevant idea. Put critical laws in the task, global instructions, or folder instructions instead of assuming last month’s chat “remembers the brand voice.”

Skipping the done check

Without a done check, Claude optimizes for “produced something.” With a done check, you optimize for “opens, calculates, lists sources.”

How to practice this week

Create a throwaway folder with 15 messy files (fake receipts are fine).
Run one organize + rename task with a rename log and no deletes.
Build expense.xlsx with formulas and a confidence column; break one input on purpose and confirm the sheet reacts.
Turn two pages of rough notes into a one-page status with a sources list.
Build a 5-slide PPTX from that status; delete any slide you would not defend.
Save your best task text as a personal template (the five-field recipe).

Still shaky on everyday Claude habits (Projects, privacy, judgment)? Stay with Learn Claude. Still choosing among chat, Code, and Cowork? Revisit the product map. Building software instead of expense sheets? Switch to the Claude Code tutorial.

What’s next

Part 4 covers plugins and connectors for office work: what a plugin bundles (skills, connectors, sub-agents), how mail/drive/calendar access changes the risk model, why browser and computer use sit higher on the ladder, and how to add power only when a folder-only task is not enough.

Quick recap

Point Cowork at a dedicated working folder; name the output files.
Win first at organize, rename, and receipts → expense with formulas.
Docs need audience, sections, and “not in sources” honesty.
Sheets need formulas and checks; decks need a job and traceable numbers.
Use the recipe every time: goal, inputs, constraints, format, done check.
Review like a skeptic; fluency is not a control total.

Sources

Research and further reading used for this article:

Anthropic Help Center: Get started with Claude Cowork (capabilities, local files, professional outputs, usage)
Anthropic Help Center: Use Claude Cowork safely (risks, permissions mindset)
Anthropic Help Center: Use Claude Cowork on web, desktop, and mobile (where sessions run)
Anthropic: Claude Cowork product page (positioning for knowledge work)
Anthropic Help Center: Create and edit files with Claude (document and file creation context across Claude surfaces)
Analytics Made Simple: Learn Claude from scratch (everyday foundation)
Analytics Made Simple: Claude product map (chat vs Code vs Cowork orientation)
Analytics Made Simple: Claude Code tutorial (software-agent counterpart to this office track)