# Task Reports

Instead of checking progress team by team, this report highlights which tasks are causing delays, where bottlenecks exist, and how many exhibitors still need to act.

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

### **Filters**

Use the filters at the top of the page to quickly refine the report:

* **By Type** – filter by task category (e.g. forms, uploads, logistics).
* **By Urgency** – focus on tasks that are overdue or due soon.
* **By Team Type** – isolate exhibitors, contractors, or other participant groups.

### **Task List Overview**

Each row in the report shows:

* **Task Title & Description** – what the task is and why it matters (e.g. *Exhibitor Pre-Show Planning Form*).
* **Assigned Teams** – the number of teams linked to the task.
* **Progress Bar** – showing how many teams have completed the task vs how many are outstanding.
  * **Green** – teams completed.
  * **Red** – teams overdue.
  * **Amber** – tasks approaching deadlines.
* **Due Date** – the deadline for task completion.
* **Actions** – open the task detail view to drill further.

### **Bulk Actions**

**Chase Teams** – send reminder notifications to all teams who haven’t completed a specific task (shown in the purple *Chase X teams* button).

{% hint style="info" %}
Filter-aware chasing – the *Chase Teams* button dynamically updates based on the filters you’ve applied. For example, if you only want to chase a specific team type (e.g. exhibitors), select it from the dropdown and the email reminders will only be sent to those filtered teams.
{% 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://docs.eventflowapp.com/eventflow-cms/eventflow-reports/task-reports.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.