20 copy-and-paste prompts for clearer emails, more useful reports and better everyday writing.
A blank email can take longer to write than it should. Getting the tone right is another matter. Meeting notes and reports pose the same problem: the information is there, but it isn’t ready to send.
Claude can help with the first draft, or improve something you’ve already written. But asking it to “make this better” leaves too much open to interpretation. Tell it who will read the piece, what matters, and what absolutely must not change, and you’ll usually get something much closer to what you had in mind.
Below are 20 Claude prompts for writing, grouped into emails, reports, and everyday writing. Copy, adapt, and reuse them. Save the companion Indexura infographic on Pinterest for quick reference.
Before You Copy a Prompt
The text in square brackets is where your information goes. You don’t need an essay; a role, a little context, and your preferred tone may be enough.
Give Claude the source material rather than asking it to reconstruct what happened. Check names, numbers, deadlines, and promises before sending the result. And don’t paste confidential client or company information into an AI tool unless you’re permitted to do so.
If the answer sounds stiff, say so. Try: “Make it sound like a straightforward note to a colleague.”
7 Claude Prompts for Better Emails
1. Rewrite an Email to Sound Professional and Friendly
Please edit this email for [RECIPIENT AND RELATIONSHIP]. I want to sound [TONE: e.g., friendly, professional, direct], without sounding scripted or unnecessarily formal. Keep my original point and preserve every name, date, figure, and commitment. Fix awkward sentences, cut repetitive wording, and make the request or next step easy to spot. Don’t add promises or information that isn’t in my draft. Give me a subject line and a version I can send as it is. If anything in the original is unclear, flag it separately rather than guessing. Here’s the draft: [PASTE EMAIL].This is useful when the substance is fine, and you just need a second pair of eyes. If you have a typical writing style, describe it in a few words.
2. Turn Bullet Points into a Polished Client Email
I need to email [CLIENT NAME/ROLE] about [PROJECT OR TOPIC]. Below are my rough notes, not a finished message. Turn them into a clear, professional email that opens with the purpose, groups related updates together, and ends with the action needed from the recipient. Include dates, deliverables, and responsibilities only where the notes support them. Keep confirmed decisions separate from questions that are still open. Use a [TONE] tone and aim for [WORD COUNT] words. Don’t invent progress or commitments to make the email sound complete. Notes: [PASTE BULLET POINTS].If the notes contain an unresolved issue, leave it visible. A tidy email shouldn’t accidentally turn a possibility into a promise.
3. Shorten a Long Email Without Losing Important Information
This email is longer than it needs to be. Please cut it by about 40% while keeping the information the reader needs to understand the situation and take action. The recipient is [RECIPIENT], and they already know [SHARED BACKGROUND]. Preserve dates, amounts, decisions, requests, and any commitments exactly. Remove repetition, unnecessary setup, and sentences that repeat the same point in different words. Keep the tone [TONE], with plain, natural language. Show the shortened email first. Underneath, briefly mention anything important you removed or any detail you think I should double-check. Email: [PASTE EMAIL].The final check matters. Sometimes the sentence that looks like background to Claude is the one your client will ask about later.
4. Write a Follow-Up Email That Encourages a Reply
Help me follow up with [RECIPIENT] about [TOPIC]. We last spoke or emailed on [DATE], when [BRIEF CONTEXT]. I haven’t received a response, and this is my [FIRST/SECOND/THIRD] follow-up. Write a short, polite email that reminds them what this is about without retelling the whole history. If relevant, include this useful update: [NEW INFORMATION OR NONE]. End with one specific, easy-to-answer question or request: [DESIRED NEXT STEP]. Keep it under [WORD COUNT] words. Don’t use guilt, false urgency, or lines such as “just circling back.” Suggest two natural subject lines.A follow-up doesn’t have to be clever. Make the next action obvious.
5. Write a Polite Reminder About a Delay or Payment
Write a reminder email to [RECIPIENT] about [DELAYED TASK, INVOICE, OR APPROVAL]. Here are the verified details: [REFERENCE NUMBER, AMOUNT IF RELEVANT, ORIGINAL DEADLINE, CURRENT STATUS]. Our working relationship is [RELATIONSHIP], and I want the message to feel [TONE OR LEVEL OF FIRMNESS]. State what is outstanding and why I am following up. Ask for [SPECIFIC ACTION] by [REQUESTED DATE], without implying consequences I haven’t authorized. If this is an invoice, avoid inventing late fees or payment terms. Keep it concise and courteous. Give me a suitable subject line and the complete email.A gentle reminder to a long-term client should sound different from an urgent escalation. The relationship and the facts should determine the tone.
6. Make an Email More Persuasive Without Being Pushy
I’d like this email to make a stronger case for [REQUEST OR PROPOSAL] without becoming a sales pitch. The recipient is [ROLE], and their likely priorities are [PRIORITIES YOU KNOW]. Review the draft and identify what the reader needs to understand before agreeing. Rewrite it with a clearer benefit, a logical explanation, and one reasonable next step. Use these supporting facts only: [EVIDENCE OR DETAILS]. Don’t manufacture savings, results, deadlines, or objections. Keep my meaning and use a [TONE] voice. Return the revised email, followed by a short note explaining the biggest changes. Draft: [PASTE EMAIL].Don’t let Claude guess what matters to the recipient if you already know. A single real concern beats three generic selling points.
7. Turn Meeting Notes into a Professional Recap Email
Turn these notes from [MEETING NAME] on [DATE] into a recap email for [ATTENDEES OR AUDIENCE]. Start with a brief reminder of the meeting’s purpose, then summarize the important discussions and decisions. Put action items in a short list with an owner and deadline where those are recorded. Include outstanding questions and the immediate next steps. If a decision wasn’t final, say that. If an owner or deadline is missing, write “To be confirmed” rather than assigning one. Keep the email under [WORD COUNT] words and use a [TONE] tone. Notes: [PASTE NOTES].Read the action list twice before sending. It is surprisingly easy for a polished recap to make an undecided item sound settled.
7 Claude Prompts for Better Reports
8. Turn Rough Notes into a Structured Business Report
I have collected notes for a report on [TOPIC], intended for [AUDIENCE]. Please organize them into a useful first draft with these sections where the material supports them: Executive Summary, Background, Objectives, Findings, Evidence, Recommendations, Action Items, and Conclusion. Keep related points together and explain the significance of each main finding in plain English. Distinguish information directly supported by my notes from assumptions or interpretations. Don’t invent sources, statistics, or conclusions. Where the notes don’t support a section, tell me what’s missing instead of filling the space. Aim for [LENGTH]. Notes: [PASTE NOTES].You may not need every heading. After Claude organizes the material, remove sections that don’t help the intended reader.
9. Summarize a Long Report for Busy Executives
Summarize the report below for [EXECUTIVE AUDIENCE], assuming they have not read the original. Start with the main conclusion in two sentences, then give five key takeaways. Cover the business impact, major risks, and decisions or next steps that matter most. Use clear language without technical detail unless it changes the decision. Keep important figures and qualifications accurate. Do not introduce outside facts or present recommendations as decisions already taken. If the report doesn’t support a strong conclusion, say so. Limit the summary to [WORD COUNT] words. Report: [PASTE REPORT].Before forwarding an executive summary, compare its headline with the report’s actual findings. That is where overstatement tends to creep in.
10. Make a Report Clearer and More Data-Driven
Review this section of my report as a careful business editor. The audience is [AUDIENCE], and these are the figures and evidence I can support: [DATA AND SOURCES]. Rewrite the section so the main point is clear, claims are precise, and the evidence appears next to the statement it supports. Separate observations from interpretations and recommendations. Flag vague phrases, unsupported comparisons, and places where a missing baseline or time period makes a number difficult to interpret. Never add statistics or imply causation without evidence. Return the revised section, followed by a brief list of data gaps. Section: [PASTE SECTION].If you don’t have the numbers, asking Claude for a list of missing evidence is more useful than asking it to sound “data-driven.”
11. Write an Introduction and Conclusion That Fit the Report
Help me write or improve the introduction and conclusion of a report about [TOPIC]. It’s for [AUDIENCE], and its purpose is [PURPOSE]. The relevant background is [CONTEXT], the main findings are [FINDINGS], and the recommendations are [RECOMMENDATIONS]. In the introduction, explain why the report exists and what the reader will learn. In the conclusion, bring together the actual findings and point toward the next action without simply repeating the introduction. Keep each section around [WORD COUNT] words, in a [TONE] voice. Do not add conclusions the body doesn’t support. Existing text, if any: [PASTE DRAFTS].Write these sections after the findings are reasonably settled. Otherwise, it’s easy to promise a story the report doesn’t tell.
12. Convert a Rough Draft into a Project Status Report
Turn this rough update into a project status report for [PROJECT] and [AUDIENCE]. Include Overall Status, Work Completed, Current Work, Upcoming Milestones, Risks and Blockers, Dependencies, Decisions Needed, and Next Steps. Keep it readable for someone who hasn’t attended the team’s meetings. Preserve all dates, percentages, milestones, and commitments exactly as supplied. Use a green, amber, or red overall status only if the information supports it; otherwise, say there isn’t enough evidence to assign one. Don’t hide blockers or invent progress to make the report sound positive. Source update: [PASTE DRAFT OR NOTES].A status report isn’t a performance review. The useful version is the one that helps people decide where attention is needed.
13. Turn a Long Report into a One-Page Leadership Brief
Condense this report into a one-page brief for [LEADERSHIP AUDIENCE], around [300–400] words. Lead with the main conclusion, then cover Key Findings, Business Impact, Top Risks, Decisions Required, and Recommended Actions. Explain just enough context for someone who hasn’t read the full report. Prioritize items that affect a decision, budget, deadline, or business outcome. Keep figures and qualifications exactly as stated. Don’t invent an action owner or pretend a recommendation has already been approved. If no decision is required, say so clearly. Report: [PASTE REPORT].In a leadership brief, keep what helps the reader act.
14. Extract Risks, Blockers, and Next Steps from a Project Update
Read this project update for [PROJECT AND OBJECTIVES]. Extract all clearly reported risks, current blockers, and next steps. Also identify possible risks implied by the information, but label those “Inferred” so I can review them. Present the results in a table with columns for Item, Type, Impact, Urgency, Owner, Suggested Mitigation, and Next Step. Include an owner only if one is named; otherwise write “Not stated.” Distinguish missed deadlines from deadlines merely at risk. Do not invent dates, dependencies, or project decisions. After the table, list up to three questions I should ask the team. Update: [PASTE NOTES].Review inferred risks before including them in a formal report.
6 Claude Prompts for Better Writing
15. Improve the Clarity and Flow of a Paragraph
Please improve the paragraph below for [TARGET AUDIENCE]. Keep my central point, facts, and personal writing style, but make the sentences easier to follow. Fix unclear references, awkward transitions, repeated ideas, and overly complicated wording. Don’t make it sound grander than the subject deserves, and don’t add examples or claims I didn’t provide. Keep the new version roughly the same length unless shortening would genuinely help. Return the edited paragraph first, followed by two or three specific observations about what changed and why. If any sentence could mean two different things, flag it. Paragraph: [PASTE PARAGRAPH].It’s worth comparing both versions. Sometimes a slightly imperfect sentence sounds more like you than the smoothest possible rewrite.
16. Rewrite Content in a Confident, Polished Voice
Rewrite this [DOCUMENT TYPE] for [AUDIENCE] so it sounds confident, capable, and natural. Remove unnecessary apologies, weak openings, and phrases such as “just checking” where they weaken the message. Make the main point direct and the next step clear. Keep genuine uncertainty where the facts require it; don’t turn an estimate into a guarantee. Avoid corporate clichés, exaggerated claims, and aggressive language. Preserve my meaning, names, figures, and commitments. Use a [TONE] tone and aim for [LENGTH]. Return the revised version and briefly note any wording you kept cautious for accuracy. Text: [PASTE TEXT].Confidence comes from saying what you know clearly, not pretending you know more than you do.
17. Turn a Rough Idea into a Useful Article Outline
Help me develop an article outline from this idea: [ROUGH IDEA]. I’m writing for [AUDIENCE] on [WEBSITE OR PUBLICATION], and the reader wants to [READER GOAL]. Suggest a specific angle and working headline, then organize the piece into useful H2 and H3 sections. For each major section, explain the question it should answer and what practical information belongs there. Suggest examples that would make the article clearer, but label anything needing research or verification. Don’t invent sources, statistics, or quotes. Avoid generic sections that could fit any topic. End with a sensible conclusion and reader takeaway.If the outline could just as easily describe ten other articles, push Claude to make the angle more specific.
18. Generate Stronger Headlines for Articles and Blog Posts
Review this working headline: [CURRENT HEADLINE]. The article is about [SUMMARY], its intended reader is [AUDIENCE], and the main search phrase is [KEYWORD]. Tell me briefly what’s unclear or unappealing about the existing headline. Then suggest three alternatives that communicate a specific benefit without exaggerating the content. Keep them under [CHARACTER LIMIT] characters where possible, and use the keyword naturally rather than forcing it in. Avoid clickbait, vague superlatives, and promises the article doesn’t deliver. Explain the difference between the three options and recommend the strongest one for this audience.A better headline makes the promise clearer. It doesn’t need to make the article sound more dramatic.
19. Edit Writing for Grammar, Brevity, and Readability
Edit the text below for [AUDIENCE], using a [TONE] tone. Correct grammar, punctuation, and awkward sentence construction. Cut filler and repetition, improve transitions, and make unclear references easier to follow. Preserve the author’s meaning, level of certainty, and distinctive voice; don’t rewrite everything simply because you can. Flag claims that are ambiguous or unsupported instead of quietly fixing them with guesses. Return a clean edited version first. Then give me a short list of the changes that materially improved clarity or accuracy, not a list of every comma you moved. Text: [PASTE TEXT].This makes a good final pass, but it shouldn’t replace your own review of facts and context.
20. Rewrite Technical Content for a Non-Technical Audience
Rewrite the technical explanation below for [AUDIENCE], who have [KNOWLEDGE LEVEL] familiarity with [TOPIC]. Start with the practical point: what it means, why it matters, and what the reader needs to know. Replace avoidable jargon with plain English and explain essential technical terms briefly. Use one simple example if it genuinely helps. Preserve technical limitations, important conditions, and any uncertainty; don’t simplify until the explanation becomes misleading. Keep it around [WORD COUNT] words, using a [TONE] voice. After the rewrite, identify any points that should be checked by a subject-matter expert. Source text: [PASTE TECHNICAL CONTENT].Keep technical terms when they help readers understand the decision.
Final Thought
A useful AI writing prompt isn’t necessarily complicated. It gives Claude enough context to make sensible choices and enough boundaries to avoid making things up.
Choose a prompt, change the placeholders, review the result, and refine it until it sounds like something you’d send. The point isn’t to have Claude write instead of you. It’s to spend less time wrestling with the first draft and more time deciding what you really want to say.
Explore more AI tools, practical guides, and prompt collections at Indexura.
FAQ
Can Claude write a professional email from scratch?
Yes. Give it the recipient, the purpose, the facts to include, and the tone you want. Even when the draft reads well, check that it doesn’t promise something you haven’t agreed to.
Is Claude useful for business reports?
It can organize notes, build an initial structure, tighten unclear sections, and summarize longer material. The underlying evidence still has to come from you, and the finished report needs review.
What if Claude’s writing sounds generic?
Share a short sample of your normal writing and ask it to match the level of formality, not to copy every phrase. You can also tell it what to avoid: overlong introductions, buzzwords, overly cheerful sign-offs, or unnecessary headings.