Tax Season Is a Document Chase With a Deadline

It’s the second week of February. A staff accountant has 60 open client files and spends the morning writing the same email in 60 slightly different ways: “Just following up on your documents.” One client sends a single PDF with eleven pages scanned sideways. Another uploads a W-2 that’s already in the file. A third asks, again, which documents the firm still needs.

By March, the shared drive has folders named “Smith new,” “Smith new 2” and “Smith FINAL scans.” A partner asks which returns are ready to prepare. Nobody can answer without opening every folder.

Then April shows up, and a stack of returns goes to extension for no reason other than one missing form.

I’ll be clear about my background. I’m not an accountant and I’ve never prepared a return. I ran a digital agency, Infographic World, for almost 18 years, and today I use AI to fix the spots inside businesses where work waits on paperwork. Tax season is the clearest example I know of skilled people spending their best weeks doing clerical work, because the clerical work has to happen before the skilled work can start.

Where the hours actually go

Follow one individual return from engagement to ready to prepare.

• The request. Someone sends the organizer or a generic document list. It’s long, it’s the same for every client, and half of it doesn’t apply to this one.
• The waiting. Documents trickle in by portal, email, text photo and the occasional envelope dropped at the front desk.
• The checking. Someone opens each upload, figures out what it is, and compares it against what the client had last year. Is this the brokerage statement from the account they had before, or a new account?
• The reminders. Every week or two, someone writes to the client about what’s still missing, often without being sure what’s still missing.
• The sorting. Files get renamed, moved into the right folder and attached to the right return in the software.
• The status. Partners and managers ask where things stand. Answering means opening folders and asking around.

Of all that, only a slice needs an accountant’s judgment: deciding whether something new matters, what an odd document means, whether a return should go on extension. The rest is matching, nagging and filing.

What the AI-assisted version looks like

It builds a checklist from last year

For each returning client, the system reads last year’s return and supporting documents and lists what came in: a W-2 from this employer, a 1099 from that bank, a mortgage interest statement from this lender, a K-1 from that partnership. A few plain questions to the client catch the changes, like a new job, a move or a new account. A preparer reviews any change before the checklist goes out.

It sends reminders that name exactly what’s missing

Instead of “please send your documents,” the client gets: “Thanks for the W-2 and the mortgage statement. Still missing are the 1099 from the brokerage account ending in 4471 and last year’s property tax bill.” Fewer words, fewer replies asking what’s needed. The firm sets the schedule and tone. Clients who’ve said a form is coming late, like a K-1 that depends on another entity’s timing, get noted, not nagged.

It sorts and names what arrives

Each upload is read, matched to a line on the checklist and renamed in the firm’s naming format. A duplicate gets flagged. An unreadable scan triggers a polite request for a better copy. Anything the system can’t identify goes to a person.

It keeps a status board

Every client sits in one of a few states: waiting on client, waiting on a third party, complete and ready to prepare, or needs a preparer’s look. Partners see the board instead of asking around. Managers assign work from the complete column.

Run the numbers

There are two pieces. The first is the chase itself: clients, times reminder touches per client, times staff minutes per touch. The second is the returns that slide into extension because documents arrived late, times the extra handling each one costs.

Say, for the sake of the math, a made-up firm prepares 500 individual returns. Each client needs an average of four reminder touches, and each touch takes six minutes of staff time to check the file, write the note and log it. That’s 12,000 minutes, or 200 hours, in the busiest weeks of the year. If the system drafts and sends most reminders and staff only handle the exceptions, cutting staff time on the chase by three quarters returns about 150 hours.

Now extensions, with made-up figures again. Say 60 returns go to extension only because a document was missing, and each one costs about 90 extra minutes: filing the extension, reopening the file in the fall, re-reviewing what’s changed. That’s 90 hours. If clearer, earlier reminders cut that group by a third, the firm saves about 30 hours and has 20 fewer files hanging over the fall.

Together that’s about 180 hours. At a made-up loaded staff cost of $60 an hour, roughly $10,800, though the real value is that those hours land in February and March, when the firm has the least of them.

To run it for real, pull three numbers from your own firm:

1. How many returns you prepare where the client provides documents.
2. Average reminder touches per client last season and minutes per touch. Count a sample of 20 clients in your portal or email.
3. Returns that went to extension last year only because documents were late, from your tracking or your preparers’ memory.

Picture a Monday, before and after

A made-up scene. Before: on the first Monday of March, a manager asks for a status update. Three staff spend the morning opening folders, building a spreadsheet and emailing clients to ask whether they sent something. The spreadsheet is out of date by lunch.

After: the manager opens the board. 212 clients complete and ready to prepare. 180 waiting on the client, each with the exact missing items listed and the date of the last reminder. 31 waiting on K-1s or corrected forms. 14 flagged for a preparer, mostly new accounts or documents the system couldn’t identify. The manager assigns the complete files before 9 AM, and the staff morning goes to preparation.

What has to be in place first

• A secure client portal clients will actually use, so documents stop arriving as email attachments.
• Last year’s returns and supporting documents organized in a consistent place the system can read.
• A naming convention and folder structure the whole firm agrees on.
• A defined set of statuses and who moves a client between them.
• A preparer assigned to review checklist changes before they go to clients.

Guardrails worth keeping

• No tax advice from the system. It answers logistics. Questions about reporting, deductions or what a client should do go to a preparer.
• Security is a requirement, not an extra. The IRS and its Security Summit partners remind firms that federal law requires tax and accounting professionals to create and maintain a Written Information Security Plan. Any new tool that touches client documents belongs inside that plan, with access controls, logging and vendor terms that keep client data out of public model training. The firm and its advisers decide what qualifies.
• The preparer decides about extensions. The status board informs the decision. It doesn’t make it.
• Clients can always reach a person. Every reminder includes a way to talk to someone at the firm.
• Everything gets logged. What was requested, what arrived, who reviewed it.

How you’ll know it’s working

• Days from engagement to “complete and ready to prepare,” by client type.
• Average reminder touches per client that needed a staff member.
• Share of clients complete by March 1.
• Returns extended only because of missing documents.
• Staff hours logged to document collection during the season.

Where I’d start

Start with one preparer’s returning individual clients who had a simple return last year. Build their checklists from last year, run the reminders and the status board for that group alone, and compare their days to complete against the rest of the firm.

To see what those hours are worth in your own firm, try the AI Opportunity Calculator.