The Meeting Notes to Action Prompt Pack

You are a professional meeting editor. Clean up the raw transcript below so it reads clearly, removing filler words (um, uh, you know, like, sort of), false starts, and repetition. Keep every substantive idea, decision, and number exactly as said. Do not summarise or change the meaning of anything. Do not add commentary. Format the output as a clean dialogue, each speaker on a new line, labelled as [SPEAKER 1], [SPEAKER 2] etc. unless names are clear from context.

Meeting type: [e.g. client kick-off / internal team standup / strategy session]
Raw transcript:
[PASTE FULL TRANSCRIPT HERE]

Constraints:
- Preserve every decision, number, deadline, and name exactly as spoken
- Remove only filler and repetition, nothing else
- Do not add bullet points or summaries
- Output clean dialogue only

Read the cleaned transcript below and extract every key point discussed. A key point is any idea, problem, decision, concern, or piece of information that someone in the meeting would need to remember. Do not include small talk or tangents.

Format as a numbered list. One point per line. No sub-bullets. Keep each point to one sentence.

Cleaned transcript:
[PASTE CLEANED TRANSCRIPT HERE]

Meeting date: [DD/MM/YYYY]
Meeting type: [e.g. quarterly review / project kick-off / sales call]

Constraints:
- One sentence per point
- No grouping or sub-bullets
- Include all concerns and objections raised, not just positive points
- If a decision was reversed during the meeting, note both the original and the final position

Using the key points below, write a one-page meeting summary in the following format. Be concise. Every section should be scannable in under 30 seconds.

FORMAT:
## Meeting: [MEETING NAME]
Date: [DATE] | Attendees: [LIST NAMES OR ROLES]

### What We Covered
3 to 5 bullet points on the main topics discussed.

### What Was Decided
Bullet list of decisions made. Each one starts with the decision, not the discussion.

### What Was Not Resolved
Anything left open, deferred, or needing more information before a decision can be made.

### Numbers and Deadlines Mentioned
Any specific figures, dates, or targets referenced in the meeting.

Key points to work from:
[PASTE KEY POINTS LIST HERE]

Constraints:
- Maximum 400 words for the whole summary
- No em dashes, no jargon
- 'What Was Decided' must be decisions only, not discussion
- Include every open question in 'What Was Not Resolved' even if it seems minor

From the summary or transcript below, extract only the decisions that were made. A decision is a commitment to do something, a choice between options, or an agreement on a direction. Do not include discussion, options considered, or anything that was raised but not resolved.

Format:
DECISION [number]: [What was decided, in one sentence]
Decided by: [Name or role if clear, otherwise 'Group']
Context: [One sentence on why this decision was made, if clear from the text]

Source text:
[PASTE SUMMARY OR TRANSCRIPT HERE]

Constraints:
- Decisions only, no actions, no open questions
- If a decision was conditional ('we will do X if Y happens'), include the condition
- If a decision overrides a previous decision, note what it replaces
- Minimum 1 decision, maximum 15 per meeting

Read the transcript or summary below and extract every action item. An action item is any task, commitment, or next step that someone agreed to do, was asked to do, or volunteered to do. Include implied actions (e.g. if someone said 'I'll look into that', that is an action).

Format each action as:
ACTION [number]:
Task: [What needs to be done, specific enough to do without re-reading the transcript]
Owner: [Name or role of the person responsible]
Deadline: [Specific date if mentioned, or 'Not specified']
Dependencies: [Anything this action is waiting on, or 'None']
Priority: [High / Medium / Low based on context]

Source text:
[PASTE TRANSCRIPT OR SUMMARY HERE]

Team members on this call: [LIST NAMES AND ROLES]

Constraints:
- If an action has no clear owner, mark Owner as '[UNASSIGNED]' and flag it
- Include every commitment, even informal ones like 'I'll ping you about that'
- Split compound actions into separate items (one task per action item)
- Do not invent deadlines. If none was given, write 'Not specified'

Take the action items list below and reorganise them by owner so each person can see their own list at a glance.

Format:
### [OWNER NAME / ROLE]
| # | Task | Deadline | Depends on |
|---|------|----------|------------|

One table per owner. If an action is shared (two people co-own it), list it under both owners and mark it as (SHARED).

At the bottom, include a separate table:
### Unassigned Actions
List any items with no clear owner, flagged for discussion.

Action items list:
[PASTE FULL ACTION ITEMS LIST HERE]

Constraints:
- Preserve every action exactly as extracted, do not rewrite or combine
- Tables must be markdown formatted
- Sort each person's actions by deadline (earliest first, 'Not specified' last)
- Unassigned table must not be left empty if any unassigned items exist

Write a follow-up email to the internal team after the meeting described below. The tone should be warm, direct, and concise. No corporate language. The email should make it completely clear what was decided and what each person needs to do next, without being bossy.

Meeting name: [MEETING NAME]
Date: [DATE]
Sender name: [YOUR NAME]
Recipients: [LIST TEAM MEMBERS]

Decisions made:
[PASTE DECISIONS LIST HERE]

Action items:
[PASTE ACTION TABLE OR LIST HERE]

Any open questions or things deferred:
[PASTE OPEN QUESTIONS HERE]

Email format:
- Subject line (clear and specific, not 'Meeting Follow-Up')
- Opening line (one sentence, friendly, references the meeting)
- Decisions section (2-4 bullet points)
- Actions section (each person's actions listed under their name)
- Open questions (bullet list, note who is resolving each one)
- Closing line (one sentence, states the next touchpoint)

Constraints:
- Maximum 300 words
- No jargon, no corporate filler
- Each person's name must appear next to their specific actions
- No 'please do not hesitate to reach out' or similar filler closings
- British spelling throughout

Write a follow-up email to a client or external stakeholder after the meeting below. The tone should be professional, warm, and reassuring. It should confirm what was agreed, set clear expectations for next steps, and make the client feel in good hands.

Meeting name: [MEETING NAME]
Date: [DATE]
Sender name and role: [YOUR NAME, YOUR ROLE]
Client name: [CLIENT NAME]
Client company: [CLIENT COMPANY]

What we covered in the meeting:
[2-4 SENTENCES SUMMARISING THE MAIN TOPICS]

Decisions and agreements:
[PASTE DECISIONS LIST]

Your next steps (your side):
[LIST YOUR TEAM'S COMMITMENTS WITH DATES]

Client next steps:
[LIST ANYTHING THE CLIENT NEEDS TO DO OR SEND]

Email format:
- Subject line (references the meeting and the project/account name)
- Opening paragraph (1-2 sentences confirming the meeting and its purpose)
- Summary of what was agreed (3-5 bullets)
- Next steps split into two groups: 'From our side' and 'From your side'
- Closing paragraph (1 sentence confirming the next contact point or meeting)

Constraints:
- Maximum 350 words
- No passive voice
- Dates for every commitment, or 'we will confirm by [DATE]' if not yet known
- British spelling
- No 'I hope this finds you well' or 'do not hesitate to contact me'

Read the transcript below and identify every disagreement, concern, blocker, or unresolved tension. This is not about blame. It is about making sure nothing that could slow down progress gets buried in the meeting notes.

For each one, format as:
ISSUE [number]:
Description: [What the disagreement or blocker is, in neutral language]
Raised by: [Name or role if clear]
Current status: [Unresolved / Partially resolved / Resolved in meeting]
Resolution (if any): [What was agreed, or 'None yet']
Next step to resolve: [Specific action needed to move this forward, with an owner if mentioned]

Source transcript or summary:
[PASTE HERE]

Constraints:
- Use neutral, factual language. Do not editorialize or take sides
- Include concerns that were brushed past or deferred without resolution
- If the same issue came up more than once, list it once and note that it recurred
- If there are no disagreements or blockers, output: 'No unresolved disagreements or blockers identified'

You are maintaining a running log for a recurring meeting. Below is the log from previous sessions and the notes from the most recent session. Update the log by adding the new session's summary, decisions, and actions, and checking off any previous actions that were confirmed as completed in this session.

Meeting name: [MEETING NAME e.g. Weekly Team Standup / Monthly Client Review]
Frequency: [WEEKLY / FORTNIGHTLY / MONTHLY]
Date of this session: [DATE]

Existing log:
[PASTE PREVIOUS LOG HERE, OR WRITE 'First session, no prior log']

This session's decisions:
[PASTE DECISIONS FROM THIS MEETING]

This session's actions:
[PASTE ACTION ITEMS FROM THIS MEETING]

Actions confirmed as done in this session:
[LIST ANY PREVIOUS ACTIONS THAT WERE SIGNED OFF AS COMPLETE]

Output the full updated log with:
1. Each session as a dated section (most recent first)
2. A 'Still Open' section at the top listing every action not yet marked done, with original owner and original deadline
3. A 'Completed' archive section at the bottom

Constraints:
- Do not delete any previous content, only add and update
- 'Still Open' actions must include the session date they were first raised
- Mark overdue actions (deadline passed, not marked done) as [OVERDUE]
- Maximum 600 words per session section