Thursday’s message is a fee increase, and the compose window is empty. There’s no thread to react to. Ellen’s most recent exchange with this client is about a partnership return, so it leaves the register for Thursday open. Four messages in eleven years resemble this one, and two of those were about something other than money.
What’s in full working order is the list of seven sentences she taught Point on the mail she sends ten times a week.
Those seven run on this message. They read it as ordinary mail, and they fire silently.
The fourth part of this series left the list at seven lines. Every one is correct, every one is scoped, and every one was earned on a routine reply that came back nearly right. This part is about the message they’ll meet cold. Two things are missing from it and one thing is present that should be gone. Only the third belongs to this series.
Two shortages with different remedies
Separate them at the start. They show up as one problem, and the remedy for one of them does nothing at all for the other.
The thread is missing. A reply hands you the recipient, the subject line, the register, the topic, and the reason the message exists. A blank window leaves all five to you. The job changes from judging a draft to specifying one, and your instruction has to carry a settled question with a settled answer. That’s what composing an email from scratch works through, and this part leaves it there. The shortage is real, and it closes the moment you type enough.
The record is thin. The first part of this series put that down to frequency rather than difficulty. What you write weekly has hundreds of specimens behind it, so it lands close. What you write quarterly has almost none. Typing more leaves that gap where it is. Be perfectly specific about the person, the occasion, the outcome and the limits, and the draft still comes back built out of the middle of professional email. That’s the material left standing where your own specimens run out.
Confusing the two is the standard error, and the symptom is easy to spot. The first draft comes back wrong in a way you can’t name, so you add more instruction. The second comes back longer and no truer. You were paying for facts you already had. The thin record wants a different expectation rather than more input, and that’s the subject of the last two sections here.
A third question sits underneath both, and this series leaves it alone. What should the message say? Does the reason get given, and how much of it? Where does the number go against the explanation? Those are decisions about a client rather than about drafting. Telling a client about a delay is the closest worked example of that kind of message, and its sentences are in the right order for a reason. Settle all of that first. Everything below assumes you already know what you’re saying.
The rules were learned on the other kind of mail
Here’s the part that belongs to this series, and you see it only if you go looking.
Every line in Ellen’s list arrived the same way. A draft came back not quite right, she said one sentence about it, and the sentence got saved. Those drafts were the mail she actually gets: acknowledging a document, confirming a figure, answering a question about a deadline. So every scope clause in the list was written while she was looking at a routine message. Every one of them was tested by the twenty routine messages that followed.
All that testing stopped short of Thursday.
Take the line part four spent its length repairing. Fixed, it reads:
Say the date before I start explaining anything, in any message with a deadline in it.
That’s a good sentence. It names a finished state. Two people could agree on whether a draft obeyed it, and the repair that produced it kept it from evicting her greeting. On the twenty messages a month where Ellen chases a document by a date, it’s exactly right, and she’s stopped noticing it.
Thursday’s letter has a date in it. The new rate starts with the January work. Whether that counts as a deadline is a question the sentence leaves open, because she wrote it with the twenty messages in front of her. A scope clause is written against the mail you can picture. It covers a wider set than the one you were picturing. The difference between those two sets is exactly the rare mail. That’s why it takes years to surface, and why it surfaces on the message you can least afford.
If it fires, the letter opens with the number and the date, then explains. Plenty of people would send that. The trouble sits one step back. A sentence Ellen wrote in September, about chasing documents, just made the biggest structural decision in a message she’s been dreading for three weeks. That decision was hers, and she didn’t make it.
The rest of the list divides the same way. Her sign-off rule covers clients she’s worked with for over a year, so it fires. Priya’s letter gets signed Ellen, first name alone, on a document that may well go to a bookkeeper and get read twice. Her rule about client mail carrying her cell number fires too, and here it’s more right than usual. A fee letter is the one you want somebody to be able to call you about. Three of the seven stay quiet: one is scoped to a person, one to an engagement that closed in September, one to first replies on a new thread.
So Thursday’s count is two firing correctly and landing wrong, two firing correctly and landing right, and three staying quiet. That’s the shape to expect. The list is in good order. It’s a list that’s good at one job, being asked to do a different one without being told.
Running the list in the other direction
The third part of this series taught a lookup. A draft comes back wrong, you name the wrongness in concrete terms, and you walk the list asking two questions of each line. Could this one have fired here? If it fired, would it produce the thing you named? Six lines fall away on the first question in six seconds, and you have your answer in under a minute.
That search runs backward, from a bad draft to the line behind it. On four messages a year, run the same list forward, before anything is written.
The questions barely change. Could this line fire on the message I’m about to send? If it fires, do I want what it does? The first is the same reading you already know how to do. The second is new, and it earns its answer only on rare mail. On routine mail, repetition settled it months ago, and you’d be spending forty seconds on a question you’ve already answered.
What makes this worth doing here is the same thing that makes a good rule pleasant the rest of the time. A well-bounded rule runs quietly, which is the virtue part two closed on. On Tuesday that’s the whole point. On Thursday it means the two lines about to shape your letter shape it invisibly. Skip the forward pass and you’ll read the draft they produced as though it were simply the draft.
Ellen’s forward pass takes about forty seconds. It produces two lines to think about and five to ignore. That’s the whole technique. It asks what the rules will do here, and it leaves the list exactly as it stands.
Say the departure, do not store it
You’ve found the two lines, and the first move that occurs is to go and edit them. Leave them alone.
The rule is right. It’s been right on several hundred messages, and it’ll be right on several hundred more. Editing it narrows it to fix one letter, and the narrowing lands on everything else Point does with that line. That was part four’s argument about rewrites having an unknown landing place. It’s worse here, because you’d have to remember to undo the change, and the reminder never comes. By February there’s a line in the list that was bent around a fee letter nobody remembers, and it’s been quietly running your document chasing ever since.
The second move is to add a line. On fee increases, use my full name and credential. That’s true, it’s well scoped, it names a finished state, and it passes every test part two set. It’s still a bad idea, for a reason those tests are built to miss.
You learn a rule as fast as the message occurs, and no faster. A line about your routine mail gets tested twenty times before the month is out, so a badly worded one announces itself quickly and cheaply. A line about mail you send four times a year is a guess that waits a season for its first test. By then you’ve forgotten which letter prompted it and what you were reacting to. In between, it sits in the list. Every backward search you run reads it, and every search slows down there, because its trigger overlaps the sign-off rules already in place. You’ve bought a slow search in exchange for a rule you can’t check.
So the departure goes in the instruction for this message, and it dies with the message.
Full name and credential at the bottom, not just my first name. Do not open with the date.
Two clauses. They override the two lines that would otherwise have decided those two things. They leave the list untouched, and next Thursday they’re gone. This is the one place where being wordy is free, because a departure stated once has no future to be wrong in.
Sorting what belongs in the list from what’s a one-time repair with nothing recurring behind it is worked through here. The rare message is the sharpest instance of it. After a hard email the urge to make it permanent runs strong, and the frequency that makes the message hard is the same frequency that makes the rule unlearnable.
Most of this letter is the part nothing can supply
Part one took an ordinary reply apart into three piles. There’s the shape Ellen puts on everything, the facts the thread already holds, and the handful of things she settled that morning in her head. On that reply, the third pile came to three phrases out of ninety words.
On Thursday the third pile is the message.
The number. The date it starts. Whether the January work already in progress bills at the old rate or the new one. Whether the reason gets said at all, and whether that reason is three years of holding the rate steady or something about what the work has become. Whether there’s room to talk about it, or the sentence is flat. Whether the engagement letter comes up now or in a separate message next week. Every one of those is a decision Ellen made this week, and every one lives in her head alone. The thread, the sent folder and the list of seven sentences are all silent on them. What she types is what reaches the letter.
That fixes the ratio, and the ratio is the useful thing to carry away. A routine composed message takes an instruction of a line or two, because most of what it needs is already on the record. A hard one takes a paragraph, and a paragraph is the right amount of work. If your instruction for Thursday runs the same length as your instruction for a Tuesday, you’ve handed the specifying over. It gets done either way, out of whatever material is left.
There’s a second half with no equivalent in routine mail, and people leave it out because it feels strange to write. Half of a hard message is the part it holds back. Do not apologize for the increase. Do not compare it to anything. Do not offer to get on a call. Each of those is a decision with a reason behind it, well past a style preference. Leave the point unstated and the draft supplies the professional default, which for a fee letter is an apology you didn’t authorize.
Say the omissions out loud. They’re cheap to type. They’re the part you’ll be angriest about if they come back wrong, and the part with no other source.
Seven years is not the shortcut it looks like
Ellen has written to Priya for seven years. The instinct says that makes Thursday easier. It makes one thing easier and one thing considerably harder.
Easier: she knows how Priya reads, what she’ll ask, and that she’ll forward the letter to her bookkeeper.
Harder: her settled register with Priya is warm and short, and warm and short is a bad vehicle for this. The same six habits that land an ordinary reply, first name, answer first, nothing over two lines, make a fee increase read as breezy. Or as closed to discussion. Or as though Ellen thinks it’s a small thing. Part one’s warning was that an unexplained rise in formality reads as distance or bad news. On Thursday the bad news is real. A small rise in formality is accurate here, and it’s information Priya will use.
That’s the inversion worth carrying off this page. Anything drafting for you matches your baseline with this person, because the baseline is right on the other ninety-nine messages. On this one, the baseline is the thing to depart from. State the departure yourself, because you’re the only one with a reason to think of it.
State it the way part two says to state anything, as a finished state rather than a direction. A bit more formal leaves two readers settling it differently. Full name and credential, no first-line pleasantry, the reason in one sentence and only one. Where warmth belongs under pressure, and where it starts working against you, is its own subject in client email that stays warm under deadline pressure.
Seven years buys you knowledge about Priya. It buys no calibration at all about your own message. Composing an email from scratch works through the study this comes from. Kruger, Epley, Parker and Ng tested whether people can predict how their email will be understood. They built half their pairs out of friends and half out of strangers, on purpose, to see whether familiarity closed the gap. The gap stayed open. The friends were as overconfident as the strangers. Those people were undergraduates trying to convey sarcasm, so the size of the gap belongs to that experiment rather than to a fee letter. The direction carries over, and the direction is the part that matters on Thursday.
Reading a draft with no baseline behind it
Part one’s check was to say your own answer in one sentence before you read the draft. Then you’re comparing two independent positions rather than grading an answer against itself. That check needs adjusting for the trip, because Thursday has a position where a routine reply has a one-sentence answer.
Here’s the version that works. Before you open the draft, write down the three sentences you’d say if Priya called you about it. The phone version, which you can do, because you’ve been rehearsing it for three weeks. Then read the draft against those three and ask two things. Are all three of them in there? Is anything in there beyond those three, and would you have said it out loud?
The second question does the heavy lifting here, and it sits idle on routine mail. A reply that says one extra helpful thing is fine. A fee letter that says one extra helpful thing has conceded something.
Then read it once more in the reader’s order, from the top, and find the sentence where Priya learns the thing. Say the position out loud: fourth sentence, second paragraph. If you chose that position, you’re done. If one of the seven chose it, you already know which of the two it was, and you know it without opening anything.
The last check is about your own expectations rather than the message. You’re going to rewrite a third of this draft, and that’s the correct outcome. The thin record is doing exactly what part one said it would. Judge the whole arrangement on Thursday and you’ve judged it on the one message with the least behind it. The evidence is in the rest of the week’s mail, where it always was.
There’s one quiet compensation. Ellen has four specimens of this kind of letter. After Thursday she has five, in her own sent folder, written the way she decided to write it. Rare mail comes back sounding like somebody else because the shelf is bare, and sending one letter is what fills it.
Where the dial is when the rare message arrives
Point is a layer over the mailbox you already run, Gmail or Microsoft 365, with nothing migrated. Thursday’s letter leaves from your own address, on your own domain, and files into the sent folder you’ve been filling for years. A hard message travels the same route as an easy one.
That last sentence is worth reading twice, because it matters here. A message you start is written from an instruction you give in plain words, typed or spoken. Everything you’ve taught Point rides along with the message, unasked. The sign-off, the cell number, the line about dates. That’s the property part two sold as the payoff of writing one careful sentence. It’s the same property, unchanged, arriving on the message you’d have wanted consulted first.
The memory list is the same list, in the same place. Plain sentences, newest at the top. The ones you typed are marked as yours, and every one is editable or removable where it sits. One list covers all your mail, and it reads every message alike. That’s why the forward pass above is a reading habit rather than a setting.
How much Point finishes without you is a separate matter. That’s held per kind of work, on three positions: suggest-only at the bottom, review in the middle, fully handled at the top. Drafting starts in the middle, where the words are prepared and the sending waits for you, and it’s raised one kind of work at a time. What’s worth noticing on Thursday is where “per kind of work” draws its line. It separates drafting from filing from scheduling. The letter you send four times a year and the twenty you send this month are both drafting, so they sit together on one setting. If several good months on routine replies have you thinking about raising that dial, the rare message is the argument for where it should sit. It’s also the message that will never be in front of you when you make the decision.
Undo reaches what Point did inside your own accounts. A fee letter that has reached Priya’s mail server sits outside that, and no setting brings it back, which undoing what Point did is exact about. Of all the mail in this series, Thursday’s is the one where that boundary is worth reading in advance. The benefits page covers what’s already finished by the time you sit down.
What comes back on Friday
The letter goes at 4:20 on Thursday afternoon, in the shape Ellen chose, carrying two lines of instruction she’ll never type again.
Priya answers at 9:40 the next morning, and the reply is long. Two paragraphs about the increase. A question about whether the January work bills at the old rate or the new one. Something about the engagement letter, and a sentence near the bottom that reads as though she’s thinking about her options.
Ellen reads the summary first, the way she’s read everything since day three, and the summary is four lines. Three are right. The fourth says Priya has accepted the new rate and has a billing question. That’s what the message says, and it’s not what the message means.
So there’s a wrong thing on a screen again, and four parts of this series say to go and find the line behind it. This time there’s no line. Nothing in the list of seven is about summaries, the backward search comes back empty in twenty seconds, and Ellen’s correction goes somewhere her other corrections have never gone. A different surface, with a different memory behind it, and a different answer to how many times you should have to say it. Correcting a summary once is the last part of this series.