Ellen has found the line. It’s hers, and it’s scoped the way she meant it. It also produced a draft she wouldn’t have sent. The repair is about thirty seconds of typing. There are two versions of it: one costs nothing, and one she pays for in March.
The third part of this series ended with the search finished. Here’s the line:
Put the date in the first line of anything with a deadline in it.
The draft it produced opened by putting March 17 in front of a client of seven years, with no greeting at all. Point read the thread right, and followed the sentence exactly as written.
This part is what to do to that sentence. The answer is smaller than it looks. Most of the sentence is sound, and one phrase in it is the trouble.
The word, not the sentence
Start with the smallest span of the line you could change to get a different draft. Work on the words themselves. The idea behind the line stays.
Ellen’s line has three parts, and one of them is in trouble. Anything with a deadline in it is the trigger, and it works. It’s also the clause that let her rule six other lines out in six seconds. The date is what she wants said, and she still wants it said. That leaves in the first line, and that phrase is the whole problem.
It’s worth being exact about why. The same fault comes back, and it’s easy to spot once it has a name. In the first line claims a location in the message, and a location holds one thing. Everything else that wanted the top of that message is now competing with a written instruction. The instruction wins, because the greeting is only a habit. The rule simply took the space the greeting was sitting in.
So here’s the check. When a draft goes wrong because something is missing rather than inaccurate, look first for a line that claimed the place the missing thing used to sit. The opening sentence is scarce. So is the subject line, and so is the last line before your name. A rule that claims one of them quietly evicts whatever was there, on every message it fires on.
A limit behaves differently. Keep it to two paragraphs holds the message down while every slot stays open. That’s why the ceiling-style rules from part two age well, and the position-style ones age badly.
The fix is to say the same thing as an order rather than a place:
Say the date before I start explaining anything, in any message with a deadline in it.
Nothing is evicted. The greeting keeps its place, because the sentence now ranks two things against each other and leaves the rest of the message alone. And it still passes the test that made the original worth writing: two people can read a draft and agree on whether it was followed.
That’s the edit. One phrase out, one phrase in, and the list stays the length it was.
Why the second line is the expensive one
There’s a faster move, and it’s the one that comes to mind first. It’s honest, and it deserves a real look rather than a wave of the hand. She could leave the original alone and add:
Always keep the greeting.
It’s true. It takes four seconds. And it lets her leave a sentence she wrote in peace, instead of reading it back and admitting she worded it badly, which is a real reason people pick this route.
Here’s what it buys. On the panel, the two lines sit there agreeing with each other. They collide weeks from now, on one message where the greeting and the date both want to be first. The draft satisfies one of them, and she’s left guessing which. She’s looking at a draft and arguing with a pair of sentences rather than one.
There’s a second cost, and it belongs to this series more than to lists in general. The lookup in part three worked because most of the list fell away on the trigger clause alone, before she had to think about what any rule does. A patch line always has a trigger that overlaps something already in the list, and overlapping triggers are the ones you have to stop and read properly. So a patched list runs longer. It also reads slower per line, in the one place you need it fast, which is the morning something goes wrong.
And the panel stores both lines the same way, with nothing to mark which one was the repair. In October she finds two sentences about how a message opens. Both are plausible, and both are hers. They read as two considered decisions rather than one decision and a patch. The general form of this argument, for any list of learned rules and Point’s among them, is worked through here.
Rewrite from the draft rather than the line
The practical trap is the edit box. The old sentence sits there, and a sentence in an editable box invites you to fiddle with the words. First becomes opening. Put becomes lead with. Twenty seconds later you’re negotiating with a sentence written by a version of you who had a completely different message on the screen.
Look away from the box. Look at the draft that’s wrong, and say what the finished message should have looked like, as though nobody had ever written a rule about this. Then read the old line once and ask one question: does the new sentence still do the job the old one was doing?
Two checks, and they run in opposite directions. Forward, the new line has to fix the draft in front of you. Backward, it has to cover whatever made the original worth writing.
The backward check has two ordinary outcomes. Sometimes you can’t remember what the original was for at all, and letting it go is the honest answer. A line you’d have to rebuild a reason for is a line to remove, which is the standing default for any rule you cannot justify while reading it.
Sometimes the new sentence misses the old case, and then you’ve learned something. Ellen wrote hers in a week she was behind. The complaint underneath it was clients missing dates that sat at the bottom of long replies. Her new sentence still handles that, because a date said before the explaining is already near the top. The old job survives the rewrite, so there’s nothing to keep.
Two rules about dates become one
Part three’s stand-back read of the list found a cluster. Two lines about dates, which is one thing she cares about, stated badly and then patched. The second line is:
Do not bury a deadline at the bottom of a long email.
Read as an instruction rather than as a sentiment, it has never worked. Two people can read the same draft and disagree about whether it buried anything, or about whether the email was long. So nobody can tell whether this line ever fired. It’s a wish that got saved, and it has sat in the list adding one more line to read during every search.
So the merge isn’t a joining. Nothing gets stapled to anything with an and. One line gets rewritten and the other gets deleted. That’s the usual shape: in a cluster of two, one is generally the wish, and the wish is what goes.
The test for whether two lines are really one lives in the drafts, rather than in the subject they share. Ask whether either of them says something about a finished message that the other leaves out. Try to name a draft that satisfies the line you’re keeping and breaks the line you’re deleting. If you can name one, they’re two rules. They both stay, and what they need is better scopes. If you come up empty, the second line was doing no work.
Ellen comes up empty. Any draft that says the date before the explaining has already surfaced it. Eight lines becomes seven.
Her two sign-off lines are the other kind, and they’re worth a moment, because from a distance they look identical. One says which version of her name goes to whom. The other says client mail carries her cell number. A draft can obey either and break the other easily. So those two are genuinely two rules about the same three inches of the message, and merging them would produce one sentence doing two jobs. They stay as they are.
Nothing happens next
She saves the line, and that’s the end of the visible part. The new sentence runs on the mail that arrives from here, rather than on last week’s, so the test is the next message of that kind. The next message with a deadline in it might be Thursday.
This is where an edit quietly fails to land. A rule with its edges on is invisible when it fires, which part two counted as a virtue and is a hazard here. An edit that worked and an edit that missed look the same from the outside. If Thursday’s draft still opens with a date, Ellen fixes the greeting by hand in four seconds and sends it, exactly as she would any other morning. The fact that she was supposed to be watching for something stays out of her head.
So name the test before you close the panel. One sentence, said in your head: the next reply with a date in it, check the greeting survived. Ten seconds of setup, for a check that has to exist before the thing it checks arrives. That makes it the sibling of the habit in part one, where you say your own answer before you read the draft. Both work because you set them up in advance. Both feel like a waste right up until the morning they pay.
If Thursday’s draft is still wrong, she has one suspect. That’s the whole return on changing one line at a time.
Removals batch, rewrites do not
Two pieces of advice pull against each other here, and it’s worth having the resolution straight before your first scheduled review of the list.
One change per occasion, because two changes at once leave you two suspects and one draft to tell them apart with. Also, if a month’s reading of the list ends with every line still in it, the reading was for show. Follow the first strictly and the list stays the length it was the day you started. Follow the second freely and you have six live changes and one week to attribute a bad draft to.
They apply to different acts. A removal has a known landing place. The line stops firing, and the decision lands back on what your sent mail already shows. The worst case is a slow drift toward your ordinary correspondence, rather than a surprise, and it’s the same landing place for all six lines you cut. Why taking a line out does not leave a hole is the fuller version of that.
A rewrite lands somewhere you can only guess at, because a rewritten line is a new instruction running for the first time.
So cut freely, and rewrite one at a time. Ellen’s Tuesday is one deletion and one rewrite. That’s a full morning’s work on the list, and it took her under a minute.
When a sentence cannot be saved
Some lines end here. You narrow one, it goes wrong somewhere else, you narrow it again. By the third attempt, the honest reading is that what you want lives outside a standing instruction. The three-attempts rule is the general form, and the move it calls for is to delete all of them and handle those messages by hand.
There’s one thing about doing that to a rule already in force that people leave out. Deleting a line you’ve leaned on for two months carries a cost of its own. That edit used to be automatic for you, and you’ve spent two months letting the rule make it, so it takes about a week to come back as a habit. A few messages go out in a shape you’d have changed. That’s the actual price. It’s small, and it beats keeping a sentence whose behavior is a guess, firing on messages you won’t be reading.
The harder case is the one where every wording fails, because what you want changes with the message rather than with the audience or the occasion. Your scoping is fine there. What you’re looking at is a decision, and the line between a habit that can be taught and a decision that stays yours is the one part one drew before any of this started. The list stops short of that line by design.
Where the sentences live
Point is a layer over the Gmail or Microsoft 365 mailbox you already have. Everything stays where it is. The address on your business cards is still the address, and the sent folder is the one you’ve been filling for years. That last part matters here more than it usually does, because a deleted line hands its decision back to that folder.
Everything Point has been told sits in one panel as plain sentences, newest first. The lines you typed yourself are marked as yours. Reword any of them in place, or take one out. Adding one is a sentence and nothing else. The wording in the box is the wording that runs, which is what makes a two-word change a real repair rather than a suggestion.
One property of a saved rule deserves a second look at editing time. A saved rule goes wherever Point is acting for you, rather than living inside drafting. That’s the reason one sentence is worth writing carefully, and the reason an edit reaches past the screen you made it on. Narrow a line to fix a reply, and you’ve narrowed it on everything else Point does with that line. Widen one, and you’ve widened it in places you were miles from thinking about when you opened the panel. Both are fine. It’s simply worth knowing that the reach of an edit is the reach of the rule.
The list leaves the dial alone. How much Point finishes without asking is a separate setting, kept per kind of work, and it runs from suggest-only at one end to fully handled at the other. Drafting starts in the middle position, where the words get prepared and the sending waits for you. Cut six lines or add six, and the dial sits where you set it. The dial is decided one kind of work at a time.
And editing works forward. A rewritten line changes what gets prepared after you save it. This morning’s drafts stay as they are, and so does anything already gone. Undo reaches what’s still yours to reach, and a message sitting on somebody else’s server is past that point, which undoing what Point did is exact about. The benefits page covers the rest of what’s already done when you open the inbox.
Seven lines
The list is shorter than it was on Monday. One sentence has two words changed in it. One sentence is gone, and Ellen has added nothing. That’s what a good session on the memory list looks like from outside. It’s why the count tends downward on the mornings you’re paying attention, and upward on the rest.
Seven lines, then. All of them correct, all of them scoped, every one earned from a draft that was nearly right.
Every one of them was also learned on the mail she sends ten times a week. Acknowledging a document, confirming a figure, answering a question about a deadline. Thursday she has to tell Priya that the fee is going up for the first time since 2023. She starts from a blank page. There’s no draft to react to, no thread that establishes the register, and almost nothing of that kind of message anywhere in her sent folder. The seven rules know the mail she sends ten times a week. They’ll fire on this one exactly as written. Composing a hard email from scratch is the fifth part of this series, and it starts with what a blank one has to be given.