Why Overtime Rate matters
Read Overtime Rate alongside the operational drivers that feed the formula. A better-looking result may come from a population change rather than a real improvement.
- Business question
- Is the latest Overtime Rate result caused by performance, mix, timing, or measurement changes?
- 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.
Overtime Rate formula
(Overtime Hours ÷ Total Hours Worked) × 100
Formula components
- Overtime Hours
- Elapsed time measured with one start event, end event, unit, and treatment of incomplete records.
- Hours Worked
- Elapsed time measured with one start event, end event, unit, and treatment of incomplete records.
- Reporting period
- The consistent day, week, month, quarter, or year covered by every input.
How to calculate Overtime Rate
- Define the business scope, reporting period, and the event or status that qualifies for Overtime Rate.
- 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 (Overtime Hours ÷ Total Hours Worked) × 100 and label the result with its period, unit, and relevant segment.
Overtime Rate example
A fictional project management team calculates Overtime Rate for one agreed reporting period.
- Overtime Hours = 73.
- Hours Worked = 800.
- Overtime Rate = 73 ÷ 800 × 100 = 9.1%.
Overtime Rate is 9.1%.
About 9.1 in every 100 eligible units meet the metric’s stated condition.
How to interpret the result
Compare Overtime Rate 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.
- Reading the headline alone
- A single value can hide offsetting movement across segments, volumes, or contributing formula components.
- 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.