How to Use Claude Cowork to Turn a Folder of Drafts Into a Board or Leadership Meeting Packet

Warning: Cowork can work on local files and make real changes. Keep its file access limited to the meeting folder you want processed, and do not include sensitive material you do not need in the 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 on the local files 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 board or leadership meeting packet is usually built from a messy folder: agenda draft, prior minutes, one or two slide decks, attached PDFs, maybe an unfinished memo, and a few files that still need cleanup. Doing it by hand is repetitive and easy to miss.

This workflow is for admins, executive assistants, chiefs of staff, and operations coordinators who already maintain a local meeting folder and want Claude Cowork to assemble the packet faster.

Prerequisites

Claude Desktop with Cowork available on your paid plan.
A single local folder for the meeting packet.
A clear packet order. Example: cover note, agenda, prior minutes, decision memo, appendix PDFs.
Permission to let Cowork access that folder.

How to gather the source material

Create one local folder for this meeting only.
Move the packet ingredients into that folder.
Rename files so the order is obvious. Example: 01-agenda.docx, 02-prior-minutes.pdf, 03-budget-memo.docx, 04-appendix.pdf.
Delete stale drafts or move them into an archive subfolder outside the working packet folder.
Add one small text file called packet-instructions.txt that lists the desired order, audience, due date, and any file that should be excluded.

Numbered workflow steps

1) Set up the folder before Cowork touches it

Cowork works best when the local workspace is clean. Give it one folder, not your entire documents library.

2) Ask Cowork for an inventory and missing-items check first

Do not ask it to assemble the final packet on the first prompt. First, make it inspect the folder and tell you what is missing or out of order.

{
  "task": "Inspect a local meeting-packet folder and prepare an assembly plan",
  "input": {
    "working_folder": "LOCAL FOLDER PATH",
    "packet_instructions_file": "packet-instructions.txt"
  },
  "rules": [
    "Read the files in the folder and report what each appears to be.",
    "Do not delete or overwrite anything yet.",
    "Flag missing expected items or duplicate drafts.",
    "Propose the final packet order before assembly."
  ],
  "output": {
    "file_inventory": "Ordered list of files and what each is for",
    "missing_items": "Expected items not found",
    "cleanup_flags": "Duplicate drafts, stale files, or naming issues",
    "proposed_packet_order": "Final packet sequence"
  }
}

3) Approve the plan, then have Cowork assemble the packet

Once the file order looks right, give Cowork permission to create the packet output inside a new final-packet subfolder.

{
  "task": "Assemble a board or leadership meeting packet from a verified local folder",
  "input": {
    "approved_packet_order": "PASTE OR CONFIRM THE ORDER FROM STEP 2",
    "output_folder": "LOCAL FOLDER PATH/final-packet"
  },
  "rules": [
    "Create output files in the final-packet folder only.",
    "Do not overwrite the source drafts.",
    "Keep the packet order exactly as approved.",
    "Produce a short cover note summarizing the contents and missing items, if any remain."
  ],
  "output_format": {
    "type": "assembled_packet"
  }
}

4) Review the packet manually before distribution

Open the finished files. Check page order, attachment inclusion, meeting date, and any version labels. Cowork saves time, but packet owners still need a final human pass.

Tool-specific instructions

Claude Cowork

Read the Claude Cowork explainer page in the site's Tools menu if you want the feature overview first.
Cowork runs in Claude Desktop and works on the files you choose to share.
It can access local files directly, run longer tasks, and coordinate multi-step work in parallel.
Use a Cowork project for recurring board series so the folder structure, instructions, and memory stay together over time.

Quality checks

Every source file in the packet is the correct version and appears once.
The packet order matches the approved order in packet-instructions.txt.
No draft file was overwritten in place.
The cover note accurately flags anything still missing.

Common failure modes and fixes

Cowork includes the wrong draft

Fix: clean the folder first and rename the approved version clearly before rerunning Step 2.

The packet order comes out wrong

Fix: state the desired order explicitly in packet-instructions.txt and approve the proposed order before assembly.

Sensitive side files get pulled in

Fix: keep Cowork limited to a dedicated meeting folder rather than a larger parent folder.

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: Installing Claude Desktop (accessed 2026-03-23) https://support.claude.com/en/articles/10065433-installing-claude-desktop
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: Organize your tasks with projects in Cowork (accessed 2026-03-23) https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-cowork
Anthropic Claude Help Center: What are projects? (accessed 2026-03-23) https://support.claude.com/en/articles/9517075-what-are-projects

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Cowork availability, mobile dispatch requirements, project behavior, and supported setup paths.