> 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/team-reports/single-team-report.md).

# Single Team Report

A Team Report gives organisers a focused view of a single team’s progress, activity, and risks.

The Team Task Report combines an overall risk score with task-level detail, helping you understand exactly where a team stands and what support may be needed.

### **Overall Risk Score**

At the top of the report, you’ll see the team’s **risk rating**, displayed as a percentage. This score uses the same data-driven algorithm as the Team Reports page, factoring in:

* Number of overdue or pending tasks.
* Whether tasks are approaching their deadlines.
* Login activity.

{% hint style="warning" %}
A higher percentage means the team is more likely to miss critical requirements without intervention.
{% endhint %}

### **Task Summary**

This panel shows a breakdown of the team’s current workload:

* **Completed** – how many tasks are fully finished.
* **Due Soon** – tasks approaching their deadline.
* **Overdue** – tasks already past due.

This snapshot allows you to immediately gauge urgency before looking at the detailed task list.

### **Login Summary**

Shows the team’s most recent login and key contact information. If a team hasn’t logged in for a long period, it may signal disengagement or missing contact details.

### **Task List**

Below the summary, you’ll find a detailed list of all tasks for the team, including:

* **Title** – the name of the task (e.g. *Exhibitor Pre-Show Planning Form*).
* **Due Date** – when the task is scheduled for completion.
* **Task Status** – colour-coded to show urgency:
  * **Red (Overdue)** – the deadline has passed.
  * **Amber (Due Soon)** – the deadline is approaching.
  * **Green (Complete)** – the task is finished.

Tasks can also be filtered by **Status** or **Type** to narrow down the list.

### **Quick Actions**

* **Generate Report** – download the team’s task data for offline review.
* **Reinvite** – resend login invites to prompt team activity if required.


---

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