Most people use ChatGPT for work the wrong way: type a vague request, get a generic draft, spend ten minutes editing, wonder why they bothered. The problem isn't the tool — it's the prompt.
These 20 copy-paste prompts are built around the 4-element structure (Role + Context + Task + Format) that gets usable output on the first try. Organized by the tasks you actually do: email, meeting notes, reports, planning, and data analysis.
In the Harvard Business School study run with BCG consultants (Dell'Acqua et al., Navigating the Jagged Technological Frontier, 2023), participants using GPT-4 completed tasks 25.1% faster and produced work rated about 40% higher in quality. Worth reading the paper for the caveat as much as the headline: on tasks outside the model's competence, the same assistance made results worse.
Why Most Work Prompts Don't Deliver
Vague prompts produce vague output. A structured prompt gives ChatGPT four things to anchor on: the role it should play, the context of your situation, the specific task, and the format you need.
Vague: "Write a follow-up email to a client."
Result: generic template, wrong tone, missing details — you rewrite it anyway.
Structured:
(Role) You are a B2B account manager.
(Context) I met with Sarah at Acme Corp last Tuesday about renewing their $40k/yr contract. She asked for a pricing breakdown by Friday.
(Task) Write a follow-up email confirming the meeting and setting a deadline.
(Format) Professional but warm tone, 3 short paragraphs, subject line included.
Result: ready-to-send draft in the right voice, with the right details.
Email Prompts
Prompt 1 — Follow-Up Email After a Meeting
(Role) You are a professional account manager.
(Context) I had a meeting with [Name] at [Company] on [date] about [topic]. The key decisions made were [decision 1] and [decision 2]. They asked for [specific deliverable] by [deadline].
(Task) Write a follow-up email summarizing the meeting, confirming next steps, and setting a clear deadline.
(Format) Professional but warm tone, subject line included, 3 short paragraphs, no filler phrases like "I hope this email finds you well."
Prompt 2 — Cold Outreach Email
(Role) You are a B2B sales professional.
(Context) I'm reaching out to [Name], [Title] at [Company], who fits our ICP: [1-sentence description of why they're a fit]. Our product [Product] helps [value proposition in one line]. I have no prior relationship with this contact.
(Task) Write a cold outreach email that leads with a relevant insight about their company or industry, then makes a single low-friction ask (15-minute call).
(Format) Subject line + 4 sentences max, no hyperbole, no buzzwords, conversational tone.
Prompt 3 — Escalation Email to Management
(Role) You are a project manager escalating a risk to senior leadership.
(Context) Project: [Project name]. Issue: [describe the problem in 1-2 sentences]. Root cause (if known): [root cause]. Impact: [what breaks if this isn't resolved]. Deadline for decision: [date].
(Task) Write a concise escalation email that clearly states the problem, impact, options considered, and the specific decision or resource needed from leadership.
(Format) Subject line with "ACTION REQUIRED," bullet points for options, under 200 words, no blame language.
Prompt 4 — Polite Decline
(Role) You are a professional declining a request while preserving the relationship.
(Context) I need to decline [type of request] from [Name/Company]. Reason I'm declining (internal, don't state directly): [actual reason]. I want to keep the door open for [future opportunity if any].
(Task) Write a polite, clear decline email that doesn't over-explain, doesn't apologize excessively, and leaves a positive impression.
(Format) Subject line, 2-3 sentences, warm but direct tone, no filler.
Meeting Notes and Agendas
Prompt 5 — Meeting Agenda Builder
(Role) You are a facilitator preparing a meeting agenda.
(Context) Meeting: [meeting name], [date], [duration], attendees: [list roles, not names]. Goals for this meeting: [goal 1], [goal 2]. Topics to cover: [topic 1], [topic 2], [topic 3]. Known constraints: [e.g., one attendee needs to leave at the 45-min mark].
(Task) Create a timed agenda that allocates minutes to each topic, reserves time for decisions and parking lot items, and includes a clear objective for each slot.
(Format) Table format with columns: Time | Topic | Owner | Objective. End with a 5-min wrap-up slot.
Prompt 6 — Action-Item Extractor
(Role) You are a project coordinator reviewing meeting notes.
(Context) Below are my raw notes from today's meeting. [PASTE YOUR NOTES HERE]
(Task) Extract every action item, decision made, and open question. For each action item, identify who is responsible and what the deadline is (mark "TBD" if not mentioned).
(Format) Three sections: Action Items (owner | task | deadline), Decisions Made (bullet list), Open Questions (bullet list). Keep each line under 20 words.
Prompt 7 — Meeting Summary Email
(Role) You are a team lead sending a post-meeting summary.
(Context) Meeting: [name], attendees: [roles]. Raw notes: [paste notes]. Key decisions: [list]. Next meeting: [date if known].
(Task) Write a summary email to send to all attendees that recaps what was discussed, confirms decisions, and lists action items with owners.
(Format) Subject line, 3 sections (Discussion Recap / Decisions / Action Items), bullets under each, under 250 words total, professional tone.
Reports, Summaries, and Briefs
Prompt 8 — Executive Summary
(Role) You are a senior analyst writing for a C-suite audience.
(Context) Below is raw data / a long report / meeting notes from [project or topic]. [PASTE CONTENT HERE]. The audience (CEO/CFO/board) has 2 minutes to read this and needs to make a decision about [decision to be made].
(Task) Write an executive summary that leads with the bottom line, then supports it with 3-5 key data points or findings. End with a clear recommendation or required action.
(Format) 5 bullets max, each under 25 words. No jargon. Bold the bottom-line sentence.
Prompt 9 — Weekly Status Report
(Role) You are a project manager writing a weekly update.
(Context) Project: [name]. This week's accomplishments: [list]. Blockers or risks: [list]. Next week's priorities: [list]. Overall status: [on track / at risk / blocked].
(Task) Write a concise weekly status report that a stakeholder can read in 60 seconds.
(Format) Three sections with bold headers: This Week / Blockers & Risks / Next Week. Status badge at the top: [GREEN / YELLOW / RED]. Under 150 words total.
Prompt 10 — Project Brief
(Role) You are a project manager writing a kickoff brief.
(Context) Project: [name]. Goal: [one-sentence goal]. Stakeholders: [list roles]. Timeline: [start] to [end]. Budget: [$X or TBD]. Constraints: [list any known constraints]. Out of scope: [list explicitly].
(Task) Write a project brief that aligns the team on goals, scope, timeline, and success metrics before work begins.
(Format) Sections: Overview (2 sentences) / Objectives (3 bullets) / Scope (in/out table) / Timeline (milestones list) / Success Metrics (2-3 measurable outcomes). One page max.
Prompt 11 — Lessons-Learned Document
(Role) You are a project lead conducting a post-mortem.
(Context) Project: [name], duration: [dates]. What went well: [list]. What didn't go well: [list]. Root causes identified: [list]. Team size: [N] people across [departments].
(Task) Write a lessons-learned document that is honest, specific, and actionable — not a feel-good recap. Focus on systemic issues, not individual blame.
(Format) Three sections: What Worked (bullets with why) / What Didn't Work (bullets with root cause) / Recommendations for Next Time (numbered list, specific and actionable). Under 400 words.
Planning, Analysis, and Problem-Solving
Prompt 12 — Project Plan
(Role) You are a project manager creating an initial project plan.
(Context) Project: [name]. Goal: [one sentence]. Team: [roles available]. Timeline: [N weeks]. Key constraints: [budget / dependencies / fixed deadlines].
(Task) Create a high-level project plan with phases, key milestones, and task dependencies. Flag any timeline risks.
(Format) Phase table (Phase | Key Tasks | Owner Role | Duration | Depends On), followed by a Risks & Assumptions bullet list.
Prompt 13 — Prioritization Framework
(Role) You are a strategic advisor helping prioritize a workload.
(Context) I have [N] tasks or projects competing for attention this [week/quarter]. Here's the list: [paste list]. My main constraint is [time / budget / headcount]. My team's top goal this quarter is [goal].
(Task) Apply an impact vs. effort prioritization framework to this list. Rank each item and briefly explain the reasoning. Flag any item that should be dropped or delegated.
(Format) Ranked table: Rank | Task | Impact (H/M/L) | Effort (H/M/L) | Recommendation (Do / Delegate / Drop / Defer). One-sentence rationale per item.
Prompt 14 — Data Trend Summary
(Role) You are a data analyst translating numbers into plain English for a non-technical audience.
(Context) Here is the data: [paste table, CSV snippet, or bullet list of key metrics]. The audience is [role] who will use this to decide [decision].
(Task) Summarize the key trends in plain language. Identify the 2-3 most significant patterns, flag any anomalies, and state what the data does and does not tell us.
(Format) 3 sections: Key Trends (3 bullets) / Anomalies to Investigate (1-2 bullets) / What the Data Doesn't Tell Us (1-2 bullets). No statistics jargon. Under 200 words.
Prompt 15 — Decision Memo
(Role) You are a senior professional writing a recommendation memo.
(Context) Decision to be made: [describe]. Options considered: [Option A], [Option B], [Option C if any]. My recommendation: [Option X] because [brief reason]. Key stakeholders: [roles]. Known objections I expect: [list 1-2].
(Task) Write a one-page decision memo that makes a clear recommendation, shows the options considered, and addresses expected objections.
(Format) Sections: Recommendation (1 bold sentence) / Background (2 sentences) / Options Compared (table) / Recommendation Rationale (3 bullets) / Anticipated Objections & Responses (2-3 bullets).
Prompt 16 — Problem Framing
(Role) You are a strategic advisor helping a team diagnose a problem before jumping to solutions.
(Context) The problem we're trying to solve: [describe the symptom or situation]. What we've already tried: [list]. Constraints on solutions: [budget / timeline / team size].
(Task) Help me reframe this problem from multiple angles. Surface 3 different ways of defining the root cause.
(Format) Three problem framings (label each), a brief explanation of what each implies about the solution, and a recommendation for which framing to use and why.
Prompt 17 — One-on-One Prep
(Role) You are a manager preparing for a 1:1 with a direct report.
(Context) Employee role: [role]. Current projects: [list]. Recent wins: [list]. Areas where they seem stuck or disengaged (if any): [describe]. My goals for this 1:1: [goal 1, goal 2].
(Task) Generate a structured 1:1 agenda with questions that open a genuine conversation — not a status check. Include one development question and one question that surfaces blockers they might not volunteer.
(Format) Agenda table (Time | Topic | Opening Question), 5-6 rows, 30-minute meeting assumed.
These 17 cover general office work. Two adjacent sets go deeper where the output is a file rather than prose: prompts for Excel and prompts for data analysis.
FAQ
Can I use these prompts with Claude or Gemini instead of ChatGPT?
Yes. The 4-element structure (Role/Context/Task/Format) works with any major LLM. The prompt text works as-is.
What if the output is still too generic?
Add more context or narrow the task. The most common cause of generic output is missing audience information or an underspecified task verb.
Should I use these prompts in a chat window or the system prompt?
For one-off tasks, the chat window is fine. For recurring use cases (e.g., you always write the same type of status report), putting the role + format instructions in the system prompt (where supported) means you only need to paste the context and task each time.
How do I build a personal prompt library?
Save the base prompts in a plain text file or Notion database. Keep the bracket placeholders. Update only the context and task for each new use.
Originally published at my-blog.org.
Top comments (0)