Use Claude to Turn a Rough Internal Email into a Clear Draft

A rough internal email usually has the facts you need, but not the order your reader needs. Claude can turn approved notes into a first draft. It should not decide what your team promised, who owns an action, or when something is due.

This guide uses a fictional set of notes. The output is an illustrative example, not a recorded Claude session or a measured time-saving result.

What you need

• Access to Claude in a surface your organization permits for this material. Interface names and limits vary by account.
• Approved, non-sensitive notes that you are allowed to paste into the service.
• A recipient and purpose for the email. If either is unclear, leave it as an open question.

Anthropic’s prompt-engineering overview recommends starting with success criteria you can check. Here, success means a factual draft whose unsupported gaps remain visible.

1. Start with complete fictional notes

Copy this block into a new Claude chat:

Project notes — fictional
- The help-centre draft has been revised after the product team's comments.
- Legal review is requested; no legal reviewer is named in these notes.
- The customer walkthrough is planned for Thursday, but the time and attendees are not confirmed.
- Two screenshots still need replacement because the interface changed.
- The project lead asked for a short status email before the next team check-in.

These notes deliberately contain gaps. “Planned for Thursday” is not a confirmed appointment. “Legal review is requested” is not evidence that review has happened.

2. Use a bounded drafting brief

Paste this instruction after the notes:

Draft a short internal status email using only the fictional notes above.

Audience: the project team.
Purpose: explain current progress, open work, and decisions needed.
Subject: specific and no more than 70 characters.
Body: 120 words maximum, with these headings:
1. Current status
2. Open work
3. Decisions or confirmations needed

Rules:
- Do not invent a person, deadline, meeting time, attendee, approval, cause,
  metric, or commitment.
- Keep “planned for Thursday” as planned, not completed or confirmed.
- If an owner or detail is missing, write “owner/details to confirm.”
- Separate completed work from requested or future work.
- After the draft, list every sentence that needs a source check.
- Do not write a greeting addressed to a named person.

The final instruction asks for a source-check list. That makes review part of the deliverable rather than a vague “look it over later.”

3. Review the draft beside the notes

Do not send the result directly from Claude. Check these items line by line:

1. Status: “revised” remains completed work; the legal review remains requested.
2. Time: Thursday remains a plan, not a confirmed calendar commitment.
3. Ownership: no reviewer or project lead is named unless the notes name one.
4. Open work: screenshot replacement is still outstanding.
5. Requests: the message asks for confirmations instead of silently filling them.

A useful acceptance result has a short email plus visible open questions. A polished paragraph that hides the missing owner has failed the task.

4. Make only supported edits

If you know the owner or time, add it to the source notes first, then ask Claude to revise the draft. Do not paste a correction as an isolated instruction that conflicts with the source. Keep the original notes and final reviewed version together so the next update can be checked.

When the draft passes, copy it manually into your normal mail client. Keep the send step human for this workflow.

Troubleshooting

• Claude invents a deadline: add the exact “do not invent” rule and ask it to quote the source bullet behind the sentence.
• Planned work becomes completed: request a two-column “source wording → draft wording” comparison for the disputed line.
• The email is too long: lower the word limit, but keep the source-check list outside the email body.
• You cannot use the chat surface: use the same brief in an approved tool or a normal template; do not move restricted notes to an unapproved service.

TRY / SKIP / USE: TRY this on a low-risk internal update with fictional or approved notes. SKIP pasting confidential material when your organization has not approved the surface. USE the draft only after a person checks each status, owner, date, and request against the notes.

Sources and next step

• Anthropic: Prompt engineering overview
• Choose your first AI workflow at work
• Get The Weekly Verdict

Next, try the same review discipline on a recurring weekly update—but keep planned work and completed work in separate sections.