> 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/export-okrs-to-csv-word-or-powerpoint.md). # Export OKRs to CSV, Word or PowerPoint You can export the OKRs in any view as a CSV file, a Word document or a PowerPoint deck. Open the view, click the **⋯** menu in the top right, and choose **Export to Excel**, **Export to Word** or **Export to PowerPoint**. You can also ask for a Word or PowerPoint export in chat. Exports contain exactly the OKRs the view shows: the view's filters, and any keyword search you have typed, apply to the export. ## Export to CSV (Export to Excel) 1. Open the view you want to export and set the filters so it shows the right OKRs. 2. Click **⋯** in the top right of the view and choose **Export to Excel**. 3. Choose what to include: * **Export top-level items**: the OKRs in the view plus their direct children. * **Export all child items**: the OKRs in the view plus every descendant, so the whole hierarchy is preserved. 4. Click **Export**. Rhythms generates the file in the background and shows a message that you will be notified when it is ready. Click **View progress**, or open **Exports** in the left sidebar, to see your exports with their status. When an export is complete, use **Download** to save the CSV or **Review** to look at it first. The file is named after the view and opens in Excel, Google Sheets or any spreadsheet tool. Whether children are filtered depends on the view's **Apply filters to children** display setting. With it off, children are included even when they do not match the view's filters, so a parent's full set of key results comes along. ## What the CSV contains Each row is one objective, key result or initiative. The columns are: * **ID**, **Short ID**, **Title**, **Type** (objective, key\_result or initiative) * **Labels**, **Owners**, **Created By**, **Team** (only when Teams are enabled in your workspace) * **OKR Status**, **Check-In Status**, **Progress**, **Delegate** * **Last Check-In**, **Last Check-In Note**, **Last Check-In Labels** * **Aligned to** and **Aligned to ID** (the parent goals; several parents appear on separate lines in the cell; a parent you cannot see shows as ‹Not visible to you›) * **Time Period**, **Start Date**, **End Date** (dates as YYYY-MM-DD), **Score**, **Contribution Percent** * **Metric Type** (Progress, Reach To, Stay Below, Stay Above or Stay Between), **Target** (shown as ‹100 for Stay Below, ›100 for Stay Above and 80-120 for Stay Between), **Unit**, **Current** ## Export to Word Click **⋯ → Export to Word** on a view. Choose a saved template or click **Upload new template** to add a .docx of your own. You will see a preview of the template and a box where you can add guidance, for example "Emphasise at-risk key results". Click **Generate**. Rhythms opens a chat thread, builds the document from the view's OKRs and delivers the .docx there as a downloadable file. The same include-children choice as the CSV export applies. ## Export to PowerPoint Click **⋯ → Export to PowerPoint** on a view. In the **Export to PowerPoint** dialog you can pick a template from your library, upload a .pptx template, or use none, and add guidance about what to emphasise. Click **Export**, or **Export with selected template** if you chose one. Rhythms opens a chat thread and delivers the .pptx there. A template you upload is saved to your library for future exports, so your colours and fonts are applied automatically next time. ## Export from chat Open the chat panel and ask, for example: * "Export the current OKR view as a PowerPoint" * "Create a Word document of the Engineering team's Q3 objectives, at risk only" * "Export the Q3 Business Review document as a Word file" Rhythms confirms what it will export, generates the file and attaches it to the conversation. OKR views can be exported to Word or PowerPoint this way; CSV export is only available from the ⋯ menu. For exporting documents from the Library, see [Exporting documents to Word](/documents-and-library/export-a-document-to-word-pdf-or-powerpoint.md). ## Automate exports with Playbooks If your workspace has Playbooks enabled, you can put an export request into a playbook so it runs on a schedule, for example a PowerPoint of the company OKRs every Monday before your business review. The playbook runs the same chat request you would type yourself and delivers the file as its output. See [Creating and running playbooks](/playbooks/create-and-run-a-playbook.md). ## FAQ **Why does the menu say Export to Excel when the file is a CSV?** The export is a CSV file that Excel opens directly. CSV keeps the export simple and importable into any spreadsheet or BI tool. **Where did my export go?** Open **Exports** in the left sidebar. It lists every export with the view it came from, the date and its status, and lets you download or review each file. **Why are some OKRs missing from my export?** The export contains what the view shows you. OKRs you cannot see are never exported, and a parent you cannot see appears as ‹Not visible to you› in the Aligned to column. Check the view's filters and any keyword search before exporting. **Can I export a report?** Not directly. Click a number in the report to open the OKRs behind it, then export that list. ## 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) * [Exporting documents to Word](/documents-and-library/export-a-document-to-word-pdf-or-powerpoint.md) * [Creating and running playbooks](/playbooks/create-and-run-a-playbook.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/export-okrs-to-csv-word-or-powerpoint.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.