---
title: "Cycle completion"
canonical_url: "https://docs.getdx.com/reports/cycle-completion/"
md_url: "https://docs.getdx.com/reports/cycle-completion.md"
last_updated: "2026-06-08"
---

# Cycle completion
The **Cycle completion** report measures the percentage of total cycle work that was finished, including both planned and unplanned items. Use this metric to evaluate overall throughput and closure rate across your cycles.

> Note: Cycle completion is only available when Linear is connected to DX.

![Cycle completion report in DX](https://docs.getdx.com/assets/images/reports/cycle-completion.png)

## When to use cycle completion

Cycle completion answers the question: _How much of everything in the cycle did we finish?_

This report helps teams:

- **Measure overall throughput** — Understand how much total work the team closed out during the cycle, regardless of when it was added.
- **Track closure rate** — Identify whether work is accumulating or being consistently completed.
- **Account for scope changes** — Get a realistic view of cycle execution that reflects mid-cycle adjustments.

## How completion percentage is calculated

The completion percentage is calculated as:

**Completed work ÷ Total work**

Where:

- **Completed work** is the story point/issue count for all issues marked complete during the cycle
- **Total work** is the story point/issue count for all issues in the cycle, whether planned or unplanned

This metric captures the full picture of cycle execution, including any work added after the cycle started. Cycle completion can be calculated based on either story points or issue counts.

## Understanding planned vs. unplanned work

| Term                 | Definition                                                                                       |
| -------------------- | ------------------------------------------------------------------------------------------------ |
| **Planned points**   | Story points for issues that existed in the cycle at the cycle start time                        |
| **Unplanned points** | Story points for issues added after the cycle started                                            |
| **Completed points** | Story points for all issues marked complete during the cycle, regardless of when they were added |

## How cycle completion differs from cycle predictability

Unlike [cycle predictability](https://docs.getdx.com/reports/cycle-predictability/), cycle completion measures against the final scope, including work added mid-cycle.

For example, if you add 10 points mid-cycle but do not finish them:

- Your **Completion** score drops (because the total scope increased).
- Your **Predictability** score stays the same (because it ignores items added after the cycle started).

Use cycle completion to see if scope creep is preventing you from closing out cycles, and cycle predictability to see if you are delivering the volume you originally promised.
---

## Sitemap

[Overview of all docs pages](/llms.txt)