> 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-an-entry.md).
# Add Entries - Mobile (Single Form)
To begin adding entries, tap on your project on the **PROJECTS** list home page.
Next, tap the **+ADD ENTRY** button at the top right to start adding an entry to the first form.
In this example, the form is called simply *'FORM 1'*.
This will begin the process of adding an entry, by answering each question on the form.
A progress indicator at the top show you how far through each form you are.
You can use the **NEXT** and **PREVIOUS** buttons to navigate back and forth.
If you decide to quit your entry early, you can choose to save your incomplete entry.
{% hint style="warning" %}
Incomplete entries cannot be uploaded.
Only fully completed entries can be synced with the server.
In order to complete an entry, you must reach the end of the form.
{% endhint %}
Once you have reached the end of the form, you can save your entry.
After the entry is saved locally, you will be taken back to the form home page where you can add more entries, view your entries or upload your entries to the server.
{% embed url="" %}
---
# 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-an-entry.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.