Time-Driven Activity-Based Costing: Cut Complexity Without Losing Cost Precision
Time-Driven Activity-Based Costing helps managers allocate costs accurately across complex, high-volume operations without the maintenance burden of traditio…
Topic: Financial Management
Why It Matters
Managers who have wrestled with cost allocation know the problem well: the system that was supposed to bring clarity to pricing, capacity, and resource decisions has become a maintenance project in its own right.
Traditional activity-based costing promised a more accurate picture of where costs were being consumed, and it delivered but at a price. As operations grow more complex, the number of activity pools multiplies, employee surveys become unreliable, and finance teams spend more time updating the model than using it.
The result is that many organisations quietly abandon their costing systems and fall back on simpler, less informative methods.
Time-driven activity-based costing was designed to solve exactly this problem. It retains the analytical rigour of traditional ABC while dramatically reducing the complexity of building and maintaining the model.
Rather than relying on surveys and interviews to allocate costs across dozens of activity pools, it uses time as the single unifying driver, expressed through equations that can be updated quickly as operations change.
For managers overseeing complex service operations, logistics networks, or customer-facing processes with high transaction volumes, this distinction matters enormously.
Before reading further, consider whether any of the following describe your current situation.
Are your existing cost figures giving you confidence in pricing decisions, or do you find yourself discounting them because you know the model hasn't been updated in over a year?
When your team's workload shifts, do your cost reports reflect that shift within a reasonable timeframe, or does the lag make the data feel irrelevant?
If you were asked to show a colleague exactly where your department's capacity is being consumed this quarter, could you do it without significant preparation?
If any of those questions prompted hesitation, time-driven activity-based costing is worth your attention.
Origin and Underlying Logic
Time-driven activity-based costing was developed by Robert Kaplan and Steven Anderson and introduced formally in 2004, as a response to the well-documented limitations of traditional ABC systems in large, dynamic organisations.
The core insight was straightforward: rather than surveying employees to estimate how much time they spend on each activity (a process that is both time-consuming and prone to bias), it is more practical to estimate the time each transaction or task requires and then multiply that by the cost of supplying one unit of time.
The underlying logic rests on two parameters.
The capacity cost rate: the total cost of a department or resource group divided by its practical capacity in time, typically expressed in cost per minute.
The time estimate for each type of transaction or activity the department performs. Multiply the two, and you have the cost of that activity. When a transaction involves multiple steps or conditional variations, these are captured through time equations rather than separate cost pools, which is what makes the system scalable and maintainable in a way traditional ABC is not.
TDABC sits within the broader tradition of management accounting and cost management, and is closely related to capacity management thinking, lean operations analysis, and process costing. It is particularly well aligned with organisations that have adopted process-improvement methodologies, since both approaches require a clear understanding of how time is consumed across operational steps.
Structure and Application
The method is built around a small number of core components, each of which serves a specific purpose in producing an accurate and maintainable cost model. Understanding what each component does, not just what it is, makes the difference between a model that gets used and one that sits in a spreadsheet until someone questions whether it is still valid.
The first component is the identification of resource groups: the departments, teams, or cost centres whose resources you want to model. Each group should be defined by shared function and a reasonably consistent cost structure. For each resource group, you calculate the total cost of supplying those resources over a given period, typically a quarter or a year, covering salaries, occupancy, equipment, and overhead.
The second component is practical capacity. This is not the theoretical maximum hours a team could work; it is the realistic working time available after accounting for breaks, meetings, training, and downtime. Kaplan and Anderson suggest that 80-85% of contracted hours is a reasonable starting estimate for most service environments, though this varies by context. Practical capacity is expressed in minutes to align with time estimates at the transaction level.
Dividing total resource cost by practical capacity in minutes gives you the capacity cost rate. This single figure anchors the entire model and can be recalculated whenever headcount, salaries, or working patterns change, without rebuilding the model from scratch.
The third component is time equations. For each activity type the resource group performs, you estimate the standard time required. When an activity has variants (a standard order versus an international order with customs documentation, for instance), the time equation captures each variant as an additive component. This replaces the need for separate activity pools for each variant, which is the primary source of complexity in traditional ABC.
The method is most commonly presented as a spreadsheet model or financial planning tool, though it integrates naturally with ERP systems and capacity planning platforms. It operates at the team or departmental level but aggregates to provide organisation-wide visibility on cost consumption and capacity utilisation.
If you want to take a concrete first step before reading further: identify one department in your organisation with a high volume of similar but slightly variable transactions, calculate its total quarterly cost and practical capacity in hours, and divide the two. That single figure, your rough capacity cost rate, will immediately raise questions about how your current costing approach handles unused capacity, which is precisely where the deeper application of this method becomes valuable.
FAQ
The following questions reflect what managers most commonly ask when first encountering time-driven activity-based costing.
Q: What is time-driven activity-based costing?
A: Time-driven activity-based costing is a cost management method that uses time as the primary driver for allocating resource costs to products, services, or customers. Rather than surveying employees across multiple activity pools, it uses two inputs: the cost of supplying resources per unit of time, and the time each type of transaction or activity requires. Developed by Kaplan and Anderson, it is designed to be more scalable and easier to maintain than traditional activity-based costing.
Q: How does TDABC differ from traditional activity-based costing?
A: Traditional ABC requires managers to define multiple activity cost pools and collect employee estimates of time spent on each, which is resource-intensive and difficult to keep current. TDABC consolidates this by using time equations instead of multiple pools, requiring only two parameters per resource group. The result is a model that is faster to build, easier to update, and more transparent in how it handles capacity.
Q: Is time-driven activity-based costing suitable for small teams or businesses?
A: TDABC is particularly well suited to environments with high transaction volumes and process variation, which are more commonly found in mid-sized to large organisations. Smaller teams can apply the principles, but if your operation is straightforward and relatively static, the setup effort may not justify the return. The method adds the most value where traditional costing is producing distorted results due to cross-subsidisation between high- and low-complexity activities.
Q: How do I know if time-driven activity-based costing is right for my situation?
A: The clearest signal is a gap between your instinct about profitability and what your cost reports show. If high-volume, low-complexity transactions appear to be subsidising customised, time-intensive ones, or if your finance team struggles to keep the cost model current as processes change, TDABC is likely a better fit than your current approach. It is also worth considering if you are in a capacity planning exercise and need to quantify the cost of unused resource time.
Q: What are the main limitations of TDABC?
A: The method's accuracy depends heavily on the quality of time estimates, which can be difficult to validate in complex or variable service environments. It also requires a baseline understanding of practical capacity that many organisations have not previously measured. The Deep Dive covers both of these limitations in more detail, along with guidance on how experienced practitioners manage them.