Action item completion rate

Action item completion rate is the percentage of committed action items that are completed by their due date over a given period. If a team had 50 action items due this month and finished 38 of them on time, the completion rate is 76 per cent. It is a measure of follow-through, the discipline that decides whether decisions made in a meeting become work that ships.

The metric matters because most organisations are far better at generating actions than completing them. Strategy sessions, retrospectives, and customer reviews all produce commitments, but those commitments only create value when they are done. A completion rate exposes the gap between what a team agreed to do and what it actually did, which is often invisible because half-finished actions quietly roll over and disappear.

Unlike a one-off count of tasks, the rate is comparable across teams and periods. A team finishing 40 of 50 actions and a team finishing 8 of 10 both run at 80 per cent, which lets you compare follow-through fairly regardless of volume. It sits close to a general completion rate but is specific to the committed actions that come out of decisions and meetings.

The calculation divides the number of action items completed on time by the total number due in the period, then multiplies by 100. The judgement sits in how you define each input, because small definitional choices change the number meaningfully. The components below are what you need to settle before the formula is reliable.

1. 1

   Action items completed on time

   Items marked done on or before their due date. Decide upfront whether an item completed late counts as completed or not. The strictest and most useful definition counts only on-time completions in the numerator.

2. 2

   Total action items due

   Every item with a due date falling inside the measurement period. This denominator must include items that slipped or were never started, otherwise the rate flatters the team by hiding the failures.

3. 3

   Ownership

   Each item needs a single accountable owner. Items with no owner or a shared owner are the ones most likely to slip, and they distort the rate unless handled consistently.

4. 4

   Measurement window

   The period over which you count, typically a sprint, month, or quarter. A consistent window is what makes the rate comparable over time, so resist the urge to change it once set.

A worked example. A leadership team leaves a quarterly review with 20 action items, all with owners and due dates. By the deadline, 14 are done on time, 3 are done late, and 3 are not started. Counting only on-time completions, the rate is (14 / 20) x 100, which is 70 per cent. If you chose to count late completions too, it would read 85 per cent. The choice is yours, but it must be consistent, because the trend over time matters more than the absolute level.

A metric tree decomposes the completion rate into the stages where an action item can fail, then traces each stage down to the specific cause. This turns a flat percentage into a diagnosis of where follow-through is breaking.

The first level splits the rate into the lifecycle of an action: whether it was clearly defined, whether it was owned, whether it was started, and whether it was finished on time. Each stage decomposes further. Clarity breaks into specific scope and a real due date. Ownership breaks into a single accountable owner and realistic capacity. Execution breaks into started on time and unblocked. When the rate falls, the tree tells you whether actions are failing because they were vague, unowned, never started, or blocked partway.

This is the gap between a dashboard and a decision. A dashboard says 70 per cent of actions got done. The tree shows that the missing 30 per cent were almost all unowned items that nobody started, which is a process problem with a clear fix, not a motivation problem.

Completion rate benchmarks depend heavily on how strictly you count late items and how disciplined the team already is, so the best comparison is your own trend over time. That said, the bands below give a practical sense of where a team sits when counting on-time completions against owned, dated actions.

The number worth watching is not just the level but which actions fall into the missing slice. A rate that drops only on cross-team actions points to a coordination problem, while a rate that drops on one owner points to capacity. The benchmark is a starting point, the decomposition is where the answer lives.

Improving the rate is about fixing the stage where actions fail, not exhorting people to try harder. The metric tree points at the weak stage, and each stage has a concrete fix.

The decomposition decides the intervention. If actions fail because they are vague, better wording at creation beats more chasing. If they fail because nobody owns them, forcing a single owner beats adding deadlines. Treating every miss as a discipline problem when it is really a clarity or ownership problem wastes effort.

KPI Tree lets you model this by connecting the completion rate to the owners and actions behind it. Every action item carries RACI ownership, so each one has a single accountable person rather than a vague team assignment. When an action stalls or a due date approaches, the metric pushes to that accountable owner rather than waiting for the next meeting to surface it. The verified impact loop then checks whether completed actions actually moved the metric they were meant to, so the team learns which commitments are worth making in the first place.

1. 1

   Counting items with no due date

   An action with no deadline cannot be on time or late. Including undated items in the denominator makes the rate meaningless. Only count owned, dated actions for a clean measure.

2. 2

   Quietly dropping slipped actions

   Removing actions that were never finished, rather than counting them as misses, inflates the rate and hides the real failure. The denominator must keep the actions that slipped.

3. 3

   Switching the late-item rule

   Counting late completions as done in one period and not the next breaks the trend. Pick one rule and hold it, because the direction of travel matters more than the absolute number.

4. 4

   Optimising the rate, not the outcome

   A team can lift the rate by committing only to trivial actions. The point is to complete the actions that matter, so pair the rate with a check on whether the completed actions actually moved the goal.

5. 5

   Ignoring who and what slips

   A headline rate hides the pattern underneath. Two teams at 70 per cent can have completely different problems, one in cross-team actions and one in a single overloaded owner. The pattern, not the average, tells you what to fix.