4. Overhead Allocation and Activity-Based Costing

Introduction and Context

Manufacturing cost information is useful only when it represents the economic resources consumed by products, customers, channels, and processes with reasonable accuracy. Direct materials and direct labour can often be traced to individual products relatively easily. Manufacturing overhead is more difficult. It includes indirect materials, supervision, maintenance, depreciation, utilities, quality assurance, production planning, material handling, information systems, and many other costs that support production without being conveniently traceable to one unit of output.

The method used to assign these costs affects product profitability, inventory valuation, pricing, make-or-buy decisions, capacity planning, performance evaluation, and investment priorities. A product may appear profitable under a broad plant-wide overhead rate but become unprofitable when the resources it actually consumes are examined. Conversely, a standard product may be charged with excessive overhead because it is produced in a complex environment created primarily for other products.

Traditional absorption costing remains important for financial reporting and for many operational settings. However, changes in manufacturing have reduced the reliability of volume-based allocation alone. Automation, product variety, shorter life cycles, stringent quality requirements, frequent setups, and sophisticated logistics have increased the proportion of costs that are driven by transactions and complexity rather than by direct labour or machine hours. Activity-based costing (ABC), and its extension, time-driven activity-based costing (TDABC), provide methods for improving visibility into these relationships.

This chapter examines the logic, design, application, and managerial implications of overhead allocation systems. It also considers the circumstances in which traditional methods remain appropriate and the governance required to prevent cost models from becoming misleading or politically manipulated.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the nature and purpose of manufacturing overhead allocation.

2. Distinguish plant-wide, departmental, and activity-based overhead rates.

3. Identify suitable cost pools and cost drivers.

4. Calculate and interpret traditional absorption, ABC, and TDABC costs.

5. Evaluate the effects of allocation choices on products, customers, channels, and decisions.

6. Recognize implementation risks, behavioural consequences, and limitations.

7. Recommend an appropriate costing approach for a manufacturing context.

Why Overhead Allocation Matters

Overhead allocation is the process of assigning indirect costs to cost objects. A cost object may be a product, batch, order, customer, production line, supplier, distribution channel, or project. The allocation is not merely an accounting exercise. It creates a representation of resource consumption, and managers may use that representation to make decisions.

A useful allocation system has three qualities. First, it should be sufficiently causal: the assigned cost should reflect the factors that cause or influence the cost. Second, it should be economically feasible: the benefit of improved information should justify the cost of collecting and maintaining it. Third, it should be understood by decision makers. A theoretically precise model that users cannot interpret or trust may have little managerial value.

The distinction between allocation and tracing is fundamental. Direct costs are traced to a cost object through an observable relationship. Indirect costs are allocated using a rational basis because direct tracing is impractical or too costly. Allocation therefore involves estimation and judgement. No allocation method automatically reveals a single indisputable “true” product cost.

Overhead also contains different types of cost behaviour. Some costs vary with units produced, such as certain consumables. Some vary with batches, such as setup and inspection costs. Some vary with product variety or engineering changes. Others support an entire facility and may not change materially with short-term output. Treating all overhead as though it were caused by units can distort cost information.

Traditional Absorption Methods

Plant-wide overhead rate

The simplest method pools manufacturing overhead for the entire plant and applies it using one allocation base. The rate is commonly calculated as:

Predetermined overhead rate = Budgeted manufacturing overhead / Budgeted allocation base

The allocation base may be direct labour hours, machine hours, direct labour cost, or units produced. If budgeted overhead is ₹12,000,000 and budgeted machine hours are 60,000, the rate is ₹200 per machine hour. A product using 1.5 machine hours receives ₹300 of overhead.

A plant-wide rate is attractive because it is inexpensive, easy to explain, and consistent. It may be reasonable where products use similar processes, labour and machine proportions are stable, and overhead is closely related to the selected base. Its weakness is that it assumes one factor adequately represents the consumption of all overhead resources.

Departmental rates

Departmental costing recognizes that different departments may have different technologies, cost structures, and drivers. A machining department may apply overhead by machine hours, while an assembly department may use direct labour hours. Each department calculates a separate rate:

Departmental rate = Departmental overhead / Departmental allocation base

Departmental rates improve accuracy when products pass through departments in different proportions. Nevertheless, a department may contain activities with different causes. For example, setup, processing, inspection, and material movement may all be combined in a machining department rate even though they are not driven by the same factor.

Normal and actual costing

Under actual costing, actual overhead and actual activity are used to calculate product cost. This can create fluctuating rates and delays. Normal costing applies actual direct costs but a predetermined overhead rate, thereby smoothing seasonal and short-term variations. At period end, under- or over-applied overhead is reviewed and adjusted according to the organization’s accounting policy.

Absorption costing assigns manufacturing overhead to inventory and cost of goods sold. It is distinct from variable costing, which treats fixed manufacturing overhead as a period cost for internal reporting. Absorption costing is generally required for external inventory valuation in many accounting regimes, but its compliance role should not be confused with its usefulness for strategic cost analysis.

Cost Pools, Cost Drivers, and Causality

A cost pool is a grouping of costs believed to have a common cause. A cost driver is a measurable factor that explains changes in the cost pool. Examples include machine hours, labour hours, number of setups, purchase orders, material movements, inspection hours, engineering change orders, and customer delivery frequency.

The choice of driver involves more than statistical correlation. A driver should have a plausible operational relationship with the cost, be measurable at reasonable cost, and be sufficiently stable for planning. A high correlation may be misleading if both cost and activity are driven by a third factor. Conversely, a causally sound driver may show weak short-term correlation because of fixed capacity or timing effects.

Drivers are often classified by the level at which activities occur:

• Unit-level activities are performed for each unit, such as machining time.
• Batch-level activities occur for each batch, such as setup and batch inspection.
• Product-sustaining activities support a product or product family, such as engineering maintenance and design changes.
• Customer- or market-level activities support specific customers, channels, or territories.
• Facility-sustaining activities support the whole plant, such as plant management, security, and building depreciation.

This hierarchy prevents a common error: assigning batch and product costs only on the basis of units. A low-volume product with many setups may consume more setup resources per unit than a high-volume product, even if its machine time is modest.

Activity-Based Costing

ABC assigns resource costs to activities and then assigns activity costs to cost objects according to their use of those activities. Its basic sequence is:

1. Identify significant activities.

2. Assign resource costs to activity cost pools.

3. Select a cost driver for each pool.

4. Calculate an activity rate.

5. Assign activity costs to products, customers, or other cost objects.

6. Interpret the results and improve the underlying processes.

The activity rate is:

Activity rate = Cost of activity pool / Practical or expected driver volume

Suppose setup costs are ₹900,000 and the plant expects 300 setups. The setup rate is ₹3,000 per setup. A product requiring 40 setups is assigned ₹120,000 of setup cost, regardless of how many units are produced in those batches. If inspection costs are separately driven by inspection hours, they should not be hidden in the setup rate.

ABC can be represented as a two-stage model. Resources such as salaries, equipment, and utilities are first assigned to activities. Activities are then assigned to products or customers. The model therefore makes visible the intermediate processes that traditional costing often obscures.

Illustrative comparison

Assume two products, Standard and Custom, use the following resources:

| Measure | Standard | Custom |

|---|---:|---:|

| Units produced | 10,000 | 1,000 |

| Machine hours per unit | 1.0 | 1.5 |

| Setups | 20 | 80 |

| Inspections | 40 | 100 |

Total overhead is ₹1,200,000. A plant-wide rate based on 11,500 machine hours is approximately ₹104.35 per machine hour. The resulting overhead assignment is approximately ₹1,043,500 to Standard and ₹156,500 to Custom.

Now suppose ABC identifies three pools: machine processing ₹575,000 driven by 11,500 machine hours; setups ₹400,000 driven by 100 setups; and inspections ₹225,000 driven by 140 inspections. The rates are ₹50 per machine hour, ₹4,000 per setup, and approximately ₹1,607 per inspection. Standard receives ₹500,000 for processing, ₹80,000 for setups, and approximately ₹64,286 for inspections: total approximately ₹644,286. Custom receives ₹75,000, ₹320,000, and approximately ₹160,714: total approximately ₹555,714.

The plant-wide system assigns most overhead to Standard because Standard has most machine hours. ABC reveals that Custom consumes a disproportionate share of setup and inspection resources. The difference is not an accounting curiosity. It may change product mix, minimum order quantities, setup reduction priorities, engineering policy, and customer pricing.

From Product Cost to Customer and Channel Cost

ABC is not limited to factory products. The same reasoning can be applied to customers and distribution channels. A customer may generate costs through order entry, technical support, special packaging, expedited delivery, returns, credit administration, and frequent small shipments. Revenue minus product cost is therefore not necessarily customer profitability.

A customer profitability model may include activities such as processing orders, scheduling production, handling complaints, conducting special inspections, and delivering products. A large customer can be unprofitable if it demands extensive service concessions, while a smaller customer may be attractive because it places predictable orders and requires little support. The analysis should distinguish avoidable costs from allocated common costs before management takes action.

Channel analysis can similarly compare direct sales, distributors, online ordering, and project-based sales. However, costs should not be assigned simply to punish a channel for using shared resources. Managers should identify which activities would actually change if the channel changed, particularly when evaluating strategic alternatives.

Time-Driven Activity-Based Costing

Conventional ABC can become difficult to maintain when there are hundreds of activities and numerous driver measurements. TDABC simplifies the model by estimating two parameters:

1. The cost per unit of supplied capacity.

2. The time required to perform a transaction or activity.

The capacity cost rate is:

Capacity cost rate = Cost of supplied capacity / Practical capacity in time units

If a customer service department costs ₹2,400,000 annually and supplies 120,000 practical minutes, its capacity cost rate is ₹20 per minute. If a standard order takes 8 minutes and a complex order takes 20 minutes, the assigned costs are ₹160 and ₹400 respectively.

TDABC can incorporate time equations. For example:

Processing time = 5 minutes + 3 minutes if international + 4 minutes if special packaging

This approach represents operational complexity without creating a separate activity pool for every variation. It also highlights unused capacity. If supplied capacity is 120,000 minutes but only 100,000 minutes are required by actual transactions, the model indicates 20,000 minutes of unused practical capacity. Management can then consider reducing capacity, redeploying employees, or developing additional business. Unused capacity should not automatically be loaded onto existing products, because doing so obscures the distinction between resource availability and resource consumption.

TDABC is particularly useful in service-intensive manufacturing environments, shared service centres, maintenance operations, logistics, and environments with many transaction types. Its accuracy depends on credible time estimates and regular validation.

Designing an Appropriate Costing System

A costing project should begin with a decision problem rather than with software. Management should ask what decisions the information must support: pricing, product rationalization, customer negotiations, process improvement, capacity planning, or strategic sourcing. A model designed for long-term product profitability may require different detail from a model designed for daily production control.

The next step is to map the value-creating and support processes. Interviews, observation, production records, maintenance data, purchasing records, quality reports, and enterprise resource planning systems can reveal where resources are consumed. The team should avoid identifying activities at an excessively fine level. An activity should be separately modelled when its cost behaviour or managerial implication differs materially from other activities.

Driver selection should combine operational knowledge with data analysis. Rates should generally be based on practical capacity rather than theoretical maximum capacity. Theoretical capacity may produce very low rates and make products appear cheaper than the resources required to support them. Practical capacity recognizes breaks, maintenance, changeovers, training, and normal interruptions.

The model should be tested against operational reality. Product managers, production supervisors, finance professionals, sales personnel, and process owners should review whether the results make sense. Unexpected results are not automatically errors; they may reveal hidden complexity. Nevertheless, unusual outcomes should be reconciled to source data and investigated before decisions are taken.

Detailed Illustrative Case: Meridian Components

Background

Meridian Components, an illustrative mid-sized manufacturer, produces two industrial assemblies: the M-10, a high-volume standardized product, and the M-90, a low-volume customized product. The plant historically applied all manufacturing overhead using machine hours. Senior management noticed that the M-90 had a high selling price and apparently strong margin, yet production and quality managers reported that it consumed considerable engineering and inspection attention.

Situation and problem

Annual overhead was ₹18 million. M-10 used 90,000 machine hours and M-90 used 30,000. The plant-wide rate was ₹150 per machine hour. M-10 therefore received ₹13.5 million of overhead and M-90 received ₹4.5 million. The reported contribution after assigned manufacturing cost suggested that M-90 was the more attractive product.

A cross-functional team examined the processes and identified three major overhead pools:

| Activity | Cost | Driver volume |

|---|---:|---:|

| Machine processing | ₹9,000,000 | 120,000 machine hours |

| Setups | ₹5,000,000 | 500 setups |

| Engineering and inspection | ₹4,000,000 | 2,000 hours |

M-10 required 200 setups and 500 engineering/inspection hours. M-90 required 300 setups and 1,500 engineering/inspection hours.

Analysis

ABC rates were ₹75 per machine hour, ₹10,000 per setup, and ₹2,000 per engineering/inspection hour. M-10 received ₹6.75 million for machine processing, ₹2 million for setups, and ₹1 million for engineering and inspection: total ₹9.75 million. M-90 received ₹2.25 million, ₹3 million, and ₹3 million: total ₹8.25 million.

The plant-wide method assigned ₹13.5 million to M-10 and ₹4.5 million to M-90. ABC therefore reduced the overhead assigned to the high-volume product by ₹3.75 million and increased the overhead assigned to the customized product by ₹3.75 million. The apparent profitability ranking changed substantially.

Approach and solution

Management did not immediately discontinue M-90. Instead, it examined the drivers of its cost. The team introduced setup reduction workshops, standardized selected design features, established engineering change approval rules, and negotiated order quantities with customers. Sales staff were given customer-specific profitability reports showing the cost consequences of special requirements. Prices for highly customized variants were revised, while strategically important customers were offered redesign assistance rather than an abrupt price increase.

The costing model was integrated with production and engineering data. Monthly reviews focused on whether the number of setups, inspection hours, and engineering changes were changing. Product costs were not used as a mechanical substitute for managerial judgement; they were used to identify questions and improvement opportunities.

Outcome

The illustrative case demonstrates that the major benefit of ABC was not simply a new overhead number. It revealed where resources were consumed and connected cost information with operational action. M-10 became a target for automation and capacity utilization analysis, while M-90 became a target for setup reduction and design simplification. Management also discovered that some facility-sustaining costs could not be meaningfully assigned to individual products and were better reported separately for strategic analysis.

Learning points

The case illustrates four principles. First, a high-volume product can be overcosted when it is used as a convenient absorber of complexity costs. Second, a low-volume customized product can appear attractive if batch and product-sustaining activities are ignored. Third, ABC is most valuable when it supports process and commercial decisions. Fourth, allocation results must be interpreted with knowledge of capacity, avoidability, and strategic purpose.

Managerial Uses and Decision Quality

Overhead information can support pricing, quoting, product design, outsourcing, process improvement, and capacity decisions. During product development, target cost teams can identify design features that create disproportionate setup, inspection, or logistics requirements. In sourcing decisions, managers should compare relevant avoidable costs rather than blindly relying on fully allocated product costs. In capacity planning, TDABC can show whether bottlenecks arise from processing time, changeovers, or support activities.

For performance evaluation, care is essential. A production manager may be charged with allocated quality or engineering costs that the manager cannot control. Such allocations may be useful for product profitability but unfair for short-term managerial evaluation. Responsibility accounting should distinguish controllable costs from common or strategic costs.

Limitations, Risks, and Common Mistakes

ABC and TDABC do not eliminate judgement. Their main limitations include data collection expense, model complexity, uncertain driver relationships, changing processes, and the risk of false precision. Time estimates may reflect opinion rather than observation. Employees may also resist models perceived as surveillance or as tools for cost cutting.

Common mistakes include:

• using revenue or units as a driver merely because the data are available;
• creating too many cost pools with no decision value;
• assigning all facility costs to products as though they were variable;
• using theoretical rather than practical capacity;
• treating allocated cost as avoidable cost;
• failing to update rates after process or technology changes;
• interpreting a customer as unprofitable without considering strategic value;
• using cost information to reduce capacity when demand is temporary or uncertain;
• confusing product cost for external reporting with relevant cost for a specific decision.

A model can also produce dysfunctional behaviour. Departments may attempt to reduce reported activity counts rather than improve processes. Sales teams may reject profitable orders because of arbitrary allocations. Managers may manipulate driver estimates to protect budgets. Governance therefore requires documented definitions, version control, periodic validation, transparent assumptions, and review by cross-functional stakeholders.

Technology, Analytics, and Emerging Practice

Enterprise resource planning systems, manufacturing execution systems, barcode data, Internet of Things sensors, and workflow platforms can provide detailed transaction and time data for costing. Machine-event records can measure runtime and setup duration; quality systems can connect inspections and defects to batches; customer relationship systems can document service contacts and order complexity.

Analytics can assist driver selection by examining cost behaviour, process variation, and unused capacity. Machine learning may identify patterns in transaction time or predict the resource implications of product configurations. However, predictive accuracy does not establish managerial causality. Automated models should remain explainable, auditable, and subject to human review. Data quality, access controls, cybersecurity, and privacy are especially important when employee performance and customer behaviour are analysed.

Emerging practice is moving toward integrated profitability models that connect product configuration, production routing, customer service, logistics, carbon information, and capacity. Environmental management may also use activity-based principles to assign energy use, emissions, waste treatment, and transport impacts to products or processes. Such extensions require care because environmental impacts often cross organizational boundaries and involve uncertain measurement.

Ethical and Governance Considerations

Cost allocations influence prices, jobs, investment, supplier relationships, and product continuation. They should therefore be governed as management information, not treated as neutral facts. Assumptions should be disclosed to users, material changes should be approved, and models should not be designed solely to justify a predetermined decision.

Professional integrity requires separating financial-reporting requirements from internal decision models when their purposes differ. Confidential customer and employee information must be protected. Managers should avoid using arbitrary allocations to transfer blame or conceal unused capacity. Where costs are shared and not causally assignable, reporting them transparently as common costs may be more honest than assigning them with spurious precision.

Best-Practice Principles

An effective overhead management system generally follows these principles:

1. Begin with the decision and cost object, not with an accounting template.

2. Map processes before selecting drivers.

3. Use multiple rates when resource consumption differs materially.

4. Distinguish unit, batch, product, customer, and facility activities.

5. Use practical capacity and report unused capacity separately.

6. Balance accuracy against the cost of measurement.

7. Validate estimates with operational data and cross-functional review.

8. Update the model when technology, product mix, or process design changes.

9. Separate cost assignment from cost responsibility and avoidability.

10. Use the model to improve processes, not merely to redistribute blame.

Chapter Summary

Overhead allocation assigns indirect manufacturing costs to products or other cost objects. Plant-wide rates are simple but can distort cost when products consume departments and activities differently. Departmental rates improve recognition of process differences, while ABC uses activity pools and cost drivers to trace resource consumption more causally. Cost drivers should reflect the level at which activities occur, including unit, batch, product, customer, and facility levels.

TDABC simplifies ABC by using capacity cost rates and estimated transaction times. It can model complexity, reveal unused capacity, and support product, customer, channel, and process analysis. Both ABC and TDABC require sound data, practical capacity assumptions, regular validation, and careful interpretation. Allocated cost is not automatically avoidable cost, and a costing model should not replace managerial judgement. Properly governed, overhead information can improve pricing, product design, process improvement, capacity planning, and strategic decision-making.

Key Terms

Absorption costing: A costing method that assigns manufacturing overhead to products and inventory.

Activity-based costing (ABC): A method that assigns resource costs to activities and then to cost objects using activity drivers.

Activity cost pool: Costs grouped around an activity or related set of activities.

Activity rate: Cost of an activity pool divided by its driver volume.

Allocation base: The measure used to assign indirect costs, such as machine hours or labour hours.

Batch-level activity: An activity performed for each batch, regardless of the number of units in the batch.

Capacity cost rate: Cost of supplied capacity divided by practical capacity in time or other capacity units.

Cost object: A product, customer, order, process, or other item for which cost is measured.

Cost pool: A grouping of indirect costs allocated using a common basis.

Cost driver: A factor that causes or explains changes in the cost of an activity.

Departmental rate: An overhead rate calculated separately for a production or service department.

Facility-sustaining activity: An activity supporting the overall facility rather than a particular product or batch.

Normal costing: Use of predetermined overhead rates with actual direct costs.

Plant-wide rate: One overhead rate applied across an entire plant.

Practical capacity: Realistic available capacity after allowing for normal interruptions and nonproductive time.

Product-sustaining activity: An activity supporting a product or product family, such as engineering changes.

Time-driven ABC: An ABC approach based primarily on capacity cost rates and estimated time requirements.

Under-applied overhead: Actual overhead exceeding overhead applied to products.

Unused capacity: Supplied capacity not consumed by actual production or transactions.

Review Questions

Short Answer Questions

1. What is the difference between tracing a direct cost and allocating an indirect cost?

2. Define a cost driver and give two manufacturing examples.

3. Why can a plant-wide overhead rate distort product cost?

4. What is practical capacity, and why is it used in TDABC?

5. Distinguish batch-level activities from product-sustaining activities.

Long Answer Questions

1. Explain the development from plant-wide rates to departmental rates and ABC. Identify the circumstances in which each method may be appropriate.

2. Describe the complete process for designing and implementing an ABC system in a manufacturing organization.

3. Explain how ABC can be used to analyse customer and distribution-channel profitability.

4. Discuss the logic, calculation, and managerial value of time-driven activity-based costing.

5. Critically evaluate the limitations and behavioural risks of overhead allocation systems.

Analytical / Application Questions

1. A plant has high setup and inspection costs but applies all overhead using machine hours. Explain the likely distortion and recommend a revised costing approach.

2. A customer generates high revenue but places many small orders, requests special packaging, and frequently returns goods. Design an activity-based customer profitability analysis for this customer.

3. A service department costs ₹3,000,000 and has 150,000 practical minutes of capacity. Standard transactions take 6 minutes and complex transactions take 18 minutes. Calculate the TDABC cost of each transaction and explain how unused capacity would be interpreted if only 120,000 minutes were used.

22. Multiple Choice Questions with Answers

Question 1

Which situation most strongly supports using departmental overhead rates rather than one plant-wide rate?

A. All products use departments in approximately the same proportions

B. Different products use departments with substantially different technologies and cost structures

C. The organization wants to avoid collecting any operational data

D. All overhead is facility-sustaining

Correct Answer: B. Different products use departments with substantially different technologies and cost structures

Question 2

A batch-level cost is most appropriately driven by which measure?

A. Units produced

B. Sales revenue

C. Number of production setups

D. Direct material cost

Correct Answer: C. Number of production setups

Question 3

Under ABC, which sequence is correct?

A. Assign costs to products, identify departments, then select customers

B. Identify activities, assign resource costs to pools, calculate rates, and assign costs to objects

C. Calculate profit, assign revenue, and then estimate overhead

D. Assign all overhead using machine hours and then divide by batches

Correct Answer: B. Identify activities, assign resource costs to pools, calculate rates, and assign costs to objects

Question 4

A plant-wide rate based on machine hours is most likely to overcost a high-volume standardized product when:

A. The product consumes most of the plant’s setup and engineering resources

B. The product uses relatively few machine hours

C. Low-volume products consume disproportionate batch and support activities

D. All products have identical routings

Correct Answer: C. Low-volume products consume disproportionate batch and support activities

Question 5

A department costs ₹2,000,000 and supplies 100,000 practical minutes. Under TDABC, the capacity cost rate is:

A. ₹5 per minute

B. ₹20 per minute

C. ₹50 per minute

D. ₹200 per minute

Correct Answer: B. ₹20 per minute

Question 6

What is a principal managerial benefit of reporting unused capacity separately in TDABC?

A. It automatically increases product cost

B. It distinguishes resource availability from resources actually consumed

C. It eliminates the need for cost drivers

D. It converts all fixed costs into variable costs

Correct Answer: B. It distinguishes resource availability from resources actually consumed

Question 7

Which statement about allocated cost is most accurate for a make-or-buy decision?

A. All allocated costs are automatically avoidable

B. Allocated cost is always irrelevant

C. Relevant analysis should focus on costs that change with the decision

D. Facility costs must always be assigned to the purchased component

Correct Answer: C. Relevant analysis should focus on costs that change with the decision

Question 8

A customer requires frequent small deliveries and extensive technical support. Which approach best captures its profitability?

A. Allocate overhead only by units purchased

B. Use activities such as order processing, delivery, and technical support as cost pools

C. Ignore service costs because they are indirect

D. Assign all corporate overhead according to revenue

Correct Answer: B. Use activities such as order processing, delivery, and technical support as cost pools

Question 9

Why may practical capacity be preferable to theoretical capacity when calculating an activity rate?

A. It recognizes normal interruptions and avoids unrealistically low rates

B. It guarantees that all capacity will be used

C. It excludes all fixed costs

D. It makes every product equally costly

Correct Answer: A. It recognizes normal interruptions and avoids unrealistically low rates

Question 10

Which is a common governance risk in ABC implementation?

A. Drivers are reviewed against operational data

B. Assumptions are documented and version-controlled

C. Managers manipulate time estimates to influence reported performance

D. Unused capacity is reported separately

Correct Answer: C. Managers manipulate time estimates to influence reported performance