The 15-Minute Meeting-to-Action Pack

You are an operations analyst. Convert the meeting transcript below into a decision log.

Meeting date: [DATE]
Attendees and roles, if known: [ATTENDEES]

Rules:
- Use only the transcript. Do not infer agreement from silence, politeness, or topic changes.
- Record a decision only when the group clearly commits to a choice.
- Put proposals, preferences, and unresolved options under “Decision candidates.”
- Preserve names, dates, amounts, and product terms exactly as stated.
- For every decision, include a short verbatim evidence quote.
- If the speaker is unclear, say “speaker unclear.”

Return:
1. Confirmed decisions table: ID, decision, decision owner, rationale stated, evidence quote
2. Decision candidates: proposal, who raised it, what remains unresolved
3. Superseded or contradictory statements
4. “No decision captured” if the meeting contains no explicit decision

TRANSCRIPT:
[PASTE OR ATTACH TRANSCRIPT]

Using the same transcript and the decision log, build an accountable action register.

Rules:
- Capture only explicit commitments or tasks required by a confirmed decision.
- Never invent an owner or deadline.
- Mark dates as exact, implied, or missing.
- Convert relative dates such as “next Friday” into a calendar date only when the meeting date makes that unambiguous.
- Separate “I can” or “we should” from an actual commitment.
- Include a short evidence quote for every action.

Return a table with:
- Action ID
- Deliverable stated as a verifiable outcome
- Owner
- Deadline
- Date status: exact / implied / missing
- Dependency
- Evidence quote
- Risk or ambiguity

Then list:
1. Actions missing an owner
2. Actions missing a deadline
3. Commitments that conflict with another statement
4. The three questions that would remove the most execution risk

Audit the decision log and action register against the transcript as a skeptical chief of staff.

Check for:
- A proposal incorrectly labeled as a decision
- An action assigned to someone who did not accept it
- A deadline invented from vague timing
- Duplicate or contradictory actions
- Missing dependencies or approvals
- Important open questions hidden by confident wording
- Names, numbers, or dates that do not match the transcript

Return:
1. A correction table: item, problem, transcript evidence, required correction
2. A traffic-light status for every decision and action:
   - Green: explicit and supported
   - Amber: plausible but needs confirmation
   - Red: unsupported or contradicted
3. A corrected final decision log and action register

Do not praise the output. If a claim is not supported, remove it or mark it for confirmation.

Turn the audited decision log and action register into a sendable meeting follow-up.

Audience: [TEAM / CLIENT / LEADERSHIP]
Tone: concise, neutral, accountable

Write:
1. Three subject-line options
2. A brief opening sentence stating the meeting purpose
3. Confirmed decisions
4. Actions grouped by owner, with deadlines
5. Open questions and the person needed to resolve each one
6. A final confirmation line asking recipients to flag corrections by [DATE/TIME]

Constraints:
- Keep the message under 350 words.
- Do not include transcript quotes or confidence labels.
- Do not present amber or red items as settled.
- Do not add praise, filler, or generic meeting language.
- Use “owner needed” and “date needed” when information is missing.
- Preserve exact names, dates, and amounts from the audited register.