How Educators Can Use Claude Cowork to Turn a Semester Folder Into a Course Retrospective Packet

Warning: A semester folder can contain more than you need, including files with student identifiers. Keep the retrospective folder tight and remove any file that should not be part of the review packet.

Cowork requirements at a glance: Claude Desktop, a paid Claude plan (Pro/Max/Team/Enterprise), and Cowork research preview access.

If Claude Cowork is new to you

Start with the Claude Cowork explainer page in the site's Tools menu before you run this workflow. Cowork runs in Claude Desktop and can work with local files and folders you choose to share. For related examples, see the Claude Cowork tool hub and the Anthropic Workflows series.

Problem and who this is for

At the end of a term, you may have feedback exports, attendance notes, assignment summaries, weekly lesson plans, and informal observations spread across a semester folder. The retrospective packet is useful, but gathering the material is the hard part. That makes it a strong Cowork job.

This workflow is for educators, course leads, program coordinators, and instructional teams who want a practical end-of-term review packet.

Prerequisites

• Claude Desktop with Cowork access.
• A local semester folder with the course artifacts you want Cowork to review.
• A short file called retrospective-brief.txt with the audience, packet length, and the decisions the packet should support.
• A willingness to trim the folder before you run Cowork.

How to gather the source material

1. Create a clean semester-review folder and copy only the files needed for the retrospective into it.
2. Good candidates include feedback exports, assignment summaries, course notes, attendance trend reports, and major revision logs.
3. Bad candidates include random downloads, duplicate slide decks, and private material that does not belong in a review packet.
4. Create retrospective-brief.txt with the audience, the decisions the packet should support, and the sections you want. Example: what worked, where students struggled, what to revise next term.
5. If key files are in spreadsheets or LMS exports, keep them in their native format if readable. Cowork can inspect local files directly.

Numbered workflow steps

1) Set up a small local project folder before you start Cowork

Cowork works best when the folder is clean, current, and limited to the specific task. Create a top-level folder for this job, drop in only the files you want Claude to use, and add one short text file that explains the output format you want.

2) Let Cowork inspect the folder and build a working plan

{
  "task": "Inspect a semester-review folder and prepare a course retrospective packet plan",
  "input": {
    "folder": "LOCAL SEMESTER REVIEW FOLDER",
    "brief_file": "retrospective-brief.txt"
  },
  "rules": [
    "Inventory the files and identify what each contributes.",
    "Separate evidence of strengths, friction points, and revision opportunities.",
    "Keep uncertain inferences visible.",
    "Do not write the final packet until the plan is reviewed."
  ],
  "output": {
    "source_inventory": "What files are being used and why",
    "evidence_map": "Strengths, problems, and revision opportunities",
    "uncertain_items": "Areas that need human interpretation",
    "packet_plan": "Recommended section structure"
  }
}

3) Review the plan before you let Cowork finish the output

Read the source inventory before you let Cowork finish the packet. This is where you remove weak or irrelevant files and keep one noisy document from shaping the whole retrospective.

4) Ask Cowork for the finished deliverable

{
  "task": "Create a course retrospective packet from the reviewed semester folder plan",
  "input": {
    "approved_plan": "USE THE REVIEWED PLAN"
  },
  "rules": [
    "Keep the packet tied to the reviewed evidence map.",
    "Use headings for strengths, friction points, and next-term changes.",
    "Make uncertainty visible instead of flattening it into certainty.",
    "End with a short next-term action list."
  ],
  "output_format": {
    "type": "retrospective_packet"
  }
}

5) Save the result and archive the input folder

Rename the finished file clearly and keep it with the source folder. If this is a recurring workflow, duplicate the folder structure next time instead of starting from zero.

Tool-specific instructions

Cowork is a good fit because the core work is evidence gathering across a local folder, not just drafting one memo from memory. Folder instructions are especially useful if you prepare retrospective packets every term.

Quality checks

1. Every major point in the packet comes from identifiable source files.
2. One dramatic comment or one unusual week did not dominate the packet.
3. Next-term actions are limited enough to be realistic.
4. The packet reflects the audience and decision goals named in retrospective-brief.txt.

Common failure modes and fixes

The packet becomes too broad

Fix: trim the folder and tighten retrospective-brief.txt so Cowork knows what the packet is for.

Too much private material is included

Fix: remove or redact sensitive files before you run Cowork.

Weak evidence becomes strong claims

Fix: keep an uncertain-items section and review it before the final packet stage.

Sources Checked

• Anthropic Claude Help Center: Get started with Cowork (accessed 2026-03-23) https://support.claude.com/en/articles/13345190-get-started-with-cowork
• Anthropic Claude Help Center: Use Cowork safely (accessed 2026-03-23) https://support.claude.com/en/articles/13364135-use-cowork-safely
• Anthropic Claude Help Center: Installing Claude Desktop (accessed 2026-03-23) https://support.claude.com/en/articles/10065433-installing-claude-desktop

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Claude Cowork, file handling, plan availability, and setup paths.