> For the complete documentation index, see [llms.txt](https://docs.eventflowapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventflowapp.com/eventflow-cms/eventflow-reports.md).

# Eventflow Reports

Our Reporting Suite is built specifically to give event organisers a quick and intuitive overview of what’s happening across the event.

From a single dashboard, you can see the vital metrics that matter most and jump straight into the details when you need a closer look.

### **1. Team Engagement**

Quickly see which team members are active, which are inactive, and who might need a little encouragement. These engagement metrics give organisers a snapshot of team involvement at a glance.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/xrg7zoecwr>" %}

{% content-ref url="/pages/GOH4qWFosNbbjQ1sfL2x" %}
[Team Reports](/eventflow-cms/eventflow-reports/team-reports.md)
{% endcontent-ref %}

### **2. Task Progress**

Understand what’s been completed, what’s overdue, and what still needs attention. For organisers, Task Progress reports offer a straightforward way to keep the event timeline on track and ensure nothing falls through the cracks.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/er5dnq0t6k>" %}

{% content-ref url="/pages/bcMYbP0eBDKDv4f5ndvw" %}
[Task Reports](/eventflow-cms/eventflow-reports/task-reports.md)
{% endcontent-ref %}

### **3. Form Submissions**

Track all your form submissions in one place, including which forms are seeing the most use and if any public forms are being utilised. This gives organisers a central hub to monitor submission activity and fill any information gaps.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/gkyvjqysdk>" %}

{% content-ref url="/pages/3L9rCUoCs6OgUtKjmRPl" %}
[Form Reports](/eventflow-cms/eventflow-reports/form-reports.md)
{% endcontent-ref %}

### Why It Matters

For event organisers, these reports mean less time digging for information and more time making informed decisions. Each report is a doorway into more granular insights, so you can maintain a smooth, well-run event with confidence.


---

# 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://docs.eventflowapp.com/eventflow-cms/eventflow-reports.md?ask=<question>&goal=<user_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.