Admins & Office Work14 min read

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.

claude coworkmeeting follow upmobile workflowvoice dictationaction tracking

Workflow summary

Quote this workflow accurately

Markdown version
Best for
Operators who need a repeatable, practical workflow instead of a blank prompt.
Input
Claude for iOS or Android, updated to the current version. Access to Cowork on mobile through Pro, Max, Ultra, Team (beta), or Enterprise where an administrator has enabled it. Cowork is not available on the Free plan...
Primary tool
Claude Cowork
Output
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.
Main risk
Fix: edit the text before sending, or send a spelling and date correction in the same conversation. Recheck the action table after the correction.
Verification step
Check the output against the source material and confirm any missing assumptions before you send, publish, or rely on it.

Continue from this article

Before you start: This workflow uses a new Claude Cowork cloud session on your phone, not the older Dispatch feature. Anthropic says Dispatch is a limited beta and is not available to new users. You do not need to pair your phone with a desktop or leave a computer awake. A session started on mobile cannot directly read a folder connected only through Claude Desktop. Use the recap you dictate and any material already available to the cloud session.

Privacy and approval: Only use meeting information that your organization permits in Claude. Do not include protected, confidential, or regulated material without an approved account and workflow. Claude drafts the packet; you check it and send any follow-up yourself.

The problem and who this is for

A meeting ends, and the useful details are still fresh: what was agreed, who owns the next step, what remains open, and when things are due. A follow-up email often waits until you get back to your desk. By then, the details may be harder to reconstruct.

This workflow is for executive assistants, office managers, coordinators, and operations leads who need to turn a short spoken recap into a usable follow-up packet while moving between meetings.

The output is a single reviewable document with three sections: a draft email, an action list, and a decision recap. The aim is to capture the facts immediately, not to automate communication with attendees.

Why Claude Cowork fits

Claude Cowork can start on mobile and create a document from your instructions and meeting recap. Its cloud sessions continue without your desktop running, and the same task and generated files are available when you later open Claude on the web or desktop.

Unlike the older phone-to-desktop Dispatch pattern, this process keeps the input and output in the Claude session. It does not depend on a local folder or a desktop-only template. That makes it more reliable for a meeting-to-meeting workday, with one tradeoff: you must manually download or place the finished file into your organization's filing system if you need a local copy.

For a one-off email, ordinary Claude chat can also work. Cowork is useful when you want a multi-part document and a repeatable review process. The method does not require a special plugin or connector.

Why not just draft a message in normal chat?

You can paste a recap into Claude chat and ask for an email. That is the simpler option if an email is all you need. The packet workflow adds an action tracker, a record of actual decisions, and a check for missing owners and dates. It also creates one file you can review and archive after the meeting.

Claude's general file-creation feature is available in regular chat too. Do not assume a file must be created in Cowork, or that the difference is access to local folders from the phone.

Prerequisites

  • Claude for iOS or Android, updated to the current version.
  • Access to Cowork on mobile through Pro, Max, Ultra, Team (beta), or Enterprise where an administrator has enabled it. Cowork is not available on the Free plan.
  • An internet connection for the mobile session.
  • The ability to use mobile dictation, or a typed/pasted meeting recap if dictation is inconvenient.
  • Permission to put the meeting's content into Claude and to download the resulting file.
  • Optional: a reusable Claude project created from scratch with project instructions. Do not use a project whose context depends on a folder that exists only on your computer.

If you see a Chat/Cowork selector in Claude, choose Cowork. If your account has the unified Claude experience, describe the task in the regular message box without switching modes. Enterprise and Team availability may depend on rollout or administrator settings.

Set up a reusable follow-up format (optional)

For a recurring meeting, create a new Claude project named Meeting Follow-Up Packet and add the standing instructions below to its project instructions. Use a project created from scratch, not one based on a local desktop folder. You can set it up ahead of time and then open that project on mobile for later meetings. Project creation and settings may be easier to manage in the current desktop app, but the actual meeting task runs on mobile.

These instructions are a readable JSON template for what to tell Claude, not a command or API request. If your project editor expects ordinary prose, paste the rules as plain text instead.

{
  "project_name": "Meeting Follow-Up Packet",
  "project_instructions": [
    "Treat the newest meeting recap in the current task as the primary source. Do not invent decisions or commitments.",
    "Create three clearly labeled sections: Follow-up email draft, Action list, and Decision recap.",
    "Include open questions and confirmation-needed items after the three main sections.",
    "For each action, show task, owner, due date, and status if they were actually provided.",
    "Mark unclear names, owners, due dates, and decisions with [CONFIRM]. Never guess them.",
    "Keep the email concise, professional, and in draft form only.",
    "Do not send messages, create calendar invitations, update third-party records, or contact attendees.",
    "Produce one downloadable Word document containing all three sections, and show a short preview in the conversation.",
    "Use the filename meeting-follow-up-packet-yyyy-mm-dd-topic.docx.",
    "Ask for human review before treating any wording or commitment as final."
  ]
}

A project can retain instructions and other project context, but do not rely on Claude automatically adding each finished packet to the project or filing it in a local directory. Download or store the file yourself after review.

If you do not want to set up a project, use the full one-off prompt in Step 2 instead.

How to capture the meeting recap

Immediately after the meeting, take 30 to 90 seconds to speak the essential points, using the same order each time:

  1. Decisions: What was explicitly approved or agreed?
  2. Actions: What must happen, and who owns it?
  3. Open questions: What remains undecided?
  4. Deadlines: Which dates or time frames were actually stated?

Say difficult names slowly, or type the spelling after dictation. Do not treat a proposed idea as a decision. If a deadline or owner was not established, say so. For confidential meetings, use your organization's approved notes process instead of recording details in an unapproved personal account.

Claude Mobile's microphone button supports dictation: it turns what you say into text. Review that text for recognition mistakes before you send it. This is different from a voice conversation; it does not require uploading a separately recorded audio memo.

Step-by-step workflow

1. Open a new cloud Cowork task on your phone

Open Claude Mobile and use Cowork, or the unified message box if your account no longer shows a separate Cowork selector. If you created the optional Meeting Follow-Up Packet project, open it first and start a new task there. Otherwise start a new Cowork task without a project.

Do not look for Dispatch, pair your phone to your desktop, or grant Claude access to your Documents folder. None of that is needed for this workflow.

2. Dictate the facts and request the packet

In the message box, tap the microphone and speak your recap. Check the transcribed text before sending, especially names, owners, dates, and the difference between an agreement and a proposal.

If you are using the reusable project, a short spoken request is enough:

Make the meeting follow-up packet from this recap. Meeting: [date and topic]. Decisions: [what was agreed]. Actions: [task and owner]. Open questions: [unresolved points]. Deadlines: [confirmed dates]. Keep anything uncertain marked [CONFIRM], and do not send anything.

If you are not using a project, paste this complete prompt into the conversation and replace the recap placeholder with the dictated or typed text:

{
  "task": "Create a meeting follow-up packet from my post-meeting recap",
  "meeting": {
    "topic": "INSERT MEETING TOPIC",
    "date": "INSERT MEETING DATE",
    "recap": "PASTE OR DICTATE DECISIONS, ACTIONS, OPEN QUESTIONS, AND DEADLINES HERE"
  },
  "source_rules": [
    "Use only the supplied recap and any files I explicitly attach to this cloud session.",
    "Separate confirmed decisions from proposed ideas and open questions.",
    "Do not invent names, owners, deadlines, commitments, or meeting attendance.",
    "Mark anything uncertain [CONFIRM]."
  ],
  "deliverables": [
    "Follow-up email draft, not sent",
    "Action list with task, owner, due date, and confirmation flags",
    "Decision recap distinguishing approved decisions from open questions"
  ],
  "output": {
    "format": "One downloadable DOCX containing all three labeled sections, plus a short in-chat preview",
    "file_name": "meeting-follow-up-packet-yyyy-mm-dd-topic.docx"
  },
  "approval_rules": [
    "Do not send emails or messages.",
    "Do not update calendars, task managers, or other systems.",
    "Leave unresolved facts visibly marked for human review."
  ]
}

The JSON is a copy/paste prompt, not a function call. Claude may ask for clarification or may return the draft before creating a downloadable file. If it does, ask it to create the DOCX from the reviewed text.

3. Review the short preview while the details are fresh

Before accepting the file, scan for factual errors. Correct names, ownership, deadlines, and sensitive wording in the same session. If you only have time for one correction, fix the action owners and due dates: those are the fields most likely to turn a plausible-looking packet into a misleading instruction.

A useful follow-up message is:

{
  "task": "Correct the packet before file creation",
  "corrections": [
    "INSERT CORRECT SPELLINGS, OWNERS, DATES, OR WORDING"
  ],
  "rules": [
    "Apply only the corrections I supply.",
    "Keep unresolved facts marked [CONFIRM].",
    "Show the revised email draft, action list, and decision recap for approval.",
    "Do not send or distribute anything."
  ]
}

4. Create and save the finished packet

Ask Claude to generate the final Word document if it has not already done so. Claude supports creating downloadable .docx files on mobile. Tap Download to open the document in your phone's preview or a compatible app. Check the file, then save or share it through your organization's approved process.

You can also reopen the same Claude session later on the web or desktop and download the file there. This is not an automatic transfer into a local folder, and it does not depend on your desktop being awake.

5. Send the reviewed follow-up yourself

Open the email-draft section, make any final edits in your email application, and send it yourself. Copy the action list into the team's approved tracker if needed. File the decision recap according to your organization's normal records process.

Do not treat Claude's finished document as permission to send messages, assign work in external systems, or make commitments on behalf of attendees.

What the finished packet should contain

The document should have a meeting date and topic, followed by:

  1. Follow-up email draft: a subject line, greeting, short summary, confirmed next steps, and a closing. No invented recipients or statements of approval.
  2. Action list: a table with action, owner, due date, status, and any [CONFIRM] flag. Unknown fields stay unassigned.
  3. Decision recap: a list of decisions actually made, with a separate section for proposals and unresolved questions.

A short Confirm before sending section should identify any missing or contradictory facts. One document with these sections is easier to review on a phone than a collection of loosely named files.

Tool-specific instructions and important limits

Claude Mobile dictation

Use the microphone in Claude's text input for a short spoken recap. Dictation converts speech into text. Check the transcription before sending because similar-sounding names and dates can be wrong. If dictation is unavailable or inconvenient, type or paste the recap instead.

Claude Cowork cloud sessions

For Pro, Max, and Ultra, new Cowork sessions run in the cloud. Anthropic also documents Cowork on mobile for eligible Team users in beta and Enterprise users when their organization enables it. Cloud sessions can continue when your computer is off and can be resumed from other devices.

Local-folder limitation: A session started on mobile cannot directly access desktop-connected local folders. If the required template exists only on your computer, put the necessary headings in the prompt or an account-accessible project ahead of time, or finish the job later from desktop. Do not claim the phone task will automatically save to follow-up-packets/ on your computer.

File creation

Claude can generate Word documents in mobile conversations, subject to the account's file-creation capability being enabled. If the document-generation option is disabled by an organization administrator or the file cannot be generated, request the three sections as text and paste them into an approved document template yourself.

Quality checks before sending

  • The email, action list, and decision recap are all present and based on the recap actually provided.
  • All names, dates, owners, and deadlines match what was said, or are marked [CONFIRM].
  • Proposed ideas are not mislabeled as final decisions.
  • The action list identifies unknown owners and deadlines instead of inventing them.
  • No email, calendar invitation, or external update was sent automatically.
  • The downloaded file opens and contains the reviewed version, not an earlier draft.
  • Sensitive or politically charged wording has been reviewed by the person responsible for the communication.
  • The packet is saved into the organization's approved records location by a human, if required.

Common failure modes and fixes

The microphone mishears a name or deadline

Fix: edit the text before sending, or send a spelling and date correction in the same conversation. Recheck the action table after the correction.

Claude adds a decision that was only discussed

Fix: require two headings, Decisions made and Still under discussion, and move each statement back to the correct section. Do not infer consensus from a rough recap.

Claude cannot find the local template

Fix: a mobile-started cloud task cannot fetch your desktop folder. Paste the template headings into the project instructions or the prompt, or reopen the work from a desktop-started workflow when the local folder is essential.

The packet looks finished but fields are missing

Fix: keep [CONFIRM] visible rather than filling blanks with plausible owners or dates. Ask Claude to list all missing fields under Confirm before sending.

No Word file appears

Fix: ask for a downloadable DOCX explicitly and check whether code execution and file creation is enabled for your account. If unavailable, copy the three plain-text sections into Word or another approved document tool.

The task appears unavailable on mobile

Fix: update Claude Mobile; check whether your account has Cowork access. Team access is in beta, and Enterprise availability may require the owner to enable Cowork. For a quick one-off, ordinary Claude chat can still dictate text and generate files where file creation is enabled.

Safety and approval boundaries

Use the minimum necessary meeting details. Do not upload private personnel information, patient data, confidential contracts, or regulated records unless your organization has approved that exact use in Claude. Be deliberate about any connectors or plugins enabled in the account; the prompt's draft-only rule is not a substitute for limiting permissions.

This process produces a draft for human review. You remain responsible for the final message, task assignments, and any recordkeeping requirements.

Sources Checked

  • Anthropic, 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 mobile Cowork access, unified-versus-selector interfaces, cloud sessions, cross-device continuation, and local-folder restrictions.
  • Anthropic, Get started with Claude Cowork: https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork (accessed 2026-11-01). Verified Cowork file output and project-based work.
  • Anthropic, Assign tasks from anywhere in Claude Cowork: https://support.claude.com/en/articles/13947068-assign-tasks-from-anywhere-in-claude-cowork (accessed 2026-11-01). Verified that Dispatch is a limited beta not available to new users.
  • Anthropic, Use dictation on Claude Mobile: https://support.claude.com/en/articles/10065434-use-dictation-on-claude-mobile (accessed 2026-11-01). Verified microphone dictation and its distinction from voice mode.
  • Anthropic, Create and edit files with Claude: https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude (accessed 2026-11-01). Verified DOCX creation and download on Claude Mobile and organization capability controls.
  • Anthropic, Organize your tasks with projects in Claude Cowork: https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork (accessed 2026-11-01). Verified reusable project instructions, cross-device project availability, and the separation of local folders from cloud project metadata.
  • Anthropic, Use Claude Cowork safely: https://support.claude.com/en/articles/13364135-use-claude-cowork-safely (accessed 2026-11-01). Verified current safety guidance and permissions risk.

Quarterly Refresh Flag

Review by 2027-02-01. Recheck mobile Cowork availability by plan, unified-versus-selector UI, mobile dictation, project setup, cloud/local file access, DOCX creation on mobile, and whether Dispatch remains limited to existing users.

Something off in this workflow?

Related Workflows

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.

Read Workflow

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 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.