> For the complete documentation index, see [llms.txt](https://docs.epicollect.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epicollect.net/common-use-cases.md).

# Common Use Cases

- [Matrix Style Questions](https://docs.epicollect.net/common-use-cases/matrix.md)
- [Consolidate data](https://docs.epicollect.net/common-use-cases/consolidate-data.md): When retrieving data from Epicollect5, individual files are generated for each form and branch. To facilitate data linkage, Epicollect5 assigns unique identifiers, integrated into the dataset.
- [Jumps 101](https://docs.epicollect.net/common-use-cases/jumps-101.md): Example Implementation of Jumps in the Epicollect5 Platform
- [Other, Please Specify](https://docs.epicollect.net/common-use-cases/specify-answer-with-jump.md): Handling "Other, Please Specify" in Epicollect5 Forms
- [Non-Hierarchical Forms](https://docs.epicollect.net/common-use-cases/non-hierarchical-forms.md)
- [Users Working Groups](https://docs.epicollect.net/common-use-cases/users-working-groups.md): Managing multiple projects for multiple sites and compare all the data
- [Excel and UTF-8](https://docs.epicollect.net/common-use-cases/excel-and-utf-8.md): Microsoft Excel may struggle to properly display UTF-8 compliant CSV files when they contain non-English characters. However, this issue is not related to Epicollect5.
- [Excel All Data in One Cell](https://docs.epicollect.net/common-use-cases/excel-all-data-in-one-cell.md)
- [Barcodes](https://docs.epicollect.net/common-use-cases/barcodes.md)
- [Child Forms vs Branches](https://docs.epicollect.net/common-use-cases/child-forms-vs-branches.md)
- [Dependent Dropdowns](https://docs.epicollect.net/common-use-cases/dependent-dropdowns.md)
- [Referencing Parent Form Responses](https://docs.epicollect.net/common-use-cases/referencing-parent-form-responses.md): Reference responses from a parent form while collecting data.


---

# 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.epicollect.net/common-use-cases.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.