Educators & Coaches16 min readUpdated Nov 1, 2026

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

Use Claude Cowork to compare past exam PDFs against the current syllabus and build a revision guide that highlights likely topic emphasis without promising exact repeats.

claude coworkrevision guideexam prepsyllabus

Workflow summary

Quote this workflow accurately

Markdown version
Best for
Students ask for a revision guide, but a course's guidance is scattered among the current syllabus, several past exam PDFs, marking schemes, and an approved note about what changed. It takes time to compare those mate...
Input
A Claude account with Cowork access on Pro, Max, Ultra, Team, or Enterprise ; consult your organization's administrator for Team/Enterprise availability. The current, approved syllabus and permitted past exam PDFs or...
Primary tool
Claude Cowork
Output
Use Claude Cowork to compare past exam PDFs against the current syllabus and build a revision guide that highlights likely topic emphasis without promising exact repeats.
Main risk
The guide is dominated by old exam questions. Revise the topic map against the current syllabus. Put the current learning objectives first; use older examples only where still relevant.
Verification step
The current syllabus controls the topic list and the guide's scope. Every historical pattern can be traced to a particular authorized past paper; the sample size and missing years are visible. No topic or question typ...

Continue from this article

Warning: A past exam is evidence of what was assessed previously, not a promise about the next exam. Treat the current syllabus as the controlling scope. Use only authorized exam documents, remove student names, answers, grades, and other personal information, and review the guide before sharing it.

Cowork requirements at a glance: Claude Cowork is available on Pro, Max, Ultra, Team, and Enterprise plans, not Free. Desktop, web, and mobile support varies by account and administrator settings. For the local-folder workflow in this article, start the task in Claude Desktop with only the revision folder connected; cloud-only work with uploaded materials is a separate route.

If Claude Cowork is new to you

Claude Cowork now operates within Claude on desktop, web, and mobile. On accounts with the unified experience, simply describe the task in the conversation; if your interface still offers Chat and Cowork, choose Cowork for the multi-step task. Pro, Max, and Ultra now run new Cowork tasks in the cloud by default; the earlier Only on your computer option was removed. Team features may be in beta, while Enterprise behavior depends on administrator controls.

Cloud execution does not make your computer's folders available from every starting device. Anthropic says desktop-connected folders remain on the computer and are accessible to a cloud session only while Claude Desktop is open and the task was started on desktop or is a scheduled task. A cloud task retrieves a copy of a needed file. A session started on mobile or web does not automatically inherit that access. A task started on desktop can be reviewed or steered from another device.

See the Claude Cowork tool hub and Anthropic Workflows series for related work.

Problem and who this is for

Students ask for a revision guide, but a course's guidance is scattered among the current syllabus, several past exam PDFs, marking schemes, and an approved note about what changed. It takes time to compare those materials without letting old assessment patterns crowd out the current curriculum.

This workflow is for instructors, tutors, program staff, and coaches preparing an authorized, source-grounded revision guide. The goal is a topic map and a useful study checklist, not prediction of unreleased questions.

Why Cowork fits this workflow

The hard part is cross-document comparison: identify which topics belong to the current syllabus, examine how past papers assessed those topics, flag content that no longer applies, and assemble a consistent draft. Cowork can organize the inspection, propose a source map, and create the draft after you approve the plan.

Historical frequency is descriptive evidence, not a valid estimate of future exam probability unless the exam setter has established such a rule. For example, a topic appearing in several old papers may be worth practicing, but the guide must still cover current syllabus requirements that have not appeared in old papers. Cowork cannot independently establish that source PDFs are correct, complete, or permitted for distribution.

Why not normal Claude chat or just a Skill?

A short guide based on a handful of uploaded documents may work in a normal Claude conversation. Cowork is useful when you want a multi-step source inventory, comparison table, approval gate, and controlled output from a larger collection. The distinction is the review process, not an assertion that Chat can never read documents.

An optional Skill can standardize headings or tone. It is not a substitute for comparing every document against the syllabus, recording missing evidence, or checking whether the past papers are applicable.

Prerequisites

  • A Claude account with Cowork access on Pro, Max, Ultra, Team, or Enterprise; consult your organization's administrator for Team/Enterprise availability.
  • The current, approved syllabus and permitted past exam PDFs or marking schemes. Do not upload unreleased, restricted, or unauthorized papers.
  • Optional approved faculty notes that explain curriculum, marking, or assessment-format changes.
  • A short revision-brief.txt identifying student level, exam date, current course scope, desired guide length, and how to describe historical patterns.
  • One scoped source workspace, plus time to inspect the proposed topic map before generating the guide.
  • A privacy check: use no student names, grades, answers, accommodations, or identifiable records. Where institutional policies apply, follow them before involving cloud AI.

Set up the revision-guide workspace

Use the original folder layout when organizing the files on your own computer:

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

Store only the current syllabus in current-syllabus/; move superseded syllabi to archive-old-syllabi/ and exclude that archive from the source set Claude may use. If connecting the parent folder would expose the archive, move that archive outside the connected folder before starting the task. Name past exams by year or term, and add a note when a paper uses a different syllabus or exam format. Keep faculty notes approved and brief. output-guide/ is the intended place for reviewed outputs, not a license to edit the source PDFs.

This is a proposed filesystem layout, not a claim that creating a Claude Project automatically creates these folders or that all project files sync as local folders. For repeated work, you can create an account Project with instructions and relevant approved knowledge files; a Project tied to a local folder supports Cowork sessions on desktop only. The JSON below is text to paste into your project or task instructions, not a command that installs a project.

Reusable project instructions

Paste these instructions into the relevant project or task instruction area and adjust the file names for your course:

{
  "project_name": "Revision Guide Builder",
  "project_purpose": "Compare permitted past exam PDFs with the current syllabus; inventory first, ask for review, then draft a syllabus-grounded revision guide.",
  "project_instructions": [
    "Treat the current syllabus in current-syllabus as the controlling document. If it is missing or ambiguous, stop.",
    "Use past exams only as supporting evidence of historical topic emphasis and question style, not predictions.",
    "Read revision-brief.txt and authorized faculty notes; do not inspect archive-old-syllabi or unrelated folders.",
    "Separate current-syllabus topics, historical patterns, and outdated or uncertain areas in a source map.",
    "Record the filename/year and relevant page or section for material claims; mark unsupported points [CONFIRM].",
    "Flag unreadable scans, missing papers, inconsistent exam years, and changes in assessment format.",
    "Do not invent citations, sample questions represented as past questions, or future exam promises.",
    "Do not process identifiable student records or other material beyond the approved source set.",
    "Create a topic map and guide plan, stop, and obtain explicit human approval before the final draft.",
    "Do not move, delete, overwrite, rename, or modify any source file.",
    "Use output-guide for drafts only when the local write path is available and specifically authorized; otherwise return downloadable drafts for manual saving."
  ],
  "file_naming": "revision-guide-course-exam-yyyy-mm-dd"
}

How to gather the source material

  1. Confirm that the syllabus is the current, approved version. Put it alone in current-syllabus/.
  2. Add only authorized past exam PDFs, labeled with their year or term, to past-exams/. Note if a paper was written for a prior syllabus.
  3. Put approved faculty change notes in faculty-notes/; do not add private emails or unreleased assessment material.
  4. Put old syllabi in archive-old-syllabi/, then keep that archive outside the connected scope if the parent folder is being shared.
  5. Make a revision-brief.txt with student level, exam date, topics included this term, output length, and a warning against exam predictions.
  6. Check PDF readability yourself. For illegible scans, improve the scan or OCR locally if allowed, and compare extracted text against the original before relying on it.
  7. Choose one of the access routes below and make the selected files available before sending the inspection prompt.

Choose the file-access route

Route A: desktop-connected folder (best for inspecting a genuine local folder). Open Claude Desktop, connect only the approved revision-guide working folder, and start the Cowork task on desktop. Keep Desktop open whenever the task needs those files or needs to write an authorized local output. The Cowork execution may run in the cloud, and file copies may be fetched for processing. You may review that same cloud session from web or mobile later, but do not start on mobile expecting direct access to desktop files.

Route B: supplied cloud inputs. On web, mobile, or desktop, add the permitted syllabus, prior papers, faculty notes, and the brief as files available to the cloud conversation or Project. Include a simple manifest with each filename and its role. This does not provide an automatically inspectable copy of a local directory, and it does not automatically save generated files into output-guide/. Download the results and place them in that folder yourself.

Before using a particular account or device, confirm supported PDF/file upload limits, whether every required page is readable, and whether the selected cloud session can save output into the intended destination. Use a manual download-and-save path if direct local writeback is unavailable.

Student-data safeguard: Do not introduce personal student information simply to use these routes. Anthropic states that Cowork cloud processing occurs on its servers, including for files accessed through Desktop. Check current Anthropic guidance on cloud-session handling, retention, and processing for any material that could count as student data before relying on a cloud-default task for this workflow. Obtain institutional permission before uploading any protected or confidential educational records; this workflow is designed to run without them.

Numbered workflow steps

1) Establish the source boundary

Ensure revision-brief.txt reflects the current course. On Desktop, verify that the connected folder is only the scoped revision workspace. With cloud uploads, verify that every required source is present and identifiable by filename. Remove private data and unauthorized papers before giving Claude access.

Use Manually approve for consequential work. Anthropic also offers Automatically approve, which runs safety checks and can fall back to asking, and Skip all approvals, which has no automatic check. These are not equivalent, and none replaces your instruction to stop after the plan. Deletions require approval; prohibit all source modifications regardless.

2) Ask for a topic map and plan first

Supply the following JSON as the request in your Cowork conversation. For cloud-only uploads, replace the folder names with the actual attached file manifest; do not imply that the local paths are connected.

{
  "task": "Inspect the approved syllabus, past exam PDFs and faculty notes; prepare a revision-guide plan only.",
  "input": {
    "source_mode": "DESKTOP CONNECTED FOLDER OR EXPLICIT CLOUD UPLOADS",
    "current_syllabus_folder": "current-syllabus",
    "past_exams_folder": "past-exams",
    "faculty_notes_folder": "faculty-notes",
    "brief_file": "revision-brief.txt",
    "uploaded_files_manifest": "IF CLOUD INPUTS, LIST EXACT FILE NAMES AND ROLES"
  },
  "rules": [
    "Treat the current syllabus as the source of truth for current coverage.",
    "Use past exams only for historical examples of topic emphasis and question style.",
    "Show evidence by source filename and page/section for each identified pattern.",
    "Classify every topic as current syllabus, historical supporting pattern, or outdated/uncertain.",
    "Count past-paper patterns only within the actual available papers and identify gaps in the sample.",
    "Flag unreadable scans and missing coverage; do not infer what a bad scan says.",
    "Do not predict what will appear on the next exam.",
    "Do not use student records, grades, or restricted source files.",
    "Return a plan and wait for approval; do not create the final guide or change any source."
  ],
  "output": {
    "source_inventory": "Syllabus and exam filenames, years and readability",
    "topic_map": "Current syllabus topics and linked evidence",
    "question_patterns": "Historical examples with specific file/page references",
    "outdated_or_uncertain_areas": "Older syllabus or unclear assessment patterns",
    "missing_coverage": "Syllabus topics not supported by the available papers",
    "draft_plan": "Proposed guide structure and length",
    "approval_gate": "Stop and ask the educator to review the plan"
  }
}

3) Inspect and approve the plan

Check that all current syllabus topics are considered, not only those repeated in past papers. Remove claims based on old syllabi, one exceptional exam, or a low-quality scan. Confirm that historical topic counts reflect the available sample, not a forecast. Verify file/page references against the PDFs. If a required syllabus topic has no corresponding past question, keep it in the guide as current material, not as an omission. Correct the topic map and state explicitly which version of the plan is approved.

If the map is unreliable, stop. Ask for a revised plan, not the final guide. The human decision here is a required workflow gate, independent of the Claude permission mode.

4) Generate the revision guide from the approved plan

Only after approval, provide the reviewed plan and ask for a first draft:

{
  "task": "Draft a syllabus-grounded revision guide from the explicitly approved topic map.",
  "input": {
    "approved_plan": "PASTE OR REFER TO THE HUMAN-APPROVED TOPIC MAP",
    "output_file": "revision-guide-course-exam-yyyy-mm-dd"
  },
  "rules": [
    "Use the current syllabus to determine what belongs in the guide.",
    "Describe past-paper patterns as historical examples, never guarantees or probability estimates.",
    "Include syllabus topics even when they have no matching historical exam example.",
    "Label outdated or weak historical support as uncertain and keep source references attached.",
    "Do not invent quotations, citations, model answers, or exam questions presented as real past questions.",
    "Keep the guide at the length specified in revision-brief.txt.",
    "End with a short revision-priority checklist derived from syllabus coverage and the approved plan.",
    "Do not modify any source documents; do not send or publish the guide.",
    "If authorized local output is unavailable, return a downloadable guide for the educator to place in output-guide manually."
  ],
  "output_format": {
    "type": "revision_guide_draft",
    "sections": [
      "Course and assessment scope",
      "Current syllabus topic map",
      "Historical question styles and examples",
      "Uncertain or outdated patterns",
      "Revision-priority checklist",
      "Source references and limitations"
    ]
  }
}

5) Save, verify, and archive

On the desktop-folder route, save the reviewed draft only to output-guide/ if Claude has the specific permitted write access. Otherwise download the output and place it there manually. Use revision-guide-course-exam-yyyy-mm-dd as the naming pattern. Keep the original syllabus, old papers, and faculty notes unchanged. Before the next exam cycle, update the syllabus and brief and move superseded syllabi outside the active source set yourself.

Expected output

The completed working set should contain a source inventory, an approved topic map, a revision-guide draft, and a revision-priority checklist. For each topic, the guide should distinguish current syllabus coverage from illustrative past-paper question styles and identify any weak or outdated evidence. A legitimate outcome may be that past exams are too old or incomplete to support much about likely emphasis; the guide can still organize the current syllabus.

A guide is ready to share only after the educator checks educational accuracy, fair topic coverage, source permissions, readability, and the non-predictive wording.

Future revision-guide runs

Use the same manually maintained folder layout and instructions for the next exam cycle. Replace the current syllabus, update the past exam inventory, and revise revision-brief.txt. Do not assume that project memory, previous sessions, or cloud file storage automatically refreshes your current source set. Start each new cycle with a fresh inventory and plan before drafting.

Reusable prompt:

{
  "task": "Prepare a revised revision-guide plan, not a final guide, for the current syllabus.",
  "rules": [
    "Inventory the explicitly accessible source files.",
    "Anchor all coverage to the current syllabus.",
    "Use old exams only for historically observed examples.",
    "List unreadable or outdated sources, missing coverage, and uncertain claims.",
    "Stop for review before producing output files."
  ]
}

Tool-specific instructions, tips, and caveats

  • Local access: Start on Claude Desktop if you need direct inspection of a connected source folder; leave the app open during local access. Starting a new task in the cloud does not mean the folder was uploaded wholesale.
  • Cloud-only access: Explicitly provide approved files and a manifest. Treat those as the task's full source boundary; do not claim other local files were read.
  • PDF quality: A document opening successfully does not prove its text or tables were interpreted correctly. Manually spot-check cited pages, especially marking schemes, images, and low-quality scans.
  • Historical patterns: Describe only what the available prior papers demonstrate. Do not invent a formula for future exam probability or label past frequency as guaranteed emphasis.
  • Permissions: Prefer Manually approve for file operations. Do not allow broad source edits or folder cleanup just because the interface offers faster approval modes.
  • No scheduling needed: This is a one-off reviewed draft workflow, not a reason to create an unattended recurring task.

Quality checks

  1. The current syllabus controls the topic list and the guide's scope.
  2. Every historical pattern can be traced to a particular authorized past paper; the sample size and missing years are visible.
  3. No topic or question type is described as certain to recur on a future exam.
  4. Outdated areas and low-confidence conclusions are visibly marked rather than hidden.
  5. Unreadable pages and weak scans are flagged, not guessed about.
  6. Personal student data, restricted assessment materials, and unapproved sources are absent.
  7. The final checklist is useful and covers important current topics, including those with no past-paper examples.
  8. The educator reviewed the draft before sharing it, and original source files were not overwritten.

Common failure modes and fixes

The guide is dominated by old exam questions. Revise the topic map against the current syllabus. Put the current learning objectives first; use older examples only where still relevant.

Claude mistakes a pattern for a prediction. Replace phrases such as “will be tested” with “appeared in the available past papers,” include the years, and note uncertainty.

A scanned PDF is poorly interpreted. Correct or replace that scan and repeat the inspection stage. Do not silently draft around unreadable pages.

Claude cannot see the folder after a mobile start. Start a new task on Desktop with the connected folder; alternatively supply the individual approved inputs directly to a cloud session and download the result.

A generated file is not in output-guide/. Inspect where the output actually lives, then save or download it to your local output folder yourself. Do not assume a cloud session wrote to the computer.

Safety and privacy

Use only teaching material the institution permits you to process and share. Do not include student identifiers, exam submissions, grades, accommodations, or restricted future-exam content. Even with a desktop-connected folder, the new Cowork task can run in Anthropic's cloud and fetch copies of selected files, so local folder placement is not a guarantee of local-only processing. For any material potentially covered by student-records policy, obtain institutional approval and verify applicable data handling before use. Never allow Cowork to send materials to learners or alter exam sources without human control.

Sources Checked

Official Anthropic documentation accessed November 1, 2026:

Quarterly Refresh Flag

Review on February 1, 2027, or sooner if Anthropic changes account eligibility, connected-folder access, permission labels, file outputs, or cloud data handling. Recheck the actual workflow on the intended account before relying on it for consequential work.

Something off in this workflow?

Related Workflows

14m
Educators & Coaches

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

Use Claude Cowork to turn a local teaching folder into a workshop pack with slides, a handout, and a missing-items list.

Read Workflow

How to Turn a Unit Folder Into a Low-Prep Review Quiz Bank With NotebookLM

Use NotebookLM to turn a unit folder of readings, slides, and checks for understanding into a grounded review quiz bank with answer key.

Read Workflow

How to Turn Quiz Results Into a Small-Group Reteach Plan With NotebookLM

Use NotebookLM to turn quiz results, standards, and item patterns into a grounded small-group reteach plan instead of guessing what to reteach.

Read Workflow
Reader Feedback

Help keep PromptedWork sharp

Share a broken step, outdated prompt, or general feedback. This is only for improving this specific workflow.