Why Cost per Deliverable matters
Movement in Cost per Deliverable should prompt a check of the underlying volume, mix, timing, and data coverage before the team attributes the change to performance.
- Business question
- How is Cost per Deliverable changing, and which operating segments explain that movement?
- 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 per Deliverable formula
Total Cost ÷ Total Deliverables
Formula components
- Cost
- The monetary amount assigned to cost for the same scope and reporting period used by Cost per Deliverable.
- Deliverables
- The consistently counted deliverables included in the metric’s documented population and period.
- Reporting period
- The consistent day, week, month, quarter, or year covered by every input.
How to calculate Cost per Deliverable
- Define the business scope, reporting period, and the event or status that qualifies for Cost per Deliverable.
- 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 Total Cost ÷ Total Deliverables and label the result with its period, unit, and relevant segment.
Cost per Deliverable example
A fictional team brings together the inputs for Cost per Deliverable over one consistent month.
- Cost = £63,918.
- Deliverables = 53.
- Cost per Deliverable = £63,918 ÷ 53 = £1,206.
Cost per Deliverable is £1,206.
This is the average or ratio for the defined population; individual records can sit well above or below it.
How to interpret the result
Compare Cost per Deliverable 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.