> 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/mobile-application/add-child-entries.md).
# Add Entries - Mobile (Multiple Forms)
On multiple forms projects, like our [**EC5 HIERARCHY PROJECT**](https://five.epicollect.net/project/ec5-hierarchy-project), the data collection follows a hierarchy structure. It is exactly like using folders on your computer. We usually create a parent folder and inside it one or more subfolders and so on. A parent folder can contain multiple subfolders. It is not possible to create a subfolder without a parent folder.
In the sample project, we set up three linked forms: **CLASS > PUPIL > TEST**.
**(**[**See linking forms**](/formbuilder/multiple-forms.md)**).**
The main idea is to add a list of **CLASS** entries and add **PUPIL** entries to each **CLASS** entry. Afterwards\*\*,\*\* we want to add **TEST** entries to each **PUPIL** entry.
Look below, we added a **CLASS** entry named "*History*" to the **EC5 HIERARCHY PROJECT**.
**(**[**More on adding an entry**](/mobile-application/add-an-entry.md)**).**
When an entry for a form is added, and there is a linked form, an arrow button appears next to the entry when viewing the list of entries. We added a CLASS entry named "History".
On larger screens like a tablet, or when the device is in landscape mode, the name of the linked form also appears. Our child/linked form is named PUPIL.
Tapping the PUPIL button takes you to the PUPIL form, where we can add child entries to the "History" CLASS entry. Tap the **+ADD ENTRY** button on the top right to add an entry.
We added a PUPIL entry named "Mirko" and that appears as a child entry of "History". At this point, following the same steps, we can either add another PUPIL entry or go a level further down the forms hierarchy to add a TEST entry to a PUPIL. The back button at the top left indicates "CLASS", our starting form.
On larger screens or in landscape mode, the name of the linked TEST form appears.
---
# 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/mobile-application/add-child-entries.md?ask=&goal=
```
`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.