This article covers completing a form using the Mobenzi mobile app. Mobenzi web forms are are covered by our Web Collection article.

Forms will be available to fieldworkers via the Mobenzi Gateway mobile app once the forms have been published and have been assigned to them. Only published (or republished) changes will be sent to the assigned fieldworker's handset. Fieldworkers must have at least one handset assigned to them to be able to receive and complete a form.

Note: No draft forms or unpublished changes will be available to fieldworkers.

Accessing the forms

To access the form, the fieldworker selects the project module (1). This module has the name of the project that is currently in context (e.g. "Demo project"). If the fieldworker is assigned to more than one project, they can view the list of these projects from the My Profile module (2) and select the relevant one from the list under My projects (3). 


Tapping on the project module (1) displays all forms in the project that are assigned to the fieldworker, listed alphabetically. The latest version published and downloaded is indicated to the right of the form name. The fieldworker launches a form by tapping on it.

If the form is available in more than one language, the fieldworker chooses the language they want to launch the form in. They will have this choice every time they launch a new form but will not be able to switch languages mid-way through a form. If a form is only available in one language, the form will automatically launch in that language without asking the fieldworker to select it. 

Capturing responses

Once launched, the name of the form will appear at the top of the screen (1). The fieldworker can capture responses for each field that is displayed. An asterisk (2) indicates that a response is required. If no asterisk is shown for a question, the fieldworker can continue the form without capturing a response for that question. 

Note: Read about the different types of fields you might encounter.

Depending on how the form was designed, there might be multiple pages that the fieldworker must step through by tapping 'Next' at the bottom of each page (4). To edit responses they can return to a previous page by tapping 'Back' (5). At the end of the form, the fieldworker selects 'Submit' (6) to finish the form. Once they have data connectivity, the form will then automatically sync to the server and be visible from the Analyse tab on the web console. 

Quit and resume form

A fieldworker can quit the form at any point selecting the 'Options' icon (1) in the top right corner and then 'Exit' (2). You can edit the form completion behaviour settings to specify what should happen after quitting a form.

In the form listing, there will be an indication that a form is in progress (3). 

Upon launching the in-progress form, the fieldworker can choose to resume the form or discard this instance and start a new one.

If a new version of the form was published while the fieldworker had forms in progress, they will be asked whether they want to discard the old form and start from scratch with the new version of the form (note: if the fieldworker selects to discard the in progress form, all the responses already captured will be lost), or if they would like to continue with the current version (4). Assuming data connectivity, all new forms launched will be the latest version by default.

Switching between pages 

By default, forms will need to be completed sequentially (i.e. starting from the first page through to the last page). This can be disabled from the Advanced fieldworker collection settings page allowing fieldworkers to switch between pages when completing a form. 

To switch between pages when completing a form, open the form menu by tapping on the three dots in the top right corner and select Page Listing. The fieldworker can switch between the pages at any time while completing a form. 

Note: Skip logic and validation rules will still apply. For example, a form cannot be submitted if all required fields have not been captured.