Number of Overdue Tasks (Project Management KPI): Formula and Example

Business context

Why Number of Overdue Tasks matters

Number of Overdue Tasks becomes decision-useful when teams can explain which input moved, where it moved, and whether the definition stayed stable.

Business question: What does Number of Overdue Tasks tell us about performance in the selected scope and period?
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.

Calculation

Number of Overdue Tasks formula

Sum of Overdue Tasks

Formula components

Overdue Tasks: The consistently counted overdue tasks included in the metric’s documented population and period.
Measurement scope: The business unit, product, channel, team, or process included in both the input data and the result.
Reporting period: The consistent day, week, month, quarter, or year covered by every input.

How to calculate Number of Overdue Tasks

Define the business scope, reporting period, and the event or status that qualifies for Number of Overdue Tasks.
Remove duplicates and exclusions according to the documented rule, while retaining a reconciliation count.
Collect each input in the workbook formula from systems that use the same cut-off and unit.
Apply Sum of Overdue Tasks and label the result with its period, unit, and relevant segment.

Worked example

Number of Overdue Tasks example

A fictional team applies the documented counting or scoring rule for Number of Overdue Tasks across three operating groups.

The three validated group values are 166, 179, 157.
All groups use the same inclusion rule and reporting cut-off.
Number of Overdue Tasks = 166 + 179 + 157 = 502.

Number of Overdue Tasks is 502 for the period.

The total can be compared only with results built from the same event, scope, and data-quality rules.

How to interpret the result

Compare Number of Overdue Tasks 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.