> 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/form-reports.md).

# Form Reports

From the Form Reports screen, you can drill down into an individual form’s detailed report to review submissions, chase missing responses, and export data.

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

### **Form List**

Each row displays:

* **Form Name** – the name of the form (e.g. *Booth Check Form*).
* **Total Entries** – the number of submissions received so far.
* **Actions** – use the **View** button to open a detailed report of which teams have completed the form. Click on a team name to view and edit their form entry.

### **Search**

Use the search bar to quickly locate a specific form if your list is long.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eventflowapp.com/eventflow-cms/eventflow-reports/form-reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.