Most clients mean to send the document. Managing client document requests well comes down to what the first ask contained. A document arrives late for about six reasons, and only one of them is forgetting. A reminder is the right treatment for that one. The other five are settled before you ever send it.
- A request works when the client can act on it the morning it lands. That’s where most of them are won.
- A request is seven items in seven different states. A follow-up written as though it were one asks again for what already came.
- Acknowledge a delivery by name and you’ve saved yourself the chase.
- Sending the same message twice is sending it once. Each fresh attempt changes the channel, the person or the consequence.
Why the document has not arrived
Chasing gets easier to think about once you treat silence as six things rather than one. A document that hasn’t come sits in one of about six states. Some of them are far more common than others.
The first is that it doesn’t exist yet. A broker’s consolidated statement, a partnership K-1, a corrected form that replaces one already issued: the client can forward these the day somebody sends them. In a practice this is probably the largest single cause of an unanswered document request, and it’s entirely immune to reminding. What the file needs here is a date. The day the document is expected.
The second is that you and the client are using different names for the same paper. You used the name the tax code uses. The paperwork on their kitchen table carries the name their bank uses, and the two look like different things. Somebody unsure whether the thing in front of them is the thing you meant will sit tight rather than send the wrong item. From your side that looks exactly like being ignored.
The third is that they have it, and sending it is a chore. It’s paper. It’s in a drawer at the office. It’s behind a login they created in 2019, where the password reset goes to an address they gave up years ago. The distance between having a document and having sent it is where most of the middle of the year goes.
The fourth is that they sent some of it. That’s common, it gets misread often, and it has a section of its own below.
The fifth is avoidance, and it repays reading properly. A client who’s sitting on the bookkeeping has usually still got the bookkeeping to do. A client sitting on a brokerage statement occasionally knows what’s on it. Silence around one specific item, from somebody who answers everything else promptly, is information rather than rudeness. What moves it is a message that makes the next step smaller. Repeating the deadline leaves it where it is.
Only the sixth is forgetting.
Laid out that way, the standard follow-up starts to look strange. “Just following up on the below” is a reminder, and a reminder treats one cause in six. Forgetting is far from the most frequent of them. That’s why the second copy performs about as well as the first, and why some firms end up sending four.
The ask that does not need chasing
Five of those six are decided by the first message, so the original request is by a distance the cheapest place to spend effort. A request the client can act on the morning it lands comes back on its own. One that leaves them stuck takes three chases.
Name each document the way the client’s own paperwork names it, and say who issues it. “The 1099-INT your bank sends in January” describes an envelope on a table. “Interest income” describes a line on a return, which is your vocabulary rather than theirs. Where they’ve sent the same thing before, point at that. It does more than any amount of precision: the same statement you sent last February, for this year. A memory is easier to act on than a definition.
One item per line, and few enough lines that somebody can hold them in their head. A block of nine reads as a project rather than a request, and projects get postponed while errands get done. Where the list genuinely is long, stage it. Ask for the three that release the most work, and hold the rest until those are in. Running the firm inbox makes the case for the client rather than the message being the unit you read by. The same logic runs one level further down, where the unit is the item rather than the request.
Say what it blocks, once, plainly, and leave the countdown out of it. “We cannot start the return until this arrives” is a fact. It costs eight words, and it’s the only sentence in the message doing any persuading.
Then one more line, and it settles the biggest cause on the list. Where the document may still be on its way, ask for a date. “If it has not reached you yet, tell me roughly when you expect it” turns an unknown into an entry with a day against it. A client can answer that from a phone at a bus stop, which is a much lower bar than finding paperwork. The answer is worth more to you this week than the document would be, because it tells you whether the file is on track and spares you asking again in two weeks.
Two smaller decisions earn their place. Make sending cheap. A legible photograph of a paper statement, taken at the kitchen table, is worth more to the practice than a properly scanned copy that arrives in April. And keep questions out of a document request. A message asking for four documents that also asks whether they sold the rental gets a reply about the rental, because answering is quicker than fetching. Now both of you believe the thread has been dealt with.
Partial delivery is the normal case
Ask for seven things and you’ll get three, then two, then a pause. That’s a client behaving normally. It’s what happens when somebody works through a list in the order the papers turn out to be findable, and it’s how most document requests in a practice actually resolve.
Firms nevertheless track requests as though they were binary. The record says the request went out on the fourth and silence since, or it says the client has replied. The real state is seven items. Four arrived on the ninth, one arrived for the wrong year, and two have gone unmentioned since.
Tracking at the level of the message flattens all of that, so the second message resends the original list. A client who spent forty minutes on Sunday evening digging out four documents then opens a note asking for all seven again. What they take from it is that their effort went unnoticed, or worse, that what they sent got lost on the way. The next batch comes slower, usually with a phone call attached asking whether you received the first lot.
So the unit of a document request is the item. Written down that way a request carries a small state: what was asked, what came, when it came, and what’s still out. Everything useful about chasing follows from that state living somewhere other than inside the thread.
It also changes what the record is for. A firm that knows it’s missing the K-1 and the vehicle log can answer the client’s own question, which is nearly always some version of what do you still need from me. Answering that in one line, correctly, on the day they ask, does more for the relationship than any amount of well-worded chasing. It works when somebody has been keeping the item-level state as deliveries came in, rather than reconstructing it from a forty-message thread on the morning of the call.
The receipt that chases for you
The single change that reduces chasing most isn’t a better follow-up. It’s acknowledging deliveries by name.
A reply that says what arrived and what’s still out does four things at once. It confirms the send. A client who’s been told their statements landed leaves them alone next week, and later you’re both working from the same record of what arrived. It corrects their copy of the list, which is always less accurate than yours and usually out of date. It’s a follow-up that reads as a thank-you, because it opens with what they did rather than with what’s outstanding. And it costs seconds, because you write it against a list you’re already holding.
Thank you, that is the bank statements and the mortgage interest in. Still to come: the K-1 and the mileage for the van.
Two sentences, and the second one is a chase.
Do that on every delivery and most of your chasing stops being a separate job. It rides on messages you were sending anyway. It arrives while the client is already thinking about their file, which is the best moment there is to ask them for anything, and the one moment a scheduled reminder can never hit.
The record it leaves behind matters too, and that argument belongs to running the firm inbox, which sets out why a practice keeps its mail rather than clearing it. A receipt is the same evidence written from the other end, and both of you agreed to it at the time.
When you do have to chase
Some requests go quiet anyway, and the rule for those is short. Sending the same message twice is sending it once. A second attempt that repeats the first has already been read and already been left. All it adds is the impression that your messages can safely be left again.
So each attempt changes one of three things.
Change the channel. For documents the phone call is worth more than it is for almost anything else you do. Fetching a document is an errand, and a call takes the errand off the client’s evening. In ninety seconds you find out which of the six states you’re in. You can often identify the document while they’re holding it. Where it’s still to be issued, you come away with a date. Firms treat the call as escalation. For a document chase it’s closer to a shortcut.
Change the person. A married couple filing jointly is two people, and one of them handles the paperwork. Which one it is often differs from whoever signed the engagement, so it’s worth checking before you write. A business client has an owner who rarely answers and a bookkeeper who always does. Writing to the second address is simply asking whoever has the document. Inside the firm the same move runs in reverse. The partner asking once is a different message from the preparer asking for the fourth time, and everybody involved knows it.
Change the consequence. This is the last rung, and the only one with any force in it, which is exactly why it has to be true. A sentence saying what changes and when works: if this is not with us by the twelfth the return goes on extension. It works once. Say it, let the date pass, and carry on as before, and you’ve taught that client that your dates are decorative. Every chase you send them afterwards costs more, for as long as they’re a client.
The dates in those sentences come out of arithmetic. Running the firm inbox derives the first one from the filing deadline and the work still to do at your end, and inbox zero during busy season explains why the same sum returns a much earlier answer in March than in July. What belongs here is that the rungs get used in order, and each of them once.
How fast people reply to anything at all, and why a long and careful message is answered slowest, is measured in unanswered emails. What’s particular about documents is that you’re waiting on an errand rather than on a decision. Errands respond to being made smaller far better than they respond to being repeated.
The clients you chase every year
Count the chases at the end of a year. Count the chases rather than the messages: the second and third and fourth asks for the same item. They concentrate hard in most practices, and the same names come up in roughly the same order every year.
That concentration is the useful finding, because it moves the problem out of the mailbox. Ten clients generating most of your chasing is a fact about ten relationships. Better wording leaves it exactly where it is. The repair belongs at the start of an engagement rather than in the third week of March.
The repairs are unremarkable and they work. Ask that client earlier than everybody else, on the honest understanding that their reply time is longer. Open with a call rather than an email, since you already know how the email goes. Split their list in two and send the second half once the first is in. Where the bottleneck is the client’s own records, the conversation is about bookkeeping rather than about documents. And where all of that leaves things where they were, the honest version is a conversation about terms. What the firm will do, by when, and what happens when the papers are late. That’s a question of scope and fees rather than of email.
What makes any of that possible is writing it down as a property of the client rather than of the season. A firm that rediscovers each February that one client needs six weeks and two phone calls is paying for the same knowledge annually. Recorded once, it becomes next year’s plan, and that client gets asked in December.
One caution. The chronic non-responder is often their bookkeeper rather than the client, and that bookkeeper is themselves waiting on a bank. Sometimes it’s a third party who has no relationship with you at all. Pushing harder down that line goes nowhere. The move is to ask the client to chase the party they have standing with. That’s a different message with a different author, and it belongs on your list as something you’re owed rather than as something sent.
Where does Point fit?
All of this works on paper. Practices chased documents on index cards for decades, and the careful ones did it well. What a tool changes is how much of it a person has to carry: the remembering, the matching and the first draft of the words. The judging stays where it was.
Point reads the mailbox before you get to it, and ranks it on importance and urgency rather than on arrival. A client with a date against them sits above a software renewal. The weighing behind that ranking has its own guide. Each thread carries a one-line summary, which on a document thread is most of what you want to know: whether anything came, and whether it was the thing you asked for.
The chase rests on two capabilities rather than one. A request you send is held as something owed to you, rather than disappearing into the sent folder, and it returns to you on the date you set rather than the day it occurs to you. And Point notices when the answer has already arrived. The follow-up gets marked as looking done and waits for you to agree, so a chase that’s already been answered stands down instead of going out. That second half is what makes an automatic follow-up safe to point at clients at all.
For a named item you’re waiting on, a standing request in plain words is enough. You hear once, on the day it lands, rather than checking. Attachments gather into a single list instead of living inside threads, each one still joined to the message that brought it, which is the difference between knowing a statement arrived and being able to put your hand on it. Ask a question of a document and the answer comes back with the place in the file it was read from. That counts for a lot in a trade where most of what a client sends you sits inside the paperwork rather than in the note above it.
Replies come back drafted the way you write, so the acknowledgment naming what arrived and what’s outstanding is an edit rather than a composition. And Point runs the scheduling back-and-forth itself on the days a chase turns into asking for fifteen minutes. Each kind of action carries its own setting for how far Point goes alone, and it starts at review. Review prepares the work and then holds it for you. The acknowledgment is the one worth raising first. The fourth chase, the one naming a consequence, wants a person reading it before it goes. Everything Point does goes down in order, with a time against each line, and an action can be reversed from the line that recorded it. One thing stays out of reach, and it’s the same in every mail program: a message that has already reached the recipient’s server can’t be pulled back.
Point sits on top of whichever mailbox the practice already has, Google or Microsoft. The address on your letterhead stays the same, and there’s nothing to move.
The list stays with you. Point works a thread at a time, so the fact that one client owes you seven things lives in your own records. Ticking the item in your tax software is yours too. So is judging which of the six states a silent client is in. Item-level state stays yours. What a tool carries is the waiting, the arrival and the words. Everything Point does is listed on the benefits page, and Point for accountants takes the same ground through a practice. Whether a tool belongs in client mail at all is its own question, answered in full in is it safe to use AI with client financial data.
Common questions
How often should I follow up on a document request?
An interval answers a question about manners, and what you need to know is which of the six states the request is in. Where the document exists and the client has it, the date comes out of arithmetic rather than politeness. Take the filing deadline, subtract the work still to do at your end once it arrives, and there’s your date. That sum is set out in running the firm inbox, and the answer moves earlier as the queue on the desks grows. Where the document is still to be issued, the chase has nothing to land on, and the calendar entry belongs on the day it’s due out. One rule holds across all of them: a second attempt identical to the first is a repeat rather than an attempt.
What should a document chase email say?
Open with what you already have. A message that begins with the four documents that arrived reads completely differently from one that begins by asking for seven. That’s the difference between a client whose Sunday evening counted and one who suspects it went to waste. After that, name what’s outstanding, in the words their own paperwork uses, and give the one sentence about what it’s holding up. Repeating the original list unchanged is the commonest form a second chase takes, and it’s the reason so many of them need a third.
The client says they already sent it. What now?
Two answers, and the useful one is upstream. In the moment, say what you hold and ask for the rest by name. That settles it while both of you keep your footing, and reasonably often they did send it, to an address the firm stopped reading two years ago. Upstream, this conversation is nearly always the bill for an unacknowledged delivery. A client told on the day that their statements arrived keeps the K-1 separate in their own mind, because every receipt you wrote kept their record of what they sent in step with yours.
Would a client portal stop the chasing?
It removes one cause and leaves the other five standing. A portal is a better destination for a document than an email attachment. Transport is cleaner, the confidentiality question is easier to answer, and files land somewhere structured rather than inside a thread. The other five survive it. A form that’s still to be issued stays unissued, a client still has to work out which of their papers you meant, and a scan on a Sunday night is still a chore. Firms that adopt one commonly find the volume of chasing unchanged, and the chasing now conducted by email about the portal. Worth having for what it’s good at, and expect the chasing to carry on beside it.
Can the chasing be automated?
Partly, and the half that automates is the half you’d hand over first. Remembering is mechanical. The date was decided the moment you sent the request, and a scheduled return holds it better than memory does. Wording the second and third attempts stays yours, because each one has to change something and what it changes depends on the client. The failure worth naming is a reminder that goes out blind to what already arrived. It tells somebody who sent six of nine documents last Thursday that you’re still waiting on their paperwork. That costs you more than silence would, and it’s the ordinary result of automating at the level of the message. In Point the return is handled, and a follow-up stands down once the reply is in. How much further Point goes is set per kind of action, and it starts at review.
The short version
A document is late for about six reasons, and only one of them is forgetting. That’s why the fourth copy of a reminder lands like the first. Most of the repair sits in the original ask. Name the document the way the client’s own paperwork names it. Keep the list short enough to be an errand rather than a project. Say what it blocks. Where the thing may still be on its way, ask for the date instead. Track the request as items rather than as a message, because partial delivery is the normal case. Acknowledge every delivery by name, since a receipt that also says what’s still outstanding is a chase that reads as a thank-you. When you do have to chase, change the channel, the person or the consequence each time, and only name a consequence you’ll honor. Then count the chases at year end. They gather on a handful of clients, and those get fixed in December rather than in March. Each of the other recurring jobs in a practice has its own guide in this collection, and AI email for accountants is where the buying question gets sorted out.