Which edit can this email actually satisfy?

The move When two edits can't both fit in one email, ask AI for the finished email both ways. Each version makes every other edit and names what it leaves out. You pick.

You've drafted the email telling Dana, a client's operations director, that the scheduling rollout slipped. Priya, your director, wants every new date kept with its reason. Marcus, the sales lead, wants it cut to the one thing Dana has to do, with the timeline saved for Thursday's call. That one thing is signing off on the merged patient records by October 19.

Both edits are fair, and they can't both fit: the timeline is either in the email or it isn't.

Ask AI to "revise this using the feedback" and you get one email back. It may spot the clash and explain its pick. One email still means it picked the winner, and that call was yours to make.

So ask for the finished email both ways. Both versions make every edit that fits. Each one names what it leaves out and comes with a sentence you can send the person whose edit didn't make it.

You pick by comparing two real emails, not by imagining the one you didn't get.

The prompt

Before you rewrite this email, check whether all the editing requests below can be met in one email.

Who the email is for and what it needs to get done: [the reader, how they'll read it, and the one thing you need from them]

Draft:
[paste the draft]

Editing requests, with who asked and why:
[paste each request]

1. Only call two requests a conflict if no single email can fully meet both. A difference in taste, like "warmer" versus "more professional," is not a conflict.
2. If nothing conflicts, rewrite the email once with every request applied.
3. If two requests conflict, quote both and name the smallest choice I have to make. Then write the complete email twice: Version A follows the first request, Version B follows the second. Make every other edit in both. Under each version, add one line saying exactly what it leaves out and one sentence I can send the person whose request it drops.
4. Don't pick a version for me. Keep every fact, date and condition from the draft unless a request removes it, and add no new promises, dates or facts. Keep it to one email.
5. Use only the requests listed here, even if earlier ones appear in this chat. If the draft, the requests or who the email is for is missing, ask for it instead of guessing.

The "who the email is for" line matters because the right cut depends on who's reading and what you need from them. The conflict rule stops "warmer" versus "more professional" from turning into a standoff. The no-new-promises rule is there because shortening is where "if the retest passes" can fall off a date.

Try it on this made-up example

Who the email is for and what it needs to get done: Dana Okafor, operations director at Harbor Clinics, our client. Dana reads email on a phone between clinic visits. We need Dana's team to sign off on the merged patient records by Monday, October 19, or the remaining go-live dates slip. We have a call with Dana on Thursday, October 15.

Draft:
Subject: Update on your scheduling rollout

Hi Dana,

I wanted to give you a full update on where the rollout stands. When we kicked off in August, we planned for all four clinics to go live on October 21. Two things have changed since then.

First, exporting records from your old system took nine days instead of three. About 2,000 patient records had duplicate IDs, and our team merged them by hand. Second, the connection to your billing vendor failed its first test on October 6. Their team can't retest until October 15.

Here's the revised plan. Eastside still goes live on October 21. Midtown moves to October 28. Riverside and Lakeview move to November 4, if the billing retest passes.

To hold these dates, we need your team to sign off on the merged patient records by Monday, October 19. If sign-off slips, every date after Eastside moves by at least a week.

Let me know if you have questions.

Best,
Sam

Editing requests, with who asked and why:
- Priya (my director): "Keep every date and the reason for each one. Dana got burned by a vague timeline from the last vendor and will ask why if a reason is missing."
- Priya: "Don't make November 4 sound firm. It depends on the billing retest."
- Marcus (sales lead on the account): "Put the records sign-off first. It's the only thing we need from Dana."
- Marcus: "This is too long for someone reading on a phone. Cut it to the sign-off and save the timeline for Thursday's call."
- Marcus: "Replace 'Let me know if you have questions' with a specific next step."

The version a single rewrite skipped

We ran the example with Claude Opus 5.5, as plain text with no files or tools. Here's the choice it named and all of Version B, with formatting marks removed. Version A isn't shown. It kept every date and both reasons below the sign-off.

Your choice: Do the revised dates and their reasons go in this email, or wait for Thursday's call?

Version B: cuts to the sign-off (Marcus)

Subject: Sign-off needed by Monday, Oct 19: merged patient records

Hi Dana,

We need your team to sign off on the merged patient records by Monday, October 19. These are the roughly 2,000 records with duplicate IDs that our team merged by hand.

If sign-off slips, every go-live date after Eastside moves by at least a week.

We'll go through the full timeline on our call Thursday, October 15.

Next step: Please reply to confirm your team can sign off by Monday, October 19, or tell me what might hold it up so we can cover it Thursday.

Best,
Sam

Leaves out: These items move to Thursday's call:
- The original October 21 plan for all four clinics
- The export delay (nine days instead of three)
- The October 6 billing test failure and October 15 retest
- The revised dates: Eastside October 21, Midtown October 28, Riverside and Lakeview November 4 if the retest passes

Sentence for Priya: "I held the dates and their reasons for Thursday's call so the email stays short enough to read on a phone, and Dana will get every date with its reason on that call."

The ordinary "revise this" request, run on the same example, kept the timeline and explained why in a note. That was a good email. The short one just never got written, so there was nothing to compare it with.

Read both versions against your draft before either goes out. In Version A of that same answer, the November 4 line said "only if the billing retest on October 15 passes." Your draft only says the vendor can't retest until October 15, so the earliest possible retest date turned into a scheduled one.

What stays yours

Which version goes out is your call, because you know whether Dana needs the reasons today. If the call belongs to Priya and Marcus, send them both versions and let them settle it in one reply. We've only run this with Claude Opus 5.5. Other Claude models and other AI tools may handle the conflict check or the two versions differently. Whichever you use, make it one your company has approved for client email.