How Tax Firms Should Think About Project Management

Tax firms run on projects, whether they admit it or not. Every engagement has a defined scope, an assigned staff member, a regulatory deadline, and a deliverable that either goes out the door on time or doesn't. Most firms still manage that work through email threads, shared spreadsheets, and whatever a senior preparer happens to remember about who's doing what. That gap, between how firms actually operate and how they think about their own operations, is where most execution failures start. Per the 2025 State of Accounting Workflow Automation Report, 55.5% of firms now name workflow inefficiency as their single biggest operational problem, and that figure alone should settle an argument firms keep having with themselves: the tools aren't the bottleneck. A firm that hasn't fixed its mental model of what it's managing will misuse any software handed to it.

The operational pressure making this problem impossible to ignore

The clearest sign of strain shows up in what firms chose to give up. Per Rightworks' 2025 Post-Tax Season Survey, 12% of firms scaled back their tax client base last year just to match the workforce they had on hand. That's revenue turned away not because demand dried up, but because the work couldn't move fast enough through the people available to do it.

The labor pipeline behind that decision is thinning. The Bureau of Labor Statistics projects more than 120,000 accounting and auditing openings a year, while the pipeline of new CPAs is shrinking. As experienced staff retire and seats stay empty, the people still on staff absorb more work during the exact weeks when there's no slack to absorb it. In 2025, 32.4% of firms responded to that pressure by simply requiring longer hours. That's the wrong fix: it treats a systems problem as a stamina problem, and stamina runs out long before tax season does.

Firms can't hire their way out of a shortage the labor market itself isn't going to solve. What they can do is move more work through the same, or fewer, hands, which is a project management problem, not a headcount problem. Per PMI's Pulse of the Profession 2020 survey, 67% of projects fail inside organizations that don't treat project management as a real discipline. That figure wasn't measured in accounting specifically, but it names exactly what's at risk across a profession built entirely on deadline-bound deliverables.

What makes tax firm project management different from generic project management

Generic project management was built for one-off work, involving a single initiative, a flexible end date, and a team that disbands once the deliverable ships. Tax work looks nothing like that, and treating it like generic project work is the mistake most firms make without realizing they've made it. Tax engagements are recurring, compliance-driven, and bound to a deadline the team never gets a vote on. A regulator sets the date. Nobody negotiates it down because the team is short-staffed.

A few structural differences follow. Deadlines are external and fixed, not internal targets a project manager can push back a week if the team needs it. Engagements repeat every year or every quarter with the same client, so the "project" isn't new work each time, it's the same system running again. And the biggest bottleneck usually sits outside the firm entirely: nothing moves until the client sends over the documents. The friction shows up right at those handoffs, the moments where work passes from client to firm or from preparer to reviewer, not in the technical work itself.

The real test of any project management approach is how it holds up across a far wider and messier range of conditions than three sample tasks in a quiet week in June. It's whether it holds when hundreds of client engagements are moving at once in the first two weeks of April. Generic tools treat every deadline as equal weight and miss the compliance sequencing tax work actually runs on, which is why so many firms end up duct-taping together email, a spreadsheet, and a couple of standalone apps. That patchwork cuts visibility exactly when visibility matters most. Stop thinking of engagements as service deliveries. Start thinking of them as recurring projects with defined stages, dependencies, and capacity requirements attached to each one.

The right mental model: recurring engagements as repeatable project systems

A tax engagement follows a predictable path: intake, document collection, preparation, review, delivery, filing. Every time that engagement comes back around, whether it's the same client's corporate return next March or next quarter's bookkeeping close, it should run through the same system. This work is familiar. It's repeatable. Project management for a tax firm is the discipline of systematizing what repeats, not improvising it fresh every cycle, and firms that improvise it fresh every cycle are the ones burning planning hours they don't have.

Standardize before scaling. Build a workflow template for each engagement type (individual returns, business returns, quarterly bookkeeping) so nobody starts from a blank page with every new client. Starting from scratch each time doesn't just waste hours, it introduces inconsistency that surfaces later as errors, usually at review, usually too late to fix cheaply.

Build the client dependency into the workflow itself. Document requests, and the follow-ups when clients go quiet, should be automated steps in the process, not something a staff member remembers to chase on their own time. Chasing down financial statements and payroll records by hand is one of the most time-consuming frictions in the entire practice, and it's exactly the kind of task a system should carry so a person doesn't have to.

Design for visibility, not just completion. The goal isn't only finishing the work, it's knowing at any given moment which engagements are on track, which have stalled, and where the next bottleneck is about to form before it does. That visibility starts at intake: an engagement letter or project charter that spells out deliverables, required inputs, and deadlines up front. Most engagements go sideways before any actual work begins, because nobody aligned on expectations at the start.

None of this holds together without knowing where workload sits across the team. Uneven distribution, some staff drowning while others have room, drives burnout and missed deadlines at the same time, and the two aren't separate problems. Capacity visibility is a core part of the workflow. It's the condition that makes the rest of the workflow mean anything.

How established project management frameworks adapt to tax work

Waterfall fits tax work about as naturally as any framework can: sequential stages, planned in advance, little appetite for changing course midstream. That rigidity, a liability in other industries, matches the compliance-driven, deadline-fixed nature of a tax return almost exactly. This is the framework most tax engagements should default to, not Agile, and firms that reach for Agile first because it's the trendier name usually find out why the mismatch matters somewhere around March.

Agile sits at the other end. It's flexible, iterative, built around adapting as circumstances change, and it fits advisory or planning engagements where client needs actually shift over the course of the work. Tax departments operate inside regulatory constraints that don't bend the way Agile expects them to. Strict deadlines have to be hit to stay compliant, and that requirement sits at odds with Agile's iterative rhythm. Firms that borrow from it anyway need a project manager in the loop specifically to hold the compliance line while the rest of the process flexes. Adopting Agile wholesale, without that safeguard, is a mismatch dressed up as innovation.

Scrum translates better: a sprint structure built around a concerted push to complete a defined batch of returns by a set date, with short daily scrums to surface what's stuck before it becomes a crisis. A week is a workable sprint length for most tax teams, long enough to get through a batch, short enough that nothing drifts unnoticed.

Kanban adds the visual layer: a board showing the status of every engagement in flight, which is what a firm actually needs for real-time visibility across 200-plus clients during peak season. Plenty of firms combine it with Scrum into what's sometimes called Scrumban. No single framework fits tax work on its own, and firms that pick one and refuse to borrow from the others tend to hit the same wall eventually. What matters is how well a team adapts elements of a methodology to its own needs, which principles serve work that's recurring, deadline-bound, and dependent on a client who might not answer email for three days. Whatever framework a firm lands on, the daily check-in, ten minutes, same time, every day during season, tends to be the piece that keeps small problems from becoming deadline threats, without pulling anyone off billable work to do it.

Capacity planning as the connective tissue between engagements

Most firms find out about a capacity problem the hard way: a deadline gets missed, or a partner looks up on a Tuesday and realizes three returns due Friday haven't been started. Proactive capacity planning flips that sequence. It means knowing, before the work even arrives, how much bandwidth each person actually has, and mapping the coming month's engagements onto that bandwidth instead of discovering the mismatch after the fact.

Imbalanced workloads are a direct cause of errors and missed deadlines, not a side effect of them. Regular workload assessment gives firm leaders what they need to allocate tasks sensibly, support collaboration between staff, and protect people's mental health during the heaviest stretches of the year. The natural point to do that assessment is the gap between seasons, when a firm can look back at productivity data, client feedback, and how resources actually got used, then feed that directly into next cycle's staffing and workload forecasts.

Firms that skip the post-season review make the same capacity mistakes every year without ever quite naming why. Firms that build the review in, even a rough version of it, push up the ceiling on how many clients they can serve without adding a single new hire. That connects straight back to the firms that cut their client base last year to match available workforce: most weren't actually understaffed in the raw sense. They lacked the visibility to sequence the work efficiently enough to serve the clients they already had.

Where purpose-built tools fit into the framework, and why the category distinction matters

The tooling question only becomes answerable once a firm has the mental model straight. Without it, new software is just a fresh place to be disorganized in.

If the work in question is purely internal tasks, a generic project tool does the job fine. But most accounting work touches client documents, compliance deadlines, and outside communication all at once, and generic tools weren't built to hold those three things together. What an accounting-specific platform adds is a built-in CRM, workflow templates already shaped around engagement types, document management, integrated time and billing, and compliance visibility, in one system instead of three or four bolted together.

The adoption picture is uneven, and it splits mostly along firm size. A meaningful share of firms now automates more than half or all of its tax workflows, though adoption varies widely across firm sizes. But a real gap separates large firms of 30 or more professionals from small shops of one to three, with the smaller end lagging well behind in how much of this technology actually gets adopted, usually because nobody on a three-person team has the bandwidth to evaluate and migrate to a new system mid-season.

A handful of platforms built specifically for accounting and tax work show up repeatedly in industry roundups. Karbon offers practice management with workflow and collaboration features built for accounting and bookkeeping firms specifically. Financial Cents and Jetpack Workflow both focus on accounting practice management and workflow. Firm360 serves the same category for accountants directly. Cflow handles workflow automation and business process management more broadly. Wolters Kluwer's CCH Axcess Marketplace supports integrations across tax, audit, and firm management workflows.

Alongside those sit the general-purpose tools that show up in the same comparisons: Asana, ClickUp, Monday.com, Trello, Basecamp, Smartsheet, Wrike. All of them handle internal task coordination well. None of them were built with the accounting-native features, engagement templates, client document handling, compliance sequencing, that tax work actually needs, and firms that pick one because a designer likes the interface tend to rediscover this gap around the second week of tax season. The evaluation criteria that matter come down to a short list: deadline tracking, workflow templates built for tax engagements, client-facing document management, integrated time and billing, capacity visibility across the whole pipeline, and room to scale from a solo practice up to a mid-size firm without switching systems. Purpose-built tax AI tools, designed for accountants from the ground up rather than adapted from generic software, push this further by automating the repetitive backend of an engagement (intake, document review, compliance checks) and freeing practitioners for the advisory work that actually needs a human judgment call.

What firms that treat project management as a core competency actually do differently

The firms that scale without turning away revenue share a pattern: structured intake, templated workflows, visible capacity, and a post-season review loop that actually gets used. None of that requires cutting-edge technology. It requires disciplined process, applied consistently, cycle after cycle, and while that's a less exciting answer than most firms want to hear, it's the one the evidence keeps pointing to.

The profession is catching up to that idea, slowly. Driving operational efficiency ranks among the top priorities for tax and accounting firms, ranked above client service, above growth, above talent, a sign that operations has stopped being treated as overhead and started being treated as a lever. Practitioners increasingly expect AI to free up meaningful time each week. That time only turns into advisory capacity if the firm has somewhere to redirect it. Without a project management structure underneath, those five hours just get reabsorbed into the same inefficiencies that were already there, which is the likeliest outcome for firms betting on AI as a substitute for process rather than a complement to it.

A growing share of tax firms are already using generative AI, with adoption of agentic AI beginning to follow. The firms positioned to get real value from those tools are the ones with clear workflows already in place, workflows the automation can slot into rather than compete with. Adding a new client or bringing on a new hire shouldn't mean reinventing the entire process from scratch, and a firm with structured systems in place makes both of those transitions close to routine.

Project management is the substance of running a tax firm, not its administrative overhead. It's the mechanism that turns expertise into revenue at scale, and firms still treating it as an afterthought will keep running into the same ceiling, year after year, no matter how good their technical work is.