Tax workflow software should track, for every return, its current stage, who is assigned, its due date and extended due date, and which client documents are still outstanding. Compare options by running a few of last season's real returns through each one in a trial, not by watching a demo, and score them on the same questions.
What tax workflow software tracks for each return
Tax workflow software tracks each return as a record that moves through the firm's stages. The record holds the client, the return type, the stage, the assigned preparer and reviewer, the due date, any extension and a note of what is blocking it. If a field changes who works on the return next, the software should hold it.
The fields a return record needs
- Client and return type. Form 1040, 1065, 1120-S and so on. The type sets the due date and often the reviewer.
- Stage. One value from the firm's own list, such as Waiting on client, Ready to prepare, In review, Waiting on signature, Filed.
- Assigned preparer and reviewer. Two separate fields, because the handoff between them is where returns wait.
- Due date. IRS Publication 509 (2026) gives the rule for each form: Form 1040 is due on the 15th day of the 4th month after the end of the tax year, and Forms 1065 and 1120-S on the 15th day of the 3rd month. It also says a due date on a Saturday, Sunday or legal holiday moves to the next business day. Good software computes the date from the return type and the client's tax year rather than asking staff to type it.
- Extension. Whether Form 4868 or Form 7004 was filed and the resulting date. Publication 509 describes both as automatic 6-month extensions of time to file.
- Blocking reason. Free text or a short list: missing documents, client question, waiting on a K-1.
- Documents outstanding. At minimum a count; better, a link to the client's list of what is still missing.
Stages are the firm's, not the vendor's
The stage list should match how your firm works. If the software forces a fixed set of stages, staff will invent workarounds in the notes field, and the reports stop meaning anything. The post on tax return status tracker statuses and entry rules covers how to define a list that stays honest.
Workflow software tracks returns. A full suite also covers time, billing and client records; what accounting practice management software covers explains where that boundary sits.
Tax workflow software versus a shared spreadsheet
A shared spreadsheet is enough for tax workflow tracking when one or two people touch every return and the client count fits on one screen. Dedicated tax workflow software earns its cost when several people hand returns to each other, when due dates vary by return type, or when the firm needs history of who changed what.
Where a spreadsheet works
A sheet with one row per return and columns for stage, preparer, reviewer, due date and blocking reason does most of what a small office needs. It is free, everyone knows how to use it, and the columns can change in a minute. Filtering by preparer gives each person a queue. Sorting by due date gives the week's priorities.
An example row, with fictional values, shows how little a sheet needs: "Marsh household, Form 1040, tax year 2025, In review, preparer J. Ortiz, reviewer L. Chen, original due date, blocked: none." Add one column for the date the stage last changed and the sheet can already show which returns have been sitting longest. That single column answers most of the questions a firm asks of dedicated software in its first season.
Where a spreadsheet breaks
- Concurrent edits. Two people sorting the same sheet at once can scramble rows.
- No history. When a return moves backward from review to preparation, the sheet shows only the current value. Nobody can see that it bounced twice.
- Manual due dates. Every date is typed, and every typo is a risk.
- No link to documents. The sheet says "waiting on client" but cannot show which document.
- No assignment notices. A reviewer finds new work by looking, not by being told.
A test for the switch
Count how many times last season someone asked "where is this return?" in a meeting or by email. If the answer was regularly found by opening the sheet, the sheet is working. If the answer usually needed asking the person who last touched it, the firm needs software that records handoffs.
How do you trial tax workflow software before the season?
To trial tax workflow software, load ten of last season's real returns, with their real stages and dates, and have the people who will use it move them through every stage over a week or two. A demo shows a perfect firm. Your own returns show how the software handles exceptions, such as a late K-1.
Pick returns that cause trouble
Choose a mix: a simple wage return, a household with brokerage accounts, a partnership with an extension, an amended return and one client who was slow to send documents. The easy returns test nothing. The awkward ones show whether the software bends or forces workarounds.
Have the real users run it
The partner who signs the contract is rarely the person who changes a return's stage forty times a day. Put the trial in the hands of a preparer and the reviewer. Ask each of them to record anything that took more than a few clicks, or that they had to write in a note because no field fit.
Score every option on the same checklist
This scoring checklist is an example. Score each question from 0 (no) to 2 (yes, without a workaround) for every option you trial.
| # | Trial question | Score 0 to 2 |
|---|---|---|
| 1 | Can we define our own stage names and order? | |
| 2 | Does it compute due dates from return type and tax year? | |
| 3 | Does it record extension filings and the new date? | |
| 4 | Can a return have a preparer and a reviewer at once? | |
| 5 | Does it keep a history of stage changes with dates and names? | |
| 6 | Can each person see only their own queue? | |
| 7 | Can we record why a return is blocked, from a short list? | |
| 8 | Can it show which client documents are still outstanding? | |
| 9 | Can we export every record to Excel or CSV? | |
| 10 | Could a seasonal hire use it after one hour of training? |
Total the scores, but read the zeros first. A zero on question 1 or 5 is hard to work around. A zero on question 8 can be covered by a separate document tool.
Giving the trial an end date
Treat the trial as a small test with an end date and a decision meeting. Two weeks with ten returns is usually enough to see the problems. Agree before it starts which questions on the checklist are deal-breakers.
Tax workflow software features that sound useful and rarely get used
Tax workflow software features that rarely get used in a small firm are the ones that need setup time nobody has in January: elaborate automation rules, custom dashboards, time budgets per stage and built-in chat. Each sounds useful in a demo. Before paying for any of them, ask who in the firm will configure it and maintain it.
Rule builders
"When a return moves to review, assign it to the reviewer with the fewest open returns" is a good rule. Writing and testing twenty of them takes days. If the firm has five people, a person assigning returns each morning is faster to set up and easier to change.
Custom dashboards
Charts of returns by stage look good in a sales call. Check that the two views you will use daily, a list sorted by due date and one filtered by person, are easy to reach before looking at charts.
Built-in messaging
Staff already have email and a chat tool. A third place to talk about a return splits the conversation. A notes field on the return record, visible to everyone, does the job.
Per-stage time budgets
Setting a target time for each stage only helps if someone reviews the overruns. Without that habit, the numbers fill up and nobody reads them.
None of these features is bad. The question is whether your firm will use them this season. The review queue for tax preparers post shows how much of review routing can be handled with a simple ordering rule before buying anything.
Does tax workflow software read client documents?
Tax workflow software, as this guide means it, does not read documents. It tracks the return: its stage, its owner and its dates. It may store files or link to a folder, but it does not open a PDF, recognise a W-2 or tell you which 1099 from last year has not arrived. Reading documents is a separate job.
Tracking a return versus reading its documents
A tracker knows a return is "Waiting on client." It does not know what the client owes. Someone still has to open each upload, work out what it is, compare it with last year's forms and write the list. That gap is where intake time goes, and a workflow tool with an attached file store does not close it.
What document reading adds
A document reader opens each file and classifies it by type, issuer and period. With last year's set as a reference, it can say which forms have arrived, which are missing and which came in twice. That list is what feeds the "documents outstanding" field in the tracker.
Schema CPA does this reading. It classifies every page a client sends, compares the folder with last year's return, and flags missing and duplicate documents; the documents section of the homepage lists the form and statement types it reads. It is not workflow or practice management software and does not track return stages.
Keeping the two tools in step
If the firm uses one tool to track returns and another to read documents, decide which one is the source of truth for "complete." A simple rule works: a return moves out of Waiting on client only when the document list shows nothing missing. The organizing client files category covers folder structures that make both tools easier to keep aligned.
A worked example
This example is fictional. Oakfield CPA tracks 220 returns in a workflow tool. On March 2, 2026, during the season for tax year 2025 returns, 38 are marked Waiting on client. The tracker cannot say why for any of them. The intake admin opens each folder, compares it with last year's and finds that 21 are waiting on a single brokerage 1099, 9 on a K-1 and 8 on several items. Those three groups get three different reminders. The tracker stays the place that shows the stage; the document comparison is what turned 38 identical rows into actions.