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

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 with local files and folders you choose to share. For related examples, see the Claude Cowork tool hub and the Anthropic Workflows series.

Problem and who this is for

Right after a coaching session, your best notes are often on your phone because that is what you have in your hand. The problem is not taking the note. The problem is turning that note into a clean follow-up email and a small action tracker once you are back at your desk.

This workflow is for coaches, advisors, mentors, and program leads who want a low-friction handoff from phone capture to desktop follow-up.

Why Cowork fits this workflow

The value of Cowork appears after the fast capture step. The phone helps you capture fresh details before they fade. Cowork helps once that note reaches the desktop folder.

In a recurring coaching workflow, Cowork can inspect the client folder, use a saved follow-up format, separate client commitments from coach tasks, and create both a follow-up email and an internal action tracker. It can also save the outputs back into the same project folder so the next session starts from a consistent place.

Use the phone for capture. Use Cowork in Claude Desktop for the structured follow-up work.

Why not normal Claude chat?

Normal Claude chat can draft one follow-up email if you paste the session note into the chat. That is fine for a one-off follow-up or a quick test.

Cowork is better for repeat client work because the folder, format file, prior outputs, archive, and project instructions stay together. You do not have to paste the same formatting rules or client context after every session. You still review before sending, but the handoff from note to draft becomes more repeatable.

Prerequisites

• Claude Desktop with Cowork available on a paid Claude plan.
• A simple phone-based way to capture notes right after the session. Example: typed note, dictated note, or voice-to-text summary.
• A desktop folder or Cowork project for the client or coaching program.
• A short file called follow-up-format.txt with your preferred email and action-tracker structure.
• A short file called client-context.txt for approved client context, program boundaries, or coaching preferences.
• A human review pass before any email is sent.

Set up a reusable Cowork project for client follow-up

Create one Cowork project for the client, cohort, or coaching program. Keep it scoped to follow-up work, not your full practice folder.

Use this folder structure:

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

Use session-notes for phone-captured notes after you move them from your phone to your desktop. Use final-followups for reviewed email drafts. Use action-trackers for the internal tracker. Move older notes and outputs into archive so Cowork can focus on the newest session unless you ask for history.

Put the email and tracker structure in follow-up-format.txt. Put approved client or program context in client-context.txt, such as preferred tone, session goals, communication boundaries, and any topics that should not be included in the follow-up email.

Add project instructions so future runs do not require the same setup prompt:

{
  "project_name": "Coaching Follow-Up and Action Tracker",
  "project_purpose": "Use Claude Cowork to turn phone-captured session notes into a client follow-up email and internal action tracker using a consistent format.",
  "project_instructions": [
    "Use the newest file in session-notes as the primary source unless I specify another file.",
    "Use follow-up-format.txt for the final email and tracker structure.",
    "Keep client commitments separate from coach tasks.",
    "Do not invent deadlines, promises, diagnoses, or commitments.",
    "Mark unclear names, dates, or ownership as [CONFIRM].",
    "Create a follow-up plan before drafting final outputs.",
    "Do not send any email. Save drafts only."
  ],
  "file_naming": "client-follow-up-client-name-yyyy-mm-dd"
}

These instructions tell Cowork how to handle the recurring folder. They do not replace your review. They help make each follow-up run more consistent.

How to gather the source material

1. Right after the session, capture the core notes on your phone while the details are still fresh. A short dictated summary is fine if that is faster than typing.
2. Save or send the note into a place you can access from your desktop. Example: a synced notes app, a plain text file, or an email to yourself that you then save into the client folder.
3. Once you are at your desktop, move that note into session-notes and name it clearly with the session date.
4. Keep follow-up-format.txt current with the sections you want. Example: recap, commitments, next session focus, and action tracker columns.
5. Keep client-context.txt short and approved. Do not use it as a dumping ground for sensitive history that is not needed for follow-up.
6. If the phone note is very rough, clean up obvious speech-to-text errors before you start Cowork.

Numbered workflow steps

1) Set up a small local project folder before you start Cowork

Cowork works best when the folder is clean, current, and limited to the specific task. Create the reusable project folder, add only the files you want Claude to use, and keep sensitive client context out unless it is needed for the follow-up.

2) Let Cowork inspect the folder and build a working plan

{
  "task": "Inspect a coaching follow-up folder and prepare a client follow-up plan from a phone-captured session note",
  "input": {
    "folder": "LOCAL CLIENT FOLLOW-UP PROJECT",
    "session_notes_folder": "session-notes",
    "format_file": "follow-up-format.txt",
    "client_context_file": "client-context.txt"
  },
  "rules": [
    "Use the newest session note in session-notes as the main source.",
    "Use client-context.txt only for approved standing context.",
    "Separate recap points, client commitments, coach tasks, and next-session items.",
    "Mark unclear names, dates, or ownership as [CONFIRM].",
    "Flag anything uncertain or incomplete.",
    "Do not send or finalize the email until the plan is reviewed."
  ],
  "output": {
    "follow_up_plan": "Recommended structure for the email and tracker",
    "client_commitments": "Actions that belong to the client",
    "coach_tasks": "Actions that belong to the coach",
    "unclear_items": "Anything that needs a human check"
  }
}

3) Review the plan before you let Cowork finish the output

Look at the commitments and task ownership before you let Cowork finish the outputs. Phone-captured notes are fast, but they can blur who said what. Fix that here rather than after the email is drafted.

Also check for sensitive details that should stay out of the client-facing email. Keep private coach notes, diagnoses, internal concerns, and unrelated client history out of the final draft unless they are appropriate and approved.

4) Ask Cowork for the finished deliverable

{
  "task": "Create a client follow-up email and action tracker from the reviewed coaching plan",
  "input": {
    "approved_plan": "USE THE REVIEWED PLAN"
  },
  "rules": [
    "Write one client-facing follow-up email and one internal action tracker.",
    "Keep client commitments and coach tasks separate.",
    "Do not invent deadlines that were never discussed.",
    "Keep uncertain items visible instead of guessing.",
    "Save drafts only. Do not send anything."
  ],
  "output_format": {
    "type": "email_and_tracker"
  }
}

5) Save the result and archive the input folder

Rename the finished files clearly and save them in final-followups and action-trackers. Move the session note and earlier drafts into archive after the follow-up is reviewed.

Do not let Claude send the email. Copy the approved draft into your email tool yourself after checking commitments, tone, dates, and privacy boundaries.

Future session runs

After the first setup, the next run can be shorter. Capture the new note on your phone, move it into session-notes, open the same Cowork project in Claude Desktop, and ask:

Create the follow-up email and action tracker from the newest session note.

For a stricter reusable prompt, use this:

{
  "task": "Create the follow-up email and action tracker from the newest session note.",
  "rules": [
    "Use the project instructions.",
    "Inspect the newest note in session-notes.",
    "Create a follow-up plan first.",
    "Ask for approval before drafting the final email and tracker.",
    "Save the final outputs without sending anything."
  ]
}

The point of the project is that follow-up-format.txt, client-context.txt, prior outputs, archive rules, and project instructions stay together. You still review every draft, but you do not rebuild the process from a blank chat after each session.

Tool-specific instructions

The phone is for fast capture only. Cowork runs in Claude Desktop. Unless you are using a separate mobile assignment workflow, move the note to the desktop project before asking Cowork to work.

Cowork is the right primary tool here because the real job happens after the phone capture step. Once the note reaches the desktop project, Cowork can inspect the newest note, use the saved format, separate client commitments from coach tasks, and produce both the email draft and the tracker.

Normal Claude chat is fine when you paste a one-off note and only need one email draft. Use Cowork for recurring client folders, saved output rules, and follow-up history.

Quality checks

1. The phone note is the only session source driving the follow-up unless extra files were intentionally added.
2. Client commitments and coach tasks are clearly separated.
3. No invented deadlines or promises slipped into the email.
4. Unclear names, dates, ownership, or commitments are marked for confirmation.
5. Sensitive client context is appropriate for the client-facing email.
6. The action tracker is short enough to use after every session.
7. Nothing is sent automatically. The user reviews and sends manually.

Common failure modes and fixes

The phone note is too rough

Fix: spend one minute cleaning up the note before it goes into the Cowork folder.

Task ownership is unclear

Fix: review the plan stage and rewrite ambiguous action items before the final output stage.

The workflow feels awkward

Fix: standardize one capture path from phone to desktop and reuse the same Cowork project so you are not improvising the handoff each time.

Sensitive context leaks into the email

Fix: keep client-context.txt short, avoid broad folder access, and review the plan before drafting. Remove private notes from the client-facing draft and keep them only in the internal action tracker if they are needed.