Why Cost Overrun Percentage matters
A change in Cost Overrun Percentage is a signal to inspect the contributing records and segments; the headline value alone does not identify the cause.
- Business question
- Are the inputs behind Cost Overrun Percentage moving in a way that requires action?
- Teams that use it
- Project managers, delivery leads, finance, operations, and project sponsors.
- Decisions it supports
- Schedule recovery, budget control, scope choices, staffing, and delivery-risk management.
Cost Overrun Percentage formula
(Actual Cost - Planned Budget) ÷ Planned Budget × 100
Formula components
- Actual Cost
- The monetary amount assigned to actual cost for the same scope and reporting period used by Cost Overrun Percentage.
- Planned Budget
- The monetary amount assigned to planned budget for the same scope and reporting period used by Cost Overrun Percentage.
- Reporting period
- The consistent day, week, month, quarter, or year covered by every input.
How to calculate Cost Overrun Percentage
- Define the business scope, reporting period, and the event or status that qualifies for Cost Overrun Percentage.
- Collect each input in the workbook formula from systems that use the same cut-off and unit.
- Remove duplicates and exclusions according to the documented rule, while retaining a reconciliation count.
- Apply (Actual Cost - Planned Budget) ÷ Planned Budget × 100 and label the result with its period, unit, and relevant segment.
Cost Overrun Percentage example
A fictional team uses one scope and period for every Cost Overrun Percentage input.
- Actual Cost = £120,000; Planned Budget = £100,000.
- Planned Budget = £100,000.
- Cost Overrun Percentage = (£120,000 − £100,000) ÷ £100,000 × 100 = 20%.
Cost Overrun Percentage is 20%.
The calculation preserves the workbook order: first take the difference, then divide by the stated comparison base.
How to interpret the result
Compare Cost Overrun Percentage over a consistent cadence and break it down only by segments large enough to support a decision. Review the formula inputs beside the result so teams can distinguish a real operating shift from a denominator or mix effect.
There is no single target that fits every organisation. Interpretation depends on project type, delivery method, scope, complexity, team capacity, and reporting date. Document the comparison group before labelling a result strong or weak.
Common mistakes and limitations
- Inconsistent scope
- Changing the included business units, products, channels, or populations makes the trend look different even when underlying performance is unchanged.
- Mismatched periods
- Formula inputs from different cut-off dates or time windows do not describe one coherent result.
- Mixing accounting treatments
- Gross and net amounts, recognition dates, allocations, refunds, taxes, and capitalisation rules must be applied consistently.
- Assuming one universal target
- A useful comparison depends on project type, delivery method, scope, complexity, team capacity, and reporting date; use like-for-like internal trends and clearly documented peer groups.