Every tax season, firms lose hours to the same job: asking clients for documents, asking again, and working out what is still missing. The work is simple, but it lands in the busiest weeks of the year. This guide sets out the workflow step by step, where it breaks, which parts to hand off, and how to tell whether the change worked.
When do client documents actually arrive?
Many client documents are not due from employers and partnerships until fixed federal deadlines, so your chasing calendar should follow them. For tax year 2026, the key dates are:
| Date | What happens | Basis |
|---|---|---|
| Monday, Feb 1, 2027 | Employers and payers must give workers W-2s and 1099-NECs | IRS January 31 deadline; Jan 31, 2027 is a Sunday, so it moves to the next business day |
| Monday, Mar 15, 2027 | Calendar-year partnerships must file Form 1065 and give partners their Schedule K-1s | IRS Form 1065 instructions |
| Thursday, Apr 15, 2027 | Individual returns due | IRS "When to file": April 15, moved only if it falls on a weekend or holiday |
The IRS has not announced its 2027 opening day as of October 29, 2026. For scale: in 2026 it opened the season on January 26 and expected about 164 million individual returns (IRS release IR-2026-02, January 8, 2026).
The practical point: W-2s are not due until February 1 and partnership K-1s not until March 15, so a plan that expects every document by mid-February will fail for any client with partnership income.
What does the workflow look like, step by step?
A reliable document-chasing workflow has seven steps:
- Build each client's list from last year. Last year's return shows which forms to expect — every W-2, 1099, K-1 and mortgage statement.
- Send the request early. Organizer plus a personal checklist in early January, with the date you need everything by.
- Collect in one place. One portal or inbox; photos texted to a staff member's phone might as well be lost.
- Log each item as it lands. Received, missing, or wrong.
- Check what arrived. Right tax year, right person, all pages, readable.
- Remind on a schedule. Name the specific missing items, not "please send your documents."
- Escalate stragglers. After a set number of reminders, a person calls.
Where does the process usually break?
It breaks in the handoffs, not the reminders. It starts with a generic checklist: a long list where only a few items apply to this client is easy to ignore. Documents then arrive through too many channels — email, portal, text, mail and the drop-off at the front desk — and nobody has a single view of what is in.
What does arrive is often partial or wrong: page one of a brokerage statement, last year's W-2, a spouse's form missing. Reminders stop in the peak weeks, because the staff who send them are busy preparing returns. Nobody owns the straggler list, so everyone assumes someone else called. And clients with partnership income may not have their K-1s until mid-March, which turns into a scramble if nobody planned for it in January.
What can you hand off, and what should stay with your team?
Hand off the repetitive tracking; keep the judgment. A good split:
| Hand off to an AI worker | Keep with your team |
|---|---|
| Building each client's checklist from last year's return | Deciding what a new life event (sale, divorce, new business) means for the return |
| Sending reminders that name the missing items | Advice of any kind |
| Logging what arrived, from every channel | Calling clients who have gone quiet after several reminders |
| First checks: tax year, form type, page count, readability | Extension decisions — an extension to file is not an extension to pay, the IRS notes |
| Weekly status note to each client | Anything unusual, sensitive or disputed |
| A daily "ready to prepare" list for staff | Preparing, reviewing and signing the return |
The AI worker never decides anything about the return. It makes sure the right paper is in the right folder, and tells a person when it is not.
How do you keep client data safe when AI is involved?
Treat any AI tool that touches client documents as a service provider under your security plan. The IRS says tax and accounting professionals are financial institutions under the Gramm-Leach-Bliley Act and must have a written information security plan (WISP); the IRS's Publication 5708 includes a template for smaller practices. One required element is overseeing your service providers.
Two more rules belong on the list before you switch anything on. Since May 2024, the FTC's Safeguards Rule has required covered firms to notify the FTC no later than 30 days after discovering a breach involving unencrypted information of at least 500 consumers. And Section 7216 of the Internal Revenue Code penalizes preparers who knowingly or recklessly disclose or use tax return information for unauthorized purposes.
Ask any vendor where documents are stored, who can see them, whether they are used to train AI models, and how access is logged. Confirm the answers fit your WISP and your advisers' view of Section 7216. This guide is not legal advice.
What should you set up before January?
Use November and December, the quieter weeks, to get ready. Most of the work is deciding things once — the channel, the cadence, who calls — so nobody has to decide them under pressure in February. The checklist:
- Pull last year's form list for every returning client.
- Choose one intake channel and tell clients about it.
- Write three reminder messages: friendly, specific, final.
- Set the cadence — for example, days 7, 14 and 21 after the first request.
- Decide who owns the straggler call list.
- Flag clients with partnership income for a March plan.
- Update your WISP to cover any new tool.
- Record last season's numbers (see below) so you have a baseline.
How do you measure whether it worked?
Compare this season against last season on four numbers, all of which you can pull from your practice software or a simple spreadsheet:
| Measure | How to count it |
|---|---|
| Completion by March 1 | Share of individual clients with every expected document in by March 1 |
| Days to complete | Median days from first request to last document |
| Staff time on chasing | Hours logged on reminders and follow-up calls in a sample week |
| Extensions from missing documents | Extensions filed because documents were late, not because the return was complex |
If completion by March 1 rises and staff hours on chasing fall, the change worked. If not, the log will show which step is slow.
Where do we fit?
Document chasing is one of the workflows our AI operator runs end to end: requests, reminders, logging and first checks, with a person handling every exception. You can see the full workflow on the document chasing page, and how the checking step works in AI document processing. If you are weighing it against a seasonal hire, our AI operator vs employee comparison sets out the trade-offs.
For a broader view of where AI fits in a small firm, the AI handoff playbook is a good next read — or book a consultation before January fills up.