To chase clients for documents without souring the relationship, run the same fixed sequence for every client: one named owner, a short list of exactly what is still missing, a set number of touches on set days, and a phone call once email stops working. Clients read a predictable schedule as process, not pressure.
A missing document follow-up workflow with one owner per client
A missing document follow-up workflow is the fixed set of steps a firm takes between the first request and the day the file is complete. It works when one person owns each client's chase from start to finish. That owner sends every reminder, makes every call, and hands the finished folder to the preparer with a short note.
One owner matters more than the wording of any email. When three staff members each send a reminder in the same week, the client gets three different lists and answers none of them. When nobody owns the client, the reminders stop in late February and restart in a panic in April. A named owner gives the client one name to reply to and gives the firm one person to ask about status.
The owner does not have to be the preparer. Many firms give the chase to an administrator or a junior staff member, because chasing is about persistence and record keeping, not technical judgment. The handoff point is what needs defining. A clean rule is that the chaser owns the client until every line on the expected-documents list is received or marked not applicable, and then passes the folder to the preparer with two things: the list itself and a note of anything odd the client said along the way.
The list the chaser works from should be the client's outstanding items and nothing else. The post on tracking missing client documents explains how each expected line gets a received, missing or duplicate status, and the chase uses only the missing lines.
A five-step chase workflow, with example timings
The table below is an example schedule for an individual return. The day counts run from the date the first request goes out. Adjust them to the firm's own season and staffing.
| Step | Day (example) | Channel | Owner | What it says |
|---|---|---|---|---|
| 1. First request | Day 0 | Email with upload link | Chaser | Full expected-documents list, one place to send files, a target date |
| 2. First reminder | Day 10 | Chaser | Only the items still missing, with issuer names | |
| 3. Second reminder | Day 20 | Email plus text message | Chaser | Shorter list, a specific date, an offer to call |
| 4. Phone call | Day 28 | Phone | Chaser | Walk through each missing item, agree a date |
| 5. Decision notice | Day 40 | Email and letter | Preparer or partner | What the firm will do on the decision date if items are still missing |
For a fictional client, Dana Okafor at Example Accounting, step 2 might list "Ridgeline Brokerage consolidated 1099, account ending XXXX-4821" and "Canopy Partners K-1," and nothing else. Step 5 belongs to someone senior because it puts a deadline consequence in writing, which is the subject of the post on handling unresponsive tax clients.
When should chasing documents move from email to a phone call?
Chasing documents should move from email to a phone call after two unanswered emails, or sooner when a missing item is one the client cannot get, such as a K-1 from a partnership or a form from a closed account. A call replaces guesswork with an answer: the client has the document, knows when it is coming, or needs help.
Two unanswered emails is a practical trigger because the first reminder can be missed for ordinary reasons and the second usually cannot. Silence after both often means the client is stuck, not careless. They may not know what a 1099-B is, may have moved accounts, or may be waiting on someone else. Email cannot find that out. A five-minute call can.
The call works best with a short script. Open with the purpose: "I'm calling about three documents we still need for your return." Read each item by name and issuer. For each one, ask a single question: do you have it, do you know when it is coming, or do you need help getting it? Write down each answer next to the item. Close by agreeing one date for everything that is in the client's hands, and confirm that date by email the same day so there is a written record.
Some items justify an early call regardless of how many emails have gone out. If a client's expected list includes a form from a brokerage account that was transferred during the year, the post on finding the figures for a missing 1099-B explains why the form may come from the old broker. A call at step 2 can save two weeks of reminders the client did not understand.
Text messages sit between the two channels. A short text that says a reminder email was sent, with the number of items still missing, gets an email opened without asking the client to read a long list on a phone.
How many reminders before an extension?
The number of reminders before an extension decision should be set in advance, and three written reminders plus one phone call is a workable example. More important than the count is the date: pick a decision day, a fixed number of days before the filing deadline, and tell the client that date in the first request.
For tax year 2025 individual returns, Form 4868 (2025) states that the return and the extension request are due April 15, 2026 for most people, and that an extension moves the filing date to October 15, 2026. It also says the extension does not extend the time to pay. That means the decision day has to leave time to estimate what the client owes as well as to file a form.
A decision day two to three weeks before the deadline gives the preparer room to work with whatever has arrived. When the day comes, the chaser hands the preparer the current outstanding list, and the preparer decides whether to prepare the return, extend it, or take another path. The trade-offs between extending and filing now are covered in full in filing an extension because of missing documents, so the chase workflow only needs to make sure that decision happens on a known date with a known list.
Sending more reminders past the decision day rarely helps. After the decision, the message changes from "please send" to "here is what we did and what we still need," and it comes from the preparer. The reminder schedule itself, including how far apart to space touches across a whole season, belongs to the post on planning client document reminders.
Firms that start the chase late compress the schedule. A first request sent in mid-March cannot fit five steps before a decision day in early April, so the gaps shrink to a few days each and the call comes sooner. Starting the sequence in January keeps the gaps comfortable; the post on when 1099s arrive lists the dates each year-end form is due to the client.
Logging every document chase in the client file
A chase log is a dated record in the client's file of every request, reminder, call and reply. Each entry names the date, the channel, who made the contact, which items were asked for, and what the client said. With a log, anyone at the firm can pick up the thread if the chaser is out.
A useful log entry is short and specific. "Mar 4, 2027, phone, J. Patel: client says 2026 Canopy K-1 expected mid-March, will forward on arrival; brokerage 1099 uploaded today" tells the next person everything. "Called client, left message" tells them almost nothing. Record the items by name, not by count, because "two items outstanding" goes out of date the moment one arrives.
The log also protects the firm. When a client later says nobody asked for a document, the log shows the date and the wording of every request. When a preparer wonders why a return was extended, the log shows the decision day, the outstanding list on that day, and the notice the client received. Keep sent emails and letters with the log, or link to them, so the entry and the evidence sit together.
Keep the log in the same place as the client's documents and expected-items list. A log in a personal inbox or a separate spreadsheet drifts from the file within weeks. The tax season workflow category has more on organizing the firm's season around shared records like this.
Chasing mistake: asking for documents the firm already has
The most damaging chasing mistake is asking a client for a document the firm already has. It tells the client their earlier effort was wasted and that the next reminder may be wrong too. The fix is a rule: before every follow-up, the chaser checks the client's folder against the outstanding list, then sends only what is still missing.
This mistake usually comes from three causes. The first is a list typed by hand that never got updated when a file came in. The second is a file that arrived but was never opened, such as a 30-page PDF that held the missing 1099-DIV on page 14. The third is a document sent to a different staff member's inbox and never moved to the client folder.
Each cause has a check. Generate every reminder from the expected-documents list rather than retyping it. Open and match every incoming file before the next reminder goes out; the tracking post shows how to match an incoming upload to an expected line by type, issuer and period. Route every channel to one client folder so nothing waits in a personal inbox.
Schema CPA handles the matching part: each client sends files through one upload link, every page is classified by document type, issuer and period, and the reminder it drafts lists only the items still flagged missing. A staff member reads that draft and sends it, which keeps a person in charge of every message the client receives. The client tracker demo on the homepage shows the received, missing and duplicate view the draft comes from.
A related mistake is asking for a document the client never had to send. If a mortgage was paid off or an account closed, the line should be marked not applicable with a note, not chased three times. Ask about changes in the first request so the list starts accurate, and the post on telling a client what is still missing covers how to word each item so the client recognizes it.