Overdue item rate

Overdue item rate is the percentage of tracked items that are past their due date and still not complete at a given moment. If a team has 200 open items and 30 of them are past due, the overdue rate is 15 per cent. It is a point-in-time health check on a backlog, work queue, or action list, showing how much of the open work has already broken its deadline.

The metric matters because volume alone hides risk. A backlog of 200 items sounds the same whether five or fifty of them are overdue, but those two situations are very different. The overdue rate surfaces the slipped commitments that would otherwise stay buried in a long list, and it does so as a comparable percentage rather than a raw count, so a small team and a large one can be measured on the same scale.

Unlike a completion measure that looks backwards at what got done, overdue rate is a snapshot of current exposure: the work that has already missed its deadline and is still owed. It is closely related to a general completion rate, but it watches the live state of open work rather than the outcome of finished work.

The calculation divides the number of open items past their due date by the total number of open items, then multiplies by 100. The judgement sits in what you count as open and how you treat items with no deadline, because both choices move the number. Settle the components below before the formula is reliable.

1. 1

   Items past due and open

   Items whose due date has passed and that are not yet complete, measured as of now. A completed item that was finished late is not overdue today, because it is no longer open, so the numerator only ever holds live slippage.

2. 2

   Total open items

   Every item that is not yet complete at the measurement moment. Decide whether items with no due date belong here. The cleanest measure restricts the denominator to dated items, so the rate reflects only work that could actually be overdue.

3. 3

   Due date definition

   What counts as the deadline for each item. A consistent rule, such as the latest agreed date rather than the original one, keeps the rate honest, because silently pushing due dates makes overdue work vanish without it being done.

4. 4

   Measurement moment

   Overdue rate is a snapshot, so the time you read it matters. Sampling on the same cadence, such as every Monday morning, makes the trend comparable and stops a convenient reading time flattering the number.

A worked example. A team has 120 open items today. Of those, 90 have due dates and 30 have none. Among the dated items, 18 are past due. If you scope the denominator to dated items, the overdue rate is (18 / 90) x 100, which is 20 per cent. If you instead count all 120 open items, it reads (18 / 120) x 100, or 15 per cent. The lower figure looks better but only because undated work is padding the denominator, which is exactly why the scoping rule must be consistent.

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

The first level splits the rate into the forces behind slippage: whether the team took on more than it could carry, whether due dates were realistic, whether items were blocked, and whether overdue work was being actively cleared. Each branch decomposes further. Intake breaks into volume added and capacity available. Date setting breaks into realistic estimates and buffer for the unexpected. Blockers break into dependencies and missing inputs. When the rate climbs, the tree tells you whether items are overdue because the team is overloaded, because deadlines were never achievable, or because work is stuck waiting on something.

This is the gap between a dashboard and a decision. A dashboard says 20 per cent of open items are overdue. The tree shows that almost all of them are blocked waiting on another team, which is a dependency problem with a clear owner, not a sign the team is lazy or overloaded.

Overdue rate benchmarks depend heavily on how strictly deadlines are set and how the team handles undated work, so your own trend over time is the most reliable comparison. A team that sets aggressive dates will run a higher rate than one that pads every estimate, without either being healthier. The bands below give a practical sense of where a team sits when measuring dated open items.

The figure worth watching is not just the level but the age of the overdue items inside it. A rate held steady by items going one day past due is very different from the same rate built on items weeks overdue. Pairing the rate with how long items have been overdue, and with cycle time, tells you whether the slippage is a minor wobble or a structural backlog.

Improving the overdue rate is about fixing the reason items slip, not clearing the backlog by brute force. The metric tree points at the weak branch, and each branch has a concrete fix.

The decomposition decides the intervention. If items are overdue because the team is overloaded, a tighter intake limit beats chasing individual items. If they are overdue because they are blocked, clearing the blocker beats reminding the owner. Treating every overdue item as a discipline problem when it is really a capacity or dependency problem wastes effort and erodes trust in the deadline.

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

1. 1

   Padding the denominator with undated items

   An item with no due date cannot be overdue. Leaving undated work in the open total inflates the denominator and quietly lowers the rate, hiding the real slippage. Scope the denominator to dated items.

2. 2

   Pushing due dates to clear the number

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

3. 3

   Reading the snapshot at convenient times

   Overdue rate is a point-in-time figure, so sampling it only when it looks good distorts the trend. Read it on a fixed cadence so the direction of travel is comparable period to period.

4. 4

   Ignoring the age of overdue items

   A rate built on items one day late is very different from the same rate built on items weeks late. The headline percentage hides how stale the backlog is, so track how long items have been overdue alongside it.

5. 5

   Treating every miss the same

   Blocked items and never-started items are both overdue but need opposite fixes. Lumping them together sends the team chasing work it cannot move. Split overdue items by reason before deciding what to do.