In a recent working session with a client's tax team, someone summed up the old way of handling notices in three words: hunting and pecking. Keying data in by hand, field by field, notice by notice. The verdict on the call was blunt and familiar: it "wasn't very effective." And the reason it wasn't was equally familiar: the volume. As one of our team put it, that approach never works, "especially with your kind of data — you guys get a lot of volume."
That short exchange captures a truth most high-volume tax operations live every day, so it's worth pulling apart. Because the lesson isn't just "automation good, manual bad." It's about what high volume actually does to a manual process, and what it really takes to fix it.
A manual, hunt-and-peck process can look perfectly fine at low volume. A handful of notices a month is annoying but survivable; someone keys them in, tracks them on a spreadsheet, and moves on. The trouble is that this approach doesn't degrade gracefully. Double the volume and you don't get twice the effort; you get twice the effort plus the rework from more transposed figures, more missed fields, more items that slip past a deadline because there simply weren't enough hours to get to them.
At real volume, hunting and pecking stops being a productivity problem and becomes a risk problem. Every manual keystroke is a chance to mis-key an amount, an entity, or a due date — and in notice handling, a missed due date isn't a typo you fix later. It's a penalty, an escalation, an avoidable scramble. The manual process doesn't just slow a busy team down. It quietly converts volume into exposure.
The other thing that comes through in any conversation with a working tax team is how little slack there is. Days run back-to-back-to-back. People cover for each other through vacations and crunch periods. The notion that someone will find a calm afternoon to carefully re-key a backlog of notices is, in practice, fiction.
This is why "just hire another person" or "just be more careful" never solves the volume problem. The constraint isn't effort or diligence — these teams have both in abundance. The constraint is that human attention is finite and expensive, and pointing it at data entry is a waste of the exact expertise you hired them for. The work that deserves a seasoned tax professional's judgment is the ambiguous notice, the contested position, the strategic call — not transcribing the routine ones one character at a time.
The fix is to take the hunting and pecking off their plate entirely: capture each notice on intake, extract the key fields automatically, and let the system do the transcription so people can do the thinking.
Here's what stood out most about that client session, though — and it had nothing to do with software features. It was the cadence. A follow-up summary going out afterward. Action items tracked between meetings. A standing check-in the following week. The relationship wasn't "here's your login, good luck." It was an ongoing partnership with people who stay engaged after go-live.
That distinction matters more than it gets credit for. Plenty of tools can automate data capture. Far fewer vendors actually sit with a client's real data, see where the volume and the edge cases live, and keep working the problem week over week until the process genuinely runs. High-volume environments are messy in specific ways — odd formats, unusual jurisdictions, exceptions that no demo anticipates — and getting from "installed" to "actually working" takes a partner who shows up, takes notes, and follows through.
The teams that succeed with automation aren't the ones who bought the cleverest software. They're the ones who gained a partner that treated their backlog and their quirks as a shared problem to be solved, not a ticket to be closed.
The throughline from that conversation is simple. Hunting and pecking fails not because the people are doing it wrong, but because manual transcription cannot keep pace with real volume — and trying to make it keep pace just burns out skilled professionals and converts workload into risk.
Replacing it does two things at once. It removes the error-prone, time-devouring keystrokes. And, when paired with a partner who stays engaged, it gives a busy team back the one thing it never has enough of: capacity to apply judgment where judgment actually matters.
That's the real end state. Not a department that types faster — a department that stopped typing, and started deciding.
RELATED POSTS