> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/analytics/reports.md). # Reports ### Overview Reports package analytics into a shareable format for stakeholders. They standardize what gets reviewed and when. {% hint style="info" %} Screenshot placeholder: Reports landing page showing existing reports and the create button. {% endhint %} ### Key Concepts * **Report**: curated output aligned to a governance purpose * **Audience**: stakeholder group that consumes the report * **Cadence**: recurring schedule, such as weekly or monthly ### How It’s Used Use reports for stakeholder status updates and outcomes reporting. Use them to reduce ad-hoc request volume during delivery. ### Benefits * Consistent stakeholder communication * Faster preparation for governance meetings * Reduced misinterpretation through stable definitions ### Setup Steps 1. Define the audience and cadence. 2. Select metrics aligned to governance needs. 3. Validate definitions and scope. ### Best Practices * Keep report definitions stable across cycles. * Pair reports with dashboards for real-time monitoring. * Include source links for audit-grade reporting when required. ### Summary Reports standardize outcomes communication for stakeholders. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.transform.ai/analytics/reports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.