Client document reminder emails: a ladder that stops when files arrive

It's February. You've sent a client their checklist, and three weeks later you have the W-2 but not the 1099-B, the property tax bill or the daycare receipts. Someone at the firm writes a reminder. Then another. Multiply that by sixty clients and chasing becomes a part-time job nobody bills for.

This article covers what firms say about the problem, how to set up reminder emails that stay polite and stop on their own, and the data-security rules that shape what those emails may contain.

Not legal or professional-standards advice. We build and test automations; we're not lawyers or CPAs. This is a plain-English summary of primary sources, checked on October 28, 2026. Your written information security plan, your state board and your counsel come first.

How big is the problem?

The most recent public number comes from a vendor. Financial Cents, which sells workflow software to accounting firms, surveyed 816 firm owners and admins for its 2025 State of Accounting Workflow and Automation Report. Getting documents from clients was the biggest workflow issue they named, ahead of manual admin tasks. One respondent put it this way: "Client reminder emails were manual and exhausting. Most of my time was spent chasing, not working."

It's a vendor survey, so treat it as a sign rather than a census. But anyone who has worked a tax season will recognize it.

What a good reminder ladder looks like

A ladder is a fixed set of reminder days, counted from when you first asked. We use day 0, 3, 7 and 14. What makes it work is less the days than the rules around them:

1. One email per client, listing everything still missing. Not one email per document. A client with five open items gets one message with five lines.
2. It stops item by item. As soon as a document is marked received, it drops off the next email. When the list is empty, the client hears nothing more and the preparer gets one "all documents received" note.
3. Missed days don't bunch up. If the automation was off for a week, the client gets one reminder with the current list, not three in a row.
4. Day 14 goes to a person. After the last reminder, the preparer is told, so a phone call or a scope conversation can happen. Automation shouldn't keep emailing forever.
5. A pause list. A client in a hard week, or one you're already talking to, can be paused by adding them to a list.
6. Running twice sends nothing twice. Each reminder is logged, so a restart or a double trigger never doubles an email.

What the email should never ask for

Tax documents carry Social Security numbers, account numbers and income figures. Two sets of federal rules matter here.

• The FTC Safeguards Rule covers tax preparers. Its definitions in 16 CFR 314.2 list tax preparation firms among the businesses it applies to. Section 314.4 requires you to "Protect by encryption all customer information held or transmitted by you both in transit over external networks and at rest" and to use multi-factor authentication "for any individual accessing any information system". Firms with data on fewer than 5,000 consumers are exempt from a few parts (314.6), but not from encryption or MFA.
• IRS Publication 4557 (Safeguarding Taxpayer Data) says tax preparers "must create and enact security plans to protect client data" and to "Encrypt all sensitive files/emails, especially those with the taxpayer's personally identifiable information."

Ordinary email isn't a safe place for those documents. So the reminder should link to your client portal and never ask the client to reply with attachments. It should also keep sensitive numbers out of the email itself: if a checklist line says "Brokerage statement, account 12345678", the email should say "account ending 5678". Our recipe cuts any run of 5 or more digits to its last four (account *5678), and replaces anything written like a Social Security, ITIN or employer ID number (123-45-6789, 12-3456789) with [removed]. That's a safety net, not a guarantee, so keep those numbers out of your checklist in the first place.

The tools sending these emails (your automation server, the email service, your spreadsheet) are service providers under your security plan. List them in your WISP, turn on MFA for each one, and keep execution logs short.

Already have a portal that reminds? Use it

Karbon's Business plan and TaxDome both send automatic reminders on client requests (Karbon pricing, TaxDome pricing). If you pay for one and its reminders work for you, keep them, and don't add a second set: clients shouldn't get two reminders for the same document. A separate ladder makes sense when you track requests in a spreadsheet and email, or want one rule and one escalation across every client.

Our recipe

The client document chase recipe is an n8n workflow that runs every weekday morning. It reads outstanding items from a Google Sheet, or read-only from TaxDome document checklists, sends the day 0, 3, 7 and 14 emails with your portal link, tells the preparer on day 14 and, if you use Karbon, adds a note to the client's work item. No AI model decides anything; the wording is yours to edit.

Two related recipes: the tax checklist recipe builds each client's January list from last year's documents and hands it to the ladder, and the waiting-on-client digest gives each preparer a Monday list of what's stuck.

We tested it with mocks of Karbon, TaxDome, Google Sheets and the email service, using invented clients, including rate limits, paging, missed days and reruns. The recipe page lists what's tested and what's only documented, plus the monthly cost from each vendor's price page. It's US only for now.