Writing an email to remind a client of a deadline

A deadline reminder is the one client message where the date is the subject and the client is the one who has to move. It works when it arrives while there’s still room to act. It names a single thing to do. And it asks a question the client can answer without doing the thing. That answer, whatever it turns out to be, is usually worth more to your week than the document would have been.

• Send it to somebody who’s still on time. A message that goes out after silence is a chase, and it reads as one however you word it.
• Ask a question instead of asking for a task. “Will you make the 20th?” gets answered from a parking lot. “Please send this by the 20th” waits for somebody who already has twenty minutes and the file.
• Two dates are in play, yours and the deadline’s. The client acts on the later one. Decide which of them the message is about before you write a sentence.
• The consequence here is arithmetic, which is something no other client message has. Use the arithmetic. Where it runs out, say the honest thing instead.

This is the message for a date that’s still ahead of you. When the client is already late and you want a specific piece of paper, that’s a different message, built differently, in the follow-up for a missing document. When the clock has run out on your own side, the message you owe is telling a client about a delay. And the turnaround your firm promised in the first place, along with what you should have asked for in return, belongs to your response time policy.

Sent to somebody who is not late yet

Most firms send chases and call them reminders. It’s an easy pattern to fall into, and it’s easy to recognize from the inside.

The first message about a date goes out when somebody notices the file is still empty. By then the client is already behind, the firm is already a little irritated, and every sentence has to carry that freight. So the writing problem people bring to this subject, which is how to ask again without sounding like a nag, is mostly a symptom of skipping the message that was meant to come first.

A reminder is a scheduled message to a client who has done everything right so far. Three things follow from that, and together they’re the reason it’s worth the trouble of sending.

The tone takes care of itself. You’re telling somebody about a date, so the sentence stands on its own, and the apologetic vocabulary that ruins later messages stays out of this one. The list of what to strike out of a message you’re sending too late is in the document guide, and the good part of sending early is that most of that list stays unwritten.

The client can afford to tell you the truth. A client who’s still on time can write back “I won’t have this until the 22nd” at no cost to themselves. It’s a scheduling fact. Two weeks later the identical sentence is a confession, and people go quiet instead of confessing. That’s the whole argument for sending early, and it rests on the answer rather than on the extra days. The honest answer is cheap only while there’s still room, and the honest answer is the thing you actually need.

It’s a job you can decide in a quiet month. A chase gets composed in the week it becomes necessary, which is reliably the week with the least left in it. A reminder run gets designed in November, when you have room to think about which clients get what and on which days. Then it runs in March, by somebody following a plan. Deciding in advance what the season will and won’t get to is its own discipline. Reminders are the item most likely to be dropped, and the least likely to complain about it.

One caution before any of this is worth doing. A reminder that reaches a client who has already done the thing costs you more than sending nothing would have. It tells them the firm has stopped reading their file, and your next message about a date gets exactly the attention that deserves. So the run has to know what’s already come in. That’s an operating problem rather than a writing one, and it’s the same problem as knowing which of your open asks are still open.

The reply you want is not the document

Here’s the ordinary version. It sits in every practice management system in the country:

Please return the signed form by April 10.

That message has exactly one acceptable response. Giving it takes three things at once: the time, the file, and the right frame of mind at the moment they read it. Anybody holding two of the three sits still, because the message offers them nothing else to do. You’ve sorted your client list into the people who were ready anyway and the people you now know precisely as much about as you did yesterday.

Ask a question instead. The question is some version of will you make this date, and it gets answered in ten seconds, standing up, with nothing to open.

Three answers come back, and all three are worth having.

Yes. You’re holding a commitment with a date on it, which is a different object from a message you sent. You can plan the week around it, and you can quote it back later.

No, but by the 26th. The most valuable of the three, and the one a compliance request never produces. Your schedule is wrong, and you’ve found out while there’s still room to act. You can move your date. You can move the work. You can start the fallback conversation now, instead of on the 19th. You can tell the client plainly that the 26th is too late for you, and why.

No, and I need help. The bookkeeping is still open. They can’t find the portal. There’s a figure in the draft they don’t understand, and they stayed quiet about it to avoid holding everyone up. This answer is the reason a lot of files sit still, and a message that only accepts a document never hears it.

Silence in answer to a question is information too, in a way that silence in answer to a request is not. A client who leaves a yes or no unanswered has told you something about the file, and it’s usually the third answer.

Four things build the question into the message.

Ask it in its own sentence, and put it last. Give it its own line, clear of the request. “Can you tell me by Thursday whether the 10th is realistic?” is a separate act from “please send the file by the 10th”, and the message needs both.

Give the reply a shape. People answer a question faster when they can see what an answer looks like. “Reply with a date, even if the date is in October” or “just yes or a different day is enough” costs six words and roughly doubles what comes back.

Say out loud that the unwelcome answer is welcome. “If it’s going to be later than that, I’d much rather know now than on the 19th.” This is the single sentence most often missing from a deadline reminder, and it’s the one that produces replies from the clients you most need to hear from. Leave it out, and a client who can’t make the date is choosing between a promise they can’t keep and silence. Silence is easier.

Ask one question only. A reminder carrying a second question gets an answer to whichever is easier. The thread then looks handled from both ends while the file sits where it was.

The ask stays. The message still has to name one thing to do, in one line, and it has to be one thing. A deadline reminder listing five outstanding items is five deadlines, and it gets treated as none of them. Where there are genuinely five, the reminder names the one that has to move first, and the rest goes in a document request.

The failure underneath all of this is worth stating plainly, because it’s the shape most calendar-generated reminders have. A date is not an ask. A message whose entire content is that April 15 is approaching asks for nothing, so it gets read, understood, agreed with and closed, and the file stays exactly where it was.

Two dates, and the one they will act on

Every deadline reminder carries at least two dates, whether or not you write both down. There’s the deadline itself, which usually belongs to a statute or to somebody outside the firm. And there’s the date you need the client’s part in hand, so your own side has room to work. The second is always earlier, sometimes by weeks.

One rule decides most of what follows. The client acts on the latest date visible in the message. Put both in, with the statute’s later than yours and the gap left unexplained, and your date is decoration. They send it on the 14th, because you told them the 15th existed.

So decide which date the message is about before you start writing. There are three answers, and the first is the default.

Your date, alone. “I need the signed authorization back by Tuesday the 10th.” The 15th stays out of it. The client has one date, and it’s the one that governs what they do. This is honest as long as your date is a built one rather than a wished one, and how that date gets built out of the work still sitting on desks at your end is covered in the document guide.

Both dates, with the gap explained. Use this when the client already knows the deadline, which for April 15 they usually do, and would otherwise read your earlier date as padding. Then you owe them the arithmetic in a clause: “I need it by the 10th, because the return then needs two days of review and a day to transmit, and the filing date is the 15th.” A gap with a reason in it is a schedule. A bare gap is a buffer, and clients spend buffers.

The deadline alone. Rare, and right only when the client’s action reaches the date without passing through your desk. A payment the client makes directly. A registration they file themselves. A form that goes straight from them to an agency. Here you give the real date and leave it at that, because this is the cheapest kind of false urgency to detect. They can look it up.

Two failures are worth naming. Both are common, and only one of them feels like a mistake at the time.

Presenting your working date as the deadline. Writing “the deadline is the 10th” when the deadline is the 15th works once. Then the client sees the real date on a notice, or hears it from somebody at the same stage with a different accountant. From that day, every date you give them carries a private discount. The discount stays invisible to you. What you see is that reminders stopped working.

Naming the deadline and leaving out your own date. The client plans on the 15th, sends the file on the 14th, and is genuinely surprised that the return sits there that afternoon. They behaved perfectly well. They used the only date they were given.

One more thing belongs here, because it costs credibility out of proportion to the effort of getting it right. A filing date that lands on a weekend or a public holiday shifts, and dates occasionally move for other reasons too. Quote the actual date for the year in front of you, rather than the one you’ve said every spring for a decade. And when a date moves in the client’s favor, send the update yourself. A postponement the client hears about elsewhere gets spent entirely on their own calendar and none of it on your queue, so the update goes out with your new working date attached in the same sentence.

Four asks that look identical on a calendar

Four different things hide behind a date in a practice, and each one needs its own message. Picking the wrong one is why a great many perfectly well-written reminders come back empty.

Sign. Two minutes, with nothing to find and nothing to weigh up, which makes it the item most damaged by being bundled with anything else. Put a signature in a list alongside three documents and it inherits the postponement of the slowest item there. So it gets its own message, its own subject line, one link or one attachment, and a sentence saying how small it is: “this is the e-file authorization, it opens on your phone, and it takes about two minutes.” Where a joint return needs two signatures, address both people and say which of them still owes one. A message addressed to the household is a message to whichever of them opens the mail.

Pay. Money moves on a lead time of its own. Funds have to move, an owner has to approve, a receivable has to land. A week to ten days is the usual shape, so a reminder arriving the afternoon before lands too late to act on. There’s a harder problem underneath it: a client who pays sends you nothing back, so silence here proves very little. What that message has to carry is worked through in quarterly estimate reminders.

Decide. An election, a contribution before year end, whether to take the extension, which of two treatments to use. The mistake is asking for the decision itself. A decision like that needs more than a paragraph in an email, so the client postpones it, and the reminder becomes a run of reminders that all say the same thing. Ask for the conversation instead: one line for each option, one line for what changes on the date, and an offer of a time. Then the date you’re really reminding them about is the last day that conversation can happen and still leave room, which is usually two weeks before the date they think you mean. Saying that plainly is what gets the call booked, and getting the slot without a five-message exchange is a separate small problem worth solving.

Hand over. A document, a file, a number. This is a document request with a date attached, and the message has two subjects competing for the same four lines. Keep the document as the subject and the deadline as a subordinate clause, which is how that message is built. The one exception is the last message before something changes. That one is genuinely about the date rather than the paper, and it’s below.

Working backward from the client’s errand

Most reminder schedules are built from the deadline: three weeks out, two weeks out, one week out, the day before. Those intervals track the calendar rather than how long the client’s job takes. And the day-before message is the worst of the set, because it arrives after the last moment at which it could have been acted on.

Build the schedule from the errand instead. Two numbers go into it, and only the first is usually counted.

How long the client’s part takes in elapsed time. Elapsed time, rather than time at the desk. A signature is two minutes of work and three days of elapsed time, because it has to survive a trip, two meetings and an evening. A year of bookkeeping is three weeks of elapsed time for a business owner who does it on Sundays. The elapsed number is the one that matters, and it usually runs four or five times the task number.

How long your part takes once theirs arrives. Review, sign-off, transmission, and the queue all of that sits in.

Add the two, add a margin, and the last message places itself. Everything before it is spacing.

Four rules make the spacing work.

Shorten the interval as the date approaches. Ten days out, then five, then two reads as a situation developing. Three evenly spaced messages read as a mailing, and people learn the rhythm and wait for the last one.

Change the fork, and leave the tone where it is. What has to be new in each message is what the client is being asked to settle. The first message is information, the second is a question, the third is a decision. A sequence built that way escalates in content, so the temperature can stay exactly where it started.

Give every message something the last one left out. Where the ask has stayed the same, what you’ve written is a countdown, and a countdown teaches the client that your messages carry no information. Two identical reminders are worth less than one.

The last message goes on the last day it can still work. Work it out: their elapsed time plus your processing time, counted back from the date. That’s the day, and it sits earlier than the day before the deadline.

One more thing about where the count starts. The first mention comes well before the first reminder. The date already exists in whatever message created the work, whether that’s the engagement letter, the organizer, or the note confirming you’ve taken the job on. Engagement letters by email and the onboarding message are where those dates get planted. A deadline whose first appearance in a client’s mailbox is a reminder is a deadline you sprang on them, and they’re entitled to treat it that way.

And the question everybody asks at this point is whether the run can go to everyone at once. It can, on one condition: the message has to be true for every person receiving it, and it has to stand on its own without a reply. A note in January is a good broadcast: partnership and S corporation returns are due in the middle of March, the organizer is open, and here’s the date the firm needs their records by. It goes to three hundred clients and it’s true for all of them. The moment the message has to say where a particular file stands, it belongs to one client, because the sentence that makes a reminder work is the one that only applies to them. A run that mixes the two produces the worst outcome available, which is three hundred replies asking what stage their return is at.

Saying what the date is worth

This message has one thing no other piece of client mail has: the consequence is computable. That’s a considerable advantage, and most reminders spend it on adjectives.

Three classes of consequence, and each is written differently.

It costs them money. Say the mechanism in one sentence, and give them their own number wherever you can compute it. In the United States, a return filed late with tax still owing carries a failure-to-file penalty of 5 percent of the unpaid tax for each month or part month it’s late, capped at 25 percent. There’s a failure-to-pay penalty of 0.5 percent a month on top of that, with interest accruing at a rate the IRS resets each quarter. In a month where both penalties apply the first is reduced by the second, so the combined figure for that month is still 5 percent. The gap between those two rates is the whole reason an extension is worth having, even for a client who can’t pay. The decision itself, along with what to tell them about it, belongs to the extensions guide.

What goes in your reminder is their figure: “if this goes in late and the balance is anything like last year’s, the first month costs about $600.” A number a client can picture moves a file. A percentage leaves it where it is, and a percentage of an amount they’ve never worked out does even less. Where you can’t compute the figure, bracket it honestly rather than gesturing at it.

It costs them a fallback you’re going to take anyway. Usually an extension, and here’s the part that’s easy to get wrong out of kindness. Naming the fallback early deletes the deadline. A client told in the first reminder that an extension is available has been told the date is optional, and they’re right. Hold it back. It belongs in the last message, where it works as a fork rather than a reassurance, and it belongs there with its price attached, because an extension moves the filing and leaves the payment due where it was.

The only cost is inside your firm. A great many real dates come from your own schedule rather than a statute. They’re the date after which the work stops fitting into the week it was planned for. Say that plainly rather than dressing it up as a penalty. It lands as the consequence it is: “if I don’t have this by the 10th, your return moves behind the ones that are ready, and the next week I can give it is the first week of June.” That’s your calendar talking, and for most of the dates a practice sets it’s the only honest urgency available.

Then the rule that governs all three. Name only a consequence you’ll carry out. A date that passes with nothing behind it is a lesson, and the client has now learned it about every date you’ll send them for the rest of the engagement. This is exactly why the fallback belongs late and the queue belongs early. Your queue is a consequence you’ll actually enforce, because it enforces itself.

Two smaller decisions. One sentence, and put it after the ask. A message that opens on the penalty reads as pressure, and with the clients who need reminding most, pressure produces resentment rather than paperwork. Keeping that message warm in the third week of March is a skill of its own. And every countdown carries a number. A phrase that tells the client the deadline is approaching, and leaves out what approaching costs, is doing an adjective’s work where a figure was available.

The last message before the date

The final reminder is a different object from the ones before it. It stops asking and starts closing.

Send it on the last day the client’s action still fits with room left for yours. You can calculate that: their elapsed time plus your processing time, subtracted from the date. If they need a day and you need two, the last call goes three business days out. A message sent the morning before a deadline is a message for your own conscience, and everybody involved knows it.

Four things belong in it.

Where things stand, in one line. The client has lost track. They almost always have.

The single action, and how small it is. If it’s two minutes, say two minutes.

The fork, with both branches named and priced. This is the part that makes it the last message rather than the fourth.

The time you need an answer by, which sits earlier than the deadline and names a specific hour.

Four things stay out. A fourth restatement of the deadline. An apology for writing again. A new item nobody has mentioned before. And a consequence the firm will let pass.

Subject: Your signature, or we file an extension. I need to know by Thursday noon.

Hi Devon,

Your return is finished and waiting on one signature. The authorization is in the message below, it opens on a phone, and it takes about two minutes.

If it’s signed by noon on Thursday the 11th, I file on Friday and you’re done for the year.

If it isn’t, I file an extension on Friday instead. That moves the filing to October 15 and leaves the payment where it is, so we’d still pay the $4,200 we have estimated by the 15th, and the return stays open all summer. It works, and it’s worse than signing.

Either one is fine by me. Tell me which by Thursday noon. And if there’s something in the return you want to talk through before you sign it, say so and I’ll call you today.

Ruth

Both branches are ones the firm will genuinely take, which is what makes the fork a fork rather than a threat. The cost of the second branch is a figure and a date rather than a warning. And the last sentence names the reason a signature most often sits untouched for a week: the client has a question about the return, and stayed quiet to avoid being the person holding everyone up. Where that question is really about a number they weren’t expecting, the answer is a message of its own.

Four situations put a phone call in front of the last message rather than in place of it. The consequence is money. The client has gone silent across two messages. The decision is one they need somebody else for. Or the relationship is already tense enough that tone will struggle to survive being read cold. Call, then send the same message in writing within the hour, with the date and the fork in it. A conversation leaves two memories and no record, and the client usually has to relay it to somebody else.

The morning after the date has passed

Something has to go out, and most firms send nothing. That’s the worst of the available options. Silence after a missed date tells the client one of two things, and both are wrong: that the date was decoration, or that they’re in trouble and you’re somewhere deciding what to do about it.

Four lines.

The date passed. Once, as a fact, with the adjectives left off.

What actually happened as a result. In real terms, including when the honest answer is nothing yet. Firms leave this part out, and it’s the only part the client is reading for.

Where things stand now, with a new date. Build it the same way you built the first one. A genuinely new date, rather than the old one repeated in a firmer voice.

What you need today.

Leave the reproach out, and this is practical rather than a matter of manners. A client who is embarrassed and then blamed goes quiet, and the file that most needs their attention gets the least of it for the next three weeks.

Subject: The 10th has passed. Where your return stands now.

Hi Beth,

The signed authorization didn’t reach me by the 10th, so the return didn’t go in on Friday as planned.

Nothing is lost. The filing date is still the 15th and we can still make it, but I need the signature by noon on the 14th to have room to transmit it.

If that’s not going to happen, tell me today and I’ll file the extension instead, which is a perfectly good outcome and not a failure. The one thing I can’t do is decide it on the 15th.

Simone

Then stop the sequence. Once the date has gone, the reminder cadence is over, and whatever you write next is a different message. It’s either a request for a specific item, which is the document follow-up, or an account of your own slipped date, which is the delay email. Reminders that keep arriving about a date already gone are the clearest possible signal that the messages are generated rather than written.

Where the date passing did cost something real, a penalty, an interest charge, a lost election, a closing that moved, the message stops being a reminder altogether. Say the number, say who carries it, and call before you write.

Six that go wrong

The client who always delivers on the last day. They’re a pattern, and treating them as an emergency for three weeks trains them to ignore you. Somebody who has come in on the final day for six years, and has always made it, hears early reminders as noise. Send one, timed to the point where their errand genuinely has to start, and make it a question. What you want from this client is confirmation that this year is like the others, and they can give you that in four words.

The client who says yes and means it. A promise is a promise, and your loop stays open until the thing arrives. Write the promise back with its date attached, in one line: “the 20th then, I’ll plan around that.” Two things follow. You’re holding a commitment rather than an intention. And when the 20th arrives empty, a message quoting their own date gets answered at a rate a fresh request rarely matches.

The date you invented. Manufacturing an early deadline to create urgency works for one cycle. Then a client notices that last year’s urgent date turned out to be three weeks before anything happened, and they mention it to somebody at the same stage with a different firm. The test that separates a working date from an invented one is whether you can say what happens on it. If the answer to “what changes on the 10th” is nothing, you have a mood rather than a date, and the client finds that out before you do.

The deadline that belongs to somebody outside. A lender’s closing, a buyer’s diligence window, a board packet, a grant application. Somebody else set it, somebody else owns it, and it almost always reaches you second-hand from a client who was relaying it loosely. Confirm it in writing before you build a schedule on it, because the date you were given is frequently the date somebody hoped for. Then say whose it is in the reminder itself: “the 14th is the bank’s date, not mine.” A client who knows the date is external stops negotiating with you about it. Where these dates arrive buried inside forwarded mail with no covering note, spotting them at all is its own problem.

The person who does the thing sits behind the person you write to. Two signatures on a joint return, an office manager who holds the records, a spouse who makes the decision, a controller who schedules the payment. Write to whoever does the thing, copy whoever owns the relationship, and say in the message which is which. Then both of them know whose job it is.

The reminder to somebody who already did it. The cheapest damage in the practice, and the most common. A client who signed on Tuesday and gets Wednesday’s reminder has learned that their replies go unread at your end, and your next reminder gets treated accordingly. This one turns on whether the run knows what has come in. That’s the same question as what to do with the asks nobody has answered, and, in a firm where more than one person sends client mail, who is watching the mailbox in the morning.

What Point does with a date you have named

All of this works on index cards, and firms sent good reminders that way for fifty years. What a tool changes is narrower. Whether the date you promised finds you again before it arrives. Whether the run can tell who has already answered. And how much of the message you assemble from a blank page. Choosing the date, judging whether it’s real, and deciding what the consequence is worth all stay exactly where they are.

The particular failure with reminders is that they’re cheap to write and free to skip. Skipping one costs nothing on the day it’s skipped; the bill turns up in April on somebody else’s file, and nobody connects the two. So anything that makes a reminder happen on its own is worth more here than any improvement to the wording.

Point sorts the mailbox before you get to it and puts what needs you today at the top. That matters here for one message above all others: the reply this page exists to produce. “I can’t make the 20th, is the 26th any use to you” is the most valuable thing in the inbox on the day it lands, and in a list ordered by arrival it reads like one more line. There’s a guide to the weighing itself, and important against urgent is the distinction that decides a week with four dates running in it.

The part touching this page most directly is what happens to a date once it exists inside a message. A day named in an email turns into an item carrying that day, with nobody copying it anywhere. It finds you while there’s still room, rather than on the morning it falls due. That works in both directions: the date you gave the client, and the date they gave you back in their reply. A request you sent becomes a debt with a day on it, and it stands itself down the moment the answer lands. That last part is the whole of the problem in the last section. A reminder run that stops for the people who have already replied is a run you can keep sending, and a run that keeps chasing them is one you’ll quietly abandon in March.

Each thread carries a plain one-line summary, so the fact you want before writing is there to read rather than excavate. That fact is what you last told this client, and when. Handing somebody a date that quietly contradicts the one you gave them last week is a small mistake with a long tail. Replies come back drafted in your own hand, so the third reminder in a sequence is an edit rather than a composition, and the send stays with you. A watch set in plain words covers an arrival you’re waiting on, so the signature that comes back at four on a Friday reaches you at four on a Friday. Where the reminder turns out to need a call instead, Point runs the back-and-forth to find the slot and writes it into the calendar you already keep.

Each type of action carries its own setting, running from suggest-only through review to fully handled, and review is where every one of them begins: the work gets prepared, and then it waits. On this subject the class worth raising first is the noticing rather than the sending, which means the watch and the item that resurfaces before its date, both of which stay on your own screen. The last message before a deadline stays with you at every setting. It names a fork, it commits the firm to a consequence, and it belongs to whoever’s name is at the bottom of it. The autonomy dial sets that out properly. Whatever is done for you is recorded as it happens, in order and with times against it, and the entry itself is where you accept it, refuse it or put it back. One limit sits outside all of it, and every mail product shares it: once a message has reached the other side it’s out of your hands, which is a reason on its own to read a fork twice before sending it.

Starting is a single sign-in against the Gmail or Microsoft 365 mailbox the practice already runs. Your mail stays where it is, and your address stays the same.

Most of what this page is about stays with you. Whether the 10th is a real date or a hopeful one. Whether this client’s yes is a real yes. Whether the consequence is worth naming. Whether the person who has to sign is the person you’ve been writing to. Everything Point does do is set out on the benefits page, and the buying question gets worked through a practice in AI email for accountants. And if the thing really stopping you is the prior question, whether client mail should be going near an AI product in the first place, settle that one before any of this: it is taken apart properly here.

Common questions

How do I write a deadline reminder email a client will actually answer?

Name one action, give one date, and end with a question the client can answer without doing the action. “Can you tell me by Thursday whether the 10th is realistic?” gets replies from the people who are going to miss the date, which is more than a request for the document itself ever produces. Add the sentence that makes the unwelcome answer safe, something like “if it’s going to be later, I’d much rather know now than on the 19th”. Leave that sentence out, and a client who’s behind is choosing between a promise they can’t keep and silence. Keep the consequence to one line, and put it after the ask.

How far ahead should the first reminder go, and how many should I send?

Work backward from how long the client’s part takes in elapsed time, rather than from the deadline. A signature is two minutes of work and three or four days of elapsed time. A payment needs a week to ten days, because money has to move. A year of records needs three to six weeks. Add your own processing time, add a margin, and that gives you the last message. Two reminders is right for a signature, three for anything that needs a conversation or a month of the client’s evenings, and one is plenty for a single number. Shorten the gaps as the date approaches, and give every message something the last one left out, because two identical reminders are worth less than one.

Should I give the client my date or the actual filing deadline?

Give yours, and give it alone unless the client already knows the real one. Clients act on the latest date they can see, so a message carrying both with the gap unexplained has effectively published the later one. Where the client does know the deadline, say what the gap is for in a clause: “I need it by the 10th, because the return then needs two days of review and a day to transmit.” Keep your working date and the statutory one clearly apart. Presenting one as the other works for a single cycle, and after that every date you send gets silently discounted.

Should I mention penalties in a deadline reminder?

Yes, when they’re real, once, and in the client’s own numbers. A sentence putting the first month’s penalty against the balance they actually owed last year moves a file. A percentage of an amount they’ve never worked out leaves it where it is. Where the only cost is inside your firm, say that instead, and it’s usually your own calendar: the work moves behind the files that are ready, and the next week you can give it is in June. Name only consequences you’ll impose, because a date that passes with nothing behind it teaches the client what all your other dates are worth.

What do I write the day after a client misses the date?

Four lines, sent the next morning. The date passed, stated once with the adjectives left off. What actually happened as a result, including when the honest answer is nothing yet, because that’s the only part they’re reading for. Where things stand now, with a genuinely new date rather than the old one repeated. And what you need today. Leave the reproach out: an embarrassed client who is then blamed goes quiet, and this is the file that can least afford it. Then stop the reminder sequence, because whatever comes next is either a request for a specific item or a conversation about your own timetable.

Can I send the same deadline reminder to my whole client list?

Only when it’s true for everyone receiving it and it stands on its own without a reply. A January note is a good broadcast: the March filing date, the date your firm needs their records by, and where the organizer is. The moment the message has to say where a particular file stands, it belongs to one client, because the sentence that makes a reminder work is the one that only applies to that client. A run that mixes the two produces the worst available outcome, which is a few hundred replies asking what stage their return has reached. The one genuinely repeatable run in most practices is the estimated payment sequence, and it has a guide to itself.

The short version

Send the reminder while the client is still on time, because that’s the only stretch in which an honest answer is cheap for them to give. Ask a question instead of asking for a task. “Will you make the 20th?” gets answered in ten seconds by everyone, and the answer is worth more to your week than the document, most of all when the answer is no. Say out loud that a later date is a welcome reply, or the client is choosing between a promise and silence. Decide which date the message is about before you write. Clients act on the latest date they can see, so give yours alone, or give both with the arithmetic of the gap in a clause. Keep a working date and a statutory one clearly apart. Build the schedule from the client’s elapsed time plus your own processing time, rather than from the deadline. Shorten the intervals as the date nears, and change the fork in each message rather than the tone. Put the consequence in one sentence after the ask, in the client’s own figures where you can compute them. Hold the fallback back until the last message, so the deadline survives the first one. Send that last message on the last day it can still work, with both branches named and priced, and an hour by which you need an answer. Then, the morning after a date goes by, write anyway: what passed, what it cost, the new date, and what you need today.