Cost Model Review Frequency: How Often Should You Update Your Costing System?
Why This Matters
A cost model is not a static artifact. It is a representation of how your business consumes resources, and that consumption pattern changes every time you add a product, modify a process, lose or gain a customer, or adjust capacity. When the model stops reflecting reality, every output it produces - product costs, customer profitability, pricing recommendations, capacity utilization reports - drifts from truth.
Research into time equation accuracy reveals three distinct sources of error in cost models. Incorrect specification of the model structure accounts for 49% of total error. Imprecise estimates of time and resource consumption contribute another 30%. And the remaining 21% comes from lack of updates - staleness that accumulates silently as operations evolve while the model stays frozen.
Organizations that review their cost model only annually can experience 15% to 25% cost distortion by mid-year, particularly in fast-moving industries where product mix, customer behavior, and operational processes change frequently. The danger is that this drift is invisible: the numbers still come out of the system looking precise, but they no longer correspond to operational reality.
The Four Maturity Levels
Level 1: No Formal Cost Model
The organization does not maintain a structured cost model. Cost information comes directly from the general ledger or accounting system without any systematic allocation or modeling layer. There is nothing to review because no model exists.
Example from the Health Check: “We don’t have a formal cost model - we rely on the accounting system as-is.”
What this means in practice: Without a model, the organization has no mechanism to translate accounting data into decision-relevant cost information. Product costs, when needed, are ad hoc calculations that vary depending on who performs them and what assumptions they use. There is no institutional memory of how costs behave.
Level 2: Annual Review
A cost model exists and is updated once per year, typically as part of the annual budget cycle. Overhead rates, allocation bases, and cost pools are recalculated using the prior year's data or the upcoming year's budget assumptions.
Example from the Health Check: “We review and update our cost model annually, usually during the budget cycle.”
What this means in practice: An annual review represents an improvement over no model, but it leaves the organization operating with increasingly stale data for up to eleven months of the year. By mid-year, process changes, new product introductions, and shifts in product mix can introduce significant distortion. The model reflects last year's reality, not this year's operations.
Level 3: Quarterly Review
The cost model is reviewed and updated quarterly. Capacity cost rates are recalculated with current data, allocation bases are refreshed, and any significant operational changes from the previous quarter are reflected in the model structure.
Example from the Health Check: “We review quarterly, updating rates and drivers based on recent operational data.”
What this means in practice: Quarterly reviews substantially reduce the staleness problem. The maximum drift from reality is limited to about three months, and the review cadence creates a natural governance discipline. However, a purely calendar-driven approach can still miss critical events that occur between review dates - a major customer win, a production line change, or a significant headcount adjustment.
Level 4: Monthly or Event-Driven Updates
The cost model is updated monthly and also responds to significant operational events. The organization maintains two triggers for model updates: a regular calendar cycle and an event-driven trigger that fires whenever a material change occurs in processes, capacity, product mix, or cost structure.
Example from the Health Check: “We update monthly or whenever significant operational changes occur (event-driven updates).”
What this means in practice: This dual-trigger approach represents best practice from the TDABC framework. Calendar-driven reviews ensure regular maintenance, while event-driven updates catch the changes that cannot wait. Events that should trigger an update include new product launches, significant process changes, capacity additions or reductions, major customer acquisitions or losses, and shifts in the cost structure such as raw material price changes or new labor agreements.
How to Move Up: Practical Steps
From Level 1 to Level 2: Build Your First Cost Model
- Extract indirect cost data from the general ledger and organize it into logical cost pools (facilities, equipment, labor support, administration)
- Select an allocation base for each pool and collect the driver data from your operational systems
- Build a simple allocation model in a spreadsheet and calculate your first set of product or service costs
- Schedule an annual review date tied to your budget cycle and document the model assumptions
From Level 2 to Level 3: Establish Quarterly Discipline
- Define a quarterly review checklist: rates, drivers, cost pool structure, and process assumptions
- Automate the extraction of driver data from ERP and operational systems to reduce the manual effort of each review cycle
- Create a cost model change log that tracks what was updated, why, and what impact it had on product and customer costs
- Assign ownership to a specific role (cost accountant, controller) with accountability for the quarterly review
From Level 3 to Level 4: Add Event-Driven Triggers
- Define a formal list of trigger events that require model updates: new product launch, process change, capacity adjustment, major customer change, cost structure shift
- Establish communication channels so operations and sales inform finance when trigger events occur
- Move from spreadsheets to a dedicated costing platform that supports rapid model updates without rebuilding from scratch
- Implement a cost model steering committee that meets monthly to review model health and decide on structural changes
Industry Benchmarks
Review frequency varies by industry, driven primarily by the pace of operational change and the complexity of the product and customer portfolio.
| Industry | Typical Level | Key Challenge |
|---|---|---|
| Manufacturing | Level 2 | Annual budget-driven reviews dominate; mid-year process changes create cost drift that is discovered only at year-end |
| Healthcare | Level 1–2 | Reimbursement rate changes and procedure mix shifts require more frequent updates than most institutions perform |
| Financial Services | Level 2–3 | Product proliferation and channel migration require at least quarterly reviews to maintain cost accuracy |
The median score for manufacturing companies on cost model review frequency is 1.9 out of 4. Healthcare organizations average 1.5. Financial services firms lead at 2.4, driven by regulatory requirements and competitive pressure for accurate product profitability.