By the editorial team · Published October 26, 2026 · 14 min read

Example 03 / Communicate

Professional email: a delivery slip, a decision, and 160 words, annotated

A vibe writing example for work: a two-week slip, a dependency the client owns, an AI draft that over-apologizes, and the 160-word email that got a decision.

Read the layers4 layers · 22 margin notes · Workplace email, under 200 words

Writer: A team lead at a 12-person software consultancy, writing to the client's VP of operations
Format: Workplace email, under 200 words
Tools used: A chat assistant
Session length: About 25 minutes, including the rewrite
Prompts used: Email mega prompt, Critique Your Draft (on her own revision), Bounded Edit (one line)
Turns: 4: brief and draft, subject lines, critique, bounded edit

A team lead at a small software consultancy has to tell a client that a launch moves by two weeks. The cause is access the client's own IT group has not granted, after three reminders. She cannot say that. She also cannot pretend the date is holding, and she needs a decision between two options by Friday, because her team plans its sprint on Monday and the client's store training is booked for the week after.

There is history. In June her team slipped a week, and that one was their fault. The client was gracious about it and said 'let's not make a habit of it'. He will feel this email as the second time, whatever the cause, and she knows it.

She used a chat assistant for a first draft, a set of subject lines, a critique of her own rewrite, and one bounded edit. The first draft is below in full. It apologizes three times, lists every date she chased, mentions June, and asks for the decision in paragraph five. The email she sent is 160 words and asks in the first sentence.

Layer 1You

Her notes, typed before opening the chat

email to Marcus. ugh.

facts: launch was Nov 2 (Mon). the order-tracking sync needs read access to their ERP test env. asked Aug 28. chased Sept 4, Sept 18, Oct 6. still nothing. it's with their IT, not Marcus, but Marcus owns the project on their side.

everything else is built. integration tests can't run without the access. I won't launch untested, not after June.

if access by Fri Oct 17: Nov 16 works. after Fri: day for day.

other option: keep Nov 2 without the live sync. stores keep doing the daily CSV upload like they do now. switch the sync on later once it's tested. means training the stores twice. I'd rather not but it's his call.

need an answer by Fri EOD. sprint planning Mon. store training booked Oct 28-29, has to move if we go to Nov 16.

history: June we slipped a week, our fault (vendor library). Marcus was fine about it but said "let's not make a habit of it." this is the second date change on the project. not the same thing. he'll feel it as the same thing.

must NOT: say it's their fault / "your IT team". he knows. "as previously mentioned" / list the dates I chased. passive aggressive. mention June. "unfortunately". apologize more than once. maybe not at all? nothing here is mine to apologize for. promise Nov 16 flat. it's conditional. bury the ask. the ask IS the email.

tone: how I talk to him on calls. direct. we get on fine. under 200 words, he reads on his phone between meetings.

Keptthe ask IS the email.
The organizing decision, made before the chat opened. The draft ignored it and she did not. Everything in the final serves the decision she needs by Friday.
Checkedasked Aug 28. chased Sept 4, Sept 18, Oct 6.
She pulled these from her sent folder so the one date she used in the email would be exact. The other three were for her own confidence, not for Marcus.
Changedapologize more than once. maybe not at all?
She allowed herself one apology in the brief and ended up using none. When she went looking for the thing to apologize for, nothing in the email was hers.
Keptit's conditional.
November 16 holds only if access arrives by Friday. The draft stated the date flat and confident. She restored the condition and the day-for-day consequence in two short sentences.
Rejectedhistory: June we slipped a week, our fault
She put June in the notes so the assistant would understand the stakes. The assistant used it. In hindsight, context the draft must not use belongs in a separate block, labeled as such, or stays out of the raw material entirely.

Layer 2You

The direction she gave, turn by turn

Turn 1. Pasted the Email mega prompt with the blocks filled in. The parts that mattered:

Writer: team lead at a 12-person consultancy. Reader: Marcus, VP of operations at the client, reads email on his phone between meetings, owns the project on their side but does not control IT.

It must: get a decision between two options by Friday end of day, without blaming anyone.

Raw material: [the notes above, whole].

Voice: like I talk on our calls. Short. I say what I recommend. I don't apologize for things that aren't mine.

Banned: "unfortunately", "I hope this finds you well", "as previously mentioned", "reach out", "transparent", any mention of June, more than one apology. Under 200 words.

No questions needed, you have everything. Draft it.

Turn 2. That's 283 words, has "unfortunately" twice, lists my chase dates, and brings up June. All of which I said no to. The ask is in paragraph five. I'm going to rewrite it myself. One thing: give me three subject lines that say a decision is needed, six words or fewer each, no "update".

Turn 3. Mine: [pasted her rewrite]. Don't rewrite it. Tell me three things, one line each: is the ask clear in the first sentence, does anything read as blame, and is November 16 stated as conditional?

Turn 4. Change only the last line. "Happy to get on a call if that's easier" sounds like I'm offering to be talked out of it. OLD and NEW.

ChangedNo questions needed, you have everything. Draft it.
She skipped the questions step because the facts were complete. In hindsight, one question would have been worth it: the assistant might have asked whether the June history was there to use or to avoid.
RejectedI'm going to rewrite it myself.
Four broken rules and a buried ask is not a bounded-edit situation. She took what the draft showed her, which was the shape of the obvious email, and wrote against it.
Addedgive me three subject lines that say a decision is needed, six words or fewer each, no "update"
Narrow, cheap, and useful. The draft's subject line was 'Update on Project Timeline', which is the subject line of an email nobody opens before lunch.
CheckedDon't rewrite it. Tell me three things, one line each
The critique turn on her own draft, with the questions fixed in advance so the answer could not wander into taste. She wanted three checks, not a second opinion on everything.
Changed"Happy to get on a call if that's easier" sounds like I'm offering to be talked out of it.
A one-line problem, stated as an effect rather than a word she disliked. That is what makes a bounded edit come back right.

Layer 3AI proposes

What the assistant returned, including the first draft verbatim

Turn 1 reply (the draft):

Subject: Update on Project Timeline

Hi Marcus,

I hope this email finds you well. I wanted to reach out to provide an update on the order-tracking portal and to apologize in advance for the news I need to share.

Unfortunately, we have run into a challenge that affects our November 2 launch date. As previously mentioned in my emails of September 4, September 18, and October 6, the integration work depends on read access to the [VERIFY: ERP system name] test environment. Unfortunately, as of today we have not yet received this access, and as a result, our team has been unable to complete integration testing.

I completely understand how frustrating this must be, and I'm sorry for the position this puts you in, especially given the delay we experienced earlier this summer, and I want to be fully transparent with you about where things stand. Please know that our team has completed all other components of the build and is ready to proceed as soon as access is granted.

Given the current situation, we are confident we can deliver the full solution by November 16. Alternatively, we could explore launching on November 2 with a temporary CSV-based workaround, and enable the live sync at a later date once testing is complete. Both options have their merits, and we're happy to go with whichever works best for your team.

If possible, it would be helpful to have your decision by Friday so we can plan accordingly. I sincerely apologize for any inconvenience this may cause, and I truly appreciate your patience and understanding.

Please don't hesitate to reach out if you have any questions or would like to discuss further.

Best regards, Lena

Turn 2 reply (subject lines). 1. Launch date: decision needed by Friday. 2. Two options for the November launch. 3. November 2 launch: your call needed.

Turn 3 reply (critique of her rewrite). 1. The ask is in the first sentence. "I'd like your call on how" may read as casual for a date change; consider "I need your decision on how." 2. "and still don't have" is the only phrase that could read as blame. It is a fact. If you want it softer: "which is still pending." 3. November 16 is stated as conditional on Friday, and the day-for-day consequence is explicit. Clear.

Turn 4 reply (bounded edit). OLD: Happy to get on a call if that's easier. NEW: If a call is easier, I can do Thursday afternoon.

RejectedAs previously mentioned in my emails of September 4, September 18, and October 6
Banned by phrase and by intent, and the draft did it anyway, with dates. Listing the reminders is how an email blames someone while claiming not to. The final uses one date, once, as a fact.
Rejectedespecially given the delay we experienced earlier this summer
June, which she said not to mention. The draft reached for it because it was in the raw material and because models like to acknowledge history. Both parties know. Saying it makes the email about her.
Changedwe are confident we can deliver the full solution by November 16
The quiet meaning change. Her notes say November 16 holds only if access arrives by Friday, and moves day for day after. The draft stated the date flat. Had she sent this, she would have been promising something she did not control.
RejectedBoth options have their merits, and we're happy to go with whichever works best for your team.
She has a recommendation and the draft hid it. A lead who asks for a decision owes an opinion, or the client has to guess what she wants and then guess again at why she did not say so.
Checked[VERIFY: ERP system name]
Her notes said 'their ERP' and never named it. The marker was correct to flag the gap. She resolved it by not naming it: 'the ERP test environment' is what she and Marcus both call it on calls.
KeptAlternatively, we could explore launching on November 2 with a temporary CSV-based workaround
The two-option structure is the one thing from the draft she kept. She turned it into a numbered pair so Marcus could reply '1' or '2' from his phone, and put her recommendation directly under it.

Layer 4You

The email she sent

Subject: Launch date: decision needed by Friday

Hi Marcus,

We need to move the November 2 launch, and I'd like your call on how.

The order-tracking sync depends on read access to the ERP test environment, which we requested on August 28 and still don't have. Without it we can't run the integration tests, and I won't launch untested.

Two options:

1. Keep November 2 and launch without the live sync. Store managers keep uploading the daily CSV, and we switch the sync on once it's tested.

2. Move the launch to November 16. This holds if access arrives by this Friday, October 17. After that it moves day for day.

I'd recommend option 2. The CSV route works, but it means training the stores twice.

Could you let me know by end of day Friday? We set the sprint plan Monday, and the store training on October 28 and 29 has to move if we go with option 2.

If a call is easier, I can do Thursday afternoon.

Lena

ChangedWe need to move the November 2 launch, and I'd like your call on how.
The ask, in sentence one, in the words she would use on a call. The critique suggested 'I need your decision' as firmer. She kept 'your call' because that is how the two of them talk, and because it gives him the decision rather than demanding it.
Checkedwhich we requested on August 28 and still don't have
The one phrase the critique flagged as possible blame. She read it as Marcus three times and kept it. It is a fact with one date and no list, and the suggested softening, 'which is still pending', is the passive voice that hides who has it.
AddedI'd recommend option 2. The CSV route works, but it means training the stores twice.
Her opinion and its cost, in two sentences. Not in the draft at all. The second sentence is the reason, stated once, so the recommendation does not read as preference.
ChangedThis holds if access arrives by this Friday, October 17. After that it moves day for day.
The condition the draft dropped, restored as two short sentences. This is the sentence that protects her in three weeks if access arrives on the 22nd. The draft's 'we are confident' would have been quoted back to her.
RejectedI won't launch untested.
Where the draft had 'our team has been unable to complete integration testing', she put a stance. Zero apologies anywhere in the email: she had budgeted for one and found nothing in the message that was hers to apologize for.
KeptIf a call is easier, I can do Thursday afternoon.
The assistant's NEW line, kept verbatim. A specific window instead of an open offer, which reads as a lead with a calendar rather than a vendor hoping to be let off the hook. Marcus replied '2' on Thursday morning.

What the example shows

The ask is the email

The draft put the decision in paragraph five, behind 'if possible, it would be helpful'. The final puts it in sentence one. A reader on a phone between meetings decides in the first line whether this email is something to act on or something to come back to. When you need a decision, the decision is the subject line and the first sentence, and everything else is supporting detail.

An apology nobody asked for reads as an admission

Three apologies in the draft, for a delay that was not hers. She budgeted for one and sent zero. In a working relationship with history, an unearned apology does not sound gracious. It sounds like a confession, and it hands the other side a reason to treat this slip like the last one.

Context the draft must not use needs its own fence

She put the June slip in the raw material so the assistant would understand the stakes, then banned mentioning it. The draft mentioned it. Material you include for understanding but not for use belongs in a separate, labeled block ('background, do not reference'), or it stays out. A banned list is weaker than the pull of a relevant fact sitting in the notes.

A conditional date is a different promise from a flat one

'We are confident we can deliver by November 16' and 'November 16 holds if access arrives by Friday' are not two phrasings of one fact. They are two commitments. The draft quietly made the stronger one, in fluent prose that sounded fine. Dates, conditions, and who holds the next action are the first things to check in any work email an assistant touched.

Critique your own draft, then disagree with it

She pasted her rewrite and asked three narrow questions. Two answers suggested softenings, and she rejected both, with reasons. The third confirmed the condition on the date was explicit, which was the check she actually needed. A critique turn is a second pair of eyes you are allowed to overrule, and it works best when you fix the questions in advance.

The ledger: who did what

An honest tally. The point is not that the human did more. It is that the human did the parts that carry the authorship.

You

Every fact and date, pulled from the sent folder and the project plan
The decision to apologize zero times
The recommendation, and the one-sentence reason for it
The first sentence, and the choice of 'your call' over 'your decision'
The stance 'I won't launch untested'
The conditional date and the day-for-day consequence
Resolving the ERP [VERIFY] by not naming the system
Sending the email to herself first and reading it on her phone, as Marcus would

AI proposes

A restatement in turn 1 that correctly identified the decision as the point of the email, which the draft then failed to act on
The first draft, 283 words, rejected nearly whole
The two-option structure, kept and turned into a numbered pair
Three subject lines, one kept verbatim
A three-point critique of her rewrite: two suggestions rejected, one confirmation useful
One OLD/NEW bounded edit on the closing line, kept verbatim
A [VERIFY] marker on the unnamed ERP system, which was the right thing to flag

Questions

Why not just write the email herself from the start?

She mostly did. The draft took two minutes and showed her the obvious version of the email, with its apologies and its buried ask, so she could write against it rather than toward it. The subject lines, the critique of her rewrite, and the bounded edit on the last line were each worth their turn. Total time was 25 minutes, which is less than she usually spends on an email like this.

Is it dishonest to leave out the earlier slip?

Both parties know about June and this email is about a decision, not a reckoning. Bringing it up would have made the message about her rather than about the two options. Leaving out shared history is not concealment. Leaving out the condition on the date would have been, which is why that is the sentence she protected.

How do I stop an assistant from over-apologizing in work email?

Say so in the brief, in plain terms: 'This is not an apology. Nothing in it is my fault. Zero apologies.' Then expect to cut one anyway. The pull toward 'I sincerely apologize for any inconvenience' is strong, and the fix is a human reading the draft once for stance before reading it for anything else.

Should a work email ever go out without a human rewrite?

A routine note with no stakes, maybe. Anything with a date, a commitment, a client relationship, or a 'no' in it should be rewritten or at least read line by line for what it promises and who it blames. The draft above would have committed her to a date she did not control. It read fine. That is the problem.

Next exampleBlog post: from a bookkeeper's notes to a published post, annotatedBlog post, about 700 words

Keep going