Skip to content

Tax extensions, and the six months of quiet after them

On this page

Managing the mail around a tax extension is mostly a matter of replacing what the extension took away. Until the deadline, the date did your chasing for you and the client’s own anxiety did the rest. Filing removes both on the same morning, and leaves a shorter list of harder jobs with six months of quiet in front of it.

  • You hear an extension as a change of date. The client hears a conclusion, and from that morning the two of you disagree about whose move it is without either of you noticing.
  • The extended list is not a random slice of the client list. It is selected for whatever made those returns slow, so more of the autumn queue is waiting on somebody outside the firm than the spring queue ever was.
  • Time to file is not time to pay. That sentence belongs in the message that goes out in April, carrying the client’s own number, not in a note you write in June.
  • Never give a client the statutory date as their date. Six months of runway is about five working weeks of capacity, and a client told October will act in October.

What an extension takes away

Mechanically an extension is the smallest thing a practice does all year. A form, a date moves, and the job that could not be finished this week can be finished in the autumn instead. That is why it gets so little thought: measured in effort it barely registers.

Measured in what it changes, it is the only event in the year that removes a mechanism rather than adding work.

Think about what has been carrying your requests since January. Not the wording. A chase sent in the middle of March works because it arrives against a date the client already believes in, one their bank, their broker and the news are mentioning to them as well. You supply the specifics. The pressure comes free, from a calendar nobody in the conversation owns.

The morning after the extension is filed, the identical sentence has no force at all. “We still need your rental statements” is as true in May as it was in March, and it will produce nothing, because the person reading it can see five months of room and is entirely correct about it. Nothing you can put in that message manufactures urgency that the situation does not contain.

So the practice has to make by hand, for a smaller and more difficult population, the thing that was supplied free for four months. Everything else on this page is a way of doing that.

There is a second removal, and it is quieter. The extended job leaves every list in the firm at the same moment. It is off the preparer’s desk, out of the week’s plan and out of the partner’s head, because that is precisely what filing an extension is for. Practices that keep a workflow stage called “on extension” usually find, if they look in June, that one stage holds a sixth of the client list and contains no dates whatsoever. It is not a stage. It is a drawer.

Then there is the third, which is the client’s side of it, and it is the one that costs the most.

“We have filed an extension for you” is a sentence about something you did. Its grammar hands the reader nothing. Received in an inbox in April, at the end of a stretch where the client has been mildly worried about a deadline, it reads as the resolution of that worry, and the honest interpretation available to them is that the matter has been dealt with by their accountant, which is what they pay you for. They are not being careless. They are reading the only thing the message actually said.

Which of your clients ends up in that position is decided earlier, by the firm’s own cut-off date, and the arithmetic behind that date is set out in inbox zero during busy season. What happens after the decision is made is this page.

Why it was extended decides the summer

Extensions get recorded as one status, and the status is nearly useless, because three unrelated situations produce it.

The first is a return waiting on a document whose arrival date belongs to somebody else entirely. A K-1 from a partnership that will itself file late, a corrected consolidated statement, a valuation, a foreign statement that comes when it comes. Nobody in the chain is at fault and there is nothing to chase, because the thing does not exist yet. That class of document, and why a reminder aimed at one does active damage, is set out in W-2s and 1099s. What these files need over the summer is a watch and a date, not a conversation. The risk attached to them is the opposite of the usual one: the document arrives in July, lands in a mailbox nobody is reading against a list, and the return still gets prepared in the second week of October.

The second is the client who was late. The bookkeeping was not done, or the documents were asked for four times and three of them came. The extension has changed the date and changed nothing about the underlying condition, and six months is a generous amount of time for that condition to reproduce itself. This is the group that needs the manufactured deadline most, and the group whose repair is managing client document requests rather than anything to do with extensions.

The third is capacity. The return was workable in March and there was no week in which to work it. Nothing is outstanding, the file is complete, and the only thing standing between the client and a finished return is a slot in your calendar. Firms are shy about this one and it is often the largest of the three.

Recording which of the three applies costs one word at the moment you file, and it sorts the summer into three lists that need three entirely different things. A watch. A chase plan. A week in a diary.

Skip it and you get the April run that does more damage than any silence would. A firm sends every extended client the same message asking them to send their outstanding items, and sixty of those clients have sent everything they were ever asked for. What they take from it is that the firm has lost their papers, and the next thing that arrives is a phone call you have to take in the worst fortnight of the year, from somebody who was previously happy.

There is a fourth reason, and it is worth keeping apart from the others because the mail it generates is different. Sometimes the client asks. They want longer, or there is something genuinely unresolved, or they would rather deal with what they owe later. It nearly always turns up half-buried, in a paragraph about something unrelated, in the week when nobody has room to notice half a paragraph, and what it wants back is an answer about money rather than an answer about documents.

The ask that comes before the filing

An extension is not free of information, which is the part firms discover on the tenth of April.

It buys time to file. It does not move what is owed, and filing one properly means putting a number against that, which means knowing enough about a return you are explicitly not finishing. So an extension carries a small input requirement of its own, and it is not the same requirement as the return’s.

That should change what you ask for, and usually does not. A client who has sent nothing by the second week of April does not need to be asked for everything again. They need to be asked for the two or three things that let you estimate, and that is a much smaller errand: it can be answered on a Tuesday evening, where the full organiser cannot. What makes any ask answerable on the morning it lands is its own subject, and none of it changes here except the length of the list.

Say what the short ask is for, too. “So we can work out what to pay with the extension” is a different sentence from “so we can prepare your return”, it carries a date the client can see, and it is about their money rather than about your process. It gets answered at a rate the second one never does.

Where nothing comes back at all, last year’s return is the fallback, and every practice already knows it. The part that belongs in the mailbox is what you then tell the client: that the figure was estimated from the prior year because nothing else was available, and what that means for them. A number the client has never seen, arriving with no explanation of where it came from, produces a reply in April and a grievance in October.

Whatever your firm’s practice is on advising a payment alongside an extension, the mailbox owes one thing and it is narrow. The number and the date have to reach the client in a message they will open, and not as the fourth paragraph of something else.

What the extension message has to say

This is the highest-value message of the spring, and the usual version of it does one job out of four.

Four things belong in it.

That the return is not finished, said in a way that leaves the client holding something. The difference is grammatical and it is not a small effect. “We have filed an extension for you” describes your action and closes. “Your return is not finished, and here is what happens next” describes their situation and opens. Same fact, and the second one produces documents in June.

What is owed, and when. Time to file is not time to pay, and this is the sentence that has to survive the whole message. Two clients need it for opposite reasons: the one who owes something and has taken the extension to have postponed it, and the one who owes nothing and has spent the summer assuming they are accruing something. Both are answered by a plain figure and a plain date, and both will otherwise ask you in September.

What you still need, by name and from whom. A list of one to three items, in the words the client’s own paperwork uses. Where the answer is nothing, say nothing is needed, because a client who is not told that will assume there is a list and will wait for it.

And a date, which is not October. This is the single most consequential line in the message and the one most often left out or filled in from the statute. The statutory date is when the return must be filed. Their date is the week you intend to prepare it, less the room your own side then needs, and there are only so many of those weeks in an autumn. That clock runs forwards from your schedule rather than backwards from a deadline, which is the same inversion an engagement letter has and produces the same feeling that the date you have arrived at is too early. It is not too early. It is the only date that describes anything real.

One more thing belongs in the template rather than in twelve individual replies. A fraction of your clients read an extension as a failure, and a smaller fraction read it as a risk. Those messages will arrive in the fortnight when you have the least room to answer them, and they will each take ten minutes and a certain amount of care. Whatever your firm’s honest line on it is, write it once, put it in the template, and let it arrive before the question does.

Then there is what comes back from the filing itself, which nobody reads. Extensions go out in a batch and are acknowledged in a batch, and the acknowledgements are machine mail: identical subject lines, identical shape, two hundred of them in a morning. A rejection sits in that pile looking exactly like its neighbours, and a rejected extension is a return that is now late while everyone involved believes it is safe. The reasons are usually clerical, a name or an identifying number that does not match the record the agency holds, which means the problem is fixable in the same week and is not fixable in September. So the batch gets read against the roster once, deliberately, by somebody whose job that is for an hour. It is the cheapest hour in the practice’s year.

The client with two open years

An extended client is a client with two tax years open at once, and this is where a summer mailbox quietly goes wrong.

The prior year is unfinished and sitting on your list. The current year carries on regardless: estimates fall due through the summer, a business client’s payroll and bookkeeping never stopped, and documents for the year in progress keep arriving. Both years produce mail. The mail looks identical. Clients do not put years on things, because from where they are sitting there is only one relationship with one accountant, and the distinction you are drawing is an internal one they have no reason to hold.

Two mistakes come out of that and they cost differently. A payment made against the wrong year is a real cost, and it surfaces months later as a notice, at which point the correspondence about it is the most tedious in the practice. A document filed against the wrong year is harmless and expensive in a different currency: somebody prepares part of a return from a statement covering the wrong twelve months, and the error is found late or not at all.

What the mailbox owes here is small and mechanical. Every message you send about either year names the year, in the subject line where a subject line will carry it, so the client’s reply inherits it. Every document arriving over the summer is matched to a year at the moment it lands rather than at preparation, because a statement for the extended year and a statement for the current one are the same object with different figures on it. Reading arrivals against a list rather than against a memory is the general form of that discipline, and it belongs to running the firm inbox.

The current year’s own rhythm, and what its recurring payment reminders should look like, is quarterly estimates rather than this page. What matters here is only that for the extended population the two streams overlap for six months, and that the overlap is invisible in a mailbox sorted by arrival.

One part of this runs the other way, and it is the only cheerful thing in the section. A few of the choices a client still has left are tied to the extended date rather than the original one, so being on extension is occasionally worth something to them. Whether that applies is a question about their file and not about your mail. What the mailbox owes is only that when they ask in July, the question is caught as a dated item rather than answered in a line at the bottom of a reply about bank statements.

Three dates between April and September

The extension list will not surface itself. That is the whole difficulty, and it follows from the first section: nothing arrives to remind you, no desk is stopped, and no client is waiting on you in a way they can feel.

So the touches are scheduled in advance, for the whole population, by somebody named, and they are calendar entries rather than judgements. Made per client, they will not happen. Three of them is enough.

The first goes out four to six weeks after the extension, and it is a status message rather than a chase. Here is what we hold, here is what is still open, here is when we plan to prepare your return. Its real work is not the list. It is correcting, early and without any fuss, the belief that the thing is finished, and doing it at a point where the client can act on the correction without anybody feeling pressed. It is also the message that costs nothing to send to the capacity group, who need no chase and do need to know they have not been forgotten.

The second goes out in the middle of the summer and it is the working ask, carrying your own date. This is where the manufactured deadline lives. The date is the week you have set aside for that client, published to them as theirs, and it is the date that decides whether September is a season or an incident. A firm that says “we need everything by the end of July” has a different autumn from a firm that says “the return is due in October”, and the difference is not in the client’s willingness. It is in what they were told.

The third goes out in the first week of September, and it is the last honest one. After that the arithmetic runs out. This is the message that has to say plainly what happens if nothing arrives, which is the last rung on a ladder set out in managing client document requests, and the rule there holds without modification: do not name a consequence you will not honour.

A note on what these messages contain, borrowed from the discipline that keeps a shared list from being ignored. Send them when something has changed and make the change the content: what closed, what opened, where the count stands. A status message that looks like last month’s teaches the client that your messages are a mailing, and by the third one it is being skimmed. That argument in full is one PBC list.

Underneath all three sits a count, and it is the same one the spring runs on: how many open jobs are blocked on somebody who has not been asked recently enough. The extended population is where that number hides best, because in the summer it produces no symptoms at all. Inbox zero during busy season is where that count gets its full treatment, and the only seasonal difference is that in July nothing whatsoever will remind you to take it.

And it is worth knowing the mix, because it tells you what the autumn will be before the autumn arrives. A list that is mostly waiting on third parties needs watches and almost no email. A list that is mostly late clients needs the three touches and a certain number of phone calls, because a document errand responds to being made smaller rather than to being repeated. A list that is mostly capacity needs weeks in a calendar and no client mail at all.

The second season is shorter and worse

The autumn is a second busy season, and every difference between it and the first runs in the wrong direction.

It is shorter. The spring compression runs for months and gives a firm room to recover from a bad week. The autumn one is measured in weeks, and a bad week is most of it.

It is staggered rather than single. The familiar shape in the United States, and one to check against the year rather than against memory, is that entity returns fall about a month ahead of individual ones, with trusts and other filers arranged around them. So the autumn is a sequence of small deadlines with different populations behind each, not one October. Firms that plan it as one October discover the first of them in the second week of September, which is exactly a fortnight too late to do anything about it.

There are fewer hands. Whoever came in for the spring left in April, and what left with them was everything they had learned by reading the mailbox.

And the population is selected for difficulty. Nobody extends their straightforward clients. The autumn list is the returns that were waiting on other people, the clients who do not answer, and the jobs nobody had a week for, which means the proportion of the queue that is blocked on somebody outside the firm is higher in October than it was in March, at the point in the year when you have the least capacity to do anything about it.

Then there is the difference that changes what you can honestly say. In the spring, the extension was the safety valve. In the autumn there is not one. A return that is not finished by the final date is late, with everything that follows from that, and the September chase is the only chase in the practice’s year with nothing standing behind it. That is not a reason to write a sharper message. It is a reason to write an accurate one, early enough that it is still true when it is read.

Which makes the firm’s own autumn cut-off more important than the spring one, not less. Same instrument, same arithmetic, and it is the last date at which a document can arrive and still be workable against a queue that is already full. The spring version of that calculation is in inbox zero during busy season, and the only thing that changes in the autumn is that there is nothing on the other side of it.

One thing to write down on the way out, in October, while it is still in front of you. The clients who have now been extended two years running for the same reason are a fact about the relationship rather than about the season. That is a conversation about scope, terms and dates, and it belongs in December with everything else you learn from counting a year’s chasing. What the run feels like from inside a firm living through it, week by week, rather than as a method, is reaching October without burning out.

Where does Point fit?

Software is not what makes any of this work. Extension seasons were run on a wall calendar and a card index long before anybody offered to help with them, and a practice paying attention still runs them that way. A tool moves the watching, the remembering and the first draft of the words off a person. Who was extended and why, what they owe, and which week in the autumn their return gets prepared are judgements, and they do not move.

The capability that suits this season best is the one that asks least of you. Point takes a standing request in plain words: name the K-1 you will be waiting on until August, and you are told once, on the morning it arrives, rather than going to look. Set those in April against every file waiting on a third party and that whole group goes quiet in the useful sense, needing nothing from you until it produces something. Against a population defined by documents whose dates belong to other people, that is close to the entire discipline.

The waiting is held the same way. A request you sent keeps your own date on it and comes back into view on that day rather than on the day the client next crosses your mind, which across a summer is the difference between a July follow-up and a September one. Where the thing has already landed, the reminder says as much and holds until you agree, so a statement does not get chased the morning after it came in. And when a client buries a request three paragraphs into a message about something else, which is how asking for longer nearly always arrives, it becomes an item with a date on it without being retyped.

The ranking earns its keep twice a year rather than every day. Point grades a message on how much it matters and how soon instead of on when it turned up, so in the April fortnight the client asking what they owe sits above two hundred filing acknowledgements, and in the autumn the delivery that frees a preparer sits above a renewal notice. What that grading measures has a guide to itself. A one-line summary rides on every thread, and through a batch of near-identical machine mail that line is usually the whole of what you needed.

Three smaller capabilities suit the summer. Attachments leave their threads and collect in one dated place, each still tied to the message that carried it, which is what a July delivery with no covering note actually needs. You can ask a document a question and be shown the part of the file the answer came from, and with two tax years open the question is nearly always which of them this covers. And drafts come back sounding like you, so a status message naming what is held and what is open is something you correct rather than something you compose, three times over a summer, across a hundred and eighty clients.

How much Point finishes on its own is a per-action setting, and out of the box each of them sits at review: the work gets prepared, then it stops and waits. The dial is where that belongs properly. Acknowledging a delivery is the setting to raise first. The message carrying a figure a client owes is not, and should be read by somebody on its way out, every year. Actions land in a timed log and can be taken back from there, with the one limit nothing gets round: mail that has reached the other server is mail that has been sent. Seats taken on for the spring come off in May and go back on in September without anything else changing.

Point signs in to whichever mailbox the practice is already on, Google or Microsoft, so nothing about the address at the head of your extension letter changes and there is no archive to move.

What Point has no version of is the list. Nothing in Point records who was extended, or why, or what any of them owes, and Point has no opinion about which week in September a given return will be prepared. Point files nothing with any agency and has never seen a statutory calendar. All of that is the judgement the season is made of, and it stays with the firm. The benefits page carries the complete inventory, Point for accountants sets the same list against a practice year, and whether an AI tool belongs anywhere near a client’s tax affairs is a question that comes before this one and is taken properly rather than waved through.

Common questions

When should we tell a client we are going on extension?

Before the deadline week, and the date comes from your own cut-off rather than from how the fortnight is going. A message sent in the middle of March saying that the return will most likely be extended, here is what that means and here is what we still need, is a plan and reads as one. The same information sent on the twelfth of April is an announcement, arrives while the client is already anxious, and gets read as an apology however carefully it is worded. The second version also wastes the one thing worth having, which is a client who still has time to act on it.

What should the extension email actually say?

Four things, and most firms send one. That the return is not finished, phrased so the client is holding something rather than being told what you did. What is owed and when, because time to file is not time to pay and that will otherwise be discovered in September by whichever of you it costs more. What you still need, by name, or a plain statement that nothing is needed. And a date, which is not the statutory one: it is the week you intend to prepare the return, less the room your side needs afterwards. Everything that goes wrong over the following six months is traceable to one of the four being missing, and it is usually the last.

Should we chase an extended client in May?

Not with a chase, because a chase in May has no force and spends credibility you will want in September. The reader can see five months of room and is right about it. Send a status message instead: what you hold, what is open, when you plan to work the return. It does the one job May can do, which is to correct the client’s belief that the matter is closed, at the only point in the year when correcting it is easy. The chase proper belongs to the second and third touches, when there is an actual date behind it.

How do we know a filed extension was accepted?

By reading the acknowledgements against the roster, once, in the week they arrive, rather than by noticing something. They come back as a batch of machine mail with identical subject lines, and a rejection is shaped exactly like the two hundred acceptances around it. What makes it worth the hour is the asymmetry: a rejected extension means a return that is late while every person involved believes it is safe, and the cause is nearly always clerical, so it can be fixed in the same week and cannot be fixed in the autumn. This is a reconciliation against a client list rather than a reading of the mail, which is why no amount of inbox discipline surfaces it.

How many extensions is too many?

The count on its own says nothing, and firms compare it as though it did. Split it by the three reasons instead. Extensions caused by documents that did not exist yet are not a problem at all and will not go away, since the dates belong to other people. Extensions caused by clients who did not send things are a client-mix fact, and the repair is a December conversation about terms rather than anything you can do in April. Extensions caused by capacity are the honest and useful number, because that one is about pricing, staffing and the shape of your spring, and it is the only one of the three you can decide to change. A firm that knows its split can answer the question. A firm with a single total cannot.

The short version

An extension moves a date and takes away the thing that was doing your chasing, so the work afterwards is manufacturing pressure by hand for a smaller and harder list. Record why each return was extended, because waiting on a third party, waiting on a client and waiting on your own calendar need a watch, a chase plan and a week in a diary respectively, and sending all three the same message is how a firm annoys sixty clients in one morning. Ask only for what lets you estimate before you file, then make the April message do four things: say the return is not finished in a way that leaves the client holding something, give the number and the date they owe, name what is still outstanding, and set a date that is yours rather than the statute’s. Read the filing acknowledgements against the roster, because a rejection looks like everything around it. Then put three dates in the calendar between April and September and give them to a named person, since nothing else in the year will remind you that the list exists. The rest of the practice year is covered a job at a time across this collection, and AI email for accountants is where a firm weighing up products should begin.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.