There is an email in your drafts folder, or more likely not even there, that you have composed in your head about nine times.
It is late. Not catastrophically, not in a way anyone has escalated, but late enough that the obvious opener no longer works. "Just following up" was true on day three. On day nineteen it reads as though you have not noticed what day it is, which is worse than saying nothing.
So you say nothing, and tomorrow it is day twenty.
Lateness compounds, and the compounding is social rather than practical
The practical cost of a late deliverable is usually flat. If the report was due on the 4th and arrives on the 12th, the person waiting is inconvenienced roughly the same amount whether it lands on the 12th or the 13th.
The social cost is not flat. It climbs, and it climbs specifically because of the silence rather than the delay. Every day without a message is another day in which the other person has to decide what your silence means, and the available interpretations get worse over time. On day two you are busy. On day twenty you are avoiding them.
That asymmetry is what makes the email hard. You are no longer writing about a report. You are writing about nineteen days of not writing about a report, and there is no opener that makes nineteen days feel like two.
The usual reaction is to try to make the message do more work. Explain the delay properly. Give the full context. Pre-empt the annoyance. The email gets longer in your head, and a long email is harder to start than a short one, so the thing that would end the problem becomes the thing you postpone.
The four sentences
A late email that works is almost always the same four sentences, in this order.
Name it, in the first line. Not "I wanted to circle back", which asks the reader to work out what this is about, but the thing itself: the report, the date it was due, the fact that it is not there. Naming it costs one sentence and it immediately removes the worst reading of your silence, which is that you had forgotten.
Say where it actually is. One clause, and only if it is true. "It is with legal" is a fact. "Things have been hectic" is not information, it is a request to be excused, and the reader has been busy too.
Give a real next step. A date you will hit, or a specific thing you need from them. This is the sentence people skip, and it is the one that ends the thread. Without it the reader has to reply asking when, which means the exchange is not over and you will be writing another one of these.
Stop. No paragraph of apology. The apology is one clause inside sentence one, or it is a second thing for them to read.
If you owe them, that is the shape. If they owe you, the same structure inverts and gets shorter: name the thing, say what it is blocking, ask for a date rather than the deliverable. Asking for a status is a smaller thing to answer than asking for the work, and a smaller ask gets answered sooner.
The reason to keep it short is not brevity for its own sake. It is that length reads as guilt, and guilt in a work email invites the reader to decide whether to forgive you, which was never a question you wanted to open.
A tool that writes it
Wasp has a free version of exactly this at meetwasp.com/write-the-email. Describe the situation in four short boxes, pick whether you owe them or they owe you, and it writes the email in that shape. There is no account, no signup, and nothing you type is stored.
It is worth being precise about why that exists on a product site. Drafting the email is the smallest thing Wasp does, and giving it away is not much of a sacrifice. The genuinely hard part is somewhere else.
The email is a symptom
Notice what had to happen for that email to become difficult.
Something was agreed. Probably in a sentence, in a thread about something else, on a day when it was obviously going to be fine. It never became a task, because it never felt like one at the time. It was just a thing you said.
Then the date arrived and nothing announced it, because nothing was watching. The commitment existed in two places, in your memory and in the other person's, and both of those degrade. Yours degraded into a vague sense that something was outstanding. Theirs degraded into wondering whether you were going to mention it.
This is the failure that produces the awkward email, and it is not a failure of intent. Nobody in that story was careless. Something got agreed in conversation and there was no system built to catch it, which is a description of almost every commitment anyone makes in a working week.
A task manager does not help here, because a task manager holds things you already decided to write down. The commitment that becomes the awkward email is by definition the one you did not write down, because at the time it did not look like the kind of thing that needed writing down.
That gap is what Wasp is for. It reads your email and your calendar, pulls out what you actually committed to, and holds onto it until it is done. When a date is about to pass it says so, while the message is still a normal one to send.
Wasp is not another task manager. Instead, it catches what never made it into one.
The best version of the email you have been avoiding is the one that goes out on day two, when it is still two sentences long and nobody has had to interpret anything.