Job statuses that mean something: designing a workflow for tax work
Vague job statuses hide bottlenecks. Here is how to design a tax workflow where every status answers who owns the job right now.
Ask five people in a practice what "in progress" means and you will get five answers. Vague statuses are the quiet enemy of good workflow because they hide the one thing managers most need to know: who owns this job right now, and what has to happen for it to move.
What a good status tells you
A status is not a label for tidiness. It is a signal about ownership and the next action. A well-designed status answers two questions at once.
- Who is responsible at this moment, the preparer, the reviewer, or the client.
- What needs to happen next for the job to progress.
"In progress" answers neither. "Waiting on client information" answers both. The art of workflow design is replacing comfortable vagueness with statuses that force clarity.
A workable set for tax jobs
You do not need many statuses. You need the right ones, each marking a genuine handover. A practical set for tax work might look like this.
The core stages
- To start, the job exists but no one has begun.
- Waiting on client, the ball is firmly in the client's court.
- In preparation, a preparer is actively working it.
- Ready for review, preparation is done and a reviewer is needed.
- In review, a reviewer is actively checking it.
- Awaiting approval, the client needs to approve or sign.
- Ready to lodge, everything is signed off and queued.
- Lodged, complete.
Notice how each status names an owner. "Waiting on client" and "awaiting approval" are especially valuable because they separate work that is genuinely stuck on you from work that is stuck on someone else.
Avoid the common traps
Two mistakes undo most status systems. The first is too many statuses, which makes the board ambiguous and tempts people to skip steps. The second is statuses that do not map to a real handover, which add clicks without adding clarity. Keep the set small and make every transition mean something happened.
When statuses are designed this way, a board becomes diagnostic. A pile of jobs in "ready for review" tells you reviewers are the bottleneck. A pile in "waiting on client" tells you to chase. Tools such as Finye let you define these statuses per workflow and see jobs grouped by them, but the value comes from the design, not the display.
Takeaway
Audit your current statuses and ask of each one: does it tell me who owns the job right now? Rename or remove any that do not. The goal is a board where a glance reveals exactly where work is stuck and whose move it is.