Most of what lands today is fine where it is, waiting for your next briefing. What’s worth an interruption is the short written list of exceptions: five or six named conditions, each one anybody in the firm can apply on their own, before they open the message. All the difficulty is in the lines.
- Every line needs a middle clause: how the thing is recognized from the outside, before anybody reads the message.
- Most lists get written out of the last three things that went wrong. The clocks already running in an ordinary month are better raw material.
- The hardest line to write is about something that didn’t arrive. Reading mail shows you what came, so an absence has the strongest case of all for reaching you.
- Where an alert lands is half the rule, and it’s the half most lists leave blank. Split the list by destination and you keep eight lines instead of cutting to three.
- In a firm of more than one person, a colleague’s forward is the interruption most likely to break your afternoon. It answers to an agreed sentence rather than to software.
The bar is one question, and it’s narrower than it sounds. Would the hours before your next briefing go differently if you knew now? Not whether the thing matters. Working that test through, and running the two-week audit that tells you which lines to cut, is deciding what is allowed to interrupt a quiet day. This page takes the test as settled and asks what the list itself should say. If importance and urgency still feel like one property, sort them out first in important versus urgent. The list stands on the difference.
All six lines of one firm’s list
Here’s the artifact, from a four-person bookkeeping and payroll practice.
What may reach me between briefings. Six lines. Reviewed January 6, next review July 7.
1. The e-file acknowledgment address, January 15 through April 20. Recognized by sender plus date range. Reaches me anywhere. 2. Any bank or payroll provider message about a run submitted and not yet confirmed. Recognized by sender plus an open payroll task. Reaches me anywhere. 3. Anything naming the Devereux sale. Recognized by the matter name in subject or body. Expires March 31 whether or not it has closed. 4. A stated deadline falling before six tonight, where the deadline is somebody else’s. Recognized by a date in the message that is today’s date. 5. A thread where somebody has been stopped waiting for my answer for more than a day. Recognized by the thread’s own waiting-on record. Desk only. 6. The three names on the reach-me list, agreed with those three people. Recognized by sender. Desk only, except in the two weeks before a filing deadline.
What does not qualify, however it is written. A high-importance flag. The word urgent in a subject line. A client asking when something will be ready. An unpaid invoice, theirs or ours. A meeting request, including one for today. Anything from Halloran and Sons on the grounds that they are Halloran and Sons.
Cut at the last review. “Anything from a client mentioning a deadline this week”: fired 34 times in a quarter, acted on inside the hour twice. “Anything about a bank feed disconnecting”: fired 11 times, acted on never, and it turned out our bookkeeper was fixing them the same afternoon.
Four things in there are worth pointing at. The length is the least of them.
Every line has a middle clause. It says how the thing is recognized before anybody reads the message. A sender, a date range, a matter name, a record the software already keeps. Drop that clause and the only way to apply the line is to read every message that arrives. That’s the work you were buying your way out of.
Four of the six say where they may reach you. That column does more work than the count does. Lines 5 and 6 appear on a screen you’re already sitting in front of, and only there. That’s why they can afford to be broad.
Two of the six carry their own dates. The Devereux line dies on March 31 on its own, with nobody left to remember it. The e-file line sleeps for eight months of the year. Expiry is what keeps a list short.
The second block is longer than the first, and it should be. Naming what may interrupt you is the easy half. Everything in the block underneath makes a perfectly good case for itself in the moment. Writing them down in advance answers the case once, so it’s already answered at 3:00 on a Thursday. It runs longer because there are simply more of them.
Line 6 comes closest to being about a person. Look at how it’s bounded.
- Three specific names, rather than a category.
- Agreed with those three people, so they know what the line means and spend it sparingly.
- Desk only for ten months of the year.
That’s a rule. “The important clients” is a feeling with a rule’s grammar.
The clocks in your week, not last month’s scare
Asked to write this list, most people write it from memory, out of the last few things that went badly. That’s the natural place to start. The sample it gives you leans three ways, and all three lean together.
It holds the things you remember, which are the ones that ended loudly. It holds the things that arrived, because a message is an object and a silence is a gap. And it holds the things where you were the bottleneck, so whatever a colleague quietly absorbed stays off the list.
Three inventories make better raw material. Together they take about twenty minutes.
The clocks. Write down every hard cutoff in an ordinary month, with its hour. A payroll submission deadline at the provider. A same-day wire cutoff. The window an e-filing has to clear. A monthly reporting date a client’s lender imposes on them. Each clock earns one line at most. Your calendar already holds the clock itself, so the line is about the thing that can still be fixed inside the day the clock runs out, and that thing stays quiet until you look for it.
The states you already track. Blocked. Waiting on you. Sent for signature and unsigned. Past terms. These make the best lines you can get, because they’re facts your system already holds. A judgment about prose is something somebody has to make; a state is simply there. Line 5 above is one of them, and it reads the same way at 11:15 on a Thursday as at 4:00 on a Monday.
The matters currently live. The named sale, the closing, the transition, the one client mid-crisis. These lines have the strongest case and the shortest lives. Write the end date into the line the moment you write the line, while you still would.
And then there’s where nearly everybody starts. Who the sender is.
Seniority, revenue and the name on the door are all real. All three tell you who, and an interrupt line runs on an hour. Put your largest client on the list and it fires on their thank-you notes. It fires on their forwarded newsletters. It fires on their bookkeeper’s routine question about a coding. A rule keyed on a person reads all of those exactly like the one message a year that genuinely couldn’t wait. Three weeks of that and you skim past the alerts, which costs you the message the line was written for.
What you want for that client is that their mail stays at the top. That’s a ranking job, and it belongs to the briefing and the feed rather than the phone in your pocket. VIP mail that never gets buried is that mechanism, and marking the people it applies to is day four of getting set up. Keep the two apart and both work. Merge them and you get an alert every time the important client says thanks.
The lines about things that did not arrive
Every list in this shape is a list of arrivals. Something comes in. It’s checked against six lines. It clears the bar, or it waits.
Now think about the Tuesdays that actually went wrong. A good share of them went wrong over something that stayed quiet. The acknowledgment is still out. The engagement letter is still unsigned, and the work was supposed to start this morning. The client who wrote “sending it this morning” is still sending, and it’s 3:00. The wire confirmation is missing and the cutoff is at 4:00.
These have the strongest interruption case of anything on the list, for a reason that’s easy to miss. Reading your mail shows you what arrived. Any hour, any order, the same answer: here’s what came. The thing that should have been there sits outside that answer entirely. A briefing can carry an absence, and the good ones lead with them, but the briefing reaches you tomorrow morning, and the window on a missing acknowledgment is today. How a page holds the things that are absent rather than present is what separates a briefing about your day from a briefing about your inbox.
A non-arrival line has its own shape, and it needs three parts.
The thing expected. A specific outstanding item: this acknowledgment, that signature, the statements from this client.
The moment by which it should have been there. This is the part that turns a worry into a rule. Four hours after submission. By 2:00 on the day of the run. The day before the work starts. Pick the last moment you could still do something, and set it half an hour earlier.
What you’d do about it. Call the provider. Call the client. Push the work a day and tell somebody. A real action earns the line its place. If the honest answer is that it can wait, it belongs on tomorrow’s page.
Written out, one reads: if an acknowledgment for a return submitted before noon is still out at 4:00, tell me, because at 4:30 I can still call. That’s a rule about a clock and a missing record. There’s no message in it anywhere.
That puts the requirement on the software rather than on you. Something has to hold the shape of what you’re owed, with dates on it, or a line like that has nothing to read. The record is worth having for its own sake, and it’s described in tracking what you are owed a reply on. Turning a request buried in a paragraph into an item with a date is what turns an ask into a loop you can close. Lacking that record you can still write the non-arrival lines. You’ll just be the one checking, and checking is what you were trying to stop.
Where it reaches you is half the rule
Two people can hold the identical six lines and have completely different days. A rule is finished once it says where the alert lands and what it says when it gets there.
Where. An alert reaches you in a client meeting, on a phone that stays in your pocket. All it buys you is the knowledge that something is happening, carried for the next forty minutes. An alert that opens on the screen already in front of you costs a few seconds. You handle it or you dismiss it. That difference is big enough to write into each line, and four of the six above carry it.
That changes the economics of the whole list, and it’s the part worth taking away from this page. The usual advice, when a list gets uncomfortable, is to cut it. A desk-only line is nearly free. It fires into a place you’re already looking, next to the work it concerns, and it costs you the two seconds of reading it. So keep eight. Let two of them reach you anywhere and six of them only where you can act. Be generous with the list and strict with the destination, and you’ll cover far more than strictness on both ever did.
What it says. An alert reading “new important message” sends you into the message to find out whether to care, which is the reading you were trying to avoid. It has to name the matter and the clock: what it’s about, and by when. Run that test on your own lines once. If you have to open the message to decide whether to act, the line failed even on the days it fired correctly.
How many times. One event produces several records. A reply arrives, a status changes, a document lands, a task closes. Six alerts about the same closing, each of them accurate, is the failure that costs a morning. It’s also why people switch the whole apparatus off rather than tune it. Being told once about an event rather than once per record is turning ten alerts about one event into one. What a month of being over-alerted does to a person’s willingness to look at all is ten correct alerts, and the morning they cost you.
One more thing sits behind all of this, outside the list entirely. The hours you most want protected have to exist in the first place, and a cleared afternoon is the easiest thing in a week to lose. An empty afternoon is not a protected one takes that problem on its own.
Whose list it is in a firm of four
A list of exceptions is a statement about the business. In a firm with more than one person, it has to be a shared document to work as a list at all.
When two people hold different thresholds, the same message is an emergency to one of them and Thursday’s problem to the other. The client on the far end learns from whichever answer they get. What they learn is that pushing works. That’s how a threshold erodes quietly, with nobody ever deciding to erode it.
Then there’s the interruption most likely to take your afternoon, and it comes from inside the firm. Somebody reads a message, decides you’ll want to see it, and forwards it with a line on top. All six rules above are about mail addressed to you, judged before anybody has read it. This one was addressed to somebody else. It’s been read already, and it arrives carrying a colleague’s judgment rather than a condition. A written rule has nothing to grip.
The fix is one agreed sentence, said out loud in a Monday meeting. Forward it now if it’s on the list; otherwise put it where I’ll read it in the morning. Which means there has to be somewhere to put it. It has to be somewhere you’ll genuinely reach before the day starts. Otherwise the person keeps forwarding, because forwarding is the one channel they trust.
Two more decisions belong to the firm rather than to you.
Who may add a line. One person. Every addition carries the date it went on and the date it dies. Let four people extend it and the list roughly doubles over a quarter, with every single addition defensible on the day it was made. Afterward the week it stopped being short is impossible to point at. So the constraint sits on who writes, rather than on what gets written.
Who the interruption is for. A surprising number of lines have a better answer than you. If the person who submitted the run is going to handle the payroll provider’s message, the line should reach that person, and you hear about it in the briefing like everything else. Interrupting the wrong person produces two interruptions: the one you got, and the message you then send to the person who should have had it. Settling who holds what, before any of this, is when you stop having to ask who has it. The same question for the days somebody is out is covering for each other.
What Point does with a list like this
In Point, the bar itself is a setting you place: what earns an interruption, and what keeps until the briefing. Placing it is what gives the quiet between reads its meaning.
Each line becomes a standing request, phrased the way you’d say it out loud. Name the mail or the condition you want raised, and Point raises it the instant that condition is met, ahead of the next read. From then on the request does the watching, which was the part you were doing yourself. Writing one in a sentence is telling your inbox to notify you when something arrives. The bar a line should clear before it becomes one is day six. Everything running is listed in one place, so a list that has grown is visible on the page rather than something you infer from feeling interrupted. That’s seeing and stopping every watch you have running. And you’re told once, at the moment it matters, rather than once per record that moved.
The absence lines are the ones that need something underneath them, and this is where it comes from. An ask buried in a paragraph arrives on your list as a task with its date attached. Work you handed to somebody else sits on the side of the list that’s owed to you, and gets chased at the right moment. Open loops come back before they go cold. That record is what a non-arrival line reads. It’s what gives “the acknowledgment is still out at 4:00” something to be true or false about.
Point is the mail client itself, so the two halves of the decision stay in agreement. How important and how urgent each message is gets weighed as it lands. The feed leads with what needs you today. That’s the same judgment deciding whether something clears your bar in the meantime, so one message reads the same way on both sides of it. And whatever stayed under your bar is sitting in the feed you’re already in, a click from the alert that did fire. A quiet afternoon becomes something you spot-check in ten seconds, rather than something you take on faith.
The destination half is real too. The same feed is on your phone, one swipe to file a thread, with your actual mailbox kept in step. So a desk-only line and an anywhere line are genuinely different arrangements, rather than the same alert arriving twice.
Two settings sit next to this one, and they’re deliberately separate.
Cadence is the first, and you tune the two together. Shorten the gap between reads and half your lines can come off, because half of what’s on a list like this is there to cover nine unwatched hours. Lengthen it and the list grows to compensate. Where the read goes, and whether you want a second one, is what time your briefing should arrive. The longest gap you’ll ever run is an absence, and coming back from one is its own problem: how to read a catch-up digest.
Authority is the second, and it sits apart from this one. How far Point may go on its own is dialed per kind of work, and each dial has three stops: suggest-only, review, fully handled. Review is where every kind of work starts out, so anything above it is a position you moved to deliberately, and at the far end that work proceeds without asking you first. Each action taken for you lands in a clear log, in sequence. An entry there can be approved, turned down or reversed, with the honest limit that mail already on somebody else’s server is past recall. Raising the dial leaves your bar where it is, and your bar leaves the dial where it is.
Setting this up leaves your mail where it is. Connect Gmail and you keep the address you have, the history behind it and the contacts in it, all in place. On Microsoft 365 the mail and the calendar land in the same surface as everything else, so one app holds the whole picture. The full inventory is everything Point does.
The lines themselves stay yours. Point holds six conditions and reads them the same way at 11:15 on a Thursday as at 4:00 on a Monday. Point raises a matter once rather than once per record that moved, and shows you afterward what fired and what stayed down. The judgment stays with you: which clock in your month is the one you have to hear about today rather than tomorrow morning. That’s a fact about the business you run, and it’s why the useful version of this page turned out to be an artifact.
Common questions
What should be allowed to interrupt me during the day?
Five or six named conditions, each one recognizable from outside a message. In practice they come from three places. The hard cutoffs in an ordinary month. The states your system already tracks, such as blocked or unsigned or past terms. And the one or two matters currently live, each with an end date written into the line. Leave a whole category of person off it. A rule keyed on a sender fires on that person’s thank-you notes as readily as on the message that couldn’t wait.
How many lines is too many?
Fewer than you think, if every line may reach you anywhere. More than you think, once you use the destination column. A line that fires onto the screen you’re already working in costs a couple of seconds. Eight lines with six of them desk only will cover you better than three that all reach your phone. So count what may interrupt you away from your desk, and keep that number at two or three.
Should my biggest client always be able to reach me?
Almost certainly not through this list. What you want for that client is that their mail stays at the top of your feed and the briefing leads with it, which is a ranking decision. An interrupt line keyed to their name reads the forty routine messages exactly like the one a year that genuinely couldn’t wait, so it fires constantly. Within a month you’ve trained yourself past the very alert you wrote it for. A short reach-me list agreed with three named people works differently, and it works because those three know what it costs to use it.
What about messages marked urgent or high importance?
Leave them off. A flag is a claim about priority made by the party with an interest in the answer, and it’s applied by senders who can see what’s on their desk rather than yours. Across forty clients you might find one or two who use it as intended. The rest flag everything or flag nothing, and either habit carries the same amount of information. The two who use it properly are already on your reach-me list.
Can something that did not happen interrupt me?
Yes, and those are usually the best lines on the list. An acknowledgment still out four hours after submission. A signature still missing the day before the work starts. A promised document still coming at mid-afternoon. Reading your mail shows you what came, so all three sit outside it. A non-arrival line needs the item, the moment by which it should have been there, and something you’d actually do at that moment. If the third part is empty, put it on tomorrow’s briefing instead.
How do I keep the list from growing?
Give every line an end date when you write it. The list then shrinks on its own, and additions have to be renewed on purpose. Let one person add to it. And keep the cut lines written down underneath, with the count of how often each fired and how often you acted inside the hour. That record is the one thing that argues back when somebody proposes the same line again in March.
The short version
- The decision produces a document. Five or six named conditions, each recognizable from outside a message. Everything else waits for the next briefing.
- Every line needs a middle clause saying how it’s recognized before anybody reads. Otherwise the only way to apply it is to read everything.
- Build it from the clocks in an ordinary month, the states your system already tracks, and the matters currently live. Memory of what went wrong leaves the hour out, and so does the name of the sender.
- Write the lines almost nobody writes: the acknowledgment still out, the signature still missing. Reading mail shows you what arrived, and an absence stays outside that view.
- Set where each line may reach you. Desk only is nearly free, so a longer list with a strict destination beats a short one that all goes to your phone.
- Put an end date on every line. Let one person add to them. Keep the cut ones written down with the counts that got them cut.