The watch did not fire.
That is the correct result and a slightly deflating one. You set it yesterday because the signed letter has not come back, and it has still not come back, so there was nothing to tell you. The bell has no badge on it. Nothing in that is evidence about anything, which yesterday’s page said in advance and is easier to read than to feel.
The check took forty seconds. The pass down the feed took the time it now takes. And you went looking for the letter anyway, four times before half past nine, which is one fewer than yesterday and not yet a trend.
So the morning is free for the thing you found by accident at the bottom of yesterday’s screen. Eleven items, most of them with a date, none of them put there by you. Every message that has asked you for something since the afternoon you connected has been lifted out and written down as a line of work, with a day against it and a way back to the words it was made from. You typed none of it and you were not consulted about any of it.
Today you go and read them. It takes about twenty minutes. At least one will be wrong, and finding out which one is the point of the exercise rather than the disappointment in it.
Where the eleven came from
Open the list in Point and read down it before you touch anything.
Each row is short. What the thing is, when it is due, how it ranks against the rest, and where it came from. Open one in full and you get the account of the thread underneath it and a tap that puts you in the sender’s own words, in the message, at the paragraph that caused it. The task and the mail stay joined, so a row that reads ambiguously is never the only copy of what was asked.
Then the rows themselves, and this is where your own inbox starts telling you something. The sign-off due Wednesday was a single clause in the fourth paragraph of something you skimmed last Tuesday. The document somebody asked for on Thursday is sitting there with the ask beside it. There is one from a forty message chain about a registration, where the obligation was three replies deep and nobody would ever have found it by scrolling. And there are two with no date at all, waiting for you to give them one, because nothing in either message said when and Point would rather ask than guess.
What is not in there is anything you have to take on faith. Every row can be walked back to the words it was made from, which is the whole of why this is checkable at all. How the finding is done, what the research says about how hard it is, and the three places a due date can honestly come from are all set out in email task management, without writing it down. This morning is the first time you have had eleven of them in front of you with your own clients’ names on.
One thing worth being clear about before you start correcting anything. Nothing in that list has reached anybody. Nobody has been chased, nothing has been promised on your behalf, and no client has heard from you about a deadline you had not read yet. A task is a note written where you can see it, and it has been sitting there quietly all week for the same reason Friday’s reply sat under its thread until you read it. Which kinds of work Point is allowed to run on its own, held separately for each of them and every one of them still where you found it on Monday, is setting how much your inbox does on its own.
Which dates you were given, and which were worked out
Now the part yesterday promised you, and it is a five minute exercise with a real answer at the end.
Go down the eleven. On each one, tap through to the message and find the words the date came from. Then mark the row on your paper as one of two things: a date somebody gave you, or a date that was worked out.
A given date is a quote. By Wednesday. Before the board meeting on the eighth. End of the month. It was in the sender’s own sentence, and all that happened was that somebody turned next Friday into an actual square on a calendar, which needs nothing more than knowing when the message was sent.
A worked out date has no such sentence behind it. Somebody wrote that they needed the figures ahead of the meeting, and the meeting is in the thread further up. Somebody said as soon as you can on a Thursday afternoon about something that plainly takes a day. Those are inferences. They are usually reasonable and they are not quotes, and the difference matters because a quote can only be wrong about your circumstances while an inference can be wrong about the message.
Count the two piles. Most people are surprised by the proportion, and it goes the same way almost every time: far less of your work arrives with a date attached than you would have said. Four given, five worked out, two blank is a thoroughly ordinary result for a week of small firm mail. What that tells you is not about the software. It is that most of what you owe people this week was never written down as a deadline by anybody, and that for eleven years you have been holding those dates in your head and calling it experience.
The two blanks are the easiest ten seconds of the morning. Put a date on each one now, while the thread is open beside you and you can remember why it matters, rather than at some later point when the row says only what and never when.
What to do with a date that is wrong
You will find one. Say the row claims Friday and Friday is not right.
Change it on the row. That is the whole repair, and it costs about as much as the flag you would have put on the message under the old arrangement, with the difference that when you look at it on Thursday it still says what it is for.
The interesting question is which sort of wrong it was, and there are two, and only one of them is worth a moment of your attention.
The first is that the date was read out of the wrong part of the message. A deadline in a forwarded chain underneath belonged to somebody else last week; a date in a quoted reply was already settled. That is an error inside the reading, it is the kind that shows up in the research, and it is the kind that gets rarer as the thing gets better at knowing which part of a message the sender actually wrote.
The second is the one you should expect more of, and it is not really an error. The date is a faithful reading of the message and the message is out of date. The client moved it on the phone yesterday. The meeting the deadline hangs off was pushed and nobody minuted it. You agreed in the car on Friday that the whole job slips to September. Nothing that read only your mailbox could know any of that, which is Wednesday’s limit and Friday’s limit arriving for the third time in a week, wearing a due date this time.
That second kind will still be happening in a year, and it is worth deciding now that it is not a fault. It is the part of the job that stayed yours. A dated list is a good input to your judgment about the week and it was never going to be a substitute for it, and a date is not a priority in any case, which why important and urgent are not the same is the long form of.
While you are in there, dismiss anything that is not a task. There will be one. Somebody signed off with let me know if you have any questions, and that sentence is an obligation about half the time and punctuation the other half. A row you did not want costs you one tap to be rid of and nothing at all afterwards.
The one that never reached the list
Here is the thing about auditing a list, and it is the reason today’s checking is only half a check.
Everything wrong that is on the list is visible on the list. You can read the eleven, find the bad date, fix it, and finish feeling that you have inspected the work. What that pass cannot show you is the ask that was never lifted out, because it is not there to be read. No amount of looking at a list finds what is missing from it.
The two mistakes are also not the same size. A task you did not want is gone in a second and costs nothing. An obligation that never became a row is the one a client rings you about in three weeks, and the fortnight has been quietly making that trade in your favour since Monday, which is worth knowing rather than assuming.
So spend thirty seconds on the other half, and do it away from the screen. Sit back and name what you are carrying that is not on that list. Do not go hunting through your mail for it. Just say what is in your head.
What comes out will be two or three things, and almost all of them will have one feature in common: they were never in an email. The price rise the supplier mentioned on the phone. The favour you agreed to in a doorway after a meeting. The thing you promised yourself you would do about the February invoice while reading about the March job, which nobody asked you for and which no reader of your mail could ever find, because it was never in anybody’s words. Those have to be typed, and typing one is deliberately about as expensive as thinking of it, which is the whole subject of adding a task in five seconds.
Type them in now. Then write the count on the paper, because that number is the honest boundary of what this part of the software is for: it covers one channel thoroughly, and your obligations do not all arrive through one channel.
There is a third category worth separating out while you have the list open, and yesterday named it. Something you are waiting on from somebody else is not work you owe and does not belong here as a task with your name on it. That has its own arrangement and unanswered emails, and the threads that come back is the whole of it.
Agreeing that something is already done
Now the row that has been sitting there since yesterday marked as looking done, which is the strangest item on the page.
It is the one you answered on Friday. You never opened a list, you never ticked anything, you did what you have always done and replied to the email, and the row noticed. It says it looks finished, it says why in plain sight beside itself, and it is waiting. One click agrees and it clears. One click says not yet and it stays open with no argument about it.
Sit with that for a second longer than it seems to deserve, because it is doing something none of your previous systems managed. Every task list you have ever kept has failed in exactly one place, and it was never the writing down. It was the closing. Items got done in the world and stayed open on the list, the list drifted from the truth by a few rows a week, and about a month in you stopped believing it and then stopped opening it. The flag on the message had the same disease. You cleared them in batches on a Friday, from memory, and the memory was three days old.
What is different here is that the completion is noticed where the work actually happened, which is in the mail. And it is put to you rather than done to you: the reason is on the screen, the decision is one click, and the click can be taken back, which undoing what Point did is exact about.
Agree with it, if it is right. Then look at the eleven again and notice that the list is now one row shorter without you having typed anything into it or out of it all week.
Your old flags are still exactly where you left them
If your mail is in Outlook, you had a system before this one, and it probably had two halves. A follow up flag on the message, and, if you were more disciplined than most people, an evening now and again spent moving flagged mail into a task list and putting a date against each one. In Gmail it was a star, or a message left unread on purpose, or a note to yourself sent from your own address.
None of that has been touched. Nothing was migrated on the afternoon you connected, no flags were cleared, and your task list in Outlook holds exactly what it held a fortnight ago. The rules you were told to leave alone on Monday are still running on the server, and your stars are where you put them. That is the same arrangement as everything else in this fortnight: the mailbox is still your provider’s, the mail is still in it, and Point is reading rather than moving.
Which leaves one honest question, and it is not whether to delete anything. It is whether you are now keeping two lists.
Do not settle it this morning. Settle it the way you have settled everything else this week, by watching for three days: when something needs writing down, notice which of the two you reach for. If you reach for the flag, that is a real finding and it means the row was not doing its job. If you reach for it and then stop, because the thing is already on the list with its date on, that is the answer arriving on its own. Prune with the evidence at the end of the fortnight rather than on a hunch this morning, which is what Monday told you and is a better instruction now than it was then, because now you have some. What stays and what does not if you ever go back is set out plainly in how to switch to an AI email client.
Running the afternoon off the list
One change to the shape of the day, and it is the only new habit today asks for.
You now have two screens with your work on them, and until this morning you only used one. The feed is what arrived. The list is what you owe. Those are different questions, and for a week you have been answering the first one and hoping it covered the second.
So run this afternoon off the list. Not the whole day, and not as a resolution. Open the list after lunch, work down it in the order it gives you, and go to the mail only where a row sends you there. The list is ordered by what matters rather than by what shouted most recently, so the sequence will not be the one your inbox would have handed you.
Two things tend to come out of that first afternoon.
The first is that the middle of the list is where your week actually is. The top three you knew about. The bottom two are small. The five in the middle are the ones that used to live in the gap between an inbox that had stopped showing them and a memory that had stopped holding them, and under the old arrangement they surfaced when somebody chased you.
The second is that it is quiet in a way the feed is not, because nothing is arriving on it. A list of eleven dated things does not grow while you look at it. That is worth an afternoon of your attention on its own, and everything Point does has more of the same character in it than the sorted inbox led you to expect.
The last thing the paper is for
The paper beside your keyboard has been collecting since Tuesday of last week. Two numbers from the first sorted morning, a dozen names on Thursday, three draft tallies from Friday, and the marks from yesterday every time you went looking for something you had asked to be told about.
Today it takes two more entries and then it is finished as a place to write things.
The first is the split from this morning: how many of the eleven carried a date somebody gave you, and how many carried one that was worked out. The second is the count of what you were carrying that had never been in an email at all. Between them those two lines say more about your own working week than anything the software has shown you, and neither of them is a verdict on it.
From tomorrow the paper stops collecting and starts being read, because there is nothing left to change. Every setting is where it was on the afternoon you connected. The dial has not moved in seven working days, the corrections number four across the whole fortnight, and each one of them was made on a separate day so that you could tell what it did. That was not caution. It was the only arrangement in which the next few days can tell you anything.
At some point this afternoon you tick something off, and the list tells you it is the third you have finished this week.
It is a small number and a slightly foolish thing to be pleased by. It is also the first thing an inbox has ever shown you that went up. For eleven years the only figure on the screen was how much was left, and it went in one direction, and the days you worked hardest were the days it grew fastest.
Tomorrow nothing new gets switched on. What happens instead is arithmetic. You take the clock time you stop dealing with mail and the count out of Other, both of them on an ordinary Wednesday with clients in it, and you set them beside the two you wrote down on the first sorted morning of last week.
One of those numbers has moved a great deal. It is the other one that decides whether any of this was worth a fortnight.