Level 3 · Guide 11
Choose between Claude Chat and Cowork
Use Chat for explanations, ideas, and short drafts that remain in the conversation. Use Cowork for outcome-oriented work involving files or tools, but define access scope, checkpoints, and external-action approval before starting.
Product features may change. Check the last verified date and official sources.
Core concepts to know first
Focus on the decisions these terms support in real work rather than memorizing them.
Core concepts
1. Distinguish answers from work
Task complexity and execution permission are separate dimensions. Cowork may handle more steps, but the operator still limits files, tools, write actions, and the point at which work must stop for review. In this guide, the first observable move is to break one recurring task into observable actions.
2. Complexity and permission are separate axes
Assign conversation-only actions to Chat and bounded execution to Cowork. Preserve the approved input and the evidence behind the result so a reviewer can distinguish what the source says from what Claude inferred. This directly controls the risk that a small request can expand into unexpected tool use.
3. Recovery matters more than apparent completion
Mark every write or external effect as a stop-and-review point. Record the decision and the remaining uncertainty instead of hiding it in polished prose. The review must explicitly test whether broad folders can expose unrelated files.
4. Use four questions to choose the surface
Treat the possibility that a completed draft can be mistaken for approval to send as a required test case. The intended result is a chat-versus-cowork delegation map with approval points, not an unreviewed answer that merely looks complete.
Synthetic work scenario
How this applies at work
This scenario was written for learning and is not a real customer case.
A fictional operations team maps a weekly report workflow. Chat explains the template; Cowork may organize synthetic files and draft the report, but it stops before sending, deleting, publishing, or changing permissions.
The scenario is newly written for this guide and is neither a customer case nor a performance claim. Its specific deliverable is a chat-versus-cowork delegation map with approval points. A reviewer can reproduce the work from the synthetic inputs without access to customer, employee, health, contract, or confidential company data.
Try it yourself
Choose one small task and follow the steps. Confirm organizational policy and data boundaries before using sensitive materials.
Step 1. Break one recurring task into observable actions
Break one recurring task into observable actions. Use only approved synthetic material and record both the evidence and any remaining uncertainty.
Verify: Confirm that another reviewer can reproduce the input, result, evidence, and stop point.
Step 2. Assign conversation-only actions to Chat and bounded execution to Cowork
Assign conversation-only actions to Chat and bounded execution to Cowork. Use only approved synthetic material and record both the evidence and any remaining uncertainty.
Verify: Confirm that another reviewer can reproduce the input, result, evidence, and stop point.
Step 3. Mark every write or external effect as a stop-and-review point
Mark every write or external effect as a stop-and-review point. Use only approved synthetic material and record both the evidence and any remaining uncertainty.
Verify: Confirm that another reviewer can reproduce the input, result, evidence, and stop point.
Completion checklist
Check only what you verified yourself. Every item must be checked before saving completion.
Some items are still unchecked. Review the result again.
What could go wrong?
Plausible language does not guarantee accuracy. Compare the result with originals, calculations, permissions, and current information.
- A small request can expand into unexpected tool use
- Broad folders can expose unrelated files
- A completed draft can be mistaken for approval to send
Boundaries that require human review
Academy practice stops at draft, preview, or approval pending. Actions with real impact require separate owner approval outside Academy.
What AI can do
- Step 1. Break one recurring task into observable actions
- Step 2. Assign conversation-only actions to Chat and bounded execution to Cowork
- Step 3. Mark every write or external effect as a stop-and-review point
What a person must approve
- Applicable law, contract, organizational security policy, and explicit approval boundaries take priority. Stop and ask the responsible owner when they conflict.
- Academy exercises never send, publish, purchase, delete, execute contracts, or change permissions. A responsible person performs any real action through a separate process.
This guide is educational and does not replace legal, security, or privacy judgment for your organization.
Questions about this guide
- When is this guide complete?
- It is complete when the stated outcome is ready and another reviewer can retrace the inputs, evidence, boundaries, and decision. The target outcome is “A Chat-versus-Cowork delegation map with approval points.”
- May I practice with real company data?
- No. Use synthetic material in the Academy. Real data requires a separate review of policy, legal basis, contracts, minimization, retention, deletion, and the approved environment.
- What if the product screen differs from this guide?
- Product behavior can change. Check the verification date and official sources, then retest the current account and plan with a small, low-risk example.
Official sources and further reading
Recheck the current product and policy status in these primary sources.
Authorship and review
Save progress
Completion and checklist items are saved only in this browser. They do not sync to other devices or browsers.
Academy does not collect or store work materials, prompts, or outputs. It runs no separate analytics scripts beyond basic server access logs.