In busy season your mailbox is the supply line for every return in the building. A full inbox is fine. Four hundred sitting in it costs you nothing. The count worth running to zero is the jobs blocked on somebody else that nobody has chased. It’s not messages, and that number stays small.
- Busy season makes the mail concurrent. That’s a different problem from urgent, and it takes a different answer.
- Your half of the work can be scheduled. Their half arrives when it arrives, and the mailbox is the only place it shows up.
- The follow-up date you’d set in July is wrong in March. It’s wrong in the same direction every time.
- Write down in December what waits until after the deadline. February is late to find out.
What busy season actually changes
You feel volume. What changed is concurrency. March brings the same mail July brought: the same deliveries, the same half-answered questions, the same signatures waiting. Several hundred of them are alive at once now. Every one is attached to a job carrying the same date as all the others.
Two facts sit underneath that, and almost no other business has them. You know the whole body of work before the year starts, client by client and date by date. And most of it starts when somebody outside the firm sends you something.
Put those together and the scarce thing in season is ready work, rather than hours. A preparer’s afternoon turns into a finished return when there’s an unblocked job in front of them. What arrived in the mail that morning decides whether there is one. For four months the mailbox is the firm’s supply.
The two get confused at exactly the wrong moment. In February the inbox looks worse than it’s looked all year, so the number on the screen is the one you go after. Emptying it takes the morning. At the end of that morning, the dozen jobs that went quiet overnight are still quiet.
The year holds more than one of these compressions, and each has its own shape. AI email for accountants sets out how the mail differs between the spring, the flat middle of the year and the extension run. This piece is about what you do inside any of them, on the day.
The zero worth running to
Take every open job in the practice on an ordinary season morning. Ask one thing of each. Whose move is it. Two answers cover the whole list, and they split it into work you can do today and work that sits with somebody else.
Cut that second half again, because its two parts behave differently. Some of those jobs have been asked for, with a date recorded against the asking, so they come back on their own. The rest sit with somebody the firm last chased a long time ago, or has yet to chase at all. Right now nobody in the firm knows which ones they are.
That third pile is the zero.
It’s the one of the three quietly costing money. Ready work is fine. It’s what the day is for. Chased and waiting is fine too, because the date brings it back to you. Blocked and unchased is the return that turns up near the deadline needing two weeks nobody has. It stays invisible in every system you own. Software keeps a record of the messages you sent, and this one was never sent.
The useful thing about that count is that it holds steady while the mail rises. Messages scale with how many clients you have and how much they enjoy writing. Blocked and unchased scales with how many jobs changed state since you last looked. On a normal morning that’s a dozen. On a bad one it’s thirty. Whatever the mailbox says at the top of the screen, that’s a coffee’s worth of decisions rather than a day’s.
Reading arrivals against a list is the job underneath all of this, and it runs all year. That reconciliation lives in running the firm inbox, along with why a client rather than a message is the unit it works in. The season changes one thing: the price of skipping it for a day. In July that price is nothing. In March it’s a week.
A tidy screen is still worth having. Clear the list if clearing it helps you think. Keep the clearing and the counting as two jobs, because only one of them keeps score. Inbox zero versus a calm inbox takes the general case apart. The seasonal version of that mistake is the expensive one.
Why chase dates shrink as the season runs
Every request you send has a last useful day. It’s the filing deadline minus whatever still has to happen at your end once the document lands. That’s the standing arithmetic of a practice, and it’s set out in full in running the firm inbox.
In season one term of that sum changes, and it’s easy to miss because the figures look the same as always. What you subtract is the wait before the work can start, rather than the length of the work itself.
In July the two match. A return needing two days takes two days, because the desk in front of it is clear. In the middle of March that same two-day return waits eleven days first. Eleven days of other people’s returns are already on the desk ahead of it. Subtract two and you’ve promised a client a three-week window the queue already spent. Subtract thirteen and you have a date you can act on.
That explains something every firm feels and few write down. The window you can give a client gets shorter every week of the season, while the deadline stays where it is. A request sent on the first of February and the identical request sent on the first of March are two different requests. The second one is nearly out of time on the morning it goes out. It reads exactly like the first, and the client reads it that way too.
Most practices already own the firm-level version of this number, and treat it as a policy rather than a calculation. It’s the published cut-off: everything in by a stated date, or the return goes on extension. That date is the last day a document can arrive and still be workable before the deadline. You work it out against the queue rather than against one job.
Two things follow from working it out this year rather than inheriting last year’s. Set it from the capacity you have now, because the queue feeds it and the queue moved when the client list did. Then use it as the chase clock rather than as an announcement. Every outstanding request gets its final chase before the cut-off, rather than before the filing date. After the cut-off you’re having a different conversation.
It changes what a late chase says, too. In January, “we still need your bank statements” is true and enough. In the third week of March, the true sentence is that those statements now decide whether the return is filed or extended. A client who sat on the first message will often move on the second. That’s an accurate description of where their file stands, and it’s fair to send. The version they’re entitled to be annoyed about is the one that arrives after the cut-off has passed.
Unanswered emails and the threads that come back has the general half of this, including how quickly people really reply. The seasonal half is simple. Both of your dates are computed against a queue that lengthens while you use them.
Which message actually goes first
Two measurements decide whether a message needs you at all: how much it matters, and how soon. They work by staying separate rather than collapsing into one score. That question runs all year, and important versus urgent answers it properly.
Season adds a third question, and for four months it settles the order among everything the first two let through. Whose hands does this free.
The reason is the shortage of ready work. A message that releases a job somebody is sitting in front of right now turns an idle afternoon into a finished return. A message that creates a job for next week leaves that afternoon idle. In an ordinary month the gap between them is small enough to ignore. In March it’s most of the ranking.
Two consequences look wrong written down and work in practice. A client’s two-line answer about which account a transfer came from outranks a warm referral from your best introducer. That holds in March, and in no other month of the year. And the highest-value message in the mailbox is frequently an internal one: a preparer saying they’re stopped. It arrives quiet, with no client anxiety, no deadline language and no attachment, which is exactly the shape a busy person skips. It’s also the one message in the list with somebody’s whole afternoon standing behind it.
Most of a season mailbox needs no ranking. It’s delivery rather than correspondence: a file, and a line above the file saying here it is. A delivery wants two things. Match it against what you were expecting, then send a short acknowledgment that it landed. That costs seconds. It stops the same document arriving three times, and it settles in advance the argument about whether it was ever sent.
So the working order is short enough to hold in your head. Anything that unstops a person goes first. Then whatever the two measurements have put at the top. Then deliveries in a batch. Then everything on the list you wrote in December.
Decide in December what will wait
Something has to wait from January to April. That’s arithmetic, and every firm meets it: one firm’s capacity against four months of work priced above it. The real question is whether the list of what waits got written in advance or discovered afterwards. That difference is the whole distance between a backlog and a mess.
The categories are much the same in most practices. Planning questions carrying no date. Inquiries that are something other than returns. Software renewals and vendor mail. Anything that would be materially better for an hour of thought, because in season that hour belongs elsewhere.
Write that list before the season, and write the sentence that goes with each entry. The sentence is the load-bearing part. What loses a firm a client in busy season is usually the silence, rather than the delay. “I have this, it needs proper thought, and I’ll come back to you in the week of the twenty-second” takes eleven seconds and buys two weeks. Silence is free, and it buys a client who assumes they were forgotten.
Two disciplines come attached to that. A deferral carrying a date is a fresh promise, so it belongs on the same list as everything else you owe. Put it anywhere else and you’ve written a covering note on an unanswered email. And the dates have to be spread. If everything you put off in February says the week of the twenty-second, you’ve moved the crisis rather than survived it.
One category deserves an exception, and it’s the one that always gets deferred because it stays quiet. A prospect who writes to you in March is worth ten minutes on the day. They arrive with no deadline, no chase and no consequence for ignoring them. That’s exactly the profile of the mail a practice loses the most money on, and busy season is where that quadrant does its worst work.
The hands you take on for four months
A firm in season is a different firm. Extra preparers, a part-timer back for the run, sometimes somebody hired just to log documents. All of them read the mailbox. In May most of them leave.
What leaves with them is everything they learned by reading it. A temporary preparer knows the second account is still coming, and that this client has already been chased twice. Both facts live in one place, and that place goes home in April. So the rule a practice can be loose about in July has to hold in February. A thing you’re waiting on gets recorded where the whole firm can read it.
Routing tightens for the same reason. Every extra pair of hands is another address a client can reply into. Clients reply to whoever wrote to them last, which is sensible of them and is how it will stay. Name the mailbox that holds the record for documents, and name it in the week before January. The second week of February is late.
Then there’s the part that outlives the season by accident. Accounts opened for four months are the accounts still open in July, and the person who finished in April is usually still on the list too. Client confidentiality in an accounting practice treats that list as the access control a firm actually operates, which it is. Read it beside the seat list on one afternoon in May.
Where does Point fit?
Every count above fits on a sheet of paper, and lived there for a long time before software offered to help with any of it. What a tool changes is who holds the running total between Monday and Thursday.
Point reads the mail before you get to it. Each message is weighed on how much it matters and how soon. So on the morning four hundred things arrive, the client with a date on them sits at the top and the software renewal sits below. Every thread carries its summary in a line, and a season needs that more than any other stretch of the year. Thirty messages about one return can be judged from the summary.
The season jobs land where you’d want them. Something a client asks of you halfway down a message turns into a dated item, with nobody copying it out. A request you sent is held as something owed to you. It comes back on the date you chose, rather than the day it happens to occur to you. That’s where the waiting half of the count keeps itself.
You can also leave a standing instruction. Ask to hear the moment a named client’s signed authorization arrives, or the last statement you’re missing. You hear about it once, when it lands, instead of checking.
Files gather in one place, dated and named, still attached to the thread they came in on. Put a question to an attachment and the answer comes back with a pointer to the line in the file. That counts for a great deal in a season, because most of what you were sent is inside the documents rather than in the messages.
Two things fit the season in particular. A short briefing gathers what needs you before the day starts. That’s as close to a stand-up as a small firm gets in March, and the same digest catches you up after a day out of the office. And you set what’s worth interrupting you for, and what waits for that briefing. That’s the difference between being reachable and being available.
How much Point does on your behalf is a dial, with its own setting for each kind of task. It sits at review out of the box. The seasonal use of that is worth saying plainly. Raise the routine kinds, acknowledging a delivery or sending a chase you’ve already worded, while anything needing judgment stays where it is. At the top of the dial Point acts without checking in, which is what the top of the dial is for.
Everything done shows up in a log with times against it, and most of it can be reversed from there. One thing stands outside that: a message already delivered to somebody else’s server has been sent. For the extra hands, seats go on as the team grows and come off again afterwards. Point signs in to whichever mailbox the practice already runs, on Google or on Microsoft, so your address and your eleven years of archive stay exactly as they are in January.
The counting this piece asks for stays with you. Point holds no job list, sees no queue depth on any desk, and takes no view on your cut-off date. All three are facts about your capacity rather than about your mail, so they stay yours. The full inventory is on the benefits page, and Point for accountants walks the rest of it through a practice.
Common questions
Should we be clearing the inbox every day in busy season?
Clear it when clearing is free. In February it costs a morning, and that morning belongs to the dozen jobs that went quiet overnight. A clean screen says nothing about those jobs, because a message you filed and a message that never arrived look identical on it. Split the open jobs three ways instead. It takes a fraction of the time, and it produces the one number the season keeps score with.
When should we chase a client in March?
Work back from the cut-off rather than from the filing date, and subtract the queue rather than the job. A return needing two days of work, with eleven days of other returns in front of it, closes its client window thirteen days before the deadline. That sum usually produces a date that feels impatient and is simply correct, which is why it’s better computed than felt.
Is it a mistake to change how we handle email in the middle of the season?
It depends on whether the change needs learning. A new inbox adopted in February means learning software in the worst month of your year, so the sensible window is the quiet middle. AI email for accountants covers that timing and what to test a product against. A drill is a different matter. Splitting your open jobs into ready, chased and unchased costs a sheet of paper and ten minutes. It needs nobody’s permission, and it can start on a Tuesday in March.
What happens to everything we deferred when the season ends?
It arrives at once, in the week everybody’s energy has run out. That’s the argument for spreading the dates as you set them. Spread the promises across the month afterwards and the pile lands as a workload rather than as a second season. Read the deferred list once before you work it. It’s the only honest record of what the compression cost you. A category that turns up on it three years running is telling you something about the shape of the practice, rather than about the season.
Our busy season is not tax season. Does any of this still hold?
Yes. All of it works on the shape rather than on the months. The shape is a fixed date somebody else set, a body of work known in advance, and half of that work sitting with people outside the firm. A bookkeeping practice meets it at every month-end, an audit team at year end, and a UK practice in January. The compression is shorter, so the queue term in the chase arithmetic moves faster and the cut-off matters more. Everything else reads the same.
The short version
Busy season makes your mail concurrent, and the shortage it creates is jobs that are ready to be worked, rather than hours. So the number to run to zero is the jobs blocked on somebody nobody has chased, which stays small however loud the mailbox gets. Work chase dates against the queue rather than against the task, and give the firm one cut-off date that does the same sum for everyone. Rank what unstops a person above what creates work. And write down in December what will wait, with the sentence and the date that go with it. The difference between a backlog and a mess is only ever whether the list was made in advance.