KPI Tree

Metric Definition

Sub-task progress

Subitem completion ratio = (Completed subitems / Total subitems) x 100
Completed subitemsSub-tasks marked done under the parent item
Total subitemsAll sub-tasks defined under the parent item

Track from

Metric GlossaryOperations Metrics

Subitem completion ratio

Subitem completion ratio is the share of sub-tasks beneath a parent item that have been finished, expressed as a percentage of the total. It shows real progress on work that a single parent status often hides. A parent item can sit at "in progress" for weeks while the ratio tells you whether it is nearly done or barely started.

6 min read

Generate AI summary

What is subitem completion ratio?

Subitem completion ratio is the share of sub-tasks beneath a parent item that have been finished, expressed as a percentage of the total. If a parent item breaks into 10 subitems and 7 are done, the ratio is 70 percent. It gives you a progress reading at a finer grain than the parent status, which usually reduces a whole body of work to a single label like "in progress".

This matters because parent status lies by omission. An item marked "in progress" tells you almost nothing about how much is left. The subitem completion ratio replaces that guesswork with a number, so a project lead can scan a board and see which parent items are genuinely close to done and which are stalled at the start. Rolled up across many parents, it becomes a clean signal of how a project, a sprint, or an onboarding flow is actually progressing.

The ratio is most honest when subitems are roughly comparable in size. If one subitem represents two days of work and another represents two minutes, a simple count overstates progress when only the small ones are finished. Where subitem effort varies a lot, weight the count by estimated effort so the ratio reflects real completion rather than items ticked off.

Definition note

A subitem completion ratio measures whether sub-tasks are marked done, not whether the parent goal is met. Closing every subitem does not guarantee the outcome was achieved if the breakdown missed something. Treat the ratio as a progress signal, and keep a separate check on whether the parent item actually delivered what it set out to.

How to calculate subitem completion ratio

The base calculation is a simple count: completed subitems divided by total subitems, expressed as a percentage. For a single parent with 12 subitems where 9 are done, that is 9 divided by 12, which is 75 percent. To read progress across a whole project, roll the ratio up by summing completed subitems and total subitems across every parent, rather than averaging the per-parent percentages, which would let a parent with one subitem count as much as a parent with fifty.

Where subitem effort varies, switch from a plain count to an effort-weighted version. Replace the counts with summed estimates: completed subitem effort divided by total subitem effort. A parent with three small subitems done and one large one outstanding might read 75 percent by count but only 40 percent by effort, and the effort figure is the one that tells you how much work actually remains.

  1. 1

    Define the parent scope

    Confirm which parent items are in scope and that each has its subitems fully listed, not half broken down.

  2. 2

    Count completed subitems

    Tally the subitems marked done. Decide upfront whether a "blocked" or "in review" subitem counts as done, and apply it consistently.

  3. 3

    Count total subitems

    Tally every subitem under the parents in scope, including ones not yet started.

  4. 4

    Divide and roll up

    Divide completed by total and multiply by 100. To report across a project, sum the numerators and denominators before dividing.

Subitem completion ratio in a metric tree

A low subitem completion ratio is a symptom with several possible causes, and the single number does not say which. A metric tree decomposes the headline ratio into the drivers that move it, so a team can see whether work is blocked, poorly scoped, unevenly distributed, or simply not being kept up to date.

The tree below splits the ratio into the forces that shape it: how clearly parents are broken down, how many subitems are blocked, how work is spread across owners, and how reliably the board reflects reality. In KPI Tree you connect each branch to the person who can move it, with RACI ownership so a blocked-subitem branch sits with the team lead who can clear the blocker. When the ratio stalls, the change is pushed to the accountable owner rather than waiting to be noticed at the next standup.

Metric tree insight

When the ratio stalls, the tree separates a real bottleneck from a reporting one. If blocked subitems are climbing, the work is genuinely stuck and needs a blocker cleared. If the stale status rate is high instead, the work may be moving while the board has fallen behind, which is a hygiene fix, not a delivery problem.

Subitem completion ratio benchmarks

There is no universal target for subitem completion ratio, because the right reading depends entirely on where the parent items sit in their lifecycle. A useful benchmark compares the ratio against expected progress for the stage of work. Early in a sprint a low ratio is normal, while late in a sprint the same number is a warning. The bands below describe how to read the ratio relative to where the work should be, rather than as a fixed standard.

ReadingRatio versus expectedWhat it signals
On trackAt or above the stage targetParents progressing in line with the plan
Slightly behind10 to 20 percent under targetMinor slippage, recoverable within the cycle
At risk20 to 40 percent under targetLikely to miss the parent deadline without intervention
StalledFlat across several check-insWork is blocked or the board is not being updated

How to improve subitem completion ratio

Improving the ratio is mostly about removing what holds subitems back and keeping the board honest, not about pushing people to tick boxes faster. The biggest gains come from clearing blockers quickly, breaking parents down into evenly sized pieces, and making sure status reflects reality. The cards below cover the highest-leverage moves.

Clear blockers fast

Blocked subitems are the most common reason a ratio stops climbing. Surface them daily and put a named owner on each, so nothing sits stuck without someone driving it.

Break parents down evenly

Subitems of wildly different sizes distort the ratio. Aim for comparable, small pieces so each completion moves the number by a meaningful and honest amount.

Balance the workload

Check subitems per owner. When one person holds most of the outstanding work, the ratio stalls behind a single queue rather than progressing in parallel.

Keep the board current

A ratio is only as good as the data behind it. Make updating subitem status a routine part of the work, so the number reflects reality rather than yesterday.

Related metrics

Cycle time

Process speed

Operations Metrics
Jira

Metric Definition

Cycle Time = Process End Time − Process Start Time

Cycle time measures the total elapsed time from the start to the end of a process. It is a fundamental operations metric used in manufacturing, software development, service delivery, and any context where the speed of a process directly affects throughput, cost, and customer satisfaction.

View metric

Sprint velocity

Agile planning metric

Operations Metrics
Jira

Metric Definition

Sprint Velocity = Sum of Story Points Completed in a Sprint

Sprint velocity measures the amount of work a team completes during a sprint, typically expressed in story points, ideal days, or another unit of estimation. It is a planning tool that helps agile teams forecast how much work they can commit to in future sprints based on their historical completion rate. Velocity is one of the most widely used and most frequently misunderstood metrics in agile software development.

View metric

Deployment frequency

DORA metric

Operations Metrics
GitHub

Metric Definition

Deployment Frequency = Number of Production Deployments / Time Period

Deployment frequency measures how often an organisation successfully releases code to production. It is one of the four DORA (DevOps Research and Assessment) metrics that predict software delivery performance and organisational outcomes. Teams that deploy more frequently deliver value to users faster, reduce the risk of each individual release, and create tighter feedback loops between development and production.

View metric

How to build a metric tree

Metric Definition

Build a metric tree so subitem completion ratio sits beneath the operational outcomes it actually drives, making sub-task progress easy to act on.

View metric

Metric trees for operations teams

Metric Definition

See how operations teams structure delivery metrics like subitem completion ratio to keep work flowing and surface where sub-tasks stall.

View metric

Build subitem completion ratio as a tree with owners on every branch

In KPI Tree you decompose subitem completion ratio into breakdown quality, blocked work, and board hygiene, then assign a RACI owner to each branch. When the ratio stalls, the change reaches the person who can clear the blocker, and the verified impact loop checks whether the intervention actually moved the work forward.

Experience That Matters

Built by a team that's been in your shoes

Our team brings deep experience from leading Data, Growth and People teams at some of the fastest growing scaleups in Europe through to IPO and beyond. We've faced the same challenges you're facing now.

Checkout.com
Planet
UK Government
Travelex
BT
Sainsbury's
Goldman Sachs
Dojo
Redpin
Farfetch
Just Eat for Business