The workspace pattern — one folder, four subfolders

TL;DR. One workspace folder per function. Inside it, four things: inbox/, output/, archive/, and CLAUDE.md. Always. Teams that pick this pattern in week one ship consistent results across operators by week three. Teams that don't pick a pattern are still arguing about file naming in month three.

The pattern#

~/cowork-{function}/
├── inbox/        # raw inputs you drop here for processing
├── output/       # cowork-generated artifacts
├── archive/      # finished work moved out of the way
└── CLAUDE.md     # house rules, prompt templates, do-nots

Three folders and one file. That is the entire pattern. The opinionated bit is that there are exactly three folders — not five, not seven — and that the file lives at the workspace root.

Why these four#

inbox/ isolates raw material from finished work. You can tell Cowork "process the new files in inbox" and it will not touch anything else. Without an inbox, every prompt becomes "look at the folder and figure out what's new" — slower, less reliable, and harder to script.

output/ is where Cowork writes. Easy to back up, easy to share, easy to audit. A single place to look for "what did Cowork ship this week?"

archive/ is the explicit we are done with this zone. Tinkso recommends a monthly automated move from output → archive so the active workspace stays focused on this period's work.

CLAUDE.md is the contract. House style, file naming, formats, things never to do. Cowork reads it on every session — it survives memory resets and acts as the team's standing agreement with the model. See CLAUDE.md and memory.

One workspace per function (not per person)#

• Do create one workspace per function — Finance, Marketing Ops, Legal, Operations. Multiple operators share the same one.
• Don't create one workspace per person. You will end up with twenty inconsistent CLAUDE.md files and nobody owning the pattern.
• Edge case: highly confidential single-user work — a CEO's personal pipeline, a CFO's board prep — gets its own workspace. Document why in writing.

The function-not-person rule is the second-biggest decision in this pattern, after the four-folder shape. It is also the one most teams resist initially. Push through it.

Where to put the folder#

• Local laptop, synced via OneDrive / Google Drive / Dropbox client — recommended for most teams. Cowork runs on the local copy; the cloud handles backup and team access.
• Network share mounted as a local path — works, but slower with more "file is locked" errors. Acceptable for less-active workspaces.
• Pure cloud (no local sync) — does not work. Cowork needs a real path on the laptop.
• Desktop, Documents root, or system folders — never. Always a dedicated path with a clear name.

Naming conventions#

• Folder names — lowercase, hyphens. cowork-finance, not Cowork Finance.
• File names — YYYY-MM-DD_description.ext for time-bound work; [client]_[doc-type]_v[n].ext for client work.
• Avoid spaces in workspace folder paths. They are not a hard error, but they make scripted prompts brittle and break shell snippets.

Sharing across the team#

• Sync the workspace via the cloud client of choice. The cloud handles distribution; Cowork operates on the local copy.
• Document who has the workspace folder grant in CLAUDE.md: "granted to: alice@…, bob@…". This is the auditable record of who can run Cowork on these files.
• For deeper governance — segmenting access, separating restricted data — see Access & folder policy.

Anti-patterns#

• "I'll just give Cowork access to my whole user folder." Never. Workspace folder, period.
• "I'll let people make their own subfolders inside." That part is fine. Don't let people invent their own top-level structure — inbox/, output/, archive/, CLAUDE.md are non-negotiable.
• "Inbox can be the team's Outlook folder." It cannot. Use a synced cloud folder dedicated to Cowork.
• "We don't need a CLAUDE.md, we'll just be consistent in our prompts." You won't. Write the file.

Tinkso's take#

The workspace pattern is the most underrated multiplier in mid-market deployments. We treat workspace creation as a hard milestone in delivery, not a tip in passing. The hour spent setting it up properly compounds across every operator and every prompt that follows.

When clients push back ("can't we just see what people do organically?"), we point to engagements where we let that happen and watched four operators end up with four incompatible folder shapes inside three weeks. The pattern is opinionated for a reason.

Try this#

Create your function's workspace right now. Use the structure above. Drop a placeholder CLAUDE.md containing nothing but TODO: house rules — see /bible/getting-started/claude-md-and-memory so the file exists and the team can edit it together at the next planning session.