Forward, add context, send: the email context note that gets read

The bare forward arrives like a puzzle: a subject line that says Fwd, a wall of previous messages, no note, no question, and, at the bottom, the sender's minimal sentence, or none at all. The reader has to reconstruct the whole chain to know whether the mail matters, and most readers, at most hours of the day, choose not to. The forward dies unreconstructed. An email context note is the one-line difference: not a summary of the thread, but the sentence that says why this thread is landing in your inbox and what it needs from you. The one line is what the reader keeps: the thread is the detail, and the line is the decision.

The bare forward has a structural problem beyond laziness: the sender's context has been building for days, and they cannot see that the reader has none. The sender lives in the thread, the receiver arrives out of nowhere, and the gulf is invisible from the sender's side. That is why the fix is not a longer forward, it is a stated purpose. The note that says why it matters is the bridge across the gulf, and the reader's first decision, open or ignore, is made at the notification, not inside the thread. The gulf widens with the thread's age: a three-day-old thread carries three days of private shorthand, and the shorthand is the part no reader can reconstruct.

The cost of the puzzle is paid twice: by the reader, who reconstructs or skips, and by the sender, who gets silence and then asks again. The ask again is the common pattern, and the second ask costs more than the note would have, because the thread is now colder and the reader's patience thinner. The bridge note is a small privacy from the replay cycle: one sentence now is cheaper than two sends and a pulled favor. The second ask also reads differently: the first ask was a request, and the second ask is evidence the first one failed. The reader who ignored the first forward answers the second from guilt, which is slower and colder than an answer to the note.

Two slots, and the formula fits in two lines. Slot one, why it matters: the decision, the deadline, the risk, who asked, whatever makes the thread real for this reader, in two clauses. Slot two, what is needed: the ask, one verb, one date, the answer you want or the action you want. The note reads: this thread is the pricing discussion from the April call, and it needs your view on the split by Thursday. Two lines, and the reader can decide to open or to defer, which is a decision the reader can be trusted to take. The formula keeps the same shape whether the ask is a review, a decision, or a name: the why in two clauses, the what in one verb and one date, and the thread below for the detail.

The why-slot carries the context, the what-slot carries the question, and the two are not interchangeable. A note that says only why it matters gives the reader a lecture; one that says only what is needed gives an order without a reason. The note is the pair, and the pair is what makes the forward a request instead of a relay. If you cannot say the why in one breath, you are forwarding out of habit rather than need, which is the moment to pause and reconsider the forward. The pair also sets the shape of the reply: the reader who gets both slots answers in the second one, with the verb and the date, and that answer is the mail's closing line.

Bridge notes have a length problem in the other direction: the summary. Do not summarize the thread, the reader has the thread. The note is the frame, and the frame contains the frame, not the picture. A paragraph of summary is the bridge note's own failure mode: it spends the reader's attention on the past of the conversation rather than the ask of it. Two lines, two slots, and then let the thread speak. The test for the summary is the first few words: a note that starts with as we discussed or to summarize has slipped. The bridge starts with this thread, this decision, or this deadline, which is the reader's present, not the conversation's past.

The dictation trick is the order: paste the thread first, then speak the bridge, rather than composing the note in the reply window and searching for the paste. Once the thread is in place, the note speaks over a settled stage, and the words come out with the ask in view. The second benefit: the engine hears the note as its own piece, and the draft arrives with the two slots intact, ready to be filled with the specific date and name that belong to this ask. The order has a third benefit: the paste is the reason the note exists, and the dictation that follows carries the intention to send, which is exactly the setting a bridge note needs.

Dictating the bridge out loud is also the review. The ear catches the vague ask, the ask that says "can you take a look" when the real need is a decision by Thursday, and it catches the note that spends the first line on background and the second on nothing. For a reader who is one of five recipients, the note is the only text of yours they will read, and hearing it is the fastest quality check the format has. The ear also catches the wrong recipient: the note that asks for an answer when the recipient is the one who supplied it, which is the most common misfire of the crowd forward.

Name the ask in a form you can time: a review, a decision, a meeting slot, or a name. If the ask is just a look, the note has a hole, and the hole is where the thread goes to wait. The discipline of the dictation is the same as the discipline of the sentence: one verb, one date, one name. The bridge that names the ask is the bridge that ends the wait, and the wait is the only real currency of the forwarded thread. The ask needs a span as well as a verb: a review by Friday, a decision before the board packet, a meeting slot this week. The span is what the reader can schedule, and the absence of one is the hole the thread falls into.

The story of the week-old thread. A program manager forwards a thread about a delivery exception, written by a vendor, buried in fifty lines about a previous issue, to six stakeholders, with no note. Silence. The manager follows up after two days with a second forward. One stakeholder replies that the thread was unread; the rest stay silent. The exception is quietly unresolved, and the manager schedules a call to solve what the mail should have solved. The details matter: the exception's date was two paragraphs down, and the manager's second forward said the same nothing. The call was scheduled for the next week, which is the week the exception became a problem.

The rewritten forward carries the bridge: this thread is the vendor's delivery exception, and it needs your decision on whether we accept the new date before the Friday board packet. Four stakeholders answered the same afternoon, two with the decision, one with a question the manager answered in two lines, and the sixth deferred with a reason. The call did not get scheduled; the thread did its job on the first pass. The difference was not the manager's authority, it was the reader's first question being answered before it was asked. The sixth deferral was not a loss: a deferral with a reason is a decision postponed, and the reason was the input the Friday packet needed.

No elaborate aside is needed to deliver the lesson: the manager's time was not saved, it was returned. The Friday packet had the answer in it because the thread closed in a day, and when the same pattern repeats across a team, the return is measured in the morning hours that used to disappear into follow-up. The bridge note is the cheapest discipline on the stakeholder list, and the one that pays the most per line. The same week, the manager's other forward, still sent bare, produced the old silence, and the comparison was the real lesson: the note was not a courtesy the manager granted, it was the mechanism the thread ran on.

Some forwards are not forwards, they are escalations wearing the wrong clothes. The escalation has a decision, a risk, and an owner who needs to act, and a forwarded thread with a two-line note is the wrong vehicle: the reader is asked to find the decision inside a history. The write-up is a short paragraph that stands outside the thread, states the decision and the options, and points at the thread for the detail. The escalation hygiene rule is simple: if the ask is a decision, forward with a bridge note to a peer; write it up for a decision-maker.

The second hygiene case is the crowd. A forward addressed to six people with no note is a request for one of them, and nobody in the crowd moves until someone does. The bridge formula handles the move, but the hygiene handles the count: the same forward with a named receiver and a cc for the rest is the version that answers. The named receiver is the difference between a decision and a discussion, and the discussion is what the week-old threads are made of. The naming has a second advantage: the cc reader knows who decided, and the thread records it, which is the difference between a decision thread and an argument thread six replies later.

The third is the legal and financial escalations, where the write-up is not optional, it is the discipline of the record. These get the written summary with the ask, the thread attached as an appendix, and the date named in the summary's first line. The record is what the team carries into the postmortem, and the forward that left no record is the one that becomes a meeting. The record also protects the colleague who reviews it: a write-up that names the ask and the date is the document the reviewer can quote, while a bridge note on a legal thread leaves the chain to be rebuilt from fifty lines. The rule of thumb is the stakes: when the thread carries a contract, a payment, or a complaint, it gets the write-up.