> 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/specify-answer-with-jump.md).

# Other, Please Specify

A very common scenario when converting a paper-based form to Epicollect5 is as follows:

![](/files/XStKN5C3zCySgJjjrk5v)

When converting paper-based forms to Epicollect5, a common requirement is collecting an open-ended answer when a user selects **"Other"** from a list of possible answers. This can be easily implemented using the platform's features. Let’s explore two effective approaches:

## 1 - Using Jumps

Open the formbuilder and add a question type with possible answers, like RADIO. For example, we could ask for a favourite colour and provide only three colours and the "Other" possible answer:

![](/files/3tv3u0uVN89Om7BaRYar)

Since we want the user to see a text question when he picks "Other", we add a TEXT question below the RADIO question:

![](/files/u7xNNzUXw8h67s9NYFPg)

The concept is really simple. We need the users to see the text question only when they select "Other". Basically, they will "jump" that question if they pick any other possible answer.

On the RADIO question ("What is your favourite colour?") we click on the jumps tab and we add a jump like so:

![](/files/4xPAqJf3wo2kDOV1CccF)

This will make the users "jump" to the end of the form when they pick any answer aside from "Other". If they pick "Other", they will not jump therefore they will see the text question "Please type your favourite colour". It's that simple!

## 2- Using Groups

If your question with the "Other" possible answer is in a group, you cannot add a jump. In this case, just add the text question below your multiple-choice question, asking the user to specify if they replied "Other" to the question above.

Tip: use a DROPDOWN question to save space.

Here is how it will look on a device:

|                                  |                                          |
| -------------------------------- | ---------------------------------------- |
| ![](/files/Upv8ba4JfDoj53th2IR2) | It will be similar to a paper based form |

{% hint style="info" %}
Regardless of the approach used, the final data on the Epicollect5 server and the exported `csv` files will be spread over two columns, one for the main question and one for the "Other" question.

To consolidate the data, it is pretty easy to merge columns in Google Sheets, Excel or similar in the post-processing.

[**For Google Sheets see here**](https://support.google.com/docs/answer/9060449?hl=en\&co=GENIE.Platform%3DDesktop#zippy=%2Cmerge-rows-or-columns).

[**For Excel see here**](https://support.microsoft.com/en-us/office/combine-text-from-two-or-more-cells-into-one-cell-81ba0946-ce78-42ed-b3c3-21340eb164a6)**.**
{% endhint %}


---

# 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/specify-answer-with-jump.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.