Tax Season Hours Saved: How to Measure Them

Tax season hours saved are the difference between staff hours per return before a process change and after it, multiplied by the number of returns that use the new process. Measure a baseline first, time the same tasks on the same return type afterwards, and credit only the change you observed, not an estimate.

Setting a baseline of staff hours per tax return

A baseline of staff hours per tax return is the measured time a return of one type takes, by stage, under the current process. It has to exist before anything changes. Without it, any later figure for hours saved is a recollection, and recollections of last season's pain tend to be generous.

Pick one return type and one complexity band, such as individual returns with wages, interest and one brokerage account. Mixing a simple 1040 with a business return in the same baseline makes the average move whenever the mix moves, which looks like savings or losses that never happened.

Measure at least ten returns. One return tells you about that client; ten start to tell you about the process. Record the median as well as the average, because one return with a missing K-1 and three rounds of follow-up can pull the average a long way.

Split the time by stage: document intake and sorting, data entry, preparation, review and client follow-up. A process change usually targets one or two stages. A stage-level baseline lets you see whether the targeted stage actually shrank, and whether the time simply moved to another stage. Time that moves from data entry to review has not been saved.

Write down the conditions as well as the numbers: who did the work, which weeks, how complete the client files were when work started. A baseline taken in February with experienced staff is not comparable with an after-measure taken in April with a new hire.

What should you time when measuring hours saved?

When measuring hours saved, time the specific tasks the change is meant to affect, plus the stages on either side of them, on the same return type, for at least ten returns before and ten after. Time active work, not elapsed calendar days, and include rework, because a faster step that causes more corrections saves nothing.

The tasks worth timing for most process changes:

• Intake and sorting: opening uploads, splitting files, naming and filing each document.
• Data entry: keying figures from W-2s, 1099s, K-1s, statements and payroll reports into the return or workpapers. The tax forms and payroll category covers what each of these forms contains, and the post on the cost of manual data entry in an accounting firm puts a season-level price on this stage.
• Checking: tying entered figures back to source documents.
• Rework: fixing errors found in review and re-entering corrected forms.
• Client follow-up: requests for missing or unreadable documents.

A simple timing method works. Each preparer starts a timer when they begin a stage for a return and stops it when they switch to anything else, logging the minutes against the return and stage. Rough minutes logged at the time are better than precise-sounding figures reconstructed a week later.

A before-and-after time log

The log below is fictional example data for a fictional firm. It tracks one return type, a 1040 with wages, interest and one brokerage account, before and after the firm changed how it receives bank and brokerage figures. Minutes are medians across ten returns in each period.

The formula for hours saved per season:

hours saved = (baseline minutes per return - after minutes per return) x returns of this type that used the new process / 60

For this example firm, 140 returns of this type used the new process, so the example works out to (165 - 135) x 140 / 60 = 70 hours for the season. Checking time went up by five minutes per return, and the total reflects that. Turning those hours into dollars is a separate calculation, covered in the manual data entry cost formula.

Which tax preparer productivity metrics reflect time saved?

Tax preparer productivity metrics that reflect time saved are the ones measured per return of a fixed type: staff minutes per return by stage, rework minutes per return and returns finished per preparer-week within one complexity band. Metrics that mix return types, or count outputs without hours, move for reasons unrelated to the change.

Returns filed per week is the most quoted metric and the least reliable. It rises in the last weeks before a deadline whether or not anything improved, because everyone works longer. Divide by hours worked, and keep the return type fixed, before reading anything into it.

Revenue per staff hour is useful to a partner but mixes pricing with time. A fee increase raises it without saving a minute.

Days from complete file to filed is worth tracking, but it measures waiting as much as working. A return can sit in a review queue for a week while taking two hours of actual work. It shows bottlenecks, not hours saved.

Rework minutes deserve their own line. A change that speeds up entry but introduces more errors shows up here first.

Hours saved claims that do not hold up

Hours saved claims do not hold up when they come from estimates rather than a measured baseline, when they multiply a per-document saving across documents the change never touched, or when they count time that simply moved to another stage. Vendor and internal estimates both tend to make these errors, usually without meaning to.

No baseline. "We used to spend forever on this" is not a number. If there is no measured before, there is no measured saving.

Multiplying the best case. A demo that processes one clean W-2 in seconds says little about a season of phone photos, corrected forms and forty-page PDFs. Apply a per-document saving only to documents of the kind that were measured.

Ignoring moved time. In the example log, checking time rose. A claim that counted only the 30-minute drop in data entry would have overstated the saving.

Counting every return. The formula multiplies by returns that actually used the new process. Clients who still mail paper do not count.

Learning curve left out. The first weeks with a new process are slower. Measure after staff are used to it, or measure both periods and report both.

Schema CPA's homepage takes the other direction: its hours calculator estimates what manual entry costs a firm now, from clients, documents per client, minutes per document and staff cost, and it states no hours-saved figure. For ways to reduce entry time in the first place, see how to reduce data entry in accounting, then measure the result with the method above.