April 15 is not when the document problem starts. It is when the polite clients finish. Everyone else is on extension, and the packet that was "coming this week" now has five months to wander.
The accounting workflow post names document chase as one of three piles. This is the pile after the deadline, when staff are tired and the missing list is longer than the filed list.
What the chase actually looks like
A partner puts a return on extension because two K-1s are missing, or a brokerage statement is still being requested. Someone sends a reminder. The client uploads a 2023 1099 into the 2024 folder. Staff rebuild the missing list in a spreadsheet because the portal's outstanding view does not match what the preparer sees in the tax software. Monday standup is a tour of who has not answered.
None of that is a tax-technical problem. It is a definition of done with a calendar attached.
Why more reminders do not fix it
Firms add a third email. Then a text. Then an admin just checking in. Volume goes up. Completeness does not. The client who will not open the organizer will not open the fourth reminder either. The client who is stuck (password, wrong year, spouse has the file) needs a person, and the sequence has no slot for that.
If every silence gets the same nudge, you train clients that the first two messages are optional.
A sequence that matches how extension season works
1. One list of complete per return type. Individual, S-corp, trust: write the required docs. "Send us your stuff" is how you get a selfie of a W-2.
2. The request names what is missing, not that something is missing. "We still need the 2025 K-1 from Oak Street LLC" beats "documents outstanding."
3. Reminders fire on a schedule, with an escape hatch. Two automated nudges. The third is a person, and only if the client has not said they are stuck.
4. Arrival has a rule. Wrong year, wrong entity, or a scan you cannot read goes back with a specific ask. It does not sit in "uploaded" until someone notices in July.
5. The missing list lives in one place. If the preparer, the portal, and a spreadsheet disagree, staff will keep rebuilding the list. That rebuild is the hours.
What not to do
Do not rip out the portal in May. Do not promise clients a new app mid-chase. Do not automate a partner's call on whether an incomplete packet can still be prepared. And do not treat October 15 as a second April 15. The clients left on the list in September are the ones who have already ignored you.
For the general version of this stack, see document automation for financial services. Extension season is the same leak, stretched, with less patience left in the firm.
How we look at it
In a workflow audit we watch a real week of chase, not the SOP on the wall. We look at where files actually arrive, who rebuilds the missing list, and whether the tax software and the portal agree. Sometimes the first build is the reminder sequence. Sometimes it is just making "complete" visible.
If your October still depends on one person who knows who you are waiting on, start with a diagnostic. You leave with three workflows ranked, whether we build together or not.