Overdue task rate

Overdue task rate is the percentage of assigned tasks that are past their due date and still open at a given moment. If a team owns 150 open tasks and 24 of them are past due, the overdue task rate is 16 per cent. It is a point-in-time read on how much owned work has already broken its deadline, across a team backlog, a project board, or an individual workload.

The metric matters because a task list is a set of promises, and an overdue task is a broken one. A long list of open tasks tells you nothing about risk on its own, but the share of it that is overdue tells you how many commitments have already slipped. Because it is a percentage, it compares fairly across people and teams of different sizes, so a heavily loaded individual and a small team can be read on the same scale.

Unlike a measure of how many tasks got done, overdue task rate is a snapshot of live exposure: the owned work that has missed its deadline and is still outstanding. It is a task-specific cousin of the overdue item rate and sits close to a general completion rate, but it watches assigned, owned tasks in their current state rather than the outcome of finished work.

The calculation divides the number of open tasks past their due date by the total number of open tasks, then multiplies by 100. The judgement sits in what you count as a task, how you treat ownership, and how you scope undated work, because each choice moves the number. Settle the components below before the formula is reliable.

1. 1

   Tasks past due and open

   Tasks whose due date has passed and that are still open, measured as of now. A task finished late is no longer overdue today, because it is no longer open, so the numerator only ever holds live slippage owed by an owner.

2. 2

   Total open tasks

   Every assigned task that is not yet complete at the measurement moment. Decide whether undated tasks belong here. The cleanest measure restricts the denominator to dated tasks, so the rate reflects only work that could actually be overdue.

3. 3

   Ownership

   Each task needs a single accountable owner. Unowned tasks are the ones most likely to slip and the hardest to chase, so handle them consistently rather than letting them drift in and out of the count.

4. 4

   Measurement moment

   Overdue task rate is a snapshot, so when you read it matters. Sampling on a fixed cadence, such as the start of each week, makes the trend comparable and stops a convenient reading time flattering the number.

A worked example. A team owns 100 open tasks today. Of those, 80 have due dates and 20 have none. Among the dated tasks, 20 are past due. Scoping the denominator to dated tasks, the overdue task rate is (20 / 80) x 100, which is 25 per cent. If you instead count all 100 open tasks, it reads (20 / 100) x 100, or 20 per cent. The lower figure looks healthier only because undated tasks pad the denominator, which is exactly why the scoping rule has to be consistent over time.

A metric tree decomposes the overdue task rate into the reasons a task slips its deadline, then traces each reason down to the specific cause. This turns a flat percentage into a diagnosis of why owned work is running late.

The first level splits the rate into the forces behind slippage: whether each task had a real owner, whether the owner had capacity, whether tasks were blocked, and whether overdue tasks were actively cleared. Each branch decomposes further. Ownership breaks into a single accountable owner and whether the owner accepted the task. Capacity breaks into workload balance and competing priorities. Blockers break into dependencies and missing inputs. When the rate climbs, the tree tells you whether tasks are overdue because they were never properly owned, because an owner is overloaded, or because they are stuck waiting on something.

This is the gap between a dashboard and a decision. A dashboard says 25 per cent of open tasks are overdue. The tree shows that nearly all of them sit with one overloaded owner, which is a workload balancing problem with a clear fix, not a sign the whole team is behind.

Overdue task rate benchmarks depend on how strictly the team sets due dates and how it handles unowned work, so your own trend over time is the most reliable comparison. A team that dates every task aggressively will run a higher rate than one that only dates the critical few, without either being healthier. The bands below give a practical sense of where a team sits when measuring owned, dated tasks.

The figure worth watching is not just the level but how the overdue tasks are distributed across owners. A rate that is healthy on average can hide one person carrying almost all the overdue work. Reading the rate per owner, alongside cycle time, tells you whether the slippage is a shared pace problem or a concentrated capacity problem on a single person.

Improving the overdue task rate is about fixing the reason tasks slip, not chasing owners to catch up. The metric tree points at the weak branch, and each branch has a concrete fix.

The decomposition decides the intervention. If tasks are overdue because they have no real owner, forcing a single accountable owner beats chasing the list. If they are overdue because one person is overloaded, rebalancing beats reminders. Treating every overdue task as a discipline problem when it is really an ownership or capacity problem wastes effort and erodes trust in the deadline.

KPI Tree lets you model this by connecting the overdue task rate to the owners and work behind it. Every task carries RACI ownership, so each one has a single accountable person rather than a vague team assignment. When a task slips or a due date approaches, the metric pushes to that accountable owner rather than waiting for the next stand-up to surface it. The verified impact loop then checks whether a change, like rebalancing workloads, actually brought the rate down, so the team learns which fixes hold.

1. 1

   Counting unowned or undated tasks

   A task with no owner has nobody accountable for the slip, and a task with no due date cannot be overdue. Including either distorts the rate. Scope both numerator and denominator to owned, dated tasks.

2. 2

   Pushing due dates to clear the number

   Silently moving a deadline forward makes a task stop being overdue without it being done. The rate improves while the work does not. Hold due dates honest, or the metric measures nothing real.

3. 3

   Reading only the team average

   A healthy headline rate can hide one owner carrying almost all the overdue tasks. The average masks the concentration, so read the rate per owner to find where the slippage actually sits.

4. 4

   Sampling at convenient times

   Overdue task rate is a snapshot, so reading it only when it looks good distorts the trend. Sample it on a fixed cadence so the direction of travel is comparable from one period to the next.

5. 5

   Treating blocked and not-started the same

   A blocked task and a never-started task are both overdue but need opposite fixes. Lumping them together sends owners chasing work they cannot move. Split overdue tasks by reason before deciding what to do.