> 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/monitoring-and-reports/monitor-okr-program-health-with-reports.md). # Monitor OKR program health with Reports Reports show the health of your OKR program: which OKRs are missing check-ins, which are unaligned, who has no OKRs, and where progress is falling behind. Open **Reports** in the left sidebar (under **More** in the Workspace section unless you have reordered your sidebar). Every workspace starts with the **Organization OKR Program Pulse**, and each team has its own Program Pulse under **Your teams**. ## The Reports page The Reports page lists every report you can access, with tabs for **All**, **Created by me** and **Shared with me**, and a **New Report** button. A report is a saved set of filters plus a choice of which of the six report cards to show and how to slice each one. Open a report to see its cards, each with a heading, a one-line description and a table of rows and columns. ## The six reports Each card answers one question. The left column lists the slice (teams, managers or people); the other columns are counts and a rate. | Report | Columns | What it tells you | | ------------------------ | ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | **Check-in Coverage** | OKRs Missing Check-ins, Total OKRs, Check-in Rate | Which OKRs have not been checked in on in the selected time range. | | **Check-in Compliance** | On time, Late, Missed, Total, On-time %, Completion % | Whether check-ins happened on time, late or not at all across each check-in cycle. Sliced by people by default. | | **Alignment Coverage** | Unaligned OKRs, Total OKRs, Alignment Rate | Which OKRs are not connected to a higher-level objective. | | **Integration Coverage** | OKRs with Integrations, Total OKRs, Integration Rate | Which OKRs are connected to a data source through a connector, so their progress updates automatically. | | **User OKR Adoption** | Users Without OKRs, Total Users, Adoption Rate | Who has no OKRs assigned. | | **Performance Report** | At Risk, Total OKRs, Avg Progress | Which OKRs are significantly behind their expected progress, and the average progress overall. | Rate columns are tinted: green at 60% and above, amber from 20% to 59%, red below 20%. Avg Progress is not coloured, because a low average is not necessarily a problem. ## Click a number to see the OKRs behind it Any count that is not zero and not a percentage is clickable; it has a dotted underline and highlights when you hover. Click it and Rhythms opens a preview list named after the row and column, for example *Engineering - OKRs Missing Check-ins*, containing exactly those OKRs. In User OKR Adoption the preview lists the people instead. Percentage columns are totals and cannot be clicked. The preview reflects the data at the moment you click. If the report was loaded a while ago, refresh it before comparing numbers. ## Slice each report Every card has a **Slice** menu that sets what the rows are: **Teams** (when Teams are enabled), **Managers**, **Users**, and any user profile fields your workspace has enabled, such as department or job title. The workspace default slice is teams, or users when Teams are turned off; Check-in Compliance always starts on Users. Turn on **Show empty rows** to include rows with no OKRs. To choose which cards a report shows, open **Manage reports** above the cards and switch each report on or off. You can set the slice for each report there as well. ## Trending **Check-in Coverage** and **Performance Report** can show change over time. Set a **Date Range** filter, then use the **Trending** picker on the card to choose **Weekly**, **Monthly**, **Quarterly** or **Yearly** columns. The options depend on how long the date range is: a range under a month is weekly only, while a range of several years is quarterly or yearly. Cells in a trending column are clickable too, and the preview is scoped to that period. ## Filter a report Filters sit above the cards and apply to every card at once. You can filter by **Time Period**, **Owner** (with the option to include direct reports or everyone below them), **Team** (with sub-teams), **Delegate**, **OKR Status**, **Labels**, **Object Type** (objectives, key results, initiatives), owner type and status, **Creator**, **Date Range**, and user profile fields such as department, division, job title and cost centre. The filter controls work the same way as in views; see [Filtering and grouping OKRs in views](/goals-and-okrs/monitoring-and-reports/filtering-and-grouping-okrs-in-views.md). Changing filters or slices marks the report as modified. Click **Save Report** to keep the changes on this report, **Save New Report** to keep them as a separate report, or the reset button to discard them. A Rhythms Admin can also reset the Organization OKR Program Pulse to its defaults. ## Share a report Open the report's **⋯** menu and choose **Share**. Add people or teams with **Can view** (open and read), **Can edit** (change filters and slices) or **Can manage** (edit, share and delete). Sharing with a team includes anyone who joins the team later. The Organization OKR Program Pulse is shared with everyone in the workspace. From the same menu you can **Edit** the name, **Add to favorites** to put the report in your sidebar, or **Delete** it. ## Put reports into your rhythm * **During planning**, watch Alignment Coverage and User OKR Adoption to confirm every team has OKRs and they connect upwards. * **During execution**, review Check-in Coverage and Check-in Compliance weekly, and the Performance Report monthly to catch OKRs that are falling behind. * **At the end of a cycle**, look at all six together and note the trend from last cycle rather than aiming for a fixed score. Before a review meeting, save a report filtered to the relevant scope and share it with Can view so attendees can explore without changing it. ## FAQ **What is the difference between Reports and Views?** Reports answer "is the program healthy?" with fixed metrics. Views answer "what needs attention today?" with any filters and display you choose. Clicking a number in a report takes you from the report into a list of OKRs. **Can I change which reports appear?** Yes. Open **Manage reports** and switch cards on or off, then save the report. **What counts as At Risk in the Performance Report?** An OKR whose progress is significantly behind what would be expected at this point in its time period. It is not the same as the At Risk status an owner sets in a check-in; filter by OKR Status if you want that. **The report says "No data available".** There are no OKRs matching the filters in that time range. Widen the time period or remove a filter. **Can I export a report?** Not directly. Click a number to open the preview of those OKRs, then export that list; see [Export OKRs to CSV, Word or PowerPoint](/goals-and-okrs/monitoring-and-reports/export-okrs-to-csv-word-or-powerpoint.md). ## Related articles * [Create and share OKR views](/goals-and-okrs/monitoring-and-reports/create-and-share-okr-views.md) * [Filtering and grouping OKRs in views](/goals-and-okrs/monitoring-and-reports/filtering-and-grouping-okrs-in-views.md) * [Effective check-ins to track OKR progress](/goals-and-okrs/managing-and-tracking-goals/write-and-submit-check-ins.md) * [Check-in rhythms](/workspace-settings-and-administration/customize-rhythms-settings/set-a-workspace-check-in-rhythm.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) * [OKR visibility: 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/monitoring-and-reports/monitor-okr-program-health-with-reports.md?ask=&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.