ChatGPT Prompts for Meeting Notes

Turn my campaign notes and metrics into a clean, shareable campaign recap.

Structure:
1. Campaign name, dates, and goal
2. Key results — bullet list, numbers first (include what hit vs. missed target)
3. What drove performance (2–3 factors, evidence-based)
4. What underperformed and the likely reason
5. Recommendations for the next campaign (3 bullets, specific and actionable)

Do not invent numbers. If a metric is missing, mark it as "not tracked."

Campaign notes and metrics: [PASTE]

Turn my rough call notes into a clean recap email to the prospect. Structure:
- One-line thank you.
- "What I heard" — 3 bullets restating their priorities (shows I listened).
- "Next steps" — who does what, by when.
- A clear ask to confirm the next meeting.

Keep it skimmable. Don't invent anything not in my notes.

My notes: [PASTE NOTES]

Convert my raw call notes into a CRM-ready summary with these exact fields:
- Stage (one of: Discovery / Evaluation / Proposal / Negotiation)
- Pain points (bullets)
- Budget signal (what they actually said about money, or "none mentioned")
- Decision makers
- Objections / risks
- Next action + date

Only use what's in the notes. If a field is empty, write "none mentioned."

Notes: [PASTE NOTES]

Help me prep a product demo. Based on what I know about the prospect, tell me which features to lead with and which to skip.

Prospect: [ROLE] at [COMPANY TYPE]
Their main pains (from discovery): [PAINS]
Our features: [LIST FEATURES]

Give me: a 3-beat demo flow mapped to their pains, the one "wow" moment to land, and two questions to ask mid-demo to keep it a conversation.

Analyze my notes from a closed deal and produce a win/loss summary:
- Outcome: Won / Lost
- Primary reason (one sentence)
- Contributing factors (bullets)
- What the competitor did, if mentioned
- One thing I'd do differently next time

Be honest, not flattering. Only use what's in the notes.

Deal notes: [PASTE NOTES]

Below are raw notes from a team meeting. Turn them into a clean summary for people who weren't there.

Format:
1. **TL;DR** — 2 sentences.
2. **Decisions made** — bullet list.
3. **Action items** — a table: Task | Owner | Due date. If an owner or date wasn't stated, write "unassigned" — do not invent one.
4. **Open questions** — anything left unresolved.

Keep it factual. Don't add advice. Here are the notes:
[PASTE NOTES OR TRANSCRIPT]

Help me build a 1:1 agenda for a meeting with [DIRECT REPORT NAME], who is a [ROLE].

Context about this person:
- Current project or focus: [PROJECT]
- Any recent wins or concerns I want to acknowledge: [NOTES]
- Open items from last 1:1: [CARRYOVER ITEMS, or "none"]

Generate a 30-minute agenda that:
1. Opens with their update, not mine (2–3 prompt questions, not yes/no).
2. Covers the carryover items.
3. Includes one development or career question.
4. Ends with clear next steps we both own.

Write a project kickoff brief for [PROJECT NAME]. This document will be shared with the team before the kickoff meeting and should answer every "why are we doing this" question before it gets asked.

Sections:
1. **Problem we're solving** — one paragraph, no jargon.
2. **Goal and success metric** — what does winning look like, with a number if possible.
3. **Scope** — what's in and explicitly what's out.
4. **Roles** — who owns what (use "unassigned" if a role isn't filled yet).
5. **Timeline** — key milestones and the ship date.
6. **Risks** — top 2, one sentence each.

Details: [PASTE PROJECT DETAILS, TEAM, DATES, CONSTRAINTS]

Synthesize interviewer notes from a candidate debrief into a structured hiring summary.

Format:
1. **Candidate**: [NAME] for [ROLE].
2. **Interviewers and their signals**: a table — Interviewer | Lean | Top strength | Top concern.
3. **Consensus strengths** — what all or most interviewers agreed on.
4. **Consensus concerns** — what came up more than once.
5. **Recommendation** — Hire / No hire / Strong hire, with a one-sentence reason.
6. **Open questions** — anything unresolved that a reference check should address.

Only use what's in the notes. If an interviewer didn't submit notes, mark them "no submission."

Notes: [PASTE INTERVIEWER NOTES]

Summarize the following standup notes into a brief status update I can share with stakeholders who didn't attend.

Format:
1. **Overall status** — one word (Green / Yellow / Red) and one sentence explaining it.
2. **Progress** — 2–4 bullets of concrete things completed or moved forward.
3. **Blockers** — each blocker on its own line: Blocker | Who owns resolution | By when. If none, write "None."
4. **Watch items** — risks that aren't blockers yet but need monitoring.

Factual only. Don't restate what people are working on — only what moved.

Standup notes: [PASTE STANDUP NOTES]

Convert my raw interview notes into a structured debrief for sharing with the hiring team.

Candidate: [NAME]
Role: [JOB TITLE]
Interviewer: [YOUR NAME]
Notes: [PASTE RAW NOTES]

Output format:
- Headline: one sentence on overall impression.
- Strengths observed (bullets)
- Concerns or gaps (bullets)
- Standout moment: one specific exchange worth sharing
- Recommendation: Advance / Hold / Pass — with one line of reasoning

Only use what's in my notes. Don't soften concerns to be polite.

Build an interview scorecard from my notes for [CANDIDATE NAME], interviewed for [JOB TITLE].

Evaluation criteria for this role: [LIST 4–6 CRITERIA — e.g., technical depth, communication, leadership, domain knowledge].

My notes: [PASTE NOTES]

For each criterion:
- Rating: 1 (well below bar) to 4 (clearly above bar)
- One sentence of evidence from the interview that supports the rating

End with: overall rating (average) and a hire / no-hire signal.
Only rate what the interview actually covered. Mark criteria as "not assessed" if they weren't.

Help me prepare for a parent-teacher conference for [STUDENT FIRST NAME], grade [GRADE].

Here are my raw notes and observations:
- Academic strengths: [NOTES]
- Academic areas to improve: [NOTES]
- Social or behavioral notes: [NOTES, or "none"]
- Any context I should be sensitive to: [FAMILY SITUATION / IEP / ELL STATUS, or "none known"]

Organize these into:
1. Two or three specific strengths to open with (evidence-based, not generic).
2. One or two focused areas for growth with a concrete example each.
3. Two questions to ask the parent (to learn what they're seeing at home).
4. One agreed next step I can propose.

Keep it all on one page I can glance at during the meeting.

I just finished a parent-teacher conference. Write a brief follow-up email to [PARENT NAME] that recaps what we discussed.

My conference notes: [PASTE ROUGH NOTES]

Structure the email as:
- Two-sentence thank-you and tone-setter.
- "What we talked about" — 3 to 4 brief bullets (strengths and concerns).
- "What we agreed to" — one or two specific next steps with who is responsible.
- A warm, open closing that invites them to reach out.

Do not add anything not in my notes. Under 180 words.

Summarize the staff meeting notes below into a clean, actionable recap.

Format:
- Decisions made: (bullet list of anything that was resolved or approved)
- Action items: (bullet list in format — [WHO]: [WHAT] by [DATE or "TBD"])
- Open questions: (anything raised but not resolved — with owner if assigned)
- Next meeting: (date/time if mentioned)

Do not add anything not in the notes. Keep it to one page.

Raw notes: [PASTE MEETING NOTES]

Help my group plan and divide a class project. Turn the brief below into a clear work plan.

Project brief: [PASTE ASSIGNMENT DESCRIPTION]
Due date: [DATE]
Number of group members: [NUMBER]
Any known constraints: [MEMBER AVAILABILITY / TOOLS / RESTRICTIONS]

Produce:
1. A task breakdown (every deliverable the assignment requires)
2. Suggested owner per task (use "Member A, B, C…" as placeholders)
3. A week-by-week timeline working backward from the due date
4. One integration checkpoint where the full group reviews progress together