> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/goals-and-okrs/creating-goals/stretch-and-committed-targets.md).

# Stretch and committed targets

{% hint style="info" %}
Committed and stretch targets are in Early Access. An admin can turn them on in **Settings** › **Early Access**.
{% endhint %}

For some goals, leaders set two targets on the same metric: one they commit to and a stretch target the team aims for. A company might commit to $4M in ARR with its board while aiming internally for $5M. An engineering team might commit to 99.9% uptime in customer contracts while working toward 99.99%.

The two targets carry different weight. A commitment has to be met, because budgets, hiring plans and customer promises depend on it. A stretch target is meant to be hard, so falling short of it can still be a strong result.

With committed and stretch targets, you can record both on a single goal, for example "Reach $5M ARR, with $4M committed." You can also set just one of them. When you review results, you'll see which commitments were met and how far each team got toward its stretch goals.

Add a target type where the difference between a commitment and an aspiration matters. Target types are available on any Objective, Key Result or Initiative measured by a number. Goals tracked by percent complete don't use them.

## When to use committed and stretch targets

### Use Committed when

* Other teams, leadership or customers depend on the number, such as a revenue plan, a budget limit or a contractual SLA.
* Falling short would mean changing plans, not just explaining the miss.
* The work is mostly within the team's control and well understood.

### Use Stretch when

* You want the team to aim higher than is safe. On a **Reach target** metric, reaching about 70% of the way is a good result. **Stay above**, **Stay below** and **Stay between** metrics are pass/fail: each check-in either meets the target (100%) or doesn't (0%).
* The outcome depends on bets that may not pay off, such as a new market, a new product or an experiment.

### Use both when

* Leadership needs a number it can plan around, and you want the team to aim beyond it.
* You'd otherwise create two near-duplicate Key Results for the same metric.
* You want to review results two ways: "Did we keep our promise?" and "How far did we get toward the ambition?"

Leave the target type off when the difference doesn't matter, such as routine operational goals that no one outside the team depends on.

### Tips for setting the numbers

* Set the committed number at a level the team is confident it can reach with its current plans and capacity. Plan capacity for commitments first, then put the remaining effort toward stretch targets.
* Set the stretch number at a level that would be a great result if most bets land. For **Reach target** metrics, if your team hits 100% of its stretch targets every period, they're probably set too low.
* Keep a meaningful gap between the two numbers. If they're almost the same, use a single committed target.
* Agree on target types during planning, not at the end of the period, so a target is never relabeled to explain away a miss.

## Turn it on

An admin needs to turn this on for the whole workspace, in two steps.

1. Go to **Settings** › **Early Access** and turn on committed and stretch targets.
2. Go to **Settings** › **OKRs** › **Model customization**.
3. Under **Targets**, turn on **Enable committed targets**.

Once it's on, any new goal created will have an option to mark its target as Stretch or Committed.

## What happens to your existing targets

Nothing changes until you choose. Targets set before your admin turned on target types keep their numbers, check-ins, progress, status and score exactly as they were. Rhythms doesn't assign a type automatically. Existing targets keep the label **Target** until someone picks a type, and their progress and score are calculated the same way as when target types are off.

### Label an existing target

You can give an existing target a type at any time.

1. Open the goal in Quick View and click its target.
2. Click **Target** beside the number. A menu opens with **Stretch** and **Committed**.
3. Choose one, then click **Save changes**.

Once the target has a type, **+ Add committed target** (or **+ Add stretch target**) appears so you can set a second number. If you leave a target unlabeled, it saves exactly as before.

## Choosing a target type

Open a goal's target. Pick a **Target rule** (**Reach target**, **Stay above**, **Stay below** or **Stay between**), then enter your number. A pill beside the number shows its type:

* **Stretch**: an ambitious number you're aiming for.
* **Committed**: a number you've promised to hit.

To change the type, click the pill and choose the other one.

### Set both targets

1. Click **+ Add committed target** (or **+ Add stretch target** if your current target is Committed). A second row appears.
2. Enter the second number.
3. Click **Save changes**.

When both targets are set, the pills are labels only. To change which number is which, remove one target and set the type on the one that's left.

To remove a target, click **Remove** on its row. The other number becomes the goal's only target, and progress is measured against it.

For **Reach target**, **Stay above** and **Stay below** metrics, Rhythms checks that the committed number is easier to reach than the stretch target:

* **Reach target**: the committed number must sit between the start value and the stretch target.
* **Stay above**: the committed number must be below the stretch target.
* **Stay below**: the committed number must be above the stretch target.

### Start value

For a **Reach target** metric, click **+ Start value** to set where the metric starts. If you remove it, the start resets to 0.

### Stay between

Each target is a range, so enter a **Min** and a **Max**. You can't save until every bound has a value.

Click **Cancel**, or click outside the editor, to discard your changes.

For metric types and how to set start and target values, see [Metric types for Key Results](https://help.rhythms.ai/goals-and-okrs/creating-goals/metric-types-for-key-results.md).

## Target types on new goals

New Key Results start as **Stretch**. Check the type when you create one, and change it to **Committed** if the number is a promise. Objectives and Initiatives measured by a number start with no type, and you can set one in the target editor. You can change the type later.

## Creating goals with AI

When you create a goal with AI, Rhythms reads the type from your wording. Words like "committed", "guaranteed" or "must-hit" make it **Committed**. Words like "stretch", "ambitious" or "aspirational" make it **Stretch**.

If you give two numbers, such as "Reach $5M ARR, committed $4M", Rhythms sets $5M as the stretch target and $4M as the committed target. If your wording doesn't mention a type, the goal starts as Stretch. You can also ask Rhythms in chat to set or change the type for you.

## Which number counts as the target

| You have                       | The target is       |
| ------------------------------ | ------------------- |
| Only committed or only stretch | That number.        |
| Both                           | The stretch number. |

Everything is measured against the target: progress, status, expected progress, score, and rollups to parent goals. The committed number never changes those. It's shown beside the target so you can see whether you've met your promise.

{% hint style="info" %}
**Example:** your stretch target is 85%, your committed target is 80%, and you check in at 82%. Progress and status are measured against 85%. You can see you're past the committed 80%, but that doesn't change the progress bar or the status.
{% endhint %}

## Where you'll see it

* **Quick View**: the target appears with its type, and the committed number sits beside it. A target with no type is labelled **Target**. In the target editor, that label opens a menu where you can choose a type.
* **Progress graph**: stretch targets are dashed lines and committed targets are dotted. The chart key names each line.
* **Check-ins**: the targets show under the value field, for example *85% Stretch · 80% Committed*.
* **Progress bars**: the value is shown with both targets, for example *82% / 85% Stretch · 80% Committed*.
* **Activity**: changes to the target type and committed number show up in the goal's history.

## Turning it off

If an admin turns the setting off, target types and committed numbers are hidden, and nobody can add new ones. Nothing is deleted. Progress doesn't change, because it never depended on the labels. If you turn it back on, everything reappears as it was.

If a target has a committed number and you change the target while the setting is off, you may see an error. Turn the setting back on, or remove the committed number, to save the change.

## Frequently asked questions

**Can I use target types with Stay above, Stay below and Stay between metrics?** Yes. For Stay between, the committed number is a range with its own minimum and maximum.

**What happens if I switch a goal to percent complete?** Choose **Percent complete** from the **Target rule** menu. The target becomes 100% complete, and the goal's target type and committed number are removed. Your current progress and status carry over, and you can edit them before you save. Earlier check-ins stay in Activity.

**Can I find goals that have a committed target?** Ask Rhythms in chat, for example "show my Key Results with a Committed target or a committed number". You can also find targets that still need a type, for example "show my Key Results with no target type".

## Related articles

* [Metric types for Key Results](https://help.rhythms.ai/goals-and-okrs/creating-goals/metric-types-for-key-results.md)
* [Create OKRs and initiatives](https://help.rhythms.ai/goals-and-okrs/creating-goals/create-okrs-and-initiatives.md)
* [Draft OKRs with AI](https://help.rhythms.ai/goals-and-okrs/creating-goals/draft-okrs-with-ai.md)
* [Import OKRs from a spreadsheet](https://help.rhythms.ai/goals-and-okrs/creating-goals/import-okrs-from-a-spreadsheet.md)
* [Write and submit check-ins](https://help.rhythms.ai/goals-and-okrs/managing-and-tracking-goals/write-and-submit-check-ins.md)
* [Close and score an OKR](https://help.rhythms.ai/goals-and-okrs/managing-and-tracking-goals/close-and-score-an-okr.md)
* [Filtering and grouping OKRs in views](https://help.rhythms.ai/goals-and-okrs/monitoring-and-reports/filtering-and-grouping-okrs-in-views.md)
* [Model customization: alignment, contribution and terminology](https://help.rhythms.ai/workspace-settings-and-administration/customize-rhythms-settings/model-customization-alignment-contribution-and-terminology.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/goals-and-okrs/creating-goals/stretch-and-committed-targets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
