> 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/create-okrs-and-initiatives.md).

# Create OKRs and initiatives

You create Objectives, Key Results and Initiatives from the **Create OKRs** button at the top right of any OKR view. It offers two paths: **Create with Rhythms**, which opens a chat that drafts a full set of OKRs with you, and **Create manually**, which opens a form with AI suggestions on every field. Key Results and Initiatives can also be added to an existing Objective from its **⋯** menu. Everything you create gets a short goal ID such as `OBJ-001`.

Not sure what a good Objective or Key Result looks like? Read [Introduction to OKRs](/goals-and-okrs/okr-foundations-and-structure/introduction-to-okrs.md) first.

## Where to start

* **Create OKRs** (top right of an OKR view) → **Create with Rhythms** or **Create manually**. On a team page the button reads **New Objective**; on an Initiatives view it reads **New Initiative**.
* **⋯** on an existing goal → **Add key result**, **Add initiative** or **Add child objective** → **Create manually** or **Generate** (AI).
* **Chat**, from anywhere: "Create Q1 OKRs for the Sales team."

You need a Member or Admin licence to create goals; Guests cannot. Your Rhythms Admin decides who can create organization-level and team-level OKRs (by default: Admins for organization-level, Team Owners for team-level). Anyone can create OKRs for themselves.

## Create OKRs with Rhythms (chat)

Chat is the fastest way to build a coherent set of OKRs, because Rhythms knows your teams, time periods and existing goals and drafts from that context.

1. Click **Create OKRs** → **Create with Rhythms**. Rhythms asks which team, which time period and what priorities you want to address.
2. Answer in plain language. You can attach a strategy document, board deck or planning memo (PDF, Word, PowerPoint, spreadsheet or text) and say "Create OKRs based on this document."
3. Refine through conversation: "Make the revenue target $1.8M", "Change the owner to Sarah", "Remove the Initiative about conferences", "Suggest different Key Results for this Objective."
4. When Rhythms proposes goals, they appear as editable cards in the chat. Change the type, title, owner, team, time period, metric or alignment on any card, remove cards you don't want, or click **Add another**.
5. Click **Publish OKRs** to create them, or **Draft OKRs** to save them as drafts that only you, the owners and their teams can see until they are published.

![Chat with Rhythms asking which team, time period and priorities to plan for](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-35bb22261e0cc767490c3305f4e4fb873b86c6d4%2F1c0e7a4c-fa06-4bf2-ac28-5880b6788fb6-Screenshot_2025-11-20_at_12_06_44_E2_80_AFPM.png?alt=media) ![Refining a proposed OKR set in chat by changing a target and removing Key Results](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-2be1e5d4036c130c261181fe31a0ac526afe0ab2%2F37702431-d7ff-4e9f-9670-46fafc2a6cdb-Screenshot_2025-11-20_at_12_38_51_E2_80_AFPM.png?alt=media) ![Generated OKR drafts listed in a table marked "Visible only to you"](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-c204ca1a8b752d942696efa0db816b895b0ddb84%2F1d50bbcf-8916-4508-b7a1-fe126c268c42-Screenshot_2025-11-20_at_12_47_17_E2_80_AFPM.png?alt=media)

If your workspace uses the [approval workflow](/goals-and-okrs/managing-and-tracking-goals/okr-approval-workflow.md), **Draft** is the primary action and published goals go through approval.

## Create an Objective manually (form)

1. Click **Create OKRs** → **Create manually**. The **Create New Objective** panel opens.
2. Type a title. Click **Suggest** for AI proposals based on your team and time period, or **Improve** to have Rhythms rewrite what you typed. Click **Use** on a suggestion to take it.
3. Set the attributes shown as pills under the title: **Time period**, **Team**, **Owner** (defaults to you), and optionally **Delegate** and **Labels**. Click **More** for **Limit visibility**.
4. Under **Aligned To**, pick the parent. The picker has **Suggested** (AI recommendations), your team, and **Company** tabs, plus an **Align to…** search.
5. In the Key Results section, click **Suggest** to have Rhythms propose Key Results, or add your own.
6. Click **Create**. The arrow next to it offers **Create Objective and add Key Result**, **… and add Initiative**, **… and add another Objective** or **… and add child Objective**, so you can keep building without leaving the form.

![Create New Objective form with Improve button and suggestions from Rhythms](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-04169ec2cd255029d9883fce720c0670368a5315%2F7c1e68f2-185d-4414-8b79-fbf8ece353ff-Screenshot-2B2025-11-20-2Bat-2B1_12_49-E2-80-AFPM.png?alt=media) ![Aligned To picker with Suggested and Company tabs](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-928d3e9774caa198badc19360f59800539c6ea3a%2Ff9de1589-fa1e-4e88-bf77-d45d7773bf69-Screenshot_2025-11-20_at_1_17_08_E2_80_AFPM.png?alt=media) ![Create button menu: Create Objective and add Key Result, Initiative, another Objective or child Objective](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-d93630f23dca6b2ecf8d29430657eb2c396517e0%2Fb538d1b2-5106-41c8-b3bc-d3d95ed86a7f-Screenshot_2025-11-20_at_4_00_28_E2_80_AFPM.png?alt=media)

## Add Key Results and Initiatives to an existing Objective

1. Find the Objective in a list, click **⋯**, then **Add key result** (or **Add initiative**, **Add child objective**) → **Create manually**. Choose **Generate** instead to have Rhythms draft them in chat; see [Draft OKRs with AI](/goals-and-okrs/creating-goals/draft-okrs-with-ai.md).
2. Type the Key Result title. Rhythms reads numbers in the title and pre-fills the metric: "Increase revenue from $1M to $1.5M" becomes a dollar metric with start 1,000,000 and target 1,500,000. Click the **Set target** pill to adjust the metric name, start, target, unit and type. The four metric types are **Reach to**, **Stay above**, **Stay below** and **Stay between**; see [Metric types for Key Results](/goals-and-okrs/creating-goals/metric-types-for-key-results.md).
3. Owner and time period default to the parent's; change them if needed.
4. Click **Create**, or use the arrow to create and add another.

Goals created this way inherit the parent's visibility list, so a child of a Limited Objective starts Limited to the same people. Whether a child Objective, Key Result or Initiative contributes to the parent's progress defaults from your workspace's [OKR model](/workspace-settings-and-administration/customize-rhythms-settings/model-customization-alignment-contribution-and-terminology.md); while creating the child you can toggle **Contribute to parent** under **More**, and afterwards you adjust it with **Manage contribution** in the parent's **⋯** menu. How contributions roll up is explained in [Understanding OKR Automatic Rollup](/goals-and-okrs/managing-and-tracking-goals/how-parent-okr-progress-and-status-roll-up.md).

## Short goal IDs

Every published goal gets a short ID in the form `PREFIX-NUMBER`: `OBJ-001` for Objectives, `KR-042` for Key Results and `INIT-007` for Initiatives by default. A Rhythms Admin can change the prefixes (2 to 6 letters, unique per type) alongside the type names in Settings under OKR model customization; see [Model customization: alignment, contribution and terminology](/workspace-settings-and-administration/customize-rhythms-settings/model-customization-alignment-contribution-and-terminology.md). Numbers count up per prefix and are never reused, even after a goal is deleted.

The short ID appears next to the goal title in the header. Use **⋯ → Copy Short ID** or **Copy link** (the link uses the short ID), type it into search, or refer to it in chat: "What's the status of KR-042?". Converting a goal to another type gives it a new ID with the new prefix; the old ID keeps opening the goal.

## Check what you created

* The new goals appear in the OKR view for their team and time period; drafts show with a Draft status until you publish them.
* Open the parent and confirm the children are listed under Key Results, Initiatives or Child Objectives.
* Owners and teams are correct, and each Key Result has a start and target value.

To change anything afterwards, see [Edit and update OKRs](/goals-and-okrs/managing-and-tracking-goals/edit-and-update-okrs.md). To record progress, see [Write and submit check-ins](/goals-and-okrs/managing-and-tracking-goals/write-and-submit-check-ins.md).

## Frequently asked questions

**Should I use chat or the form?** Use chat when you are planning a period and want help thinking through strategy or want a whole set at once; it can also read your planning documents. Use the form when you already know exactly what to enter or want control over every field. You can mix both, for example draft in chat and add Key Results from the form later.

**What is the difference between progress-based and metric-based tracking?** Progress-based goals track a percentage from 0 to 100, which Objectives and Initiatives use by default. Metric-based goals track a real value (revenue, users, hours) and Rhythms calculates the percentage; Key Results use this by default. To switch a Key Result to a percentage, open its metric pill and click **Change to progress based**. To give a progress-based goal a real metric, click its progress pill (labelled **Set target** when no metric is defined) and fill in the metric.

**Where do drafts go?** Drafts stay in your OKR views with a Draft status and are visible only to you, the owners and their teams. Publish them from the goal's **⋯** menu (**Publish**, or **Request Approval** when the approval workflow is on).

**Can I create OKRs for several teams at once?** Yes. In chat, name the teams and Rhythms proposes a set per team, each card carrying its own owner and team. Chat can also **Cascade to Teams** from an existing Objective's **⋯** menu.

**Can I bring OKRs in from a spreadsheet?** Yes; see [Import OKRs from a spreadsheet](/goals-and-okrs/creating-goals/import-okrs-from-a-spreadsheet.md).

## Related articles

* [Introduction to OKRs](/goals-and-okrs/okr-foundations-and-structure/introduction-to-okrs.md)
* [Draft OKRs with AI](/goals-and-okrs/creating-goals/draft-okrs-with-ai.md)
* [Metric types for Key Results](/goals-and-okrs/creating-goals/metric-types-for-key-results.md)
* [Understanding OKR Automatic Rollup](/goals-and-okrs/managing-and-tracking-goals/how-parent-okr-progress-and-status-roll-up.md)
* [Edit and update OKRs](/goals-and-okrs/managing-and-tracking-goals/edit-and-update-okrs.md)
* [Control who can see an OKR](/goals-and-okrs/creating-goals/control-who-can-see-an-okr.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/goals-and-okrs/creating-goals/create-okrs-and-initiatives.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.