Define the outcome and action limits
By the end, you will brief a Cowork task with inputs, deliverables, checks and stop conditions. The scenario turns two fictional notes into a course plan. Examples are teaching material, not filmed demos.
Cowork fits multi-step work using tools and deliverables. Documentation checked on September 30, 2026 describes a rollout joining Chat and Cowork in one interface. A missing Cowork selector can mean the account has the new interface, not that the capability disappeared.
Begin with a small task requiring no sending, system changes or disclosure to others. “Handle the course” is not a sufficient brief.
Prepare fictional inputs and criteria
Create two text files or paste their contents:
course-notes.txt
Audience: employees with no AI-tool experience.
Goal: learn to write a request and check an answer.
Structure: three 30-minute units.
Date and budget are not set.
constraints.txt
Each unit needs a short exercise and a success check.
Do not use customers' personal information.
Do not publish or send material during preparation.
For local access, use a practice folder with copies only and inspect the granted access. For uploaded files, there is no need to connect your entire working folder.
A copyable brief
Draft a course plan from course-notes.txt and constraints.txt.
Before creating outputs, briefly show your plan and the inputs found.
Deliverable: a document with three 30-minute units,
each with a goal, short content outline, exercise and success check.
Keep a separate missing-details list: date, budget and approvals.
Do not invent missing details or use the web.
Do not modify source files, send, share or publish.
If a connection or change outside the practice folder is needed, stop and ask.
Read the plan. Confirm both files were found, total duration is 90 minutes and no date was chosen. A plan is intent; the eventual deliverable still needs inspection.
Redirect without restarting
Watch what Claude does and requests. If it proposes supplier research:
Stop supplier research. This task uses the files only to plan learning content.
Do not choose a supplier or price. Continue only with the defined deliverables.
Read any requested action and destination before approving. Creating a new file is not deleting its source. Stop unexpected actions and inspect before continuing.
Clarification can be the correct behavior. Do not demand “no questions” when a missing fact determines the outcome.
Check the deliverable against the brief
Illustrative structure:
Unit 1, 30 minutes: goal, audience and source; write a short request.
Unit 2, 30 minutes: facts and missing details; identify invented claims.
Unit 3, 30 minutes: revise a draft; change audience without changing facts.
Unresolved: date, budget and plan approval.
Open the file if created. Check three units, appropriate exercises and usable success criteria. Preserve missing details rather than hiding them under “ready to distribute”.
Unit 2 lacks a success check.
Add: the learner identifies at least two unsupported claims and corrects them.
Keep unit durations and approval status unchanged.
Reopen the updated file. Completion messages do not replace reading the output.
Cloud continuation and account state
Cloud tasks can continue with the computer closed. Local files and Desktop-browser capabilities depend on the computer and app being available. The next chapter examines that difference.
The official source includes a future October 6, 2026 notice moving new Pro and Max tasks to the cloud. That is a dated announcement, not a change already applied everywhere on September 30. Inspect where your actual task runs.
Continue with a focused revision or a new task using the output as input. Do not assume every work detail becomes Project knowledge or every generated file is written back locally.
Graded practice
Easy: a bounded brief
Provide two files and request a plan. Success: inputs, output and prohibited actions are explicit.
Intermediate: a focused correction
Add a success check to one unit. Success: the other units, durations and missing details stay unchanged.
Challenging: completion review
Compare every brief criterion with the deliverable. Success: distinguish task completion from suitability for use.
Troubleshooting and what not to approve
No Cowork selector: check new-interface rollout, plan and organization policy.
File missing: check access route, filename and app availability. Do not widen access automatically.
Plan too broad: define one output and permitted sources; require questions before widening scope.
Accidental sending or publication: drafting and execution differ. Explicitly prohibit sending during preparation and inspect what actually happened.
Missing-detail questions: provide only known facts. Leave the rest unresolved rather than inviting invention.
A good brief delegates work, not judgment about unlimited actions. The desired finish and forbidden paths are clear.