How Educators Can Use Claude Cowork to Turn a Folder of Readings, Notes, and Slide Drafts Into a Workshop Pack

Warning: Cowork can make real changes to local files. Give it access only to the folder for this workshop, not your whole teaching archive.

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

A workshop pack usually lives in too many places at once: readings in one folder, notes in another, half-finished slides somewhere else, and the handout still in your head. Claude Cowork is a good fit when the real problem is not writing one paragraph. The real problem is gathering local files, sorting what matters, and producing a finished working set.

This workflow is for instructors, trainers, faculty, and coaches building a workshop from material they already have on their computer.

Prerequisites

• Claude Desktop with Cowork access.
• One local folder containing the workshop readings, your notes, and any prior slide drafts.
• A short file called workshop-brief.txt with audience, session length, and learning goals.
• Enough disk organization that you can isolate only the files for this workshop.

How to gather the source material

1. Create one local folder for the workshop and copy only the relevant source files into it.
2. Rename files clearly. Example: week-3-reading.pdf, slide-draft-v2.pptx, facilitation-notes.txt.
3. Move outdated materials into an archive subfolder if you want to keep them nearby but out of the main run.
4. Create workshop-brief.txt with the audience, time limit, learning goals, and the exact outputs you want. Example: slide deck outline, participant handout, missing-items list.
5. If the readings include scans or images, make sure they are readable or convert them to searchable PDFs first.

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 this workshop folder and prepare a plan for a complete workshop pack",
  "input": {
    "folder": "LOCAL WORKSHOP FOLDER",
    "brief_file": "workshop-brief.txt"
  },
  "rules": [
    "Inspect only files in the selected workshop folder.",
    "Identify readings, notes, existing slides, and missing source gaps.",
    "Propose a slide structure, handout structure, and unresolved item list.",
    "Do not finalize files until the plan is reviewed."
  ],
  "output": {
    "workshop_plan": "Clear plan for the pack",
    "source_inventory": "What files are being used",
    "missing_items": "What is still needed or unclear"
  }
}

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

Check the source inventory first. If Cowork pulled in the wrong draft or an outdated reading, fix that before the output stage. Then confirm the workshop plan still matches the audience and time limit in workshop-brief.txt.

4) Ask Cowork for the finished deliverable

{
  "task": "Create a workshop pack from the reviewed local folder plan",
  "input": {
    "approved_plan": "USE THE REVIEWED PLAN",
    "deliverables": [
      "slide deck outline or draft",
      "participant handout",
      "missing-items checklist"
    ]
  },
  "rules": [
    "Write outputs directly from the files in the selected folder.",
    "Keep the workshop aligned to the stated time limit.",
    "Use the missing-items checklist to show what still needs human input.",
    "Do not fabricate citations or source details not present in the folder."
  ],
  "output_format": {
    "type": "workshop_pack"
  }
}

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 fits this job because the friction is folder-level work: file inspection, source sorting, gap finding, and multi-file output. Use folder instructions in Claude Desktop if you run this kind of workshop build repeatedly.

Quality checks

1. The source inventory lists only files that belong to this workshop.
2. The slide structure fits the session length.
3. The participant handout matches the actual workshop plan.
4. The missing-items list is honest about what Cowork could not infer.

Common failure modes and fixes

Old materials leak into the pack

Fix: archive or remove outdated files before you start Cowork.

The output is too broad

Fix: make workshop-brief.txt tighter. Session length and audience level matter a lot.

Scanned readings are hard to use

Fix: convert them to searchable PDFs before you run the folder through Cowork.

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.