Use Claude to Turn 1:1 Notes into a Reviewable Follow-Up Plan

A one-to-one meeting often ends with a sentence like “we should follow up on that.” That is not a plan. It is a future scavenger hunt.

This worked template uses Claude to turn fictional 1:1 notes into a reviewable follow-up plan. The example is illustrative. It is not a recorded Claude run or a claim about output quality.

What you will create

You will create a short follow-up memo containing:

decisions and confirmed facts
actions with an owner and date only when the notes support them
risks or requests that need a human answer
a list of missing details

Level: Beginner. You need access to Claude on the web and notes that you are allowed to share. No project, connector, or coding setup is required.

The fictional input

Copy this into a plain text file or paste it directly into Claude:

1:1 notes, 10 October

People: Mira, Operations Manager; Emre, Customer Support Lead

Mira said the support team is still using the old refund reply. Emre said the new policy draft is waiting for legal review. No legal approval date was given.

The team wants a shorter weekly queue review. Emre suggested Tuesday morning, but no time was agreed.

Mira asked for a sample of five difficult tickets before the next review. Emre said he can collect examples from the last two weeks. The notes do not say who will write the summary.

Open concern: the old reply may still be copied from a shared document. The document owner was not identified.

The prompt

You are preparing a reviewable follow-up memo from meeting notes.

Rules:
1. Use only the information in the notes.
2. Separate confirmed facts from suggestions and open questions.
3. Do not invent an owner, date, approval, priority, or outcome.
4. If the notes suggest an action but do not name an owner or date, write "unassigned" or "not set".
5. Keep the memo under 350 words.
6. Preserve uncertainty. Do not turn a proposal into a decision.

Return these sections:

1. Confirmed facts
2. Decisions made
3. Follow-up actions as a table with columns: action, owner, date, evidence from notes
4. Open questions
5. Missing details to resolve at the next review

After the memo, add a short "Claim check". For each action, say whether the owner and date are supported by the notes.

Meeting notes:
[PASTE NOTES HERE]

Replace [PASTE NOTES HERE] with your own approved notes. Leave out personal data that the task does not need.

Review the result in three passes

Compare every fact in the memo with the original notes. Delete anything that does not have a clear source.
Check the action table. An owner and date should be present only when the notes provide them. In the example, collecting five difficult tickets is attributed to Emre, but the summary writer remains unassigned.
Ask the meeting participants to confirm decisions and fill the missing details. Do not send the memo as an official record before that check.

Acceptance check

The workflow passes when:

the old refund reply appears as a concern, not as a confirmed policy violation
legal review is described as pending, with no invented deadline
Emre owns collecting the five examples because the notes say he can do it
the summary owner is marked unassigned
Tuesday morning remains a suggestion, not a scheduled meeting
every action has a note reference or is flagged for review

If the output goes wrong

Claude invents dates or owners. Repeat the prompt with the sentence “Treat every missing owner and date as unknown. Do not infer them from job titles.”

Claude writes a polished summary that hides uncertainty. Ask for a two-column comparison of confirmed facts and suggestions before asking for the memo.

The notes contain sensitive details. Remove names, customer identifiers, account numbers, and unrelated personal information before uploading them. Use a fictional copy when you are learning the workflow.

Limits

This template improves organization, not accuracy. The notes remain the source of truth. Claude can make an unsupported sentence sound tidy, so a participant still needs to approve the final memo. The example uses fictional input and an illustrative acceptance result. It does not report a measured time saving or a personal test.

For the same review habit with a document instead of notes, see Use ChatGPT to Review a Draft Against a Written Brief.

Want one useful workflow each week? Join The Weekly Verdict.

Sources

Evidence label: Illustrative example. The input and acceptance result are fictional. Capability and safety notes are documentation-based. No hands-on Claude run is claimed.