50 Prompt Templates for Everyday Work: Email, Reports, Meetings and Analysis

Write a reply to the customer email below. The problem: [what went wrong]. What we will do: [fix, refund or next step]. What we cannot offer: [limit]. Calm and direct, no excuses, under 150 words, ending with one clear next step.
"""
[paste email]
"""

Write a short follow-up to [name] about [topic]. I wrote on [date] asking for [request]. Restate the ask in one sentence, make it easy to answer yes or no, and offer [alternative]. Friendly, under 80 words.

Write an email declining [request] from [person, role]. Reason: [real reason]. What I can offer instead: [alternative or nothing]. Make the no clear in the first sentence. Warm, under 120 words.

Write an email to [person] asking to move [deliverable] from [date] to [new date]. Reason: [reason]. Done so far: [progress]. Offer what they can have by the original date. Under 120 words.

Write an email telling [audience] that [what changes] on [date]. Put the change and date in the first line, explain why in two sentences, say what they need to do, and name a contact: [contact]. Plain language, under 180 words.

Write an email introducing [person A, role, company] to [person B, role, company]. Why they should talk: [reason]. Suggest one concrete next step. Under 100 words.

Summarize the email thread below for someone who was not on it: the decision or open question in one sentence, who wants what, deadlines, and what is expected from [me or my team]. Bullets, under 150 words.
"""
[paste thread]
"""

Turn my notes into an email to [recipient, role] whose goal is [goal]. Keep every fact and number exactly as written, fix the order and add a subject line. Under [N] words.
"""
[paste notes]
"""

Rewrite my email to half its length. Keep the request, the deadline and all numbers, and move the ask to the first paragraph. Then list what you removed.
"""
[paste email]
"""

Write an email escalating [problem] to [manager or team]: what happened, the impact so far ([numbers]), what I have tried, and the decision I need by [date]. Factual, no blame, under 200 words.

Draft an agenda for a [length]-minute meeting with [attendees and roles]. Goal: [decision or outcome]. Put the decision first, and give each item a time, an owner and anything to read beforehand.

Summarize the document below as a one-page pre-read for [meeting]: the question the meeting must answer, the three facts that matter most, the options, and open risks. Bullets.
"""
[paste document]
"""

Turn this transcript into minutes with four sections: Decisions, Action items (owner, task, due date), Open questions, Numbers mentioned. Use only the transcript, and write "not stated" where an owner or date is missing.
"""
[paste transcript]
"""

List every action item in the notes below as a table: Task, Owner, Due date, Depends on. Put tasks without an owner in a separate list called "Needs an owner".
"""
[paste notes]
"""

Write a follow-up email to [attendees] after our meeting on [topic]: decisions, each action with owner and date, and the next check-in date. Under 150 words, based only on these notes:
"""
[paste notes]
"""

I have a one-to-one with [person, role]. Context: [projects, concerns, recent wins]. Suggest 8 open questions that help me understand [workload, career plans or blockers]. No yes-or-no questions.

Turn these notes into a stand-up update of three lines: Done, Doing today, Blocked by. Each line under 20 words; name people only where I need something from them.
"""
[paste notes]
"""

I need to talk to [person, role] about [issue]. Facts: [examples with dates]. Outcome I want: [outcome]. Write a 3-sentence opening, three questions to understand their side, and two replies if they disagree. Respectful and direct.

Write a weekly status report on [project] for [audience] with four sections: Status (on track, at risk or off track, and why), Done this week, Next week, Risks and help needed. Use only my notes:
"""
[paste notes]
"""

Summarize the document below for [audience] who has two minutes: the recommendation first, then three supporting facts, the cost or risk, and the decision needed. Maximum 200 words.
"""
[paste document]
"""

Outline a proposal for [idea] to [decision-maker]: problem, solution, cost and resources, expected result and how we measure it, risks, timeline. Under each heading, list the questions I must answer and the data I need.

Write a one-page brief on [project] that a new team member can read in five minutes: goal, audience, in and out of scope, deadline, owner, success measure, and links to [sources]. Headings and short bullets.

Rewrite the text below for [new audience]. Keep every fact and number, replace jargon with plain words, explain any term that must stay, and keep roughly the same length.
"""
[paste text]
"""

Compare version A and version B. List every change in meaning, not wording, as a table: Section, Version A, Version B, Why it matters. Ignore formatting and typo fixes.
Version A: """[paste]"""
Version B: """[paste]"""

Turn this report into an outline for [number] slides for [audience]. For each slide: a title that states the point as a full sentence, three bullets, and the chart or table to show.
"""
[paste report]
"""

Write the 8 questions employees are most likely to ask about the policy below, with answers taken from the policy. If the policy does not answer a question, say so instead of guessing.
"""
[paste policy]
"""

Proofread the document below without rewriting it. Return a table of location, problem and fix. Check spelling, grammar, inconsistent terms, numbers that contradict each other, and names or dates that differ between sections.
"""
[paste document]
"""

Before any analysis, describe the attached file: rows and columns, what each column contains, blanks, duplicates and odd values. Then suggest 5 questions this data can answer. Do not invent columns.

Find the 3 most important trends in the table below, with the exact numbers that show them. Use only this data and say if something cannot be calculated. Give two possible explanations to check for each trend.
"""
[paste table]
"""

Explain this spreadsheet formula step by step in plain English, then show what it returns for an example row. Formula: [formula]. The referenced columns contain: [description].

Write a [Excel or Google Sheets] formula that [goal]. Column [A] holds [contents], column [B] holds [contents], headers in row 1. Explain how it works and how it handles blanks and errors.

Compare [options] for [decision] with these weighted criteria: [criterion: weight, ...]. Score each option 1 to 5 per criterion, justify each score in one line from the facts below, and show weighted totals.
Facts: [facts]

Group the survey answers below into themes. For each: a short name, how many answers mention it and two direct quotes. Put the rest under "Other" and show the total count.
"""
[paste answers]
"""

Problem: [what went wrong, when, how often]. Known facts: [facts]. Run a 5 whys analysis. Mark each answer "known" or "assumption to verify", and end with the checks that would confirm the root cause.

Write commentary on the KPI table below for [audience]. For each KPI: change against last month in percent and absolute terms, one likely reason from my notes, and a flag if it moved more than [threshold].
Notes: [notes]
"""
[paste table]
"""

Recalculate this step by step and show your working. Tell me whether my result is right, and if not, point to the step where it goes wrong.
Calculation: [paste calculation]

Break [project] into tasks for [N] people with a deadline of [date]. For each task: description, hours, dependencies and a suggested owner role. Group them into weekly milestones and mark the critical path.

Sort my to-do list into four groups by impact and effort, with one line per task explaining why. My main goal this [week or month] is [goal].
"""
[paste list]
"""

Imagine it is [date] and [project] has failed. Based on this plan, give the 10 likeliest reasons, rate each for likelihood and impact, and add one early warning sign and one prevention step.
Plan: [paste plan]

Write a decision memo on [decision] for [decision-maker]. For each option ([options]): cost, benefits, risks, and what we would need to believe for it to win. End with my recommendation, [option], in two sentences.

Turn this goal into one objective and three measurable key results for [team] in [quarter]: [goal]. Baseline: [numbers]. Each key result needs a number and a measurement method. Flag any that depend on other teams.

Plan my week. Fixed meetings: [list with times]. Tasks with estimates and deadlines: [list]. I focus best in the [morning or afternoon]. Give a day-by-day plan with 90-minute focus blocks and a daily buffer, and tell me what will not fit.

Write a [Slack or Teams] message announcing [news] to [team]. News in the first line, then why it matters, what changes for them and who to ask. Under 100 words, friendly, no corporate phrases.

Turn my description into a process document: purpose, who does it, tools, numbered steps, what "done" looks like and common mistakes. Ask me about unclear steps instead of filling gaps.
"""
[paste description]
"""

Write a job post for a [role] at [company], [location or remote]. Must-haves: [list]. Nice to have: [list]. Salary range: [range]. First 90 days: [list]. Plain language, under 350 words.

Help me give [colleague] feedback on [behavior]. Example: [situation, what they did, the result]. Use situation, behavior, impact, then one question that invites their view. Specific and kind, under 120 words.

Write a LinkedIn post about [milestone] for [audience]. Include this detail: [number or fact]. Open with a statement, not a question, end with [call to action], and stay under 150 words.

A prospect said: "[objection]". Our product: [one line]. Facts I can use: [pricing, results, features]. Write three replies under 60 words each: one that asks a question, one that answers with a fact, one that proposes a next step.

Summarize this feedback for the product team in three groups: problems, feature requests and praise. Order items by frequency with counts and one quote each. Do not merge different problems.
"""
[paste feedback]
"""

Write a reusable support reply for customers who ask [question]. Correct answer: [answer and steps]. Give the steps as a numbered list, add [help article link], and say what to do if the steps fail. Under 120 words.