About two-thirds of workplace AI writing is editing text you already wrote, not blank-page drafting. Every prompt here takes rough notes or a draft, and sets tone by dials.
Most of the writing you need help with already exists
The largest study of how people actually use a general-purpose AI assistant — How People Use ChatGPT, an NBER working paper by Chatterji, Cunningham, Deming, Hitzig, Ong, Shan and Wadman, drawing on a privacy-preserving analysis of 1.5 million conversations — found that writing is the most common thing people do with these tools at work, at roughly 40% of work-related messages.
The more useful finding is the second one. About two-thirds of those writing messages ask the model to modify text the user already supplied — editing, critiquing, summarising, translating — rather than producing something from nothing.
That is not what most prompt libraries assume. The blank page is the rarer problem. The common one is a draft that is too long, too blunt, too hedged, or written while annoyed, and needs to become something you can send.
So every prompt in this pack accepts either input: rough notes, or a draft you want reworked. If you have already written the thing, paste it in. That is the normal case, not the fallback.
Tone as dials, not adjectives
The second design decision worth explaining. Make it professional
is not an instruction — it means something different to everyone, and it is why AI-polished writing so often comes back sounding like a press release.
These prompts use discrete dials instead: formality, warmth, and directness, set independently. A message can be informal and direct, or formal and warm. Those are different documents, and the difference is usually the entire point of the email you are struggling with.
The everyday messages
Turn Rough Notes Into a Polished Email is the workhorse and the best demonstration of the notes-or-draft pattern.
Write a Follow-Up That Doesn't Sound Pushy solves the message people rewrite four times, mostly by giving the recipient a reason to reply that is not your need for a reply.
Write a Message That Asks for Something — an introduction, a favour, time, a decision — is built around making the ask specific and easy to decline, which is what makes it easy to accept.
Write a Professional Networking Message covers outreach to someone who does not know you, and its core rule is that a genuine specific reason beats any amount of flattery.
Write an Out-of-Office and Handoff Brief is small and consistently useful, because the real work is the internal handoff rather than the auto-reply.
Saying difficult things
Say No or Push Back Without Damaging the Relationship produces the decline with a reason and, where there is one, an alternative — the register set by the dials rather than by a template.
Prepare for a Difficult Conversation is preparation rather than a script, which matters because a scripted difficult conversation fails the moment the other person departs from it. It works through what you want, what they likely want, what you might be wrong about, and where your actual limit is.
Give Constructive Feedback to a Colleague is peer-to-peer feedback without the authority a manager has — the management pack covers the version with a reporting line attached.
Write an Apology or Service-Recovery Message carries a hard constraint: it will not promise remedies, refunds, timelines, or root causes you have not confirmed. A great many apologies create a second problem by committing to something nobody checked.
Communicating upward and outward
Write a Status Update for Stakeholders uses a fixed schema, because a status update whose shape changes every week cannot be skimmed and therefore is not read.
Write an Executive Summary With a Recommendation enforces the inversion executives actually need: the recommendation first, the reasoning after, the detail available but not in the way.
Turn Notes Into Briefing Talking Points and Turn a Long Thread Into a Stakeholder Recap are both compression tasks — the second one being the forty messages happened, what do I tell the client
problem that eats an hour and produces nothing anyone values.
Announce a Change to Your Team carries the same no-invented-commitments guardrail as the apology prompt, for the same reason.
The same craft in higher-stakes settings
Several prompts tagged here belong to other packs but are fundamentally the same skill under more pressure. Write an Investor or Lender Update That Builds Confidence from business finance, where the credibility of your bad news is the whole product. Pitch a Partnership From the Partner's Side of the Table from partnerships. And four from the nonprofit pack — Write a Case for Support, Write a Letter of Inquiry, Write the Grant Report Your Funder Will Actually Read, and Report Your Impact Without Overclaiming — where the discipline of not overstating is a professional obligation rather than a stylistic preference.
Where this stops
These prompts will not commit you to anything you have not told them is true. They are written to refuse to invent dates, remedies, figures, or facts about your organisation, and to flag when a message depends on information you have not supplied. Anything with legal weight — a formal complaint, a termination, a contractual notice, a regulatory disclosure, a response to a legal threat — should be reviewed by someone qualified before it goes out, no matter how good the draft reads.
Sources
- Aaron Chatterji, Tom Cunningham, David Deming, Zoë Hitzig, Christopher Ong, Carl Shan and Kevin Wadman, How People Use ChatGPT, NBER Working Paper 34255, September 2025 — 1.5 million conversations; writing ≈40% of work-related messages, about two-thirds of which modify user-supplied text