> 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/workspace-settings-and-administration/customize-rhythms-settings/rename-okr-status-labels.md).

# Rename OKR status labels

Rhythms uses a standard set of OKR statuses — such as On Track, Behind, and At Risk — to describe how a goal is progressing. If your team uses different language, you can rename these statuses so the labels people see match the words your organization already uses. "On Track" can become "Green," "Behind" can become "Off Pace," or whatever fits your culture.

Only the display name changes. The underlying status logic stays exactly the same, so reports, filters, and automations keep working without any reconfiguration.

This guide is for Rhythms Admins.

***

## What you can rename

You can edit the display name of any of the nine OKR statuses: Draft, Pending Approval, Not Started, In Progress, On Track, Behind, At Risk, Closed, and Postponed. Renaming is purely cosmetic — it changes the label shown across the platform, not how the status behaves. Because the logic is unchanged:

* Reports and program-health views continue to group goals by the same underlying statuses.
* Filters and views that reference a status keep returning the same goals.
* Automations and rollups that depend on status continue to run unchanged.

***

## Renaming a status

1. Go to **Settings › OKRs › Model customization**.
2. Scroll to the **Status Labels** section. Each row shows the status, its **Default Label**, and a **Custom Label** field.
3. Click the **Custom Label** field for the status you want to rename and type the new name.
4. Click outside the field. The label saves immediately and the new name appears across the platform — on goals, in the status picker, in reports, and in views.

Your changes apply to everyone in the workspace.

***

## Examples

| Default status | Example rename |
| -------------- | -------------- |
| On Track       | Green          |
| Behind         | Off Pace       |
| At Risk        | Watch          |
| Not Started    | Not Begun      |

These are only examples — you can use any label that fits your team.

***

## Status labels vs. OKR terminology

Renaming statuses is different from renaming the OKR object terms. Use status labels to change how *progress states* are named (On Track, Behind, and so on). Use terminology customization to change what the *objects themselves* are called (OKRs, objectives, key results, initiatives). Both live on the Model customization page and can be used together; see [Model customization: alignment, contribution and terminology](/workspace-settings-and-administration/customize-rhythms-settings/model-customization-alignment-contribution-and-terminology.md).

***

## Frequently Asked Questions

**Does renaming a status change how it works?** No. Only the display name changes. The status logic, reports, filters, and automations behave exactly as before.

**Will my existing reports and views break if I rename a status?** No. They reference the underlying status, not its label, so they continue to work and simply show the new name.

**Who can rename statuses?** Rhythms Admins, from Settings › OKRs › Model customization.

**Can I change a label back to the default?** Yes. Clear the Custom Label field (or type the default label again) and click outside it. An empty custom label falls back to the default.

**Do renamed statuses apply to everyone?** Yes. Status label changes apply across the entire workspace, including Slack and Teams notifications.

***

## Related Articles

* [Model customization: alignment, contribution and terminology](/workspace-settings-and-administration/customize-rhythms-settings/model-customization-alignment-contribution-and-terminology.md)
* [How parent OKR progress and status roll up](/goals-and-okrs/managing-and-tracking-goals/how-parent-okr-progress-and-status-roll-up.md)
* [Managing and Updating OKRs in Rhythms](/goals-and-okrs/managing-and-tracking-goals/edit-and-update-okrs.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 dynamically 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/workspace-settings-and-administration/customize-rhythms-settings/rename-okr-status-labels.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 `build a script that syncs our docs to a CMS` 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.