Turn Rough Intent into a Work Email with One Clear Reply

Before drafting a work email, decide what its recipient needs to answer. Put that request near the beginning, add the context needed to make the choice, and say what you will do after the reply. If your rough notes say only "soon," clarify whether a deadline was actually agreed before turning it into a date.

This is a new-message task. There is no email paragraph to polish yet. The useful result is a complete message, from subject to sign-off, that the colleague can answer without reconstructing your thinking or opening a missing attachment.

The FAQ example below is original fiction. Sam, Morgan, the rough capture, clarification, emails and error were authored for this tutorial. They are not real correspondence, a recording, captured model output or a reader test. Everything needed is supplied as text; no mailbox access is required.

Start with the whole rough thought

Here is the complete E0 capture:

E0 — Original fictional rough capture; no existing email draft
I need to email Morgan about the FAQ. We need to get moving. Setup or Troubleshooting first? I lean toward Troubleshooting because its outline feels rougher to me. Both still need work. I'll draft one section after Morgan answers. Need a response soon.

E0 contains a subject, a preference and a next step, but "get moving" and "soon" do not tell the writer what commitment to put in the email. Morgan might be asked to pick a first section, approve a finished document or agree to a delivery date. Those would be different messages.

Ask the writer the question that settles this draft:

Before drafting: what exact reply do you want from Morgan, and does "soon" mean an agreed deadline? What is your working relationship? Are any files actually supplied for attachment?

Sam's complete authored answer is:

C1 — Authored fictional clarification from Sam
I'm Sam; Morgan is my internal colleague and owns the FAQ's content priorities. Ask Morgan to choose Setup or Troubleshooting for the first drafting pass. Troubleshooting is my preference because I think its outline is less developed; it is not a user-research finding. No response deadline is agreed, so omit the urgency. I'll prepare the selected section for review after the reply; no completion date is promised. There is no previous email, and no file is supplied or authorized for attachment. Draft only.

Now the request is specific: Morgan chooses one section for the first drafting pass. Sam will prepare that section for review afterward. Morgan owns the content priorities, while Sam's preference is an opinion about the outline. No reply deadline or completion date has been agreed, so neither belongs in the message.

The clarification also settles the supposed attachment: there is none. Do not add "see attached" to make an email feel complete. The recipient needs enough context to choose, not a reference to a file that was never supplied.

Turn the clarified intent into a complete message

These are the writing decisions for this case:

Here is a complete draft:

Subject: Which FAQ section should I draft first?

Hi Morgan,

Could you choose which FAQ section I should draft first: Setup or Troubleshooting?

My preference is Troubleshooting because its outline seems less developed to me, but both sections still need work. Once you choose, I'll prepare that section for review.

Please reply with Setup or Troubleshooting.

Thanks,
Sam

The subject and opening make the decision visible before the explanation. The second paragraph gives Morgan a reason to consider Troubleshooting without treating Sam's view as a customer finding or a decision already made. The final request makes the reply small: one section name.

The email does not restate every drafting constraint. Morgan needs the choice, the relevant context and Sam's next step. The absence of an agreed deadline is handled by leaving out urgency, rather than adding a defensive paragraph to the message.

No approval is being requested for a finished FAQ. "Prepare that section for review" describes what happens after Morgan chooses; it does not say a section has already been written, reviewed or approved.

Give a drafting assistant the actual inputs

If you want help composing, copy this complete filled request. It contains E0 and C1, so the references do not depend on an earlier conversation:

Compose a new internal work email from the complete rough capture and clarification below. No baseline email exists. Put the requested decision first, give only enough context to answer, keep Sam's recommendation as a preference and ask Morgan to reply with one option. No response/completion date is agreed. Return the complete subject, greeting, body, requested reply and sign-off. Explain any necessary missing information outside the email; do not invent an address, attachment, approval, benefit, earlier agreement or publication. Draft for review only; do not send or access any mailbox.

E0 — Original fictional rough capture; no existing email draft
I need to email Morgan about the FAQ. We need to get moving. Setup or Troubleshooting first? I lean toward Troubleshooting because its outline feels rougher to me. Both still need work. I'll draft one section after Morgan answers. Need a response soon.

C1 — Authored fictional clarification from Sam
I'm Sam; Morgan is my internal colleague and owns the FAQ's content priorities. Ask Morgan to choose Setup or Troubleshooting for the first drafting pass. Troubleshooting is my preference because I think its outline is less developed; it is not a user-research finding. No response deadline is agreed, so omit the urgency. I'll prepare the selected section for review after the reply; no completion date is promised. There is no previous email, and no file is supplied or authorized for attachment. Draft only.

The same text is available as a complete composition request, with a separate source packet. These are plain-text materials. They do not assume that an assistant can read an inbox, inspect an attachment or send the result.

You can also write the email directly from the clarified request. For a short choice between two options, manual drafting may be enough. If the recipient does not need a lasting email and your working context allows a direct conversation or short message, use that channel instead; first make the requested decision clear.

Reject a complete email that invents agreement

Here is the entire deliberately wrong version:

Subject: FAQ updates approved for Friday

Hi Morgan,

As agreed, both updated FAQ sections are approved and attached. We'll publish them on Friday and reduce support questions by 30%.

No reply is needed.

Thanks,
Sam

It has a subject, a greeting and a sign-off, but its purpose has changed. It tells Morgan about an approved release instead of asking Morgan which section Sam should draft. A complete-looking format cannot repair that change in meaning.

The error is not that the prose lacks warmth. The email has acquired decisions, artifacts and outcomes that Sam never supplied. Making those sentences friendlier would leave the wrong message in place.

Repair the whole email from the clarified intent

Use this instruction with the complete E0, C1 and wrong email above:

Repair the complete bad email using the complete raw capture and clarification. Start again from that intent, not from the invented agreement in the bad email. Return a whole new subject-to-signoff email. Ask Morgan to choose Setup or Troubleshooting. Retain Sam's preference and the plan to draft one chosen section for review after the reply. Remove approval, attachments, Friday/publication, benefit percentage and no-reply wording. No deadline is agreed. Do not send or access a mailbox. This is an authored exercise, not a real model failure.

The complete standalone repair request includes all three inputs. Starting again from E0 and C1 avoids treating the wrong email's "as agreed" as another source of facts.

Here is the entire corrected email:

Subject: Which FAQ section should I draft first?

Hi Morgan,

Could you choose which FAQ section I should draft first: Setup or Troubleshooting?

My preference is Troubleshooting because its outline seems less developed to me, but both sections still need work. Once you choose, I'll prepare that section for review.

Please reply with Setup or Troubleshooting.

Thanks,
Sam

The corrected copy restores the decision rather than trying to preserve the bad email's release announcement. It retains the same two options, Sam's preference and the review step after the reply. A missing deadline remains absent; a nonexistent attachment is removed rather than replaced with a guessed file.

The complete email file is the same authored copy shown in both places. Repeating it here makes the repair inspectable as a whole message, not just a list of suggested edits. It was not produced by submitting either request to a model.

Read it from Morgan's side before choosing a version

Read the finished email without E0 or C1 beside it:

This is an inspection of the supplied copy, not evidence that Morgan or another reader tried it. You can check whether the message contains those answers. Whether a real recipient understands or responds would require an actual exchange.

One recipient discussion about unclear work email includes both an account of reduced follow-up with drafting help and reports of longer messages with less useful information. A separate discussion about AI-written colleague emails raises authenticity and whether the sender understands the message. These are differing individual accounts, not a measured comparison or proof that a particular tool will improve this task. The worked example applies those concerns to a new email; it is an editorial design.

If you speak your rough thought instead of typing it, inspect the resulting text before using it. In this case, the section names, the negative statements and the correction of "soon" matter more than smooth transcription. Speaking is an optional way to capture the input; it does not establish that a tool understands the decision or preserves your personal voice.

Keep the version you actually mean to send for your own review. Preparing this draft has not sent an email, chosen a section for Morgan, created a file attachment or approved FAQ publication. The finished writing should make the next reply clear while leaving those decisions where Sam and Morgan placed them.