# 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**.

<figure><img src="/files/lWYEi02z6hdjXlo6FySP" alt=""><figcaption></figcaption></figure>

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.

### Exercise report (.docx)

All observations are exported to a Word document. Generates a comprehensive After Action Review (AAR) indexed by injects and includes all:

* Observations (the observation, observers' names and emails, observer timestamp, player content observer, player data and timestamp, related rich media)
* Data points (pie & bar charts)

### Engagement data (.csv)

Generates a report of all social media engagement (social media, website data) into an Excel document. This report includes data such as:&#x20;

* Date
* Persona
* Channel
* Messages
* Likes
* Replies
* Reposts
* Followers
* Following etc.

{% hint style="warning" %}
Email data is not included in this report.
{% endhint %}

### Report data (.csv)

All messaging activity from an exercise can be exported to an Excel document. This includes:

* Players' names & email addresses
* Date
* Channels used
* Actions (reply/like/composing a new message)
* The message
* Who the message was sent to & the receiver's email address

{% hint style="info" %}
To find out more about the Colibri and Exception report, **visit the Colibri section** in HelpDocs.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://helpdocs.conducttr.com/feature-documentation/reporting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.