Some of what you’re waiting on is the start of a job that begins the moment it lands. A watch carries both halves of that in one sentence: the thing to wait for, and the next step to have ready when it arrives. Point catches the arrival and prepares the work.
- The second clause is the whole of it. Tell me when the filing is accepted is a watch. Tell me when the filing is accepted, and start the note to the client is a watch that lines up work.
- Everything appears when the trigger fires. While you’re waiting, the watch waits too, so your list stays as short as you left it.
- Your setting for that kind of work decides how far Point goes with what it prepared. On a new account, every kind of work waits for you.
- Attach a next step only when you could name it before reading the message. If the right move depends on what the message turns out to say, leave the watch as a watch.
The clause most people leave off
In its ordinary form a watch is one clause long. You name what you’re waiting for, and you get told when it turns up. Most people stop there, and for most of what you’re waiting on that’s the right place to stop.
Then there’s the other kind, where the arrival was only ever a signal. The point is the thing you do about it. You wanted to know quickly so you could get on with it. The filing is accepted, and now the client has to be told. The transfer confirms, and now the invoice can go out. The engagement letter comes back signed, and now the file can actually be opened. In all three, being told is a step on the way to something rather than the end of it.
For those, the sentence gets a second clause. You describe the trigger and the next step together, in the same plain words, in one go. You write it in one place, in one sentence, the way you’d say it out loud. How to phrase the trigger half well is the part that decides whether any of this fires at all, and it belongs to telling your inbox to notify you when something arrives. Adding a second clause leaves that half exactly as it was: you’re describing the same arrival, and then saying what it starts.
Point reads the instruction back before the watch is set, and the readback covers what will happen to the prepared work. So you find out on the day you write the sentence whether the thing you just described will wait for you. You find out then, rather than three weeks later at the moment it fires.
Four that are worth writing:
- Tell me when Marchetti signs and returns the engagement letter, and open the task to get the file started. The arrival is the fact. The task reads the same whatever the covering email says.
- The moment the bank confirms the transfer on the Ridgeway matter, draft the line to the client telling them it cleared. One arrival, one obvious next move, one message that was always going to say the same thing.
- Tell me when the draft accounts come back approved, and put the invoice on my list for that afternoon. The step is yours to do rather than Point’s to do for you, and lining it up is still worth the clause.
- Tell me each time a bank feed error notice comes in, and make a task to sort it out. This is the recurring kind. It stands until you end it, and every fire lines up its own task.
And one that’s deliberately left plain:
- Tell me if anyone from the state board writes. The letter could say anything, so whatever you lined up would be wrong by the time you’d read it. This one stays a watch.
One thing worth knowing before you go further, because it saves a wasted sentence. The trigger here is a message arriving. A clock can start a watch too, and then Point goes and looks rather than waits, and comes back with what it found. That’s a different arrangement with a different rhythm, and it’s watching things outside your inbox.
What actually happens when it fires
Between the sentence and the fire there’s one thing to look at, and that’s the watch itself. Nothing is created yet. It waits for you. The watch lives in your task list as a standing item assigned to Point rather than in a preferences screen, so you can read it back in the words you used. What it has caught, how often, and how to end it are the subject of seeing and stopping every watch.
Then a message lands that matches, and two things happen in the same moment. You’re told, in one small receipt with a click through to the message that set it off. And the next step is prepared.
Prepared is the exact word, and the whole page turns on it. The work is worked out, written, and sitting there. The task sits ready to be created. The reply sits ready to send. On everything you’ve left at review, releasing it is one click. The watch did the work, and the decision about whether the work happens is still yours, in the same place you left it.
The return on that second clause is measured in hours, and it’s worth being concrete about where the hours come from. The message that starts the job arrives when the other side sends it, which is often 5:20 on a Friday afternoon. With one clause, the work starts when you next look, which is Monday. With two, the work was done at 5:20, and Monday morning opens with something to approve instead of something to begin. Those four minutes of writing moved to the far side of the weekend.
There’s a cost on the other side of that, and it’s small but real. Work that’s prepared and left alone sits on your list, looking like a thing you have to deal with. That’s precisely what you were trying to have less of. One clause, one step, and only on watches whose step you genuinely want.
Where the prepared work waits
Here’s the part that surprises people, and it’s the most useful thing to take away from this page. What happens to the prepared work is decided by the autonomy setting for that kind of work. That setting is held separately for filing, drafting, scheduling and the rest, and the sentence you wrote never touches it. Writing a second clause gives the watch no authority it didn’t already have.
Out of the box, every kind of work sits at review, meaning Point does the job and holds the result until you agree. So on a new account, a watch with a second clause always produces something waiting rather than something done. Raise the setting for one kind of work and the same watch behaves differently. Say you’ve taken filing to the top and left replies at review. A sentence that says catch this, file the thread, and draft the reply then gives you one thing finished and one thing waiting, from one instruction, on one message. That’s your setting doing what you set it to, rather than the watch forming an opinion.
Which has a consequence worth writing on the wall, because the change is a quiet one. Raising a setting in November changes what a watch you wrote in August does. The sentence says exactly what it always said, and the outcome is different. No prompt appears to tell you so. If you’re going to run standing instructions and move settings, read your watches on the day you move a setting. Each position, and how far it reaches, is laid out in setting how much your inbox does on its own. At the top of a setting the work simply happens, which leaves the activity log behind every action as the only place that work becomes visible.
Which next steps are worth attaching
One test does most of the work. Could you say the next step out loud, correctly, before you’ve read the message?
If you could, write the clause. The transfer confirmation is the clean case. Whatever the bank’s message says, your client is going to be told the money arrived, and that note was always going to say the same thing. The arrival is the fact, and the fact is the entire content of the next step.
If you couldn’t, what you have is a watch, and attaching a step to it is guessing on your own behalf. A lender’s decision is the example everyone recognizes. The answer lands one way or the other, and the two lead to opposite mornings. A prepared reply that assumes one of them costs you more than it saves, because a wrong draft in front of you at the wrong moment is something you have to notice and turn down.
There’s a middle move for those, and it’s the one most people settle on. Attach the part that’s the same either way. Whichever way the lender answers, you’ll be calling the client that afternoon, so the clause is a task rather than a draft. A step that’s right whichever way the news falls is a step you can safely attach to news you can only guess at.
What can go in the clause is the work Point already does elsewhere: writing a reply in your words, putting a dated item on your list, filing the thread where it belongs. It’s the same set of things you’d ask for in any other sentence, hung on a trigger instead of on right now, and everything there is to ask for sits on the benefits page.
Two habits worth forming early. Keep it to one step: the clause names what comes next, rather than a sequence of five things, and anybody who wants five things chained has a process on their hands rather than a watch. And keep second clauses off your widest watches. Tell me if anyone from the state board writes is a good watch precisely because it’s wide, and anything attached to it would be wrong most of the times it fired. The wider the trigger, the smaller the step it should carry, and the widest ones are best left plain.
Worth saying plainly: most of your task list gets made another way. Somebody asks you for something in a message, and Point lifts the ask out of it unprompted, dates it, and links it back to their own words, which is email task management, without writing it down. A watch with a second clause is the reverse arrangement: you decide in advance what should happen, and the message merely sets it off. Most people need the first far more often than the second, and a firm running nine chained watches has usually replaced a decision it should have made once.
And if the real trouble is that six systems already mail you about the same event, attaching steps to any of them makes the noise worse rather than better. The job to do first is turning ten alerts into one.
When what arrives is not what you expected
Two versions of this happen, and they want different answers.
The first is that the watch caught the right message and the news was bad. The approval was refused. The letter came back with three clauses struck out. The prepared step was written for the other outcome, and it’s now wrong. Turn it down. At review the work is still yours to release, so declining costs you the few seconds of reading it and nothing more. It should also send you back to the sentence, because a step that only survives good news is a step that wanted to be a task.
The second is that the watch caught the wrong message. Something matched by accident, and the prepared work is aimed at a thread that belongs to another job entirely. Turn that one down as well, then narrow the trigger rather than the step. The trigger is the part to fix, and editing the step leaves the next false catch exactly where it is.
Either way, the watch goes on watching, unless it was the one-shot kind or you stop it yourself. Stopping it is one click, and it leaves a dated line in the record behind it.
If a kind of work is sitting above review, the shape of all this changes, and it’s better to know that before you raise anything. The work is already done, so what you have is a record rather than a prepared version to decline. What Point did is in the log, and Point’s own moves can be put back from there, which is undoing what Point did. A message that has reached the other side’s server stays sent, and it stays sent for good. That’s the plainest argument for leaving anything that goes outside your firm at review, and for pointing the second clause of a watch at work where a wrong version costs you a click rather than a client.
Common questions
Can an email watch do the next step, or does it only tell me?
It can do both, and which one you get is decided by the sentence you wrote and by your setting for that kind of work. A watch with one clause tells you. A watch with a second clause has the next step prepared at the moment the message lands: worked out, written, and waiting for your go on everything you’ve left at review. The preparing happens on the day something matches, so a watch you set in March sits quiet until then.
Is this just an if-this-then-that rule with more words?
The two differ on both halves of the sentence. A rule matches text you had to commit to in advance, then performs a fixed action on the message whether or not the action suits what actually arrived. A watch is read against what a message means. Its second clause produces work that’s prepared rather than performed, held at the level you set for that kind of work. Where a rule runs out on the telling half alone is in telling your inbox to notify you when something arrives.
Does attaching a next step mean Point will send mail for me?
Only if you’ve already taken replies to the top of their own setting, which is a choice you make in the autonomy settings. Out of the box, replies sit at review: Point writes them, and pressing send is still a thing you do. The clause changes what gets prepared. Your setting for that kind of work decides how far the prepared work goes.
What if the message that arrives is not the one I meant?
Turn the prepared work down, then narrow the trigger rather than rewriting the step. A watch described loosely will catch things you meant to leave out, and at review that costs you a glance. It’s also the reason to keep the attached step modest on any watch you’ve deliberately made wide. An unexpected catch should cost you a moment of reading, rather than a message somebody else has already received.
Can one watch line up more than one thing?
The clause names the next step, singular, and that’s the shape worth keeping even where you could stretch it. If you find yourself wanting one sentence to set off four things in order, what you’re describing is a process your firm runs, and it needs somebody who owns it rather than a standing instruction in your inbox. One trigger, one step, is also the version that still makes sense to you in October.
What happens if it fires while I am on vacation?
The work is prepared at the hour the message landed, so it’s done and waiting by the time you get back. For anyone who takes a real week off, that’s most of the value of the second clause. Your decisions stay where you left them: what was set to wait is still waiting, and the pile you come back to is a shorter one rather than an empty one.
The short version
A watch tells you. A watch with a second clause tells you and has the next step ready, prepared at the moment the message landed rather than the moment you next looked. Write the clause when you could name the step before reading the message, and leave it off when the right move depends on what the message says. What then happens to that prepared work is your setting for that kind of work, sitting at review until you move it, which is why a sentence written in August can behave differently in November if you moved something in September. Start with one, on a watch that has already earned your trust, and see what Monday looks like when the thing that landed at 5:20 on Friday is already written.