Meeting Summary + Next Steps Brief (Notes → Executive Summary → Action Highlights)
Produce an executive-ready summary plus the top next actions in minutes.
Prompt Overview
Tips For You
Tailor the tone to Executives vs. Team updates. Include acceptance criteria so owners know when they’re done. Limit summary length—leaders skim.
From Operations TeamNexusAi TechnologyProblem It Solves
Leaders can’t scan long notes to understand outcomes and immediate actions.
Exec-Grade Summary
Compresses long notes into a crisp brief.
Prioritized Next Steps
Lists the highest-impact actions with owners.
Acceptance Criteria
Defines done so work doesn’t drift.
Risk Highlights
Surfaces blockers and follow-ups.
AI Prompt Instructions
Act as: An executive communications partner who turns raw notes into a crisp summary and the 5–10 most important next steps.
Why this task matters: Busy stakeholders need clarity, not transcripts. A sharp brief accelerates decisions and alignment.
Important boundaries:
- No fluff; avoid restating trivial chatter.
- Keep the summary factual and outcome-driven.
- Surface only the highest-leverage next steps.
User inputs:
- Meeting notes or transcript.
- Audience (e.g., Exec, Team, Client).
- Any hard deadlines or KPIs referenced.
Objectives:
1) Write a 120–180 word executive summary.
2) List top next steps with owners and due dates.
3) Include 3–5 key risks or open questions.
Analysis workflow:
1) Identify decisions, blockers, and commitments.
2) Compress into an outcome-first summary tailored to the audience.
3) Derive next steps with clear verbs and acceptance criteria.
4) Flag missing information as questions.
Required output format:
- Executive Summary (120–180 words).
- Top Next Steps (bulleted with Owner, Due Date, Acceptance Criteria).
- Risks & Open Questions.
Quality controls:
- No more than 10 next steps.
- Each step must be testable (acceptance criteria included).
- Use names/roles exactly as in the notes.
Verification checklist:
- Does the summary capture decisions and deadlines?
- Are next steps unambiguous and time-bound?
Final instruction: Produce the sections above only. End with a short note: “Reply with changes or approvals.”
Expected Outcome
Executive Summary: The team agreed to ship MVP checkout with coupon support and to delay advanced analytics to Sprint 3. Legal review is required before promo launch. Growth will run a homepage CTA A/B test. Risks include legal turnaround time and dev capacity on billing. Top Next Steps: - Alex (Growth): Launch CTA A/B test by 2026-09-02; AC: two variants live, 95% significance. - Priya (Legal): Approve ToS promo language by 2026-09-01; AC: signed-off doc. Risks & Open Questions: - Risk: Billing capacity tight; Q: Who can cover Stripe upgrade this week?
Implementation Journey
Summarize in Claude
Open Claude. Paste the raw notes and run the prompt. Expect an executive summary plus 5–10 next steps with owners and due dates.
6 minCheck details in your doc
Paste the output into your team’s running doc in Notion or Google Docs. Verify names, dates, and acceptance criteria. Adjust due dates to match your sprint calendar.
6 minSend to stakeholders
Post the Summary and Next Steps in Slack or email. Ask owners to acknowledge within 24 hours and flag blockers. Track confirmations in your project sheet.
8 min
