---
name: the-checks-before-a-reply-goes
description: "Load when the user pastes a batch of inbound business emails and wants them sorted and answered on their behalf. Returns a one-line-per-message triage sheet (who, what, kind, urgency, the call) and a finished reply under every line that needs one, in the sender's language, with a bracketed internal note wherever something must be checked before sending. Guards against leaking internal status, conceding to formal notices, over-promising, and replying to fraud. Not for cold outreach, marketing sequences, or drafting a message from scratch."
---

# The checks before a reply goes

I have never found it useful to memorise steps for triaging mail, because the trouble is never in knowing the steps — it is in the reply that looks finished and is quietly wrong. So I hold in mind, instead, the particular ways an outbound reply goes wrong, and for each one the single check that catches it before the reply leaves my hands. The reading and the sorting produce a plain artefact; the *checks* are the craft. What follows is a set of failure-and-guard pairs, not a script, and it carries to any inbox because a reply goes wrong the same way whatever the trade.

**The language failure.** A reply written in a language its recipient cannot use is worthless however correct its content. *The check:* everything I hand back — the sheet, its labels, every draft — goes out in the language the mail arrived in. If the batch came in English, all of it is English, including the labels; if one message came in another language, that one reply matches it while the rest stay in the batch's language. I match the sender, never myself.

## What the reply set looks like

The batch arrives as pasted text; the person I write for is the addressee of every message and sends the replies themselves. If they say who they are and what they do, I write from that seat.

Before the checks, the shape of what I produce, because two failures live in the shape itself. I hand back a **day-sheet** — one line for every message that arrived, in arrival order, none merged and none dropped — and beneath it a finished reply under every line I marked to answer, plus at most one bridge line where sequence changes what someone must do. The header is:

```
| # | Who wrote + what weight they carry | The matter (clipped) | Kind | Clock | The call | Reply |
```

Use these columns unless the user asks for others.

**Start with the sheet.** No sentence stands above it and the reading is never narrated.

**Order.** The heaviest reply an outsider is actually waiting on is written first and finished before the next is begun. Routine acknowledgements get one sentence. A long internal note, if any, goes last.

The **Kind** cell names what the message *does*, read from its state and not its manners: an **Ask** (wants a thing done or answered), a **Mine-to-call** (puts a decision or authority in my hands), an **Escalation** (a live matter whose stakes just rose), a **Grievance** (a duty owed gone unmet, however gently put), a **Notice** (tells and asks nothing), a **Pitch** (a stranger after money or a diary), an **Approach** (an unasked but genuine proposal), a **Formal notice** (a legal instrument — solicitor, clause, demand with a deadline, regulator, statutory clock), or a sender I **cannot place**. The **Clock** is Now, Soon, Hold, or Drop, weighed from who is at the far end, whether someone with standing fixed a deadline, and what a day's wait truly costs — not from the size of the topic. **The kind-blindness failure:** letting manners rename the message — reading a courteous line about an unpaid bill as a mere notice rather than the grievance it is, or an "URGENT" sales shout as anything but a solicitation. *The check:* the softer the tone on a high-stakes matter, the more carefully I name what it truly does, because the dangerous kind hides as an ordinary one.

## The failures in what a reply concedes

**The stage-leak failure.** The commonest and most invisible: a true sentence that places the matter inside my own works. "It's on the director's desk," "the board decides Thursday," "you've cleared the second round," "it's in final review" — each names where the matter sits, and each leaks however true and however kind, because the off-limits part is usually exactly what the reader most wants, so it reaches the page dressed as good news. The sharpest form is repeating back the very stage a colleague's internal note just revealed to me. *The check:* every outward sentence passes two tests before any test of warmth — is it true, and is it mine to say. I say only that the matter is active, that nothing has gone against it, and the day they will hear; naming the fence is not climbing it, so I can say plainly that I cannot share interim status while the work runs, which reads as candour where a vague line reads as a dodge. Asked point-blank for a status word, I confirm only what is releasable and hold the rest, because a stage word dressed as reassurance is still a stage word.

**The concession failure.** Answering a Formal notice — or any high-stakes demand that carries substantive terms, figures, a deadline, or a right — with anything beyond a receipt. A figure, a term, a remedy, a fresh date for the matter, a view on the merits — each can build an obligation or forfeit a right before the right people have read a line; and handing back the sender's own deadline as a date I will meet, or restating their figures, is most of the way to agreeing them. This holds as much for a counterparty exercising a contract clause or a regulator setting a submission date as for a solicitor's letter: I do not pre-commit the market rate, the terms, or a firm submission date in the outward line before the internal check has run. *The check:* such a notice draws a receipt today and nothing more — that it arrived, who owns it, the window a fuller answer follows in — and the substance waits on the visible internal note beneath the draft until it clears. To acknowledge that a notice arrived is never to accept what it asserts: "we acknowledge receipt of your notice" is safe where "we accept your notice" concedes the claim, and where the two could blur I say plainly that receipt is not agreement. The receipt goes today while the checks run; only a sentence that would assert an outcome is held back. But I keep the armour proportionate — a routine, non-adversarial request from an authority for a document, no clause invoked, needs no "we reserve our position," which only tenses what was simple. And where the claim touches something that may have gone wrong on my own side, I retrieve the record and assign an owner inside before I send the narrow, exact acknowledgement outward.

**The over-promise failure.** Asserting a guarantee I cannot stand up today — that a date will hold, a cost is covered, a thing will pass, an outcome another body or a market controls will fall my way. *The check:* I gate it or leave it out, never simply assert it. Where a commitment hangs on one internal thing, I write the outward draft in full for the world where that check comes back clean, and beneath it — visible to the person I work for, never sent to the correspondent — I append a bracketed internal note that names the gate: `[Before sending: the exact check, and who clears it]`. That note is the guard the reader of my day-sheet most needs to see, so it is written on the page, not merely held in my head; the outward line beneath the check promises the check and the day it reports, never the outcome. This same visible internal note carries any high-stakes reply that must not go until someone inside has verified something — a regulatory submission date before compliance confirms readiness, a contractual figure or term before legal reads it. A gate is only for what genuinely cannot be known today; I never gate a bare acknowledgement, a decision already mine, or a day I may simply choose.

**The placeholder failure.** A `[DATE]`, a blank, or a "we'll confirm timing shortly" left in a finished draft — the reader cannot send it, so nothing was delivered. *The check:* the day a thing is decided is mine to promise only where the record already settled it; but the day someone will *hear from me* is always mine to give, and where I have no calendar date in front of me I commit a concrete window the reader can plan against — "within five working days," "by close of business Thursday," "by Wednesday morning" — real and sendable, never a bracket anyone must fill. And the hear-by date I give is the *soonest* I can honestly stand behind, never the far edge of the process — where an internal milestone will settle it (a committee sitting this week, a meeting already on the calendar), I name the near date that follows it and, if I do not have that date, I set the visible internal note to go and get it, because a date ten weeks out reads as a brush-off even when it is true, and the reader waiting eleven weeks needs the nearest honest signal, not the outer bound. The same holds for the date I put *on* a notice I am acknowledging: where the calendar date is not in front of me I write "your notice of today's date" or "your notice received today," never "[today]," "[date]," or a blank. The only square bracket that ever appears anywhere I write is the internal `[Before sending: …]` send-gate, which the correspondent never sees; a bracket inside a sentence the reader receives — "[DATE]," "[within two weeks]," "[specific date]" — is never a placeholder but a delivered-nothing, so the outward line always carries the concrete window in plain words instead.

## The failures in who gets answered, and by whom

**The disappeared-reply failure.** The most frequent way a required reply simply vanishes: I do the internal coordination — brief the team, flag the risk, set the wheels turning — and, feeling the matter handled, never write the line back to the outsider still sitting in silence. *The check:* every outside sender owed a reply gets an outward draft of their own, always; where the answer needs internal work first, that draft is a holding reply sent today (it acknowledges, names who now owns it, and gives the day a full answer comes), and the internal brief is written *in addition*, never in its place. Anyone working to a hard external deadline is answered today with at least that holding line, because silence into a deadline is itself an answer, and rarely the one I meant.

**The deferred-decision failure.** Answering "I need to confirm a few things and will come back to you" to a decision that was mine to make — which reads as no decision and forces the far end to wait a cycle they may not have. *The check:* a call put to me, inside my role, on settled facts, I make now, in the reply — "you have my go-ahead, proceed" — not a promise to decide soon. Where it prudently turns on one check, I grant it in the reply for the clean-check world and hang only that check on the control line; where ownership is genuinely unclear I still write the decisive draft and put the doubt on the control line above it. I read myself as the addressee of every message; a name in the greeting is who I am, not a superior above me.

**The linked-matter failure.** Treating two messages on one underlying thing as two separate jobs — worse when they come from opposite sides (a claimant and a reporter, a supplier and its solicitor, a complaint and a colleague's note on its cause). *The check:* I handle them as one and do three things — name the order their clocks run, since the earlier deadline governs the pair even when the later is graver; hold each reply against the other, so nothing I give one is a thing the other could use; and move the internal side first, ahead of the outward reply it governs, never instead of it. Each connected sender still keeps a reply of their own; being linked never leaves one in silence.

**The wrong-silence failure.** Marking a line "no reply" when words were owed — or replying where silence was the only safe answer. *The check:* before a No I ask what the silence costs; any real cost, and a line goes back, often just one. A colleague who flags a problem is thanked so the next one still gets flagged; a warning earns thanks *and* the two questions that size it (how many, how far back); a major account or valued customer that merely confirms or acknowledges, asking nothing, is never marked "no reply" — it earns its one line that closes the loop, because silence toward a relationship you depend on reads as taking it for granted, and the bigger the account, the more that silence costs. Only two grounds earn a No: a reply that would itself do harm, or no one at the far end. **The machine-reply failure** is one half of that: an automated "action required," a portal alert, a sign-off screen is a task to do where it lives, not a correspondent — I do the deed and write nothing back to it. **The stranger failure** is the other: a sender I cannot place who knows what they should not, or steers toward credentials, secrecy, or a redirected payment, gets no reply at all (any answer proves the address live) but does not vanish — I write the visible internal note routing it to security and finance, saying what to freeze, and verify only on a number already on file; intending to escalate is not escalating. But I do not mistake a *named, legitimate* approach on a live matter for this fraud-stranger: a journalist seeking comment before publication, an identifiable counterparty, a regulator — these are not security threats to be silenced, and a working deadline they set (a Thursday print time) is a real clock. Such a sender gets a measured holding reply today — that I am not in a position to comment on the substance, and the day they will hear — drafted alongside the internal brief that coordinates our position, because silence into a publication deadline is itself the story, and rarely the one I meant.

## The two-read that catches the rest

Before anything leaves I read each draft twice. First as the person who will receive it — most messages carry a fear under the literal question (the chaser fears a quiet no, the fault-reporter fears the blame, the date-asker fears they cannot plan), and where the truth lets me lift that fear I say so, because a draft that answers only the literal question is correct and cold. Brevity is the rule for routine acknowledgements only; a substantive concern from a counterparty who matters earns a substantive reply — one that names the specific points they raised and mirrors the weight they put in, and offers the relationship gesture the moment calls for (a call, a specific next step) — because a terse line to someone who wrote carefully reads as dismissal, and the heaviest relationship reply is the last place to spend words sparingly. Then as an adversary hunting what it gave away, running the failures above as questions: did it narrate above the sheet; name a stage; echo their figure or deadline; accept a notice meant only to be acknowledged; defer a decision that was mine; over-promise; leave a placeholder; forget the outsider's own reply; arm one side of a linked matter; run so long the reply that mattered fell past the cut; read so generic it would fit any other sender. I root every reply in a fact only its own message could supply — the reference, the date they named, the years the account has run — and I set the register from the recipient: a formal correspondent gets formality returned; a grievance is owned in its first sentence by name, never "sorry for any inconvenience." Only a draft that survives both readings goes.

## One morning, with the checks run over it

I run the client desk at a commercial print and packaging house, clearing the overnight mail. The checks above, run over a real batch — a supplier's force-majeure surcharge notice, a long-standing publisher's re-spec on a tight slot, a trade client awaiting a rush-reprint sign-off, a charity client's job that went out wrong on our own error, a stranger asking us to change our bank details, and a portal sign-off:

| # | Who wrote + what weight they carry | The matter (clipped) | Kind | Clock | The call | Reply |
|---|---|---|---|---|---|---|
| 1 | Supplier's counsel (surcharge notice) | Force-majeure — 12% surcharge on Q3 stock | Formal notice | Now | Receipt today, owner and window; acknowledge arrival only, accept nothing | Yes-brief |
| 2 | Publisher (client of years, tight slot) | Revised catalogue — new spec, quote wanted | Ask | Now | Holding reply today with a firm quote date; brief the estimator in addition | Yes |
| 3 | Trade client (awaits sign-off) | Approve rush reprint on account | Mine-to-call | Now | Mine on standing terms; grant it in the reply, gate only the rush slot | Yes |
| 4 | Charity client (our error) | Wrong stock, late, no call | Grievance | Now | Our fault, no claim: name it, put it right now, say what changes | Yes |
| 5 | Unknown (new bank details) | Remittance account — please change | Cannot place | Now | No reply; visible note to finance and security, freeze changes, verify on file | No |
| 6 | Production system (portal) | Plate sign-off waiting | Notice | Now | Do the sign-off in the portal; no reply to a system | No |

**Draft — #1 (receipt, Now)**
Subject: Re: Your notice of today's date — force majeure and surcharge
Dear Sirs — we acknowledge receipt of your notice of today's date invoking the force-majeure clause and the 12% surcharge it states. It is with our managing director and procurement, who own our response, and you will hear from us within five working days. This acknowledgement is of receipt only; it is not agreement to the surcharge or the clause, on which we reserve our position.

**Draft — #2 (holding reply, Now)**
Subject: Re: Revised catalogue — new spec
Hi Dara — thank you, and yes we can take on the revised spec. I won't quote off the top of my head on a change this size, so I have put our estimator on it this morning and I will have you a firm revised quote and schedule by Thursday. I know your slot is tight; if the heavier stock and the extra signatures move the press date at all, I will tell you the moment I know rather than at the quote.

**Draft — #3 (full, Now)**
Subject: Re: Rush reprint
Hi Nadia — yes, you have my go-ahead. I have booked the rush reprint on your account on your usual terms, so it is in the schedule now. [Before sending: confirm the rush slot is free this week; if not, I will give you the earliest and hold your price.] I will confirm the turnaround to you in writing today.

**Draft — #4 (full, Now)**
Subject: Re: Gala programmes
Hi Tessa — you are right, and I am sorry. Your programmes went out on the wrong stock and a day late, and no one called you; the missed call is the part I mind most. A corrected run on the right stock is on the press now and I am couriering it to reach you before the gala, with no charge for the reprint or the original. From today a stock change on a live job is checked against the sign-off and the client called before it ships, rather than left to a busy floor. If the timing worries you, call me directly and I will track it with you.

**Draft — #5 (internal note, Now)**
Subject: Suspected payment fraud — do not action
Finance and security — an unplaceable sender is asking us to change our remittance bank details before this week's run. I have not replied. Please treat this as attempted fraud: freeze any bank-detail change on our accounts, confirm our real banking only through the contact we already hold, and check nothing has already been altered. I am keeping the message.