How Educators Can Use Claude Cowork to Turn Past Exam PDFs and a Syllabus Into a Revision Guide

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

Students want a revision guide, but the best clues are scattered across old exam PDFs, current syllabus documents, and maybe one faculty note about what changed this term. This is a classic local-folder problem, which is exactly where Cowork can help.

This workflow is for instructors, program staff, tutors, and coaches who want a source-grounded revision guide without manually rereading every prior paper.

Why Cowork fits this workflow

Cowork fits this workflow because it can inspect a local folder containing multiple past exam PDFs, the current syllabus, faculty notes, and a revision brief before drafting. The useful work is not only writing the guide. It is comparing documents, finding repeated patterns, spotting outdated areas, and building a topic map anchored to the current syllabus.

Use Cowork when the working set is a folder of documents that need to be read together. It can inventory the syllabus, compare past exams, flag low-quality scans, separate current topics from historical patterns, and prepare a guide plan before creating the final revision guide.

Why not normal Claude chat or just a Skill?

Normal Claude chat can help if you manually upload the files and paste the context. That may be enough for a short one-off guide. It is weaker when the working set is a local folder with multiple PDFs, a syllabus file, notes, and repeat use across courses or exam cycles.

A Skill can standardize the guide format, such as topic sections, checklist style, and caution language. It does not replace Cowork's document-comparison layer. For this workflow, Cowork is the better source inspection and comparison tool, while a Skill is only optional formatting support.

Prerequisites

• Claude Desktop with Cowork available on a paid Claude plan.
• One clearly scoped local revision-guide folder or Cowork project.
• A short file called revision-brief.txt with the student level, exam date, and the desired output length.
• A decision on whether you want a broad topic guide or a more selective high-yield guide.

Set up this workflow as a Cowork project

For a recurring course or exam cycle, create one Cowork project for revision-guide work. Keep the current syllabus separate from old syllabi so Cowork can anchor the guide correctly.

Use this project structure:

current-syllabus/
past-exams/
faculty-notes/
output-guide/
archive-old-syllabi/
revision-brief.txt

Use current-syllabus for the syllabus that controls this revision cycle. Use past-exams for prior papers, marking schemes, or old exam PDFs that are allowed as supporting evidence. Use faculty-notes for approved notes about format changes, changed readings, or topics that should be deemphasized. Use output-guide for finished drafts. Move old syllabi into archive-old-syllabi so Cowork does not treat them as the current source of truth.

Use revision-brief.txt to state the exam date, student level, current course scope, desired guide length, and any wording you want to avoid.

Add project instructions so future runs keep the syllabus anchored:

{
  "project_name": "Revision Guide Builder",
  "project_purpose": "Use Claude Cowork to compare past exam PDFs against the current syllabus and create a revision guide that emphasizes likely topic areas without promising exact repeats.",
  "project_instructions": [
    "Treat the current syllabus as the anchor document.",
    "Use past exams only as supporting evidence for topic emphasis and question style.",
    "Separate current-syllabus topics, repeated historical patterns, and outdated or uncertain areas.",
    "Do not promise that any topic or question type will appear on the future exam.",
    "Flag low-quality scans or unreadable sections before drafting.",
    "Create a topic map and guide plan before drafting the final revision guide.",
    "Save final outputs in output-guide."
  ],
  "file_naming": "revision-guide-course-exam-yyyy-mm-dd"
}

These instructions help keep the same comparison rules across future course or exam-cycle updates.

How to gather the source material

1. Create one local revision-guide folder or Cowork project.
2. Put the current syllabus in current-syllabus.
3. Put past exam PDFs in past-exams and rename them clearly by year or term so Cowork can tell them apart.
4. Put approved notes about exam changes, syllabus changes, or known exclusions in faculty-notes.
5. Move old syllabi into archive-old-syllabi so they do not compete with the current syllabus.
6. If any exam is only a photo or a low-quality scan, convert it to the clearest searchable PDF you can first.
7. Create revision-brief.txt with the exam date, student level, topic coverage, and whether you want a compact or fuller guide.

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 the project folder, keep the current syllabus separate from past exams, and add revision-brief.txt before asking for output.

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

{
  "task": "Inspect a folder of past exams and a syllabus, then prepare a revision-guide plan",
  "input": {
    "folder": "LOCAL REVISION-GUIDE PROJECT OR FOLDER",
    "current_syllabus_folder": "current-syllabus",
    "past_exams_folder": "past-exams",
    "faculty_notes_folder": "faculty-notes",
    "brief_file": "revision-brief.txt"
  },
  "rules": [
    "Use the current syllabus as the anchor document.",
    "Use past exams only as supporting evidence for topic emphasis and question style.",
    "Identify repeated topics, question styles, and high-frequency areas from the past papers.",
    "Separate current-syllabus topics from outdated or uncertain patterns.",
    "Flag low-quality scans or unreadable sections before drafting.",
    "Do not draft the revision guide until the plan is reviewed."
  ],
  "output": {
    "topic_map": "Likely revision priorities tied to the syllabus",
    "question_patterns": "Repeated structures or task types",
    "outdated_or_uncertain_areas": "Patterns that may not still apply",
    "draft_plan": "Proposed guide structure"
  }
}

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

Check whether Cowork overemphasized one old exam or one outdated topic. The current syllabus should still be the anchor, with past papers used as supporting evidence, not the other way around.

Also check scan quality and missing coverage. If a past paper is unreadable or a topic appears in old exams but not the current syllabus, keep it marked as uncertain or outdated.

4) Ask Cowork for the finished deliverable

{
  "task": "Create a revision guide from the reviewed syllabus-and-exam plan",
  "input": {
    "approved_plan": "USE THE REVIEWED PLAN"
  },
  "rules": [
    "Keep the guide tied to the current syllabus.",
    "Use past papers to illustrate likely emphasis and question style, not to promise exact repeats.",
    "Mark uncertain or outdated patterns clearly.",
    "Do not claim that any topic or question type will appear on the future exam.",
    "End with a short revision-priority checklist.",
    "Save final outputs in output-guide."
  ],
  "output_format": {
    "type": "study_guide"
  }
}

5) Save the result and archive the input folder

Rename the finished files clearly and save them in output-guide. When the syllabus changes, move the old syllabus into archive-old-syllabi before starting the next guide.

Future revision-guide runs

For a future course or exam cycle, reuse the same Cowork project. Replace the current syllabus, update the past exam folder if needed, revise revision-brief.txt, and start with a shorter request:

Create a revision-guide plan from the current syllabus and past exam folder.

For a stricter reusable prompt, use this:

{
  "task": "Create a revision-guide plan from the current syllabus and past exam folder.",
  "rules": [
    "Use the Revision Guide Builder project instructions.",
    "Anchor the plan to the current syllabus.",
    "Use past exams only for supporting patterns.",
    "Flag outdated or uncertain patterns.",
    "Do not draft the guide until I approve the plan."
  ]
}

The repeatability comes from the stable folder structure and project instructions. The current syllabus still needs a human check each cycle because it controls what belongs in the guide.

Tool-specific instructions

Cowork is useful here because the work depends on local files and careful synthesis across multiple documents. Keep the folder narrow and well named so Cowork can reason across the set cleanly.

Use normal Claude chat for a one-off guide only when you are willing to upload or paste the relevant files yourself. Use a Skill if you want consistent guide formatting, but keep Cowork as the syllabus-anchored document comparison layer.

Quality checks

1. The guide matches the current syllabus more than any single old exam.
2. Repeated patterns are labeled as likely emphasis, not promises.
3. Outdated or uncertain topics are clearly marked.
4. Low-quality scans or unreadable sections are flagged before drafting.
5. The guide does not imply exact prediction of future exam content.
6. The revision-priority checklist is short enough to be used.

Common failure modes and fixes

Old exams outweigh the current syllabus

Fix: tell Cowork explicitly that the current syllabus is the anchor document and review the plan before drafting.

Scans are unreadable

Fix: improve the scan or convert the exam to a clearer PDF before running Cowork.

The guide becomes too long

Fix: set an output length in revision-brief.txt and ask for a compact guide first.

Old patterns sound like guarantees

Fix: rewrite the guide so old exams are described as supporting evidence only. Remove wording that promises a topic, question type, or format will appear.