askROI Blog
Edit a work email so it gets read and answered
Three edits get a work email answered: mark the facts, cut the padding, lift the ask to the top. Here they are on one real draft, before and after.
By askROI · · Updated
Try it
Paste a draft and say who it's going to. The button opens a chat with Mara's draft from this post already filled in, so you can swap in your own email before you send.
Opens a new chat with a message you can edit before sending
Mara needs her manager to say yes to a new date for the team offsite, and the venue will only hold that date until Friday. She writes a friendly email, reads it once, and sends it. Priya opens her inbox between two meetings and sees: Quick question. Hope your week is going well! I know things are hectic with the Q3 push...
Nothing in that preview tells Priya what Mara needs or that there's a clock running, so the email waits for later. The email wasn't rude, and every fact in it was right. They were just in the wrong places. Flip between the two versions below and look at what Priya can tell before she opens anything.

The reader decides from two lines
A phone inbox shows the subject and the start of the body. For a busy reader, that's the whole decision: answer now, or later. So an email gets answered when those two lines say what it's about and what the reader has to do.
Three habits push the ask out of those lines:
- The warm-up. Hope you're well, sorry to bother you, I know you're busy. Each one is polite, and each one pushes the point further down.
- The buried ask. The request comes last, after the history and the context, where the preview never reaches.
- The hedge. "No rush" and "whenever you get a chance" tell the reader nothing happens if they wait. Mara wrote "No rush at all" about a date the venue only holds until Friday.
Three edits, in this order
Here are the edits on Mara's draft, and the version askROI handed back underneath.

1. Mark the facts before you cut anything
Go through the draft and highlight every name, date, amount, link and attachment. In Mara's email that's October 14, October 21, Sam, Lena and Joao, and until Friday. Those words come through the edit exactly as written. Marking them first means you can cut hard everywhere else without trimming a date by accident, and a short email with a wrong date is worse than a long one that gets it right.
2. Cut the padding, including the polite kind
Anything that isn't a fact or the ask is up for cutting: the warm-up, the apology, the history the reader already knows, and the softeners wrapped around the request ("Not sure if this is possible, but would it make sense to"). Expect to lose a lot: Mara's draft went from 117 words to 53.
Keep the warmth that does a job. "Happy to go with whatever you think is best" stayed, because it tells Priya the call is hers.
3. Lift the ask into the subject line
Find the sentence that says what you want and move it to where the preview shows it. The best spot is the subject line itself. "Move team offsite from Oct 14 to Oct 21?" is a question Priya can answer without opening the email; "Quick question" and "Following up" give her nothing to go on. Then open the body with the reason and give the ask its own short line. If the email carries two requests, list them, so each one can be answered on its own.
This is why the subject line comes last. Once the email has one obvious ask, the subject line is mostly that ask.
What askROI did with the same draft
The edit card in the scene above is the email askROI returned for the Try it prompt, word for word. It moved the reason and the ask to the top, turned the subject line into the question, and cut the warm-up, the apology and the "no rush". The four facts are in the body exactly as Mara wrote them (the subject line shortens October to Oct). The reply ends with a two-sentence note on what changed, so you can check the edit before you paste it anywhere.
For your own drafts, use the email editor. It runs this edit with the rules already built in: a subject line that names the topic and the ask or deadline, the reason in the first sentence, the ask on its own line, and every fact, name, date, amount, link and attachment reference kept as given. It's set up never to add a deadline, a commitment or a promise you didn't make.
It also keeps your tone, on purpose. When we gave it Mara's draft with no other instructions, it kept "No rush, whenever you get a chance", because that's how Mara talks to Priya. If a soft line like that undercuts a real deadline, say so in the same chat and it goes. And if you've connected Outlook, askROI can save the finished email as an Outlook draft instead of you copying it over (see the Microsoft 365 AI assistant).
The thirty-second check before you send
Read only the subject line and the first two lines of the body, then ask:
- Can the reader tell what this is about?
- Can they tell what to do, and by when?
- Could the email be half as long with nothing lost?
A no to any of them means one more edit. None of them is about writing better sentences. Most emails that sit unanswered already say the right thing; they say it in the fourth paragraph, where nobody reads on a phone.