> 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/exercise-report.md). # Exercise report The exercise report provides you with an overview of the exercise in the form of a Word document and generates a comprehensive After Action Review (AAR) indexed by injects. Use this to **provide feedback to clients or for your own records**. In the report, you'll be able to review:

Feature	Description	Use when
Observations	AAR observations, observers' names and emails, observer timestamp, player content observer, player data and timestamp, related rich media	You want to review what observers recorded during the exercise alongside the player activity that prompted it
Pie charts	Anonymous visualisations of data (multiselect questions will be visualised as a bar chart)	You want to see which answer won the majority
Participant answers	See which options players selected as their answers for each data point	You want to see how specific participants answered questions
Participant response times	See how long participants took to choose an answer for each data point (this is the time it takes between the button appearing on the screen and the player clicking it)	You want to see which questions players took breaks on/took longer to ponder (this will also allow you to judge if some questions were too difficult)

## How to To export an exercise report, navigate to the `Review` tab in the Facilitator Dashboard:

Check the checkbox in the pop-up window if you want to see all player messages/interactions in all channels:

#### Example Below is an example of what an exercise report looks like:

{% file src="/files/xCzqH1vBz9jJkirHCqc2" %} --- # 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://helpdocs.conducttr.com/feature-documentation/reporting/exercise-report.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.