Get the management writing done in minutes — status reports, 1:1 agendas, decision memos, and clean meeting notes — so you can spend your time on the people, not the paperwork.
Management generates a steady stream of documents nobody enjoys writing: the weekly update to your boss, the memo that forces a decision, the meeting notes that turn talk into owned action items. These prompts produce them fast, and the meeting and standup prompts include a hard rule — never invent an owner or a due date — so the summary is safe to share.
The harder prompts help with people, not paperwork: prepping a difficult feedback conversation by role-playing it first, or drafting a balanced performance review from scattered notes. Use them to organize your thinking; the judgment, and the conversation itself, stay yours.
12 prompts · free to copy · example output on each
ChatGPTGeminiClaude
Turn messy meeting notes into clear action items
Convert raw notes or a transcript into decisions, owners, and next steps.
The prompt
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]
Example output
**TL;DR** — The team approved the Q3 pricing test and pushed the mobile redesign to August. Two action items are unassigned.
**Decisions made**
- Run the pricing A/B test on the Pro plan starting July 1.
- Delay the mobile redesign to August to avoid the holiday code freeze.
**Action items**
| Task | Owner | Due date |
|---|---|---|
| Set up pricing test in billing | Priya | Jun 27 |
| Draft August launch timeline | unassigned | unassigned |
| Tell support about the price change | Marco | Jun 30 |
**Open questions**
- Who signs off on the final August date?
TipThe "do not invent owners or dates" rule is what makes this trustworthy — AI otherwise fills gaps with plausible-but-wrong names. Paste a Zoom/Meet transcript directly for best results.
ChatGPTGeminiClaude
Write a weekly status report for your boss
Turn the week's work into a tight update leadership actually reads.
The prompt
You are a senior manager writing a weekly status report. Turn my bullet-point notes into a clean update my director will read in under two minutes.
Format:
1. **This week** — 3–5 bullets of concrete progress (metrics or deliverables, not effort).
2. **Next week** — 2–3 priorities with owners.
3. **Blockers** — anything I need from leadership. If none, write "None."
Rules: plain language, no filler phrases like "we continued to work on," numbers wherever I have them, under 200 words total.
My notes: [PASTE YOUR WEEK'S NOTES]
Example output
**This week**
- Shipped the onboarding email sequence; open rate at 41% vs. 29% baseline.
- Closed two enterprise pilots — Meridian Health and Solis Finance (combined ARR: $84,000).
- Reduced P1 ticket backlog from 34 to 11 by reallocating two engineers from the feature queue.
- Completed Q3 headcount plan; submitted to HR on Thursday.
**Next week**
- Priya: finalize security review for Meridian (due Thu).
- Tom: start sprint 14 with new backlog priority order.
- Me: present Q3 plan to leadership on Wednesday.
**Blockers**
- Need sign-off on the contractor extension for Tom's team by Monday — delays sprint 14 otherwise.
TipForce yourself to write numbers into the notes before pasting — "shipped onboarding emails" is useless; "open rate 41% vs. 29% baseline" is what leadership remembers. The AI can't invent metrics you didn't give it.
ChatGPTGeminiClaude
Build a 1:1 meeting agenda
Prep a focused agenda for a one-on-one with a direct report.
The prompt
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.
Example output
**1:1 — Priya / Jun 17 — 30 min**
**Her update (10 min)**
- How is the Meridian security review going — any surprises?
- What's felt most and least useful to you this week?
- Anything slowing you down I don't know about?
**Carryover (8 min)**
- Decision: timeline for looping in Legal on the data agreement.
- Status: conference talk proposal — did she submit?
**Development (7 min)**
- You've been handling more client-facing work lately — is that something you want more of, or is it pulling you off the work you'd rather do?
**Next steps (5 min)**
- Me: get Legal intro by Wed.
- Priya: send talk proposal link by EOD Fri.
TipOpen with their update, not yours — it signals you're there to unblock them, not broadcast at them, and you'll surface problems that never make it into a status email. Carry the open items from last time in a persistent doc so nothing drops.
ChatGPTGeminiClaude
Draft a performance review from your notes
Turn scattered feedback notes into a balanced, specific review.
The prompt
You are an experienced manager writing a formal performance review. Turn my raw notes into a draft review for [EMPLOYEE NAME], a [ROLE], covering the period [DATES].
Structure:
1. **Overall summary** — 2 sentences.
2. **Strengths** — 2–3 specific examples from the notes (quote real outcomes, not personality traits).
3. **Areas to develop** — 1–2 honest, specific gaps with a suggested action, not vague criticism.
4. **Rating recommendation** — [RATING SCALE, e.g. Exceeds / Meets / Below].
Rules: use specific evidence from my notes. If a section has no evidence, write "no data provided" — don't pad it. Avoid empty praise. Neutral professional tone.
My notes: [PASTE NOTES]
Example output
**Overall summary**
Priya had a strong half-year marked by two significant enterprise closes and consistent technical quality. Her communication to stakeholders improved noticeably after Q1; cross-functional friction dropped as a result.
**Strengths**
- Closed Meridian Health and Solis Finance ($84,000 combined ARR) with minimal manager involvement after the first call.
- Delivered the security review framework three days early; Legal called it "the clearest submission we've seen."
**Areas to develop**
- Tends to absorb scope quietly rather than flagging tradeoffs early — missed the sprint 12 deadline was partly caused by this. Agree on a "flag or negotiate" norm before sprint planning each cycle.
**Rating recommendation**
Exceeds expectations.
TipFeed in quotes and numbers from real events, not adjectives — "delivered security review early, Legal praised it" forces the model to write evidence-based copy instead of filler like "demonstrates strong ownership." The difference is what makes reviews defensible in an HR escalation.
ChatGPTGeminiClaude
Delegate a task clearly over email
Hand off a task with context, expectations, and a deadline.
The prompt
Write a delegation email assigning a task to [PERSON NAME]. The email should not feel like a dump — it should give them what they need to succeed.
Include:
- What the task is and why it matters (one sentence of context).
- What "done" looks like (specific deliverable and format).
- The deadline and any key constraints.
- Who to loop in and who NOT to loop in.
- An explicit invitation to flag problems early.
Under 150 words. Plain language. No "per my last email."
Task details: [DESCRIBE THE TASK, DEADLINE, CONSTRAINTS]
Example output
Subject: Meridian security review — over to you
Hi Priya,
Meridian asked for a security questionnaire before they sign — this is the last gate before the contract. I'd like you to own the response.
Deliverable: completed questionnaire + a one-page summary of anything we can't answer today. Google Doc, shared with me and Legal.
Deadline: draft by Tue Jun 24, final by Thu Jun 26.
Loop in: Tom for the infrastructure questions (sections 3–4). Do not loop in Sales yet — I'll brief them after Legal reviews.
If you hit something that looks like a real gap, flag it to me before writing around it — better to surface it early than have Legal catch it.
Thanks,
[Your name]
TipSpelling out "what done looks like" is the single biggest delegation failure point — without a concrete deliverable format, you get back whatever the person assumed you wanted. The "flag problems early" line prevents the quiet struggle that kills deadlines.
ChatGPTGeminiClaude
Write a project kickoff brief
Align a team on goals, scope, roles, and timeline before work starts.
The prompt
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]
Example output
**Project: Customer Onboarding Revamp**
**Problem we're solving**
New customers take 34 days on average to complete onboarding, against a 14-day target. Half of support tickets in the first 90 days trace back to setup confusion. This is causing churn we can prevent.
**Goal and success metric**
Reduce median time-to-first-value from 34 to 16 days by August 31. Secondary: cut setup-related support tickets by 30%.
**Scope**
In: email sequence, in-app checklist, docs rewrite for steps 1–5.
Out: enterprise onboarding (separate project), SSO configuration.
**Roles**
Project lead: Priya | Docs: Tom | Design: unassigned | Eng: Diego
**Timeline**
Jun 23 — kickoff | Jul 14 — design review | Aug 4 — soft launch | Aug 31 — full rollout
**Risks**
- Design role unfilled; delays design review if not hired by Jul 1.
- Docs rewrite depends on Product sign-off; needs scheduling this week.
TipThe "explicitly out of scope" line prevents the brief from becoming a wish list — stating what you won't do is as important as stating what you will, and it stops scope creep before it starts.
ChatGPTGeminiClaude
Summarize options into a decision memo
Lay out choices, trade-offs, and a recommendation for a fast decision.
The prompt
Write a decision memo for [DECISION MAKER / AUDIENCE] on the question: [THE DECISION TO BE MADE].
Format:
1. **Context** — why this decision is needed now (2–3 sentences).
2. **Options** — a table: Option | Pros | Cons | Cost/Effort.
3. **Recommendation** — which option you recommend and the one-sentence reason.
4. **What we need from you** — the specific ask (approval, a call, a sign-off).
Be direct. State a recommendation even if the data is imperfect. Under 300 words.
Details: [PASTE OPTIONS, TRADE-OFFS, YOUR PREFERRED CHOICE AND WHY]
Example output
**Decision: Hire vs. Contract for Design Role**
To: [Director] | Date: Jun 17
**Context**
The onboarding project needs a designer by July 1 to hit the Aug 31 ship date. The role has been open for six weeks; the pipeline has two candidates but no offer-ready finalist.
**Options**
| Option | Pros | Cons | Cost |
|---|---|---|---|
| Extend contractor (Lena) | Available now, knows the product | 20% premium, not a long-term fix | $12,000 for 8 weeks |
| Wait for hire | Right long-term | Delays project 3–6 weeks | $0 now, risk of Q3 miss |
| Freelancer via agency | Fast, low overhead | Ramp time, no product context | $8,000–$14,000 |
**Recommendation**
Extend Lena's contract through August. She's already ramped, and missing the August date costs more than the premium.
**What we need from you**
Approval to extend Lena at the current rate through Aug 31. I need this by Monday to give her enough notice.
TipState your recommendation explicitly — "option B" is not a recommendation. Saying "I recommend X because Y" forces you to commit, and it's exactly what decision-makers need to move fast. A memo that hedges everything is a memo that gets no action.
ChatGPTGeminiClaude
Announce a change to your team
Communicate a decision clearly, addressing the "what about me" questions.
The prompt
Write an internal announcement email to my team about [THE CHANGE]. The change has already been decided — this email is to communicate it, not debate it.
The email must:
- State the change clearly in the first sentence.
- Explain the reason in plain language (one short paragraph).
- Address the two most likely "what does this mean for me" questions.
- Say what stays the same.
- Give a specific time for questions (team meeting, open Slack thread, etc.).
Tone: direct, human, not corporate-speak. No "exciting journey." Under 200 words.
Change details: [DESCRIBE THE CHANGE, REASON, IMPACT ON THE TEAM, ANY OPEN QUESTIONS]
Example output
Subject: team structure update — effective July 1
Hi team,
Starting July 1, our team is splitting into two pods: a growth pod (owned by Priya) and a retention pod (owned by Marco). I'm still your overall manager — this doesn't change reporting lines, comp, or your current projects.
Why: our work has grown in two directions that need different rhythms. Splitting now means both areas get real focus instead of sharing a backlog.
What this means for you:
- Your day-to-day lead for sprint planning shifts to your pod lead.
- Nothing changes until July 1 — finish the current sprint as-is.
What stays the same: 1:1s with me, team all-hands, compensation, and career conversations.
I'll have 30 minutes at Friday's all-hands for questions. If you'd rather talk before then, book time on my calendar.
[Your name]
TipAnswer "what changes for me" before anyone has to ask — most team anxiety in change announcements comes from imagining worse outcomes than the reality. Saying explicitly what stays the same is often more reassuring than the announcement itself.
ChatGPTGeminiClaude
Create interview questions for a role
Generate role-specific behavioral questions that predict performance.
The prompt
You are a hiring manager writing an interview guide. Create behavioral interview questions for a [JOB TITLE] role at a [COMPANY TYPE / SIZE].
The role's most important competencies are: [LIST 3–4 KEY COMPETENCIES, e.g. stakeholder communication, technical judgment, execution under ambiguity].
For each competency, write:
- One behavioral question (past-tense, "Tell me about a time...").
- What a strong answer looks like (2–3 signal words or phrases to listen for).
- One follow-up probe.
Avoid questions that can be answered with rehearsed platitudes. No "What's your greatest weakness?"
Example output
**Stakeholder communication**
Q: Tell me about a time you had to deliver bad news to a client or executive who didn't want to hear it. What did you do?
Strong answer signals: gave early warning (not surprise), separated facts from opinions, had a proposed path forward.
Follow-up: What did they say, and how did it end?
**Execution under ambiguity**
Q: Describe a project where the requirements changed significantly mid-way. How did you handle it?
Strong answer signals: re-scoped rather than absorbed scope, renegotiated the deadline, communicated tradeoffs explicitly.
Follow-up: What would you do differently?
**Technical judgment**
Q: Tell me about a technical decision you made that you later regretted. What did you learn?
Strong answer signals: owns the decision rather than blaming constraints, describes what they'd change, shows updated mental model.
Follow-up: Did you change how you make that type of decision now?
TipWrite "what a strong answer sounds like" before you run the interview — interviewers who don't know what they're listening for get captured by confident delivery instead of actual signal. The follow-up probe is where you separate prepared storytellers from people who actually did the thing.
ChatGPTGeminiClaude
Run a structured candidate debrief
Turn interviewer notes into a clear hire / no-hire recommendation.
The prompt
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]
Example output
**Candidate: Jordan Lee — Senior Product Manager**
| Interviewer | Lean | Top strength | Top concern |
|---|---|---|---|
| Priya | Hire | Clear on tradeoffs | Thin on data fluency |
| Tom | No hire | Great communicator | Avoided specifics on past failures |
| Diego | Hire | Strong stakeholder instincts | no submission |
**Consensus strengths**
Stakeholder communication, clear prioritization logic.
**Consensus concerns**
Vague on failures and data-driven decisions — came up in both Priya's and Tom's debrief notes.
**Recommendation**
No hire. Stakeholder skills are real, but two interviewers independently flagged the same gap in analytical depth and self-awareness — too consistent to dismiss.
**Open questions for reference check**
- How does Jordan handle decisions when data is inconclusive?
- How did past managers describe their response to critical feedback?
TipRun this synthesis before the debrief meeting, not in it — when everyone sits down already having read a summary, you spend the meeting resolving real disagreements instead of retelling stories. The open questions for references are often more valuable than the hire/no-hire itself.
ChatGPTGeminiClaude
Summarize a standup into a status update
Condense daily updates into blockers and progress for stakeholders.
The prompt
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]
Example output
**Overall status: Yellow** — on track for the sprint goal but one blocker needs resolution by tomorrow to stay there.
**Progress**
- Diego merged the API rate-limit fix; staging verified clean.
- Priya completed sections 1–2 of the Meridian security questionnaire.
- Tom finished the doc rewrites for onboarding steps 3 and 4.
**Blockers**
| Blocker | Owner | By when |
|---|---|---|
| Legal hasn't reviewed the data agreement; Priya can't complete section 5 | [Manager] to escalate | Jun 18 EOD |
**Watch items**
- QA environment has been flaky — if it goes down again it delays Diego's next PR review.
TipTrain yourself to distinguish progress (something finished or unblocked) from activity (someone working on something) — stakeholders need the first, not the second. The blocker table with an owner and a deadline is the part that actually gets blockers resolved.
ChatGPTGeminiClaude
Prep for a difficult conversation
Plan and role-play a hard feedback conversation before you have it.
The prompt
Help me prepare for a difficult conversation with [PERSON / ROLE] about [ISSUE].
Step 1 — Give me a one-paragraph framing of the issue in neutral, factual language I can open with (no blame, no softening to the point of hiding the point).
Step 2 — List the 2–3 most likely defensive responses they might have, and a calm, specific reply to each.
Step 3 — Draft the one outcome I need from this conversation (a behavior change, a decision, or an agreement).
Step 4 — Role-play as the person. Respond to my opening statement as they might — push back realistically, don't make it easy.
Context: [DESCRIBE THE SITUATION, WHAT'S HAPPENED, WHAT YOU NEED TO CHANGE]
Example output
**Step 1 — Opening framing**
"I want to talk about the last three sprint reviews. In each one, the scope changed after we'd already committed — sprint 11 by two features, sprint 12 by one, sprint 13 by three. I'm not attributing intent; I want to understand what's happening and agree on how we handle scope changes going forward."
**Step 2 — Likely responses and replies**
- "The requests came from leadership, not me." → "I understand — and I need us to agree on a process so that when leadership asks, we have a way to respond that doesn't silently absorb the change."
- "I didn't think they were that significant." → "That's useful to know. Going forward, I'd like us to define what triggers a conversation before we say yes."
**Step 3 — Outcome I need**
Agreement that any mid-sprint scope addition requires a 10-minute trade-off conversation with me before it's accepted.
**Step 4 — Role-play**
"Honestly, I feel like I'm being blamed for trying to be helpful. Leadership asks for things and I'm supposed to just say no?"
TipWriting the opening statement before the conversation is the most underused prep step — most difficult conversations go sideways in the first 30 seconds because the manager led with emotion or hedged so much the other person didn't know what the conversation was about. Read your opening aloud; if it sounds like an accusation or a non-statement, revise before you sit down.
How do I turn meeting notes into action items with ChatGPT?
Paste your raw notes or a transcript into the meeting-notes prompt. It returns a TL;DR, the decisions made, and an action-item table with owners and due dates — marking anything unstated as “unassigned” instead of guessing.
Can ChatGPT write my weekly status report?
Yes. The status-report prompt turns your week’s rough notes into a tight, skimmable update for leadership — progress, blockers, and what’s next — in the format busy execs actually read.
Is it a good idea to use AI for performance reviews?
As a drafting aid, yes — the review prompt turns your own notes into balanced, specific language. But the assessment must be yours: review and rewrite every line, and never paste confidential employee data into a tool that isn’t approved by your company.
How can AI help with a difficult conversation?
The tough-conversation prompt helps you plan and role-play before you talk: it drafts your opening, anticipates reactions, and lets you rehearse responses — so you go in clear and calm rather than scripted.