How Educators Can Use Claude Cowork to Turn a Semester Folder Into a Course Retrospective Packet
Use Claude Cowork to inspect a semester-review folder, map strengths and friction points across course artifacts, and draft a practical end-of-term retrospective packet.
Workflow summary
Quote this workflow accurately
- Best for
- End of semester evidence is fragmented. There may be aggregate feedback exports, attendance trends, assessment summaries, teaching notes, revision logs, and staff observations. A retrospective should say what worked,...
- Input
- Claude Cowork on an eligible plan: Pro, Max, Ultra, Team, or Enterprise, with any required administrator enablement. Institutional approval for the specific account, vendor, data category, and cloud processing. If tha...
- Primary tool
- Claude Cowork
- Output
- Use Claude Cowork to inspect a semester-review folder, map strengths and friction points across course artifacts, and draft a practical end-of-term retrospective packet.
- Main risk
- Fix: Stop before running Cowork. Move the original outside the entire connected tree, then recheck source filenames, hidden worksheets, and metadata. An instruction not to read a folder is not a substitute for access...
- Verification step
- Every major finding links to a named, approved source and the period it covers. Weak, contradictory, incomplete, or unrepresentative data stays labeled as such. Single comments and anomalous weeks are not presented as...
Continue from this article
Warning: A semester folder may contain student identifiers, grades, accommodations, private messages, and small-group results that can identify individuals indirectly. Remove or redact such material before it is uploaded or connected to Cowork. Merely placing a private file in a named excluded subfolder does not technically revoke access if that subfolder is inside a connected parent folder. Use institution-approved AI tools and data-handling rules.
Cowork requirements at a glance: Claude Cowork is available on Pro, Max, Ultra, Team, and Enterprise plans, not the Free plan. Team web/mobile availability may be in beta and Enterprise access depends on an administrator. New Pro, Max, and Ultra tasks run in the cloud. A connected semester folder needs Claude Desktop open and a task started on desktop; files supplied directly to a cloud task do not need a desktop connection.
If Claude Cowork is new to you
Cowork now operates within Claude across desktop, web, and mobile. If your account has unified chat and Cowork, describe the task in a normal conversation. If you still see Chat/Cowork mode choices, select Cowork for the multi-step job. See the Claude Cowork tool hub and the Anthropic Workflows series.
For Pro, Max, and Ultra accounts, new tasks execute in the cloud by default and the old Only on your computer setting is gone. Cloud execution does not make sensitive data local. A task that reads a file from a connected desktop folder processes that file in Anthropic's cloud environment. Your computer's folders stay on your device; only files requested through the connected folder are fetched. Confirm organizational approval before providing any educational records, using either route.
Problem and who this is for
End-of-semester evidence is fragmented. There may be aggregate feedback exports, attendance trends, assessment summaries, teaching notes, revision logs, and staff observations. A retrospective should say what worked, what was difficult, what evidence is weak, and what could change next term. It should not convert isolated complaints or unexamined grades into definitive findings.
This workflow is for educators, course leads, program coordinators, and instructional teams preparing a source-grounded end-of-term improvement packet. It supports a human decision process; it does not decide grading, staffing, curriculum, or policy.
Why Cowork fits this workflow
The hard part is not drafting the summary. It is inventorying permitted files, mapping evidence for and against each finding, exposing gaps, and creating a packet after a review checkpoint. Cowork can help with this multi-file, multi-step task using explicitly supplied cloud files or a tightly scoped desktop-connected folder.
The source set must be vetted first. Cowork is not a privacy or statistical validity auditor. A persuasive-looking synthesis from too few comments can mislead. Keep denominators, uncertainty, and counterexamples visible, and verify summaries against the actual aggregate exports.
Why not normal Claude chat or just a Skill?
A normal conversation can summarize a short, pasted de-identified feedback sample. A Skill can enforce a consistent retrospective outline. Cowork is useful when the job includes an inventory, an evidence map with traceable sources, missing-data checks, and several related output sections. The distinction is the workflow and source discipline, not an assumption that normal chat cannot access files on any device.
Prerequisites
- Claude Cowork on an eligible plan: Pro, Max, Ultra, Team, or Enterprise, with any required administrator enablement.
- Institutional approval for the specific account, vendor, data category, and cloud processing. If that approval is absent or unclear, use only public, synthetic, or explicitly approved non-identifiable materials and keep protected records outside Claude.
- A curated set of approved, aggregated or appropriately de-identified term evidence, with source names and coverage information.
- A brief named
retrospective-brief.txtdefining course/term, intended audience, evaluation questions, packet length, and decision boundaries. - For local-folder access, Claude Desktop open on the computer holding the approved files, a narrowly connected folder, and a Cowork session started from desktop.
- For cloud-only work, the approved source files supplied intentionally to the session or project, without assuming they can see your computer.
- A reviewer with appropriate academic and privacy authority to verify the evidence map and final packet.
Ask the educational institution's data/privacy lead whether this Claude account and either proposed processing route are authorized for the particular student or employee data. No claim of FERPA compliance, data-residency equivalence, or permission to process identifiable records is made here.
Set up this workflow as a Cowork project
Use this layout for the local preparation folder. It is not a promise that the same directory hierarchy appears automatically in a cloud project:
source-artifacts/
excluded-private-material/
output-packet/
review-notes/
archive-prior-terms/
retrospective-brief.txt
source-artifacts: the only current, reviewed materials Cowork should inspect: aggregate feedback, de-identified summaries, approved attendance trends, or approved teaching observations.excluded-private-material: an empty reminder/placeholder in the working directory. Store raw gradebooks, identifiable accommodations, private messages, and other excluded records outside any folder connected to Claude. An instruction saying "do not read this subfolder" is not an access control.output-packet: reviewed retrospective outputs, not raw student data.review-notes: human corrections, questions, and approvals, with no unnecessary identifiers.archive-prior-terms: past approved summaries. Keep old term materials out of the source set and unconnected unless deliberately needed.retrospective-brief.txt: audience, course, term, decision questions, packet length, and explicit exclusions.
For a cloud-only session, attach only the files from source-artifacts plus the brief; do not attach the excluded or archive directories. If the service cannot access a document, tell it to report the gap rather than guess its contents.
These are example task/project instructions, not an automatically importable Cowork configuration file. Adapt them in the project's instructions or send them as part of the task:
{
"project_name": "Course Retrospective Packet",
"project_purpose": "Use a vetted semester evidence set to create a source inventory, evidence map, reviewed plan, and end-of-term retrospective packet.",
"project_instructions": [
"Use only approved files in source-artifacts or files explicitly attached for this term.",
"Do not read, request, or use excluded-private-material, raw gradebooks, accommodations, student messages, or other unapproved records.",
"Stop and ask if a source contains identifiers or other data outside institutional approval.",
"Inventory all actual source files before planning; list inaccessible files as gaps.",
"Separate evidence of strengths, friction points, and revision opportunities.",
"Show source names, coverage periods, denominators when provided, and contradictory evidence.",
"Mark uncertain or weak evidence instead of presenting it as certain.",
"Keep student identifiers, grades, and private details out of the packet.",
"Create a retrospective plan and wait for explicit human approval before final drafting.",
"Do not delete, overwrite, rename, or move source files.",
"Save or export outputs to output-packet after approval; if local write access is unavailable, provide files to download and save manually."
],
"file_naming": "course-retrospective-course-term-yyyy"
}
Avoid relying on project memory as the evidence archive. Files from older terms must be explicitly selected for comparison; the model's remembered context is not a substitute for verifying the original data.
How to gather the source material
- Identify the retrospective's decision questions. For example: Which activities helped learners achieve the stated objectives, and what should be tested next term?
- Ask the institution which data the designated Claude account is permitted to receive and process. Do not upload identifiable student or employee information while that remains unresolved.
- Build
source-artifactsfrom approved, relevant material. Prefer aggregate feedback, attendance patterns that cannot identify individuals, assignment-level summaries, approved lesson revisions, and instructor notes with identifiers removed. - Remove direct identifiers, private comments, grades linked to individuals, accommodations, and identifiers hidden in file names, metadata, or spreadsheet tabs. Small-group figures may also be identifying; apply the institution's disclosure thresholds.
- Keep sensitive originals somewhere outside the connected workspace.
excluded-private-materialstays empty in the connected project layout, or do not connect its parent folder. - Record the period covered, number of responses where available, changes in participation, and known gaps. Do not claim that missing survey responses represent silent agreement.
- Create
retrospective-brief.txtand keepoutput-packetempty until approval.
Numbered workflow steps
1) Choose the approved access path and validate the source set
Desktop-connected folder: Start Cowork on desktop after granting access only to the prepared, non-sensitive review folder. Keep Claude Desktop open while files are needed. The task can run in the cloud, but the approved files it accesses are processed there. Desktop connectivity is not a privacy exemption.
Files supplied to a cloud session: Start from desktop, web, or mobile only if institutional policy permits the exact material and account. Attach or otherwise provide approved source files; no local file access is implied. A project tied to a local folder does not provide a mobile Cowork file-access path.
Do not treat the two paths as automatically equivalent for privacy approval. If approval is uncertain, stop and use the institution's established analysis environment instead.
2) Inventory the permitted evidence and create the plan
{
"task": "Inspect approved semester sources and prepare an evidence-mapped course retrospective plan; do not draft the packet yet",
"input": {
"approved_sources": "ONLY VETTED FILES IN source-artifacts OR THOSE EXPLICITLY PROVIDED TO THIS SESSION",
"excluded_folder": "excluded-private-material is off limits and must contain no connected sensitive records",
"brief_file": "retrospective-brief.txt"
},
"rules": [
"List each actual source read, its date range and relevance; identify missing or unreadable sources.",
"Do not access student identifiers, identifiable grades, accommodations, private messages, or unapproved records.",
"Separate strengths, friction points, and possible revisions.",
"For every major observation, include evidence files and denominators if supplied.",
"Flag single comments, small samples, inconsistent findings, and missing counterevidence.",
"Do not infer causation from correlations or assume survey respondents represent the full course.",
"Keep uncertain inferences visible and do not create final outputs yet."
],
"output": {
"source_inventory": "Actual sources, periods covered, evidence limitations and access gaps",
"evidence_map": "Strengths, friction points and revision opportunities with source references",
"uncertain_items": "Weak, conflicting or sensitive areas requiring human interpretation",
"packet_plan": "Section outline and proposed next-term action categories"
}
}
3) Review the inventory, evidence map, and privacy boundaries
Verify all source names and sample sizes against the underlying files. Question dramatic examples and trends from a single week. Check for omitted counterexamples and unrepresentative response rates. Confirm no identifiable information appears in the plan, including small-cell disclosures or quotations that reveal a student. Remove weak or irrelevant sources and keep remaining limitations on record.
Use Manually approve for this task and give separate explicit approval to proceed with the retrospective content plan. Automatically approve screens actions for safety but is not a privacy review; Skip all approvals removes that automated screening. None of the three modes grants institutional authority to process student records. Permanent deletion still requires permission; do not authorize deletion in this task.
4) Draft the retrospective packet only after approval
{
"task": "Create the course retrospective packet using the reviewed evidence map and explicitly approved source set",
"input": {
"approved_plan": "THE RETROSPECTIVE PLAN I APPROVED ABOVE",
"approved_evidence_map": "THE REVIEWED EVIDENCE MAP",
"source_set": "ONLY THE APPROVED SOURCE INVENTORY"
},
"rules": [
"Organize the packet under strengths, friction points, next-term changes, and unresolved evidence gaps.",
"Tie each important claim to an identifiable approved file, not to memory or inference alone.",
"State response coverage, evidence conflicts, and limitations where known.",
"Do not include student identifiers, identifiable grades, accommodation details, or private comments.",
"Describe options and testable changes rather than issuing curricular, grading, staffing, or policy decisions.",
"End with a short, owner-reviewable next-term action list.",
"Do not delete or overwrite any source or existing output.",
"Save final drafts in output-packet only if explicitly authorized local writeback is available; otherwise provide files for me to download and file there."
],
"output_format": {
"type": "retrospective_packet",
"sections": ["strengths", "friction_points", "next_term_options", "evidence_limitations", "next_term_action_list"]
}
}
5) Review, save, and archive the approved packet
Check every major assertion against the original approved source. Edit exaggerated conclusions, remove identifiable phrases, and ask the program lead to confirm actionable changes. Name the file course-retrospective-course-term-yyyy with an appropriate extension. Place reviewed downloads or permitted generated files in output-packet. Do not let Claude move raw student files into an archive; handle records according to institutional retention and access rules.
Expected output
The result is a brief, reviewable packet containing an inventory, an evidence map, supported strengths, documented friction points, proposed next-term experiments, explicit limitations, and a short action list. A source-map entry might say "Feedback export A: a recurring request reported by several responses; respondent coverage unknown". It should not turn that example into a majority claim. The packet is input to a human course review, not an automated verdict.
Future term runs
Use the existing project instructions if appropriate, but rebuild the approved source set each term. Do not assume the local folders have synchronized into the Claude account or that project memory reliably remembers the documents. Exclude old terms unless the review explicitly calls for a comparison.
{
"task": "Prepare this term's course retrospective inventory, evidence map, and draft plan",
"rules": [
"Use only the approved current-term files made available in this task.",
"Do not inspect excluded-private-material, old raw records, or other folders.",
"Keep evidence gaps, sample limitations, and conflicting findings visible.",
"Request my explicit plan approval before creating any final packet."
]
}
Tool-specific instructions, tips and caveats
Use Cowork for the sequence of file inventory, evidence review, and packet creation, not because it can decide curriculum objectively. A Skill can standardize headings; it does not solve missing data or privacy clearance. If source exports contain row-level student records, create authorized aggregate summaries outside Cowork and provide only those after approval. A de-identified small cohort may still be re-identifiable. Verify claims against real denominators instead of asking Cowork to extrapolate from a handful of comments.
Quality checks
- Every major finding links to a named, approved source and the period it covers.
- Weak, contradictory, incomplete, or unrepresentative data stays labeled as such.
- Single comments and anomalous weeks are not presented as broad consensus or causal evidence.
- No student identifiers, linked grades, accommodations, private messages, or identifying small-group findings appear in outputs.
- No excluded files were given to Cowork or made accessible through the connected folder.
- The packet follows
retrospective-brief.txtand distinguishes observations from proposed action. - A qualified human verifies the report before it is used for decisions about students, teaching, grading, or programs.
Common failure modes and fixes
A sensitive file is inside the connected folder
Fix: Stop before running Cowork. Move the original outside the entire connected tree, then recheck source filenames, hidden worksheets, and metadata. An instruction not to read a folder is not a substitute for access isolation.
The retrospective overstates weak feedback
Fix: Require source counts, known response coverage, competing evidence, and an explicit uncertainty table. If evidence is too thin, report it as a question for next term.
The packet contains student-identifying quotations
Fix: Remove or generalize identifiable language at the source-preparation stage; review the generated packet again before distribution.
Cloud outputs do not appear in the local output folder
Fix: Download the produced draft, inspect it, and save it into output-packet manually. Do not assume a cloud or mobile task can write to connected desktop folders.
The packet treats recommendations as final decisions
Fix: Recast conclusions as options with rationale, limitations, proposed owner, and validation step; send to the educator or program lead for a decision.
Safety and review boundary
Only approved, minimized material may enter the Cowork workspace. These restrictions apply even if the source files remain on a desktop, because accessed files are processed in the cloud. Minimize internet and connector access, use Manually approve, do not give delete or external-sharing permission, and keep source originals in the institution's authorized systems. Review any sharing, cloud retention, and service agreement with the privacy lead before use. Human faculty or administrators own final academic decisions.
Sources Checked
- Anthropic, Get started with Claude Cowork. Accessed 2026-11-01. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork
- Anthropic, Use Claude Cowork on web, desktop, and mobile. Accessed 2026-11-01. https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile
- Anthropic, Claude Cowork product guide: Getting started. Accessed 2026-11-01. https://claude.com/resources/guides/claude-cowork-product-guide/getting-started
- Anthropic, Claude Desktop Cowork changelog. Accessed 2026-11-01. https://claude.com/docs/cowork/changelog
Quarterly Refresh Flag
Next review: 2027-02-01. Recheck eligible plans and organizational enablement, cloud and local-folder access, project instructions, permission modes, file-export paths, and this workflow's privacy safeguards.
Related Workflows
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.
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.
How Educators Can Use Claude Skills to Turn Course Feedback Into a Keep, Change, Try Memo
Turn raw course feedback into a practical Keep, Change, Try memo using Claude Skills and a repeatable reflection format.
Help keep PromptedWork sharp
Share a broken step, outdated prompt, or general feedback. This is only for improving this specific workflow.