The mail around a tax extension is about replacing what the extension took away. Until the deadline, the date did your chasing and the client’s own worry did the rest. Filing clears both on the same morning. What’s left is a shorter list of harder jobs, with six months of quiet in front of it.
- You hear an extension as a change of date. Your client hears a conclusion. From that morning you each think it’s the other’s move, and neither of you notices.
- Your extended list is selected for whatever made those returns slow. So more of the fall queue sits with somebody outside the firm than the spring queue ever did.
- 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. June is too late for it.
- Give each client your date, the week you’ll prepare their return. Six months of runway is about five working weeks of capacity, and a client told October acts in October.
What an extension takes away
An extension is the smallest thing a practice does all year. A form goes in, a date moves, and the job you couldn’t finish this week gets finished in the fall. That’s why it gets so little thought. Measured in effort, it barely registers.
Measured in what it changes, it’s the one event in the year that takes a mechanism away instead of adding work.
Think about what’s been carrying your requests since January. A chase sent in the middle of March works because it lands against a date the client already believes in. Their bank mentions it. So do their broker and the news. You supply the specifics, and the pressure arrives free, from a calendar nobody in the conversation owns.
The morning after you file, that same sentence lands flat. “We still need your rental statements” is as true in May as it was in March. It sits there, because the person reading it can see five months of room and is right about it. Whatever you put in that message, the urgency now has to come from you.
So for four months you got that pressure free. Now you make it by hand, for a smaller and harder group of clients. Everything else on this page is a way of doing that.
There’s a second removal, and it’s quieter. The extended job leaves every list in the firm at the same moment. It comes off the preparer’s desk, out of the week’s plan, out of the partner’s head. That’s exactly what filing an extension is for. Keep a workflow stage called “on extension” and look in June: one stage holds a sixth of the client list, and every item in it is undated. It’s a drawer.
Then there’s a third, on the client’s side, and it costs the most.
“We have filed an extension for you” is a sentence about something you did. Its grammar hands the reader nothing. It arrives in April, at the end of a stretch where they’ve been mildly worried about a deadline, and it reads as the end of that worry. Their accountant has handled it, which is what they pay you for. That’s a fair reading. They’re reading the only thing the message said.
Which clients end up there is decided earlier, by your own cut-off date. The arithmetic behind that date is in inbox zero during busy season. This page picks up after the decision.
Why it was extended decides the summer
Extensions get recorded as one status. Three unrelated situations produce that status, which is what makes it nearly useless.
The first is a return waiting on a document whose arrival date belongs to somebody else. 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 the document doesn’t exist yet. That class of document, and why a reminder aimed at one does active damage, is set out in W-2s and 1099s. Over the summer these files need a watch and a date. Their risk runs the other way from the usual one. The document arrives in July, lands in a mailbox nobody’s reading against a list, and the return still gets prepared in the second week of October.
The second is the client who ran late. The bookkeeping sat undone, or you asked four times for documents and three of them came. The extension moved the date and left the underlying condition exactly where it was. Six months is generous room for that condition to repeat itself. This group needs the manufactured deadline most, and its repair is managing client document requests rather than anything to do with extensions.
The third is capacity. The return was workable in March, and every week was full. The file is complete, and what stands between this client and a finished return is a slot in your calendar. Firms are shy about this one. It’s often the largest of the three.
Recording which of the three applies costs one word at the moment you file. It sorts the summer into three lists that need three different things. A watch. A chase plan. A week on the calendar.
Skip it and the April run does the damage. A firm sends every extended client the same message asking for their outstanding items. Sixty of those clients have already sent everything they were ever asked for. What they take from it is that the firm has lost their papers. The next thing that arrives is a phone call in the worst two weeks of the year, from somebody who was happy an hour ago.
There’s a fourth reason, and it’s worth keeping apart, because the mail it generates is different. Sometimes the client asks. They want longer, or something’s genuinely unresolved, or they’d rather deal with what they owe later. It nearly always turns up half-buried in a paragraph about something else, in the week when nobody has room to notice half a paragraph. What it wants back is an answer about money rather than an answer about documents.
The ask that comes before the filing
An extension asks something of you too, and firms discover that on the tenth of April.
It buys time to file. What’s owed stays where it is, and filing properly means putting a number against it. That means knowing enough about a return you’re deliberately leaving unfinished. So an extension carries a small input requirement of its own, and it’s a different one from the return’s.
That should change what you ask for, and it usually doesn’t. A client who’s sent nothing by the second week of April needs a much smaller errand. Ask for the two or three things that let you estimate. That’s answerable on a Tuesday evening, where the full organizer waits for a weekend. What makes any ask answerable on the morning it lands is its own subject, and the only thing that changes here is the length of the list.
Say what the short ask is for, too. “So we can work out what to pay with the extension” carries a date the client can see. It’s about their money rather than your process. It gets answered at a rate “so we can prepare your return” never reaches.
Where nothing comes back, last year’s return is the fallback, and every practice already knows that. What belongs in the mailbox is what you tell the client next. Say the figure was estimated from the prior year, say why, and say what it means for them. A number they’ve never seen, arriving with no account 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 narrow thing. The number and the date reach the client in a message they’ll open, standing on their own rather than as the fourth paragraph of something else.
What the extension message has to say
This is the highest-value message of the spring. The usual version does one job out of four.
Four things belong in it.
First, that the return is still open, said in a way that leaves the client holding something. The difference is grammatical, and the effect is large. “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. The second one produces documents in June.
Second, what’s owed and when. Time to file is not time to pay, and that’s the sentence that has to survive the whole message. Two clients need it for opposite reasons. One owes something and has read the extension as a postponement. The other owes nothing and spends the summer assuming a bill is building. A plain figure and a plain date answer both, and both ask you in September otherwise.
Third, what you still need, by name and from whom. One to three items, in the words the client’s own paperwork uses. Where the answer is nothing, say so plainly. A client left to guess assumes there’s a list somewhere and waits for it.
Fourth, a date of your own rather than the statutory one. This is the most consequential line in the message, and the one most often left out or copied 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 side needs afterwards, and there are only so many of those weeks in the fall. That clock runs forwards from your schedule rather than backwards from a deadline. An engagement letter runs the same way, and it leaves the same feeling that the date you’ve landed on is too early. It’s the right date. It’s the only one 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 arrive in the two weeks when you have the least room for them, and each one takes ten minutes and some care. Whatever your firm’s honest line is, write it once, put it in the template, and let it arrive before the question does.
Then there’s what comes back from the filing, which nobody reads. Extensions go out in a batch and get acknowledged in a batch. The acknowledgments 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 neighbors. A rejected extension is a return that’s late while everyone involved believes it’s safe. The reasons are usually clerical, a name or an identifying number that misses the record the agency holds. That’s fixable in the same week, and out of reach by September. So somebody reads the batch against the roster once, deliberately, for an hour. It’s the cheapest hour in the practice’s year.
The client with two open years
An extended client has two tax years open at once. This is where a summer mailbox quietly goes wrong.
The prior year sits unfinished on your list. The current year carries on regardless. Estimates fall due through the summer, a business client’s payroll and bookkeeping run straight through, and documents for the year in progress keep arriving. Both years produce mail. The mail looks identical. Clients put years on nothing, because from where they sit there’s one relationship with one accountant. The distinction you’re drawing is internal to your firm.
Two mistakes come out of that, and they cost differently. A payment made against the wrong year is a real cost. It surfaces months later as a notice, and the correspondence that follows is the most tedious in the practice. A document filed against the wrong year costs in another currency. Somebody prepares part of a return from a statement covering the wrong twelve months, and the error surfaces late or stays hidden.
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 carries it, so the client’s reply inherits it. Every document arriving over the summer gets matched to a year the moment it lands, rather than at preparation. 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 your 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, belongs to quarterly estimates rather than this page. What matters here is that for the extended population the two streams overlap for six months. A mailbox sorted by arrival hides the overlap completely.
One part of this runs the other way, and it’s the only cheerful thing in the section. A few of the choices a client still has are tied to the extended date rather than the original one, so being on extension is occasionally worth something to them. Whether it applies is a question about their file, and your mail has no say in it. What the mailbox owes is this. When they ask in July, the question gets 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 stays exactly where you put it. That’s the whole difficulty, and it follows from the first section. Nothing arrives to remind you, no desk is stopped, and no client feels they’re waiting on you.
So you schedule the touches in advance, for the whole population, with a named person on each. They’re calendar entries rather than judgments. Left to per-client judgment, they slip. Three of them is enough.
The first goes out four to six weeks after the extension, and it’s 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 sits under the list. It corrects the belief that the thing is finished, early and without fuss, at a point where the client can act on it while everyone is still relaxed. It costs nothing to send to the capacity group too. They want no chase, and they do want to know they’re still on somebody’s list.
The second goes out in the middle of the summer. It’s the working ask, and it carries your own date. This is where the manufactured deadline lives. The date is the week you’ve set aside for that client, published to them as theirs. It decides whether September is a season or an incident. A firm that says “we need everything by the end of July” has a different fall from a firm that says “the return is due in October”. The difference sits in what the client was told, rather than in how willing they were.
The third goes out in the first week of September, and it’s the last honest one. After that the arithmetic runs out. This message says plainly what happens if nothing arrives. It’s 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 honor.
A note on what these messages contain, borrowed from the discipline that keeps a shared list alive. 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’s being skimmed. That argument in full is one PBC list.
Underneath all three sits a count, the same one the spring runs on. How many open jobs are blocked on somebody who hasn’t been asked recently enough. The extended population is where that number hides best, because in the summer it produces no symptoms. Inbox zero during busy season gives that count its full treatment. The seasonal difference is that in July you take it from memory, with nothing in the mailbox prompting you.
Knowing the mix is worth the effort, because it tells you what the fall will be before the fall arrives. A list that’s mostly waiting on third parties needs watches and very little email. A list that’s 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’s mostly capacity needs weeks in a calendar and no client mail at all.
The second season is shorter and worse
The fall is a second busy season, and every difference between it and the first runs in the wrong direction.
It’s shorter. The spring compression runs for months, which leaves a firm room to recover from a bad week. The fall one is measured in weeks, and a bad week is most of it.
It’s staggered rather than single. The familiar shape in the United States is that entity returns fall about a month ahead of individual ones, with trusts and other filers arranged around them. Check it against this year’s calendar rather than against your memory. So the fall is a sequence of small deadlines, each with a different population behind it. Firms that plan it as one October meet the first of them in the second week of September, which is exactly two weeks too late to do anything about it.
There are fewer hands. Whoever came in for the spring left in April, and everything they’d learned from reading the mailbox left with them.
And the population is selected for difficulty. Straightforward clients get filed in the spring. The fall list is the returns waiting on other people, the clients who stay quiet, and the jobs nobody had a week for. So the share of the queue blocked on somebody outside the firm is higher in October than it was in March. That lands at the point in the year when you have the least capacity for it.
Then there’s the difference that changes what you can honestly say. In the spring, the extension was the safety valve. The fall runs without one. A return still open at 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. The answer is an accurate message rather than a sharper one, sent early enough that it’s still true when it’s read.
Which makes your own fall cut-off more important than the spring one. Same instrument, same arithmetic. It’s the last date a document can arrive and still be workable against a queue that’s already full. The spring version of that calculation is in inbox zero during busy season. In the fall, the one thing that changes is that the other side of that date is empty.
One thing to write down on the way out, in October, while it’s still in front of you. The clients extended two years running for the same reason are telling you about the relationship rather than about the season. That’s 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, is reaching October without burning out.
Where does Point fit?
The method above is what makes this work. Extension seasons ran 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 fall their return gets prepared stay with you. Those are judgments.
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’ll be waiting on until August. On the morning it arrives, Point tells you once, and you go looking for nothing. Set those in April against every file waiting on a third party, and that whole group goes quiet in the useful sense. It needs nothing from you until it produces something. Against a population defined by documents whose dates belong to other people, that’s 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. Across a summer that’s the difference between a July follow-up and a September one. Where the thing has already landed, the reminder says so and holds until you agree, so a statement that came in yesterday stays unchased. 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 and you retype nothing.
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 those two weeks in April, the client asking what they owe sits above two hundred filing acknowledgments. In the fall, 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’s held and what’s 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. Out of the box each of them sits at review: Point prepares the work, then waits for your go. The dial is where that belongs properly. Acknowledging a delivery is the setting to raise first. The message carrying a figure a client owes stays at review, and somebody reads it 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, and everything else stays as it was.
Point signs in to whichever mailbox the practice is already on, Google or Microsoft. The address at the head of your extension letter stays exactly as it is, and your archive stays where it is.
The list is the one thing Point has no version of. Who was extended, why, and what each of them owes live outside Point, and the judgment about which week in September a given return gets prepared is yours. Point files nothing with any agency and has never seen a statutory calendar. All of that is the judgment 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 it’s taken properly rather than waved through.
Common questions
When should we tell a client we are going on extension?
Before the deadline week. The date comes from your own cut-off rather than from how the two weeks are going. A message sent in the middle of March reads as a plan: the return will most likely be extended, here is what that means, here is what we still need. The same information on the twelfth of April is an announcement. It arrives while the client is already anxious, and it reads as an apology however carefully you word it. It also spends 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 still open, phrased so the client is holding something rather than hearing what you did. What’s owed and when, because time to file is not time to pay, and September is where that gets discovered by whichever of you it costs more. What you still need, by name, or a plain line saying you have everything. And a date of your own rather than the statutory one: the week you intend to prepare the return, less the room your side needs afterwards. Everything that goes wrong over the following six months traces back to one of the four being missing, and it’s usually the last.
Should we chase an extended client in May?
Send a status message instead. A chase in May has no force, and it spends credibility you’ll want in September. Your client can see five months of room, and they’re right about it. So send what you hold, what’s open, and when you plan to work the return. That does the one job May can do. It corrects 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’s an actual date behind it.
How do we know a filed extension was accepted?
By reading the acknowledgments against the roster, once, in the week they arrive. 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. The asymmetry is what makes the hour worth it. A rejected extension means a return that’s late while every person involved believes it’s safe. The cause is nearly always clerical, so the same week fixes it and the fall can’t. This is a reconciliation against a client list rather than a reading of the mail, which is why inbox discipline alone leaves it buried.
How many extensions is too many?
Split it by the three reasons. The count on its own says nothing, and firms compare it as though it did. Extensions caused by documents that did not exist yet are fine, and they’ll keep happening, because the dates belong to other people. Extensions caused by clients who sat on 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. That one is about pricing, staffing and the shape of your spring, and it’s the one of the three you can decide to change. A firm that knows its split can answer the question, and a single total leaves you guessing.
The short version
An extension moves a date and takes away the thing that was doing your chasing. The work afterwards is manufacturing that pressure by hand, for a smaller and harder list. Record why each return was extended. Waiting on a third party needs a watch, waiting on a client needs a chase plan, and waiting on your own capacity needs a week on the calendar. 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. Set a date that is yours rather than the statute’s. Read the filing acknowledgments 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, because 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.