The matter is almost ready to move. You need one signed engagement letter, last year's return, and a single bank statement, and then the whole thing goes forward. Instead it sits, because the client hasn't sent the last piece, and you've already asked twice.
So you're stuck in a familiar spot. Ask again and you feel like a nag, chasing a person who's paying you good money. Don't ask, and the deadline creeps closer while the file gathers dust. Neither option feels like the professional you want to be.
Here's the good news: most of that chasing is a process problem, not a relationship problem. A clear request, a place to drop the files, and a few well timed reminders will collect most of what you need before you ever send a personal note. You save the personal note for the one client who genuinely needs a nudge, and it lands better because it's rare.
Where the hours actually go
Chasing a document isn't one task. It's a dozen little ones spread across two weeks. You draft the request, remember what this particular client already gave you, send it, wait, check whether it arrived, dig through your inbox to confirm, send a nudge, field the reply asking which statement you meant, and finally save the file where it belongs.
Do that across thirty clients during tax season or a heavy stretch of case prep and it's easily an afternoon a week, most of it not billable. Worse, it's the kind of scattered work that interrupts the deep work, the return or the brief, that clients actually pay for.
Automation won't do your judgment for you. It's very good, though, at the repetitive shell around the judgment: the asking, the reminding, the filing, and the keeping track of who still owes what.
Build the checklist once, then reuse it
Almost every request you send is a variation on a handful of standard ones. A new tax client needs the same core set of documents as the last new tax client. A personal injury intake, an estate matter, a new group dental plan: each has a predictable list.
Write those lists down once, per matter type. A document checklist is just the itemized set of things you need before you can start, in plain language a client understands. "Bank statements" becomes "your December statement for every checking and savings account." Precise beats short, because a vague request is what generates the confused reply and the second round of chasing.
- Name each item the way the client would recognize it, not the way it reads on a form.
- Mark what's required versus optional so nobody stalls the whole packet over a nice to have.
- Note the format you can accept, a photo, a PDF, a login, so you don't get forty screenshots you can't read.
- Keep one master version per matter type and tweak per client, rather than writing each request from scratch.
Once these lists exist, the software can send them, track them line by line, and check items off as files arrive. That per item tracking is the part that quietly kills the nag, because the system reminds people only about what's still missing, never about what they already sent.
Use a portal, not your inbox
Email is a bad filing cabinet. Documents arrive buried in threads, get renamed by phone cameras, and sometimes carry a client's Social Security number in plain text through a channel you don't control. For a practice with real compliance obligations, that last part alone is reason enough to change.
A secure client portal is a private web page where a client sees their checklist and uploads files straight into your system. No attachments, no reply-all, no hunting. The good ones show the client exactly what's left, which means many people finish the list on their own, the same way a progress bar makes you want to fill it.
You don't need anything elaborate. You need a link that's easy to open on a phone between meetings, a checklist behind it, and uploads that land somewhere organized and encrypted. If your practice management software already includes a portal, start there before buying anything new.
A reminder cadence that collects without nagging
The trick with reminders is that they should feel like a service, not a poke. Space them out, keep them short, and make each one do a small favor: tell the person exactly what's outstanding and how to send it.
A cadence that works for most tax and case-prep timelines looks like this:
- Day 0: the initial request with the full checklist and the portal link.
- Day 3: a gentle "just a heads up, here's what's still outstanding," listing only the missing items.
- Day 7: a second reminder that mentions the deadline in plain terms.
- Day 10 to 12: a short note that the clock is getting tight, still friendly.
- After that: the system flags the client for a personal call from you, and stops the automatic emails.
That last rule matters more than the timing. When a machine has asked politely a few times and nothing's moved, more machine messages won't help, and they start to feel like pestering. Hand those few stragglers to a human, you, and let the automation quietly handle everyone else who just needed a reminder.
One more setting is worth getting right: stop the reminders the instant a document arrives. Nothing burns trust faster than a "you still owe us your W-2" email sent the morning after the client uploaded their W-2.
Keep it sounding like you
An automated message doesn't have to read like a parking ticket. You write the words once, in your own voice, and the system just handles the timing and the mail merge. Warm, brief, and specific carries a long way.
A few habits keep the tone right:
- Write like a person: "Hi Susan, we're almost ready to file, just need a couple of things." Not "This is an automated notice regarding outstanding items."
- Always name what's left, so the message is useful even to someone who did most of it.
- Give an easy out: a line like "already sent it? ignore this, and thanks" saves a defensive reply and an awkward moment.
- Sign it from a real person at your office, with a real phone number, so a confused client can reach someone.
Done this way, the reminders read as helpfulness, not surveillance. The client feels tracked in a good way, the way a sharp paralegal or a steady front desk keeps things moving without ever making anyone feel managed.
What this won't fix
Automation collects documents. It doesn't judge whether a document is the right one, complete, or legible, and it won't chase the client who's gone quiet because the news is bad. A photo of page one of a three page statement will sail through an upload and still be useless.
So keep a human review step. Someone glances at each packet to confirm the pieces are real and readable before you mark the file ready. And for the genuinely reluctant client, the one dodging a hard conversation, a warm phone call will always beat the fourth email. The system's job is to shrink that pile of hard cases down to the few that actually need you.
Worth doing this week
You don't have to rebuild your whole intake to feel the difference. Start small.
- Pick your most common request, one return type or matter type, and write the document checklist in plain, client-friendly language.
- Check whether your existing practice software already has a portal and a reminder feature. Most do, and it's often already paid for.
- Draft three short reminder messages in your own voice: a friendly nudge, a deadline note, and a final heads up.
- Set one hard rule: reminders stop the moment a file arrives, and stragglers get a human call, not more email.
- Run it on the next ten clients and count the follow-ups you didn't have to send by hand.
Get that loop working for one matter type and you'll want it for the rest. If you'd like help setting it up around the software you already run, that's the kind of quiet, practical automation we build with practices around Massachusetts. Either way, the goal's the same: collect what you need, keep the relationship warm, and get your afternoons back.