> 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/child-forms-vs-branches.md).

# Child Forms vs Branches

In Epicollect5 there are two ways to implement nested forms: child forms ([**linking forms using a hierarchy structure**](https://docs.epicollect.net/formbuilder/multiple-forms)) or [**branches**](https://docs.epicollect.net/formbuilder/branches).

While these two approaches look similar, there are some important differences.

{% hint style="success" %}
Nothing stops you from using a combination of hierarchy (child) forms and branches on your project!
{% endhint %}

### Uniqueness

When using a hierarchy structure you can choose between a [**form or a hierarchy uniqueness**](https://docs.epicollect.net/formbuilder/uniqueness). This is not possible when using branches. The branch uniqueness will be limited only to each branch scope as the hierarchy uniqueness cannot be applied.

### Nested forms

When using child forms, you can have only one child form per parent ([**see linking forms**](https://docs.epicollect.net/formbuilder/multiple-forms)). Using branches, you can have multiple branches for a single form. Using branches though, you can go down only one level (it is not possible to add a branch within another branch), while child forms can have a hierarchy of maximum 5 forms.

### Rendering on the mobile app

Child forms and branches are rendered differently on the mobile app.

[**See how to add a child entry**.](https://docs.epicollect.net/web-application/adding-data#add-or-edit-entries-for-multiple-forms-projects)

### Bookmarks

The mobile app [**bookmarks**](https://docs.epicollect.net/mobile-application/add-bookmarks) feature only works with child forms.

### Downloading entries to the mobile app

Branch entries **are not** downloaded to the mobile app, only hierarchy entries are. [**Learn more.**](https://docs.epicollect.net/mobile-application/download-entries)


---

# 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/child-forms-vs-branches.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.