# Team Reports

Team Reports is designed to help you spot which teams are on track, which are falling behind, and who might need a reminder or extra support.

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

### **Filters**

Use the filters at the top of the page to refine the view:

* **Team Type** – focus on exhibitors, stand sharers, or other groups.
* **Login Status** – quickly identify who hasn’t logged in yet.
* **Stand Share** – check progress for shared stands.

### **Task Breakdown**

Each team has a progress bar showing how many tasks are completed out of the total.

* **Colour coding reflects due dates**:
  * **Green** – tasks completed on time.
  * **Amber** – tasks approaching their deadline.
  * **Red** – tasks overdue.

This makes it easy to spot where deadlines are at risk before they become a problem.

### **Risk Score**

Every team is assigned a **risk percentage**. This is calculated using a combination of factors:

* Login activity (how recently a team logged in, or if they haven’t logged in at all).
* The number of completed tasks vs outstanding tasks.
* Pending or overdue items.

By combining these data points, the risk score gives organisers a **data-driven way to focus on the teams most likely to need intervention**.&#x20;

{% hint style="warning" %}
High scores usually mean a team requires attention — often due to something as simple as an incorrect contact email or missing team assignment.
{% endhint %}

### **Login Status**

See whether teams are **Active** or still **Pending** (not yet logged in). This helps you track early engagement and ensure every exhibitor is connected.

### **Actions**

The **View** button opens a detailed team-level report, showing specific tasks, submissions, and engagement history.

### Quick Actions

* **Generate Report** – export team engagement data for offline review or sharing.
* **Reinvite** – resend invites to teams who haven’t logged in, directly from the report page.


---

# 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/team-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.