Claude Cowork in Practice – Real Files, Real Workflows By the end of this lesson, students should be able to: What the Cowork task loop is. In Chat mode, every Claude response is a direct reply to your message – you prompt, Claude responds, you prompt again. In Cowork, Claude can take multiple actions in sequence before returning to you: reading files, using plugins, writing outputs, calling tools. This changes the nature of the interaction. The Cowork task loop has four phases: 1. Assignment: You give Claude a clear task with context. In Cowork, this assignment may span multiple actions – Claude will work through them in sequence. The clearer and more specific the assignment, the more autonomously Claude can work before needing guidance. 2. Generation: Claude works through the task steps. For multi-step tasks, this involves Claude making decisions about how to proceed. You may or may not see intermediate steps depending on the task and mode. 3. Review: When Claude presents output or completes a task phase, you review what it produced. Was the approach correct? Are the outputs accurate? Does the direction need to change? 4. Steer: Based on your review, you provide steering input – confirming to continue, redirecting an approach, correcting an error, or stopping work entirely. Then the loop repeats for the next phase. Writing effective task assignments for multi-step work. A good Cowork assignment includes: "Review the three documents in this Project and produce a single two-page synthesis identifying the major disagreements between them. Do not access external sources – use only the uploaded files. Check in with me before writing the final synthesis if the documents cover more than five distinct disagreements." – This is a Cowork-ready assignment. Appropriate intervention points. In multi-step work, resist the urge to intervene at every step – that defeats the efficiency purpose. Intervene when: Trust Claude to work through defined task steps without constant checking. Responsible steering vs. over-reliance. Steering is maintaining appropriate oversight while allowing efficient operation. Over-reliance is trusting Cowork output without reviewing whether it achieved the goal. Both directions are failure modes – steering too aggressively negates the efficiency; not steering at all leads to undiscovered errors at the end. A research analyst gives Claude a Cowork task assignment: "Read the three market reports in this Project. Produce a bulleted list of the five most significant market trends they collectively support. For each trend, note which reports support it. Work from the uploaded files only. Come back to me before writing up if any trend seems contradicted by one of the reports." Claude works through the files, identifies trends, and returns with a check-in because one trend is supported by two reports but contradicted by a third. The analyst reviews the contradiction and provides steering: "Note the contradiction in the trend description – don't resolve it, just flag it." The loop completes with a useful output that accurately reflects the source material. You can set the "check-in threshold" explicitly in a Cowork assignment by telling Claude at what points you want it to confirm before proceeding. "Proceed without checking in unless you encounter a decision point where the right approach is genuinely ambiguous" keeps Claude moving efficiently while preserving oversight on real judgment calls. Without this instruction, Claude's check-in frequency may not match what you need. Cowork tasks that involve writing or editing files, sending communications, or performing actions through connected apps (email, calendar, project management tools) have direct real-world effects. Review assignments carefully before initiating. Multi-step Cowork tasks touching production systems, client-facing content, or sensitive data warrant a conservative approach: ask Claude to present what it will do before doing it, rather than proceeding autonomously. Design a Cowork task assignment for a real task from your work. Write the assignment following the five-component structure: goal, scope, available resources, constraints, and check-in preference. Do not execute it yet – just write and review the assignment. Assess: is the scope clear enough for Claude to work without ambiguity? Is the check-in preference explicitly stated? Revise until both answers are yes. You should be able to name the four phases of the Cowork task loop, describe what a good multi-step assignment includes, explain when to intervene versus let Claude proceed, and distinguish between responsible steering and over-reliance. Log in and enroll to access lesson quizzes.
Lesson 1: The Cowork Task Loop – Assign, Review, Steer
Lesson Objectives
Lesson Content
Practical Example
Lesser-Known Tip
Safety Notes
Practice Task
Completion Check