> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/reporting.md).
# Reporting
In Conducttr, you can export various types/formats of reports for exercises from the facilitator dashboard. These reports allow you to gain access to **qualitative and quantitative reports so performance from the exercise can be analysed and reviewed**.
Under the `Review` tab you have two options: *Evaluate* vs *Reports*. Under Reports there are multiple options for exporting. Click the desired option to automatically export the file.
The most important reports for teams-based Conducttr exercises are:
1. **Exercise report (.docx)**
2. **Engagement data (.csv)**
3. **Report data**
{% hint style="info" %}
To find out more about the Colibri and Exception report, **visit the Colibri section** in HelpDocs.
{% endhint %}
{% content-ref url="/spaces/kKsE69Z3PsghYNFs2oFd" %}
[Colibri](https://helpdocs.conducttr.com/colibri/)
{% endcontent-ref %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://helpdocs.conducttr.com/feature-documentation/reporting.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 `automate deployments from our CI pipeline` 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.
