Educators & Coaches13 min readUpdated Nov 1, 2026

How Coaches Can Capture Session Notes on a Phone and Let Claude Cowork Turn Them Into a Follow-Up Email and Action Tracker

Capture coaching session notes on a phone, then let Claude Cowork turn them into a follow-up email and action tracker.

claude coworkcoaching follow upphone notesaction tracker

Workflow summary

Quote this workflow accurately

Markdown version
Best for
You finish a coaching session with the next steps fresh in your head. You can capture a quick note on your phone, but turning that rough note into a clear client email and an internal action tracker often waits until...
Input
A Claude plan with Cowork access on your chosen device: Pro, Max, Ultra, Team (mobile in beta), or Enterprise (mobile subject to admin enablement). The current Claude app for iOS or Android, or claude.ai on the web as...
Primary tool
Claude Cowork
Output
Capture coaching session notes on a phone, then let Claude Cowork turn them into a follow-up email and action tracker.
Main risk
Fix: If this is a mobile started task, supply the approved format and context in its cloud project or paste them directly. Do not point it at a desktop directory. If the files are local only, start a separate task fro...
Verification step
The current session note is identified as the primary source, and accessible supporting files are named. Client commitments and coach tasks are separated in the plan and tracker. No invented deadline, promise, diagnos...

Continue from this article

Privacy and review warning: Coaching notes can contain personal or confidential information. Capture only what you are permitted to process in Claude, use an approved account, and do not record a session without appropriate consent. Keep private observations out of client-facing follow-ups. Claude drafts; you decide what to share and send the email yourself.

Cowork requirements at a glance: Cowork is available on Claude Pro, Max, Ultra, Team, and Enterprise plans, not Free. Mobile Cowork is supported on Pro, Max, and Ultra, is in beta for Team, and requires Enterprise admin enablement. The simplest phone-first version uses a Claude account project or session containing the approved follow-up format and context. A local-folder version must be started on Claude Desktop, not on the phone.

If Claude Cowork is new to you

Start with the Claude Cowork tool hub or the Anthropic Workflows series. Cowork now works on Claude mobile, web, and desktop. In the unified Claude experience, simply describe a task in a conversation. If your app still has a Chat/Cowork selector, choose Cowork for this multistep job. No separate Dispatch setup is required.

New tasks on Pro, Max, and Ultra run in the cloud by default. The session can continue when you put your phone away. But cloud execution does not upload folders from your computer automatically, and a mobile-started session cannot directly open a connected desktop folder.

Problem and who this is for

You finish a coaching session with the next steps fresh in your head. You can capture a quick note on your phone, but turning that rough note into a clear client email and an internal action tracker often waits until later. By then, ownership and details can be blurred.

This workflow is for coaches, advisors, mentors, and program leads who need a repeatable way to produce the follow-up while keeping client commitments distinct from their own tasks. It is a drafting workflow, not an automated client-messaging system.

Why Cowork fits this workflow

Cowork can take a session note, compare it against approved formatting and context, prepare a follow-up plan for review, and produce two separate deliverables. Since Cowork sessions run in the cloud, you can begin from the phone rather than waiting to return to your desk.

The benefit is consistency, not automatic truth. A clear format, explicit source rules, and a human approval step do more for quality than adding more background files.

Why not normal Claude chat?

For a single short email, a regular Claude response to pasted notes may be sufficient. Cowork is useful when you need two deliverables, an explicit plan-and-approve sequence, saved project instructions, and downloadable files. Claude's unified interface may perform that work within the same conversation, without a separate mode selection.

Prerequisites

  • A Claude plan with Cowork access on your chosen device: Pro, Max, Ultra, Team (mobile in beta), or Enterprise (mobile subject to admin enablement).
  • The current Claude app for iOS or Android, or claude.ai on the web as an alternative.
  • A phone note or dictated summary from a session you are authorized to process.
  • An approved follow-up-format.txt and short client-context.txt, available to the cloud session, or pasted into that session explicitly.
  • A named person who reviews the follow-up and sends it manually.

For sensitive client, student, or patient information, confirm your organization's authorization and privacy requirements before uploading anything. An ordinary paid account is not, by itself, an approval to process regulated data.

Set up the reusable follow-up workspace

Keep the original folder convention for your own filing and for optional desktop work:

session-notes/
final-followups/
action-trackers/
archive/
follow-up-format.txt
client-context.txt

session-notes/ contains dated raw notes. final-followups/ is where you store approved email drafts, action-trackers/ holds internal actions, and archive/ holds older material. These are your organization folders; naming them in a phone prompt does not grant a mobile session access to them or guarantee automatic saving there.

In follow-up-format.txt, specify a brief recap, client commitments, coach tasks, next-session focus, and action tracker columns such as task, owner, due date, status, evidence. In client-context.txt, include only approved standing information: communication style, relevant goals, boundaries, and topics to exclude. Do not store a full sensitive history there.

Create an account-based Claude project for the client or program where permitted. Put the approved rules in its instructions and make the format/context files available as project knowledge or in the current cloud session. A project attached to a local computer folder is a different path and supports Cowork sessions starting on desktop only. Projects do not automatically write completed outputs back into their knowledge; save important reviewed results yourself.

Use this JSON as the content of your project instructions. It is a prompt, not a special Claude configuration file that executes when saved to disk:

{
  "project_name": "Coaching Follow-Up and Action Tracker",
  "project_purpose": "Turn phone-captured coaching notes into a reviewed client email draft and internal action tracker.",
  "project_instructions": [
    "Use the session note explicitly supplied for this run as the primary source; if working in a local folder, use the newest specified file in session-notes.",
    "Use follow-up-format.txt when it is actually accessible in the current task; otherwise ask me to supply its contents.",
    "Use client-context.txt only for approved standing context.",
    "Keep client commitments separate from coach tasks in both the plan and final outputs.",
    "Do not invent deadlines, promises, diagnoses, or commitments.",
    "Mark unclear names, dates, ownership, and decisions as [CONFIRM].",
    "Create a follow-up plan and request human approval before creating final drafts.",
    "Do not send emails or messages. Create drafts only."
  ],
  "file_naming": "client-follow-up-client-name-yyyy-mm-dd"
}

How to gather the source material

  1. Immediately after the session, type or dictate a short note on your phone. Capture topics discussed, client commitments, coach tasks, open questions, and dates. Use your phone keyboard's dictation feature if that is easiest.
  2. Spend a minute correcting obvious speech-to-text mistakes. Check names, who agreed to do what, and numbers. Do not ask Claude to infer missing commitments.
  3. Phone-first route: Open Claude mobile and paste the corrected note into the task message. Refer to your account-based project if its rules and files are accessible. You do not have to move the note into a desktop folder first.
  4. Desktop-folder route: If the approved format or past notes exist only in a local folder, place the note in session-notes/, connect just that folder in Claude Desktop, and start the task from desktop. You can then check or steer that same session on your phone; the desktop app must stay open for local file access. A new cloud task itself does not need the computer awake to keep processing cloud-accessible inputs.
  5. If the note begins in a third-party notes app, use a straightforward copy/paste or manual file export. Confirm that your specific notes app and mobile operating system support the copy, share, or export path you plan to use into Claude; no automatic notes-app sync is assumed.

Numbered workflow steps

1) Open the right Cowork session and confirm the inputs

From Claude mobile, open the account-based project (if using one) and start a task with your corrected note. In the unified experience, simply describe the job. If your account still shows a mode selector, choose Cowork. Ask Claude to identify which of the format and context documents it can actually read, before proceeding. If either is absent, paste the approved text into the session rather than assuming a local folder is visible.

A project name is a helpful reference but not a substitute for accessible source files. When in doubt, begin with just the short session recap and your formatting rules.

2) Inspect the note and prepare a follow-up plan

Paste this JSON prompt, replacing the placeholder with the corrected note. Do not ask for the client email yet.

{
  "task": "Inspect my session recap and prepare a coaching follow-up plan for approval",
  "input": {
    "session_note": "PASTE THE CORRECTED SESSION NOTE HERE",
    "format_file": "follow-up-format.txt, only if accessible to this cloud task",
    "client_context_file": "client-context.txt, approved information only"
  },
  "rules": [
    "Treat this supplied note as the source of truth for the session.",
    "State which supporting files you actually read; ask for any missing format or context.",
    "Separate the client's commitments from the coach's tasks.",
    "List the recap, next-session focus, and unclear items.",
    "Do not invent deadlines, promises, diagnoses, or commitments.",
    "Mark unclear names, dates, task owners, and decisions as [CONFIRM].",
    "Do not draft or send the email yet. Stop for my approval."
  ],
  "output": {
    "follow_up_plan": "Brief outline for the email and tracker",
    "client_commitments": "Only actions actually agreed to by the client",
    "coach_tasks": "Only actions assigned to the coach",
    "next_session_focus": "Explicitly discussed topics or [CONFIRM]",
    "unclear_items": "Information needing human confirmation"
  }
}

3) Correct the plan before drafting

Check every owner, date, and commitment against your note. Remove private coach observations that are not appropriate in the client email. If the note does not identify an owner, do not silently make the coach or client responsible; leave [CONFIRM] in the plan. Approve the revised plan explicitly.

4) Create the two reviewed deliverables

Only after approving the plan, send this second JSON prompt in the same session:

{
  "task": "Create the coaching follow-up email draft and separate internal action tracker",
  "input": {
    "approved_plan": "USE THE PLAN I JUST APPROVED",
    "output_names": ["client-follow-up-client-name-yyyy-mm-dd", "action-tracker-client-name-yyyy-mm-dd"]
  },
  "rules": [
    "Use only the approved plan, the source note, and approved context.",
    "Draft one client-facing email and one internal action tracker.",
    "Keep client commitments and coach tasks clearly separate.",
    "Do not add new promises, diagnoses, deadlines, or commitments.",
    "Keep any unresolved point marked [CONFIRM].",
    "Return reviewable drafts. Do not send messages or edit external records."
  ],
  "output_format": {
    "client_email": "Short subject line, recap, client commitments, next steps, closing",
    "internal_action_tracker": "Table with task, owner, due date, status, and source/confirmation note"
  }
}

5) Save, review, and send manually

On mobile, open the output in your Claude session, then download or copy it when available. Store the approved email draft in your own final-followups/ folder and the tracker in action-trackers/ when you return to your file system. Keep the raw note for traceability according to your retention rules; archive it yourself after checking the outputs. Cowork does not automatically synchronize a local folder or append the tracker to an external system merely because those paths appear in your instructions.

Copy the approved email into your email app, review the recipient and content one final time, and send it yourself.

Expected output

You should have an unsent client email that accurately summarizes the conversation, plus an internal action tracker that distinguishes client commitments from coach tasks. Any unresolved name, owner, or date remains marked [CONFIRM] rather than being invented.

Future session runs

Reuse the same account-based project with its approved instructions and context. After each session, paste the corrected note and run the inspect-and-plan prompt first. Do not assume the project has automatically archived earlier results or updated its own files.

{
  "task": "Prepare the next coaching follow-up from the note supplied in this message",
  "rules": [
    "Use the current note as the primary source.",
    "Use only accessible, approved project context.",
    "Separate client commitments and coach tasks.",
    "Stop after the plan for my review; draft only after approval.",
    "Mark uncertainty [CONFIRM], and never send anything."
  ]
}

Tool-specific instructions and tips

  • Claude mobile: Start, steer, and review a cloud Cowork task from your phone. You do not need Dispatch or a continuously awake computer for cloud-only work.
  • Claude projects: An account-based project can supply instructions and context on mobile. Check which files are available in the session; local-folder-based project sessions are desktop-only.
  • Claude Desktop: Use a desktop-started session when local session-notes/ or templates must be accessed directly. Desktop must remain open for that file bridge. A mobile-started task does not gain local folder access merely because Desktop is open.
  • Approvals: Use Manually approve for file or connector actions with consequences. Automatically approve performs automated safety checks and may ask you; Skip all approvals skips those checks. These are different settings. Deleting files still requires approval.

Quality checks

  1. The current session note is identified as the primary source, and accessible supporting files are named.
  2. Client commitments and coach tasks are separated in the plan and tracker.
  3. No invented deadline, promise, diagnosis, or commitment appears.
  4. Ambiguous names, dates, owners, and decisions remain [CONFIRM] until checked.
  5. Confidential internal observations do not appear in the client-facing email.
  6. The tracker has usable owners and next steps without adding speculative tasks.
  7. The outputs were saved deliberately, not assumed to have appeared in a desktop folder.
  8. Nothing was sent automatically; the coach approved and sent the message.

Common failure modes and fixes

Claude cannot see the format or client-context file

Fix: If this is a mobile-started task, supply the approved format and context in its cloud project or paste them directly. Do not point it at a desktop directory. If the files are local-only, start a separate task from Claude Desktop with that folder connected.

The dictated note confuses who owns an action

Fix: Edit the source note first, then correct the plan before producing a client-facing draft. Mark unresolved ownership [CONFIRM].

The output appears in Claude but not in your local folders

Fix: Download or copy the result and place it in final-followups/ or action-trackers/ yourself. A cloud project is not a folder synchronization service.

Sensitive context enters the client email

Fix: Keep client-context.txt brief and approved. Remove private observations from the plan and final draft; do not store unnecessary personal history in the project.

The follow-up reads like a diagnosis or promises an outcome

Fix: Restrict it to session discussion, client-stated goals, and agreed next steps. Delete any inferred diagnosis, guarantee, or outcome claim.

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).
  • 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).
  • Anthropic, Claude Cowork product guide: Getting started. https://claude.com/resources/guides/claude-cowork-product-guide/getting-started (accessed 2026-11-01; some desktop-only setup language predates the cloud/mobile rollout, so use the current Help Center articles for surface behavior).
  • Anthropic, Claude Cowork changelog. https://claude.com/docs/cowork/changelog (accessed 2026-11-01).
  • Anthropic Claude Help Center, 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; reverified for project instructions, account context, and local-folder distinction).

Quarterly Refresh Flag

Review on 2027-02-01. Recheck mobile Cowork access by plan, the unified interface, project-context availability, local-folder restrictions, file export behavior, permissions, and privacy guidance.

Something off in this workflow?

Related Workflows

11m
Educators & Coaches

How Coaches Can Use Claude Skills to Turn a Session Recording Into a Client Recap and Next-Step Plan

Use Claude Skills to turn a coaching session transcript and client-goals note into a structured recap, client commitments list, and next-session plan.

Read Workflow

How Coaches Can Turn a Session Voice Memo Into a Participant Worksheet and Facilitation Run Sheet With NotebookLM

Use NotebookLM to turn a coaching session voice memo or workshop debrief into a participant worksheet, a facilitation run sheet, and a clean slide outline for the next session.

Read Workflow

How to Turn an End-of-Day Voice Memo Into a Substitute Plan or Assistant-Coach Handoff

Turn a short end-of-day voice memo into either a substitute plan or an assistant-coach handoff with timing, materials, priorities, and watch-fors for the next day.

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.