Admins & Office Work15 min readUpdated Nov 1, 2026

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

Use Claude Cowork to inventory meeting drafts, resolve missing or duplicate files, and assemble a board packet with human approval and without overwriting sources.

claude coworkmeeting packetboard packetdocument assemblyleadership support

Workflow summary

Quote this workflow accurately

Markdown version
Best for
A board or leadership packet often starts as a scattered set of agenda drafts, prior minutes, slide decks, PDFs, and an unfinished memo. Older versions may look nearly identical to approved files. Sending the wrong dr...
Input
A paid Claude plan with Cowork: Pro, Max, Ultra, Team, or Enterprise. Web/mobile capabilities vary by plan; an Enterprise owner may need to enable them. Preferred local path: latest Claude Desktop, a folder connected...
Primary tool
Claude Cowork
Output
Use Claude Cowork to inventory meeting drafts, resolve missing or duplicate files, and assemble a board packet with human approval and without overwriting sources.
Main risk
Fix: verify that you started the task from Desktop , connected the dedicated meeting folder, and kept Claude Desktop open. A fresh web/mobile started cloud session does not automatically inherit your local folder. If...
Verification step
Every included document matches the approved filename and version and appears exactly once. The packet follows the approved order in packet instructions.txt. No draft source was overwritten, moved, renamed, or deleted.

Continue from this article

Safety first: Cowork can read connected files and create or modify real files. Work from a dedicated meeting folder containing only approved material. Keep source drafts unchanged, require an inventory and your approval before assembly, and have a human review everything before distribution.

Cowork requirements at a glance: Claude Cowork is available on paid Pro, Max, Ultra, Team, and Enterprise plans, not Free. It runs on desktop, web, and mobile, subject to plan and organization settings. For the local-folder workflow below, use Claude Desktop, connect only the meeting folder, and keep Desktop open while Claude needs to read or write those files. New Pro, Max, and Ultra Cowork tasks run in the cloud by default, but local folders remain on your computer.

If Claude Cowork is new to you

Start with the Claude Cowork tool hub and the Anthropic Workflows series. In Claude's unified experience, describe your task in the conversation box. If your account still shows separate Chat and Cowork choices, select Cowork for this multi-step file task. Team is in beta for some Cowork experiences, and Enterprise access may require an owner to enable it.

There are two ways to run this workflow. The preferred path starts on Claude Desktop with a connected local folder, so Claude can inspect drafts and put finished files back in final-packet/. A web or mobile session started from scratch can instead work with files you upload, but it does not gain direct access to a desktop-connected local folder. You must download its finished files and place them in your local output folder yourself. Do not assume the two paths have identical file access.

Problem and who this is for

A board or leadership packet often starts as a scattered set of agenda drafts, prior minutes, slide decks, PDFs, and an unfinished memo. Older versions may look nearly identical to approved files. Sending the wrong draft or dropping an appendix can undermine the entire meeting.

This workflow is for admins, executive assistants, chiefs of staff, and operations coordinators who prepare these packets and need a controlled way to inventory the sources, agree on an order, and create a reviewable set of final files.

Why Cowork fits this workflow

The useful part is not simply writing a cover note. Claude needs to inspect several files, identify missing or conflicting versions, propose an assembly plan, and make outputs in a defined location. Cowork supports multi-step work and file creation. A cloud task started on desktop can reach only folders you explicitly connected through the desktop app while it remains open. When the cloud task needs a local file, it retrieves a copy of that file; connecting a folder does not upload the entire folder by default.

Use one control sequence every time: inspect, approve, assemble, review. Cowork's inspection is a draft assessment, not proof that a particular version is approved.

Why not normal Claude chat or just a Skill?

A simple Claude conversation with uploaded materials may be enough to draft a cover note or summarize a small packet. In Claude's newer experience, chat and Cowork can share one entry point, so the distinction is what access and actions the task has, not which tab you opened.

This workflow adds a controlled source inventory, version checks, an explicit stop for approval, a source map, and bounded output creation. A Skill can standardize the cover-note language or formatting, but it cannot substitute for verifying the source files or approving the assembly plan.

Prerequisites

  • A paid Claude plan with Cowork: Pro, Max, Ultra, Team, or Enterprise. Web/mobile capabilities vary by plan; an Enterprise owner may need to enable them.
  • Preferred local path: latest Claude Desktop, a folder connected only for this meeting, and the app open while local file reads or writes are needed. Your computer must remain available for that connection. Cloud processing itself can continue when the app is closed, but local-file operations cannot.
  • Upload alternative: Claude on desktop, web, or mobile, plus copies of the current source files uploaded into the session or an accessible cloud project. No automatic write-back to your local folder is implied.
  • Meeting date, intended audience, packet deadline, approved source versions, and the required packet order.
  • Organization approval to process the materials in Anthropic's cloud. Keep regulated, confidential, or unnecessary sensitive data out unless your organization has approved this exact use.

Set up this workflow as a Cowork project

For a recurring meeting series, use a dedicated project and a separate folder for the files being prepared. Do not confuse a project's saved context with unrestricted access to your computer's folders. If the project is tied to a local folder, start the file-working Cowork session from Desktop; uploaded cloud-project files are a different input path.

Use this structure inside a single meeting folder:

source-drafts/
archive-do-not-use/
final-packet/
review-notes/
packet-instructions.txt

Keep only current, eligible inputs in source-drafts/. Put old versions in archive-do-not-use/, but do not grant Claude unnecessary access to that folder. Use review-notes/ for human decisions and corrections, and reserve final-packet/ for newly created deliverables. In packet-instructions.txt, record the audience, meeting and due dates, file exclusions, desired order, and any formatting or distribution rules.

Add the following instructions to the Cowork project, or paste them at the start of a standalone task if the project instructions are not available on that surface. This JSON is an instruction template, not a configuration file that Claude installs automatically:

{
  "project_name": "Board Packet Assembly",
  "project_purpose": "Inspect meeting materials, propose packet order, and create reviewed packet outputs without modifying sources.",
  "project_instructions": [
    "Always inspect the folder or uploaded source set and create an inventory before assembling the packet.",
    "Use only current files in source-drafts, or the files I explicitly uploaded for this meeting.",
    "Do not delete, overwrite, move, or rename source drafts without my explicit approval.",
    "Flag missing agenda items, duplicate drafts, version conflicts, and unrelated files.",
    "Propose the final packet order and source map before creating outputs.",
    "Stop and ask for approval before assembling the packet.",
    "For a connected local folder, create outputs only inside final-packet.",
    "For uploaded files, return downloadable outputs for me to place inside final-packet myself.",
    "Create a source map and a cover note identifying anything still missing or unresolved.",
    "Do not distribute the packet or send messages."
  ],
  "file_naming": "board-packet-yyyy-mm-dd"
}

How to gather the source material

  1. Make a working copy of the current meeting documents. Do not expose a live shared folder containing unrelated board records.
  2. Put current drafts in source-drafts/; keep stale or excluded documents in archive-do-not-use/ and outside Claude's permitted source set.
  3. Give files clear names, for example 01-agenda.docx, 02-prior-minutes.pdf, 03-budget-memo.docx, and 04-appendix.pdf. Rename your working copies before starting; do not ask Cowork to rename originals.
  4. Write packet-instructions.txt with the proposed order, audience, meeting date, due date, and excluded filenames. Note where a board secretary or document owner must confirm a version.
  5. Leave final-packet/ empty. Do not ask Claude to create the final files yet.
  6. Choose the input route. On Desktop, connect the dedicated meeting folder and begin the Cowork task there. On web/mobile, upload the exact current files and packet-instructions.txt; provide the file list explicitly if a folder structure is not retained in the upload.

Numbered workflow steps

1. Prepare the bounded workspace

For the local path, open Claude Desktop and connect the meeting folder. Confirm Claude can see source-drafts/ and packet-instructions.txt, without authorizing a broad parent directory. For the upload path, attach only the current input files. If the account has a unified message box, enter the task there; otherwise choose Cowork if shown.

Choose Manually approve (Manual) for a sensitive board packet or a first run. Automatically approve (Auto) checks actions before allowing them and may ask for confirmation; it is not the same as Skip all approvals (Skip), which has no automatic action screening. Claude still requires approval for permanent deletion. Organization settings may restrict available modes. The instruction to stop after inventory is separate from the mode setting.

2. Request an inventory, not a finished packet

Use this prompt. Replace the location description with the route you actually chose. For an upload-based session, the source set means the attached files, not a folder Claude can magically read on your computer.

{
  "task": "Inspect the board or leadership meeting sources and propose an assembly plan only",
  "input": {
    "source_route": "CONNECTED LOCAL FOLDER STARTED FROM DESKTOP, OR UPLOADED CURRENT FILES",
    "working_folder": "DEDICATED MEETING FOLDER IF CONNECTED; OTHERWISE ATTACHED FILE SET",
    "source_folder": "source-drafts (local path) or the uploaded current files",
    "packet_instructions_file": "packet-instructions.txt"
  },
  "rules": [
    "Read only the approved current sources and packet-instructions.txt.",
    "Do not assemble, delete, overwrite, move, rename, or distribute files yet.",
    "Identify every file by filename and apparent document purpose.",
    "Flag missing required items, duplicate drafts, version conflicts, stale material, and unrelated files.",
    "Propose the packet order and a source map, but stop for my approval.",
    "Mark uncertain facts, dates, and versions [CONFIRM]."
  ],
  "output": {
    "file_inventory": "Filename, document purpose, apparent version and review status",
    "missing_items": "Expected items not present or readable",
    "cleanup_flags": "Duplicates, stale files, naming problems, and version conflicts",
    "proposed_packet_order": "Numbered order for cover note, agenda, minutes, memos, and appendices",
    "source_map_plan": "Approved candidate source filename for each packet component"
  }
}

Read the inventory and open any conflicting versions yourself. Confirm the actual approved draft with the document owner rather than trusting a filename or Claude's guess. If something is missing, either obtain it or mark it clearly as missing before proceeding.

3. Approve the plan and assemble only the approved outputs

Once the inventory is correct, give explicit approval for the specific order and source versions. Keep the source originals unchanged. Ask Cowork to create a cover note, an ordered packet or a set of ordered final files as appropriate for your source formats, and a source map. Do not assume mixed DOCX, PDF, and slide files will merge into one flawless PDF automatically; inspect the format and pagination it actually produces.

{
  "task": "Assemble the approved board or leadership packet without changing source drafts",
  "input": {
    "approved_packet_order": "PASTE THE APPROVED ORDER AND EXACT SOURCE FILENAMES",
    "approved_source_versions": "LIST THE APPROVED FILENAMES OR VERSION IDENTIFIERS",
    "output_folder": "final-packet (connected local Desktop workflow); otherwise provide downloadable outputs"
  },
  "rules": [
    "Use only the approved source versions in the approved order.",
    "Do not delete, overwrite, move, or rename the source drafts.",
    "Do not include stale or unrelated files.",
    "For a connected local folder, create new outputs only inside final-packet.",
    "For an upload session, create downloadable files and let me save them into final-packet manually.",
    "Create a source map listing the source filenames used for each packet component.",
    "Create a short cover note listing included sections and any remaining missing items.",
    "Mark unresolved dates, versions, or claims [CONFIRM].",
    "Do not email, post, share, or distribute anything."
  ],
  "output_format": {
    "type": "assembled_packet_for_human_review"
  }
}

If your account, organization permissions, or connected-folder configuration do not allow the cloud task to save new files into the local final-packet/ directory, download the generated files and save them there manually. Anthropic documents this general connected-folder capability, but an actual local save is dependent on the user's setup.

4. Review the assembled packet before distribution

Open every output. Check agenda order, dates, pagination, attachments, table and slide readability, version labels, and missing materials. Compare the final source map with the actual approved input files. Confirm that source-drafts/ was not modified and that the cover note has not turned uncertain claims into confirmed decisions. Distribute only after the human packet owner approves it.

Expected output

The finished working set should contain the board or leadership packet (as ordered individual files or an assembled document), a short cover note, and a source map with filenames and source-version notes. Any gaps should be clearly visible. On the local path, these outputs belong in final-packet/; on the upload path, they are downloadable until you place them there yourself.

Future packet runs

Reuse the same bounded structure. Replace or archive working copies from the previous meeting, update packet-instructions.txt, and start again with an inventory rather than immediately assembling.

{
  "task": "Prepare the source inventory and assembly plan for the next board meeting",
  "rules": [
    "Use the Board Packet Assembly project instructions if they are available in this task.",
    "Inspect only current source-drafts files or the attached current files.",
    "List the inventory, missing items, duplicate/version flags, and proposed packet order.",
    "Stop before assembly and wait for my explicit approval."
  ]
}

Tool-specific instructions and caveats

Claude Cowork using a connected local folder

Start from Claude Desktop if the task must inspect or write a folder on your computer. New Cowork sessions on Pro, Max, and Ultra are cloud-hosted, but the desktop app acts as the bridge for permitted local files. If the app closes, the cloud task may continue, but it cannot access those local files until the bridge is available again. Projects linked to local folders should be handled from Desktop rather than assumed accessible from a new mobile or web session.

Claude Cowork with uploaded files

A new web or mobile session can process files you upload and return generated files. It is not equivalent to authorizing direct inspection or modification of your local meeting folder. Upload packet-instructions.txt alongside the exact current files, review the inventory, and save downloaded outputs into final-packet/ yourself. If the upload omits a source or its filename, correct that before assembly.

Skills and permission settings

Use a Skill only if it genuinely helps with writing or formatting after approval. For sensitive packets, favor Manually approve. Automatically approve uses safety checks but cannot guarantee accuracy or appropriate scope. Avoid Skip all approvals for this task, and remember that any connected apps, browser tools, and plugins expand what Claude may be able to reach.

Quality checks

  1. Every included document matches the approved filename and version and appears exactly once.
  2. The packet follows the approved order in packet-instructions.txt.
  3. No draft source was overwritten, moved, renamed, or deleted.
  4. Outputs exist only in final-packet/, or downloaded outputs were placed there manually for an upload-based session.
  5. The source map identifies each source used; gaps and version conflicts remain visible.
  6. The cover note does not claim that a missing attachment or unapproved decision is complete.
  7. The packet owner checked layout, page order, links, and attachments before sending.
  8. Nothing was automatically distributed or shared.

Common failure modes and fixes

Claude cannot see the local files

Fix: verify that you started the task from Desktop, connected the dedicated meeting folder, and kept Claude Desktop open. A fresh web/mobile-started cloud session does not automatically inherit your local folder. If using uploaded files, attach the exact sources instead.

Claude includes the wrong version

Fix: stop before assembly. Move the stale working copy outside the approved source set, obtain the approved version, and rerun the inventory. Do not rely on an apparently newer filename alone.

The packet order or formatting is wrong

Fix: compare the inventory's proposed order with packet-instructions.txt, approve the exact sequence, and inspect pagination and document rendering after assembly. If merging file formats is unreliable, keep the final packet as clearly numbered files.

Sensitive side files appear in the inventory

Fix: remove them from the connected or uploaded source set, narrow folder permissions, and restart with only intended sources. An archive-do-not-use/ label is an instruction, not an access-control boundary.

Claude begins assembling before approval

Fix: stop the task. Use Manually approve, repeat the inventory-only prompt, and insist on a human approval message before a second assembly prompt.

Files appear in Claude but not in final-packet/

Fix: distinguish a cloud-created downloadable artifact from a file written to your computer. Test the permitted local output path on Desktop; otherwise download and save the deliverables manually.

Sources Checked

  • Anthropic Claude Help Center, Get started with Claude Cowork. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork (accessed 2026-11-01). Verified current plan coverage, shared Cowork entry point, local-file bridge, and permission modes.
  • Anthropic Claude Help Center, Use Claude Cowork on web, desktop, and mobile. https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile (accessed 2026-11-01). Verified cloud-first execution, surface-specific local-folder limits, and continuation across devices.
  • Anthropic, Claude Cowork product guide: Getting started. https://claude.com/resources/guides/claude-cowork-product-guide/getting-started (accessed 2026-11-01). Used for guidance on connecting a folder and project-specific instructions. Some older interface and permission terminology in this guide is superseded by the current Help Center pages above.
  • Anthropic, Claude Desktop Cowork changelog. https://claude.com/docs/cowork/changelog (accessed 2026-11-01). Reviewed current release history for interface and permission changes.

Quarterly Refresh Flag

Review by 2027-02-01. Recheck Cowork's unified entry point, Team/Enterprise access, project and local-folder handling, cloud session file write-back, permission controls, and supported file outputs. Repeat the local final-packet/ write test after material product changes.

Something off in this workflow?

Related Workflows

How to Combine Claude Cowork and the Internal-Comms Skill for a Recurring Weekly 3P Update

Use Claude Cowork to gather the week's project material, then apply the internal-comms skill pattern to produce a consistent weekly 3P update.

Read Workflow

How to Build a Meeting Follow-Up Packet From Your Phone With Claude Cowork

Dictate a short meeting recap into Claude on your phone, then create a reviewed follow-up email, action list, and decision recap in one downloadable packet without Dispatch or a running desktop.

Read Workflow

How to Use NotebookLM to Turn Multi-Document Meeting Prep Into a One-Page Briefing Pack

Use NotebookLM to turn agendas, notes, proposals, and reference docs into a one-page meeting brief with key decisions, risks, and open questions.

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.