# Single Task Report

The Single Task Report makes it simple to track who has submitted, who is still outstanding, and when submissions were made.

### **Task Context**

At the top of the page you’ll see:

* **Task name** (e.g. *Exhibitor Pre-show Planning Form*).
* **Restrictions** (some tasks may only apply to certain team types, such as exhibitors).

### **Filters**

Filter the list by **Status** to focus on pending, overdue, or completed teams.

### **Team Submissions List**

Each row displays:

* **Team name** (e.g. *Siemens AG*).
* **Assigned user** – who submitted or is responsible for the task.
* **Submission date** – when the task was completed.
* **Status** – colour-coded for clarity:
  * **Green (Completed)** – the team has submitted.
  * **Amber (Pending)** – not yet complete, deadline approaching.
  * **Red (Overdue)** – deadline missed.

### **Bulk Actions**

**Chase Teams** – send reminder notifications to all teams that haven’t completed the task yet (visible in the purple *Chase X teams* button).

{% hint style="info" %}
The *Chase Teams* feature respects filters. For example, if you filter by Status = Overdue, the chaser email will only go to overdue teams.
{% endhint %}

**Generate Report** – export the submission data to Excel for offline use or sharing.

{% hint style="info" %}
Exports are also filter-aware. If you’ve applied filters (e.g. by status or team type), the Excel file will only include those filtered results.
{% 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/single-task-report.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.