Task completion rate

Task completion rate is the percentage of assigned or scheduled tasks that a person or team actually completes within a set period. If 40 tasks are due this week and 34 get done, the completion rate is 85 percent. It is one of the cleanest signals of whether work is reliably finished, and whether the commitments being made are realistic in the first place.

The metric matters because activity and completion are not the same thing. A team can look busy, with tasks started and meetings held, while the actual rate of finishing slips. Completion rate cuts through that. A high rate held steady means the team plans well and delivers. A low or falling rate means tasks are being assigned that cannot be finished in the time available, or that something is consistently getting in the way.

A completion rate is only honest if the denominator is honest. If tasks are quietly dropped, pushed to next period, or never given a due date, the rate flatters reality. The cleanest version counts every task that was due in the period, whether it was finished, missed, or rolled forward. Read it alongside cycle time, because a high completion rate achieved by stretching every deadline is not the same as one achieved by finishing on time.

The calculation divides tasks completed by tasks assigned in the same period, then multiplies by 100 for a percentage. The hard part is defining the denominator. Decide upfront whether assigned means tasks created in the period, tasks due in the period, or tasks open at any point during it, and apply that definition consistently.

For example, a team with 50 tasks due this month that completes 45 has a 90 percent completion rate. If five of those were finished a week late, the rate still reads 90 percent, which is why on-time completion is often tracked as a stricter companion measure.

1. 1

   Tasks completed

   Count tasks marked done within the period. Decide whether a task closed late still counts as completed.

2. 2

   Tasks assigned

   Count tasks due or scheduled in the period, including the ones that were missed or deferred.

3. 3

   Completion rate

   Divide completed by assigned and multiply by 100. This is the headline percentage.

4. 4

   On-time rate

   Optionally narrow completed to tasks finished by their due date, for a stricter read on reliability.

A completion rate that drops can be caused by overcommitment, by blockers, by unclear ownership, or by tasks that were never properly scoped. The single percentage tells you something is wrong but not where to look. A metric tree decomposes the rate into the drivers beneath it, so the dip can be traced to the branch that actually moved.

KPI Tree lets you connect each driver to the team and the action that influences it. When each person can see their specific node in the tree and how it connects to the headline number, accountability becomes clear and interventions become precise. With RACI ownership on every metric, the person accountable for capacity planning sees their branch and the person accountable for unblocking work sees theirs. When the rate moves, the change is pushed to the accountable owner, and the verified impact loop checks whether the fix actually lifted the number back up.

A healthy completion rate sits high but not at 100 percent, because a team that finishes every single task is almost certainly under-committing. The right range depends on how rigid the deadlines are. Operational and support work needs a higher rate, because missed tasks have immediate consequences. Discovery and planning work tolerates a lower rate, because some tasks are meant to be dropped once they prove unnecessary.

The fastest route to a better completion rate is usually committing to less, not working faster. A team that assigns only what it can realistically finish will complete more of it and build trust in its own estimates. Beyond planning, the biggest gains come from removing the friction that stalls work that has already started.

1. 1

   Excluding missed tasks from the denominator

   Counting only completed and deferred tasks inflates the rate. Include everything that was due to keep the metric honest.

2. 2

   Chasing 100 percent

   A perfect rate signals under-committing, not excellence. A healthy team plans enough to occasionally fall short.

3. 3

   Ignoring late completion

   A task finished a week late still counts as done in the headline rate. Track on-time completion as a stricter companion.

4. 4

   Comparing teams with different definitions

   One team counts tasks due, another counts tasks touched. Fix a single definition before comparing rates across teams.