Templates and examples for work messages.

Hi {name},

We missed the {time} deadline for the {deliverable}, which left your team without what you needed for {reader impact}. I am sorry for putting you in that position.

The corrected {deliverable} will reach you by {new time} today. The delay came from {specific internal cause}, and I am changing {specific fix} so the same handoff does not slip again.

Once it lands, a quick "received" is all I need, and I will confirm from our side as well.

Thanks for your patience,
{your name}

Hi {name},

Your {invoice/charge} was incorrect, and I am sorry for the time this cost you to catch. The corrected version is attached; the difference is {amount}.

Our billing system applied the {discount/rate} incorrectly when the renewal invoice was generated, and we should have caught the mismatch before it went out. We have voided the original invoice and issued the corrected one. You do not need to resubmit anything on your side.

You can disregard the earlier invoice. If anything on the corrected version looks off, reply here and I will sort it out.

{your name}

Hi {name},

Since {time}, {feature/service} has been {failure}, and I know this is affecting your team's work. I am sorry for the disruption.

We {containment action, e.g. paused the affected job} at {time} and are investigating the cause now. What we can confirm is that {confirmed scope} is affected; we have not yet confirmed whether {open question}.

We will send the next update by {time} {timezone}, even if the root-cause review is still in progress. You do not need to take any action on your side while we work on this.

{your name}

Hi {name},

The {deliverable} you needed is late, and it held up your {downstream step}. Sorry about that.

What is left is {remaining work}, and I can get it to you by {time} today. It slipped because I started it too late; from now on I will scope the time on receipt and flag early if it is tight.

If any part of it would help you now, tell me and I will send that piece first.

{your name}

Subject: Approval requested by {day} {time} {timezone}: {topic}

Hi {name},

Could you approve the attached {proposal} by {day} {time} {timezone}? We need approval before {dependency}.

I recommend {option} because {reason}. The tradeoff is {tradeoff}. Please reply "approve {option}" or "hold."

If you would like to talk it through first, I can find 15 minutes tomorrow.

Thanks,
{your name}

Subject: 10-min review requested by {day}: {object}

Hi {name},

Could you spend about 10 minutes checking whether {specific section} is accurate for {lens, e.g. the pricing logic} by {day}?

No need to edit wording or look at {exclusion}. Comments in the doc are ideal; a one-line "looks fine" by email works too. If this week is tight, {specific section} alone is enough.

Thanks,
{your name}

Hi {name},

Please send the revised {document} with the corrected {reference, e.g. PO number} by {day} {time} {timezone}.

We cannot {downstream action, e.g. process payment} until the {reference} matches the {record, e.g. contract record}. Once the corrected {document} is in, we will {next step} the same day.

If the timing is not workable, let me know what is realistic and I will adjust.

{your name}

Hi {name},

Would you be comfortable forwarding the note below to {contact}? No worries at all if the timing or fit is not right.

--- Forwardable note ---
Hi {contact}, I am {your name} at {company}. I am reaching out because {relevant reason}. It would take about {time} to see whether there is a fit; I am not asking for anything confidential or for an endorsement at this stage. Would you be open to a short conversation?

Thanks either way,
{your name}

Hi {name},

Following up on the approval request below. Could you reply with "approved" or "hold" by {day} {time} {timezone}?

We need the decision before {dependency}. If a full review is not possible this week, your call on the {section} alone is enough to unblock us.

Thanks,
{your name}

Hi {name},

We still need a decision on {item} to move forward this week.

If we do not have your go-ahead by {day} {time} {timezone}, I'll hold {deliverable} until next week rather than send it without sign-off. That keeps us safe but pushes the {downstream step} back by a week.

A one-line "go" or "hold" is all I need.

{your name}

Hi {name},

Closing the loop on {item}. Since we did not have a decision by the deadline, we are moving it to {next window} rather than proceeding without sign-off.

No action needed unless you want us to reopen it, in which case just reply here and I'll bring it back into this week.

Thanks,
{your name}

Hi {name},

Following up on my note about {problem}. Since I wrote, {new trigger} came up, which usually makes {specific issue} harder to manage.

One team in a similar setup handled it by {mechanism in one line}. I would not assume the same fit without comparing your workflow, but the pattern may be relevant.

Worth a 20-minute call to compare notes, or should I send a short example first?

{your name}

Subject: {specific operating issue}

Hi {name},

I am reaching out because {real trigger, e.g. your enterprise plan launch} usually puts more pressure on {specific issue, e.g. onboarding and support handoffs}.

When {plausible situation}, {specific problem} tends to become the bottleneck. We help {reader's role} teams by {mechanism in one plain sentence}. In one similar rollout, the team {concrete, non-guaranteed result}.

Is it worth sending a short example of how similar teams handle this? No worries if the timing is not right.

{your name}

Hi {name},

Looking at your current usage, {specific observation, e.g. exports are heavily used but the reporting workspace is not}, and with your renewal coming up in {timeframe}, I wanted to flag something worth a quick look.

Teams in a similar spot often {relevant pattern}. If that matches where you are, {mechanism in one line} could reduce the manual part.

Would 20 minutes be useful to compare notes before renewal, or should I send a short summary first?

{your name}

Hi {name},

Thanks for the time yesterday. To make sure I captured it: what seems to matter most on your side is {priority the buyer stated}, with {open question} still to work out.

Where we fit is {specific fit}. One risk I would flag honestly is {real rollout or decision risk}, which is worth planning for rather than glossing over.

Next step from my side is {owner and action} by {date}. Does that match how you want to move?

{your name}

Hi {name},

Following up on the proposal. From our conversation, the decision seems to come down to three points: {point one}, {point two}, and whether {value} replaces enough manual work to justify {first-year cost}.

If it would help, I can put together a short comparison on {the point most in question} so your team has what it needs to decide.

What is the best next step from your side?

{your name}

Hi {name},

Thanks for the details, and I can see the screenshot you sent. Here is what I found and what to try.

I checked the account tied to {identifier}. {Confirmed finding, e.g. The account is active, but the dashboard is failing to load its data}. Let's work through this one step at a time:

1. Open a private/incognito window and sign in again. Expected result: the dashboard loads normally.
2. If it is still blank, disable browser extensions and reload. Expected result: the left navigation appears.
3. If step 2 does not work, reply with a screenshot of the browser console and I will continue from there.

I will keep this thread open until it is resolved.

{your name}

Hi {name},

I reviewed the purchase date and subscription status on your account.

This charge is not eligible for a refund because the renewal occurred on {renewal date} and the refund window ended on {window end date}. I want to be straight with you about that rather than leave it unclear.

What I can do: I have canceled the subscription so it will not renew again, and you will keep full access until {access end date}. If you believe the renewal notice did not reach you, reply here and I will review the delivery record.

{your name}

Hi {name},

An update on the {feature} issue you reported.

What we know so far:
- {Confirmed fact one, e.g. Exports fail when the file exceeds 50 MB}.
- {Confirmed fact two, e.g. This started after yesterday's workspace migration}.

What we have not confirmed yet:
- {Open question, e.g. Whether this affects all workspaces or only migrated ones}.

What we are doing next:
- We attached your workspace ID, the export timestamp, and the error code to the engineering investigation.
- Next update by {time} {timezone}, even if the investigation is still open.

{your name}

Hi {name},

I am moving this to our {specialist team} because {reason frontline cannot resolve it, e.g. the processor returned a code we cannot override here}.

So you do not have to repeat anything, I passed along {details, e.g. the charge ID, timestamp, and the screenshot you sent}. Here is what happens next: {next step and rough timing}.

I will keep this thread open and send the next update once we have confirmation, so you always have one place to follow it.

{your name}

[Layer 1 | Notation] Clear the mechanical stuff
[ ] Removed raw markdown in prose (**bold**, ### headings, ---, link syntax, stray backticks)
[ ] Deleted assistant/tool residue ("Certainly!", "Here is a polished version:", "as mentioned above" with nothing above)
[ ] Turned stacked label colons ("The result: ...") into sentences
[ ] Used sentence case, not Title Case On Ordinary Headings
[ ] Cut needless precision (acronyms every reader knows; "approximately 3,167")

[Layer 2 | Wording] Put content back
[ ] Replaced "In today's fast-paced world" / "In conclusion" openers and closers
[ ] Cut empty significance words (testament, pivotal, underscores the importance)
[ ] Removed promotional gloss (boasts, seamless, cutting-edge)
[ ] Stopped hedging by default (may, might, arguably) where the draft has grounds
[ ] Returned inflated verbs to plain ones (utilize/leverage -> use, facilitate -> help)

[Layer 3 | Sentences] Shape and rhythm
[ ] Kept "not just X but Y" and rule-of-three lists only when each part has content
[ ] Varied sentence length instead of a uniform block
[ ] Repeated the right term instead of cycling synonyms (the company/the firm/the org)

[Layer 4 | Document] Structure and specifics
[ ] Turned persuade/explain bullets back into prose
[ ] Dropped numbered lists on content with no order, and unasked-for "Key Takeaways"
[ ] Confirmed there are names, numbers, conditions, or scenes somewhere
[ ] Ended on a judgment, next step, or fact, not a restated summary

- Formulaic framing
In today's fast-paced world, businesses must... -> Start from the subject, problem, or conclusion
In conclusion, this is a crucial step. -> End on a judgment, a next step, or the last concrete fact

- Empty significance
This is a testament to our commitment to quality. -> State what you did and what changed
These findings underscore the importance of X. -> Name the finding and what it means

- Promotional gloss / inflated verbs
Our platform boasts a seamless, cutting-edge workflow. -> Say what it does: cuts three handoffs to one
We utilize AI to leverage data and facilitate growth. -> We use AI to [do a specific thing]

- Hedging by default
This may arguably improve results. -> It cut resolution time from 2 days to 6 hours (if you have grounds)
Studies show this is generally effective. -> Name the source, or drop the claim

- Fake depth
It is not just fast but also flexible and scalable. -> Keep only the parts that carry real content

1. Run Layer 1 only. Strip markdown residue, assistant preambles, label colons, and needless acronym glosses
2. Read each paragraph opener. If it starts with "In today's..." or "This article will...", start from the subject, problem, or conclusion instead
3. Underline appraisal words (crucial, pivotal, seamless, testament). If the sentence survives without them, cut them and let the fact stand
4. Search for "utilize", "leverage", "facilitate", "not just X but Y". Return them to plain verbs and drop hollow contrasts
5. Read three sentences at a time. If they are the same length or cycle synonyms for one thing, merge, split, or repeat the right term
6. Step back to the whole document. Turn persuade/explain bullets into prose, and change a restated-summary ending into a judgment, next step, or fact

Writing templates

Email

How to Write an Apology Email That Rebuilds Trust

How to Write a Request Email That Gets a Fast Yes

How to Write a Follow-Up Email That Gets a Reply

How to Write a B2B Sales Email That Earns a Reply

How to Write a Customer Support Email That Resolves

Natural writing

How to Make Writing Sound Natural: A 4-Layer Checklist and Rewrites