> 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/set-a-check-in-rhythm-for-one-goal.md).

# Set a check-in rhythm for one goal

Every OKR follows a check-in rhythm: the workspace rhythm, or its team's rhythm if the team has one. When a single OKR needs a different cadence, anyone who can manage that OKR can give it its own rhythm from the **Check-in Rhythm** control on the goal, or by asking Rhythms in chat. The custom rhythm applies to that goal only and can be reverted at any time.

## How a goal check-in rhythm works

A goal check-in rhythm replaces the inherited rhythm for one objective, key result, or initiative. The goal gets its own check-in cycles, its own **Check-in Status** (Due, Overdue, Complete, and so on), and its own reminders, sent to the goal's delegates if it has any and otherwise to its owners. The workspace rhythm, the team rhythm, and every other goal are unaffected. Remove the custom rhythm and the goal goes back to following whatever it inherited. For how rhythms, windows, and reminders work in general, see [Set a workspace check-in rhythm](/workspace-settings-and-administration/customize-rhythms-settings/set-a-workspace-check-in-rhythm.md).

## Who can set a goal check-in rhythm

Setting, changing, or removing a goal's check-in rhythm requires **manage** permission on that goal: by default the OKR owners and their managers, plus Rhythms Admins. Delegates can check in and edit the goal but cannot change its check-in rhythm. Everyone who can see the goal can open the Check-in Rhythm control to read the current rhythm. Manage permission is configured per OKR level in **Settings › OKRs › Permissions**; see [Rhythms OKR Roles and Permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md).

## Set a check-in rhythm for a goal

1. Open the goal. In its properties, find the **Check-in Rhythm** control. Its value shows the frequency the goal currently follows, for example "Every week".
2. Click it. The summary shows the inherited rhythm (for example "Every week · Monday · 3-day window · PST") and where it comes from: "Following the organization check-in rhythm" or "Following the Product team check-in rhythm".
3. Click **Set a custom rhythm for this objective** (the label uses the goal's type).
4. Choose the **Cycle frequency** (Every week, Every 2 weeks, Every month, or Every quarter), the **Deadline** weekday or monthly position, how many days before the deadline the **window opens**, and the timezone the deadline is measured in.
5. Tick the reminders to send: **When window opens**, **At midpoint**, **On deadline date**. Reminders go out around 9 AM in the chosen timezone.
6. If the goal's progress comes from a rollup or a connector, decide whether a manual check-in is **Required** or **Not required** for the goal to count as complete.
7. Close the control. The rhythm is saved when the control closes, and a "Custom check-in rhythm created" message confirms it.

The goal's Check-in Rhythm value now shows the custom frequency, and its check-in status is recalculated against the new cycles.

## Change or remove a goal check-in rhythm

To change the rhythm, open the **Check-in Rhythm** control again, adjust the settings, and close it; changes are saved on close. To remove it, click **Revert to organization rhythm** (or **Revert to Product team rhythm**, naming the team) at the bottom of the control and close it. The custom cycles are deleted and the goal follows the inherited rhythm again, exactly as if the override had never existed. Both actions are recorded in the goal's activity.

## Set a goal check-in rhythm from chat

You can set, change, or revert a goal's check-in rhythm by asking Rhythms in chat, for example "Set a custom check-in rhythm for the Expand into EMEA objective: every 2 weeks, due Friday, window opens 3 days before" or "Reset the check-in rhythm on KR-42 to the team rhythm". The same manage permission applies.

## Goal rhythm compared with the workspace rhythm

|             | Workspace or team check-in rhythm                            | Goal check-in rhythm                         |
| ----------- | ------------------------------------------------------------ | -------------------------------------------- |
| Scope       | Every governed OKR without an override                       | One objective, key result, or initiative     |
| Who sets it | Rhythms Admins; Team Owners for their team                   | Anyone with manage permission on the goal    |
| Set from    | Settings › OKRs › Check-ins; the team's Check-in Rhythm page | The goal's Check-in Rhythm control, or chat  |
| When to use | A shared cadence for the organization or a team              | A goal that genuinely needs its own schedule |

## Frequently asked questions

**Does a goal check-in rhythm change the workspace or team rhythm?** No. It applies only to the goal you edit.

**Who is reminded when a goal rhythm comes due?** The goal's delegates if it has any, otherwise its owners, on every notification channel enabled for the workspace and in the Rhythms inbox.

**Can a delegate set the rhythm?** No. Delegates can check in and edit, but the check-in rhythm requires manage permission.

**Can I set a rhythm on key results and initiatives?** Yes. Any goal type can have its own rhythm.

**What happens to compliance history when I revert?** Reverting deletes the goal's custom cycles, including their compliance records; the goal is then evaluated against the inherited rhythm's cycles. If you need the history, export or note it before reverting.

## Related articles

* [Set a workspace check-in rhythm](/workspace-settings-and-administration/customize-rhythms-settings/set-a-workspace-check-in-rhythm.md)
* [Effective Check-ins to Track OKR Progress in Rhythms](/goals-and-okrs/managing-and-tracking-goals/write-and-submit-check-ins.md)
* [Assign a delegate to an OKR](/goals-and-okrs/creating-goals/assign-delegates-to-an-okr.md)
* [Rhythms OKR Roles and Permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.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/set-a-check-in-rhythm-for-one-goal.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.