This article is accompanied by sample forms and dataset definitions saved in this folder. For help on deploying the workflow, skip to 2. Deploy the workflow now!

1. Overview #

Assessing the availability and the details of infrastructure helps to identify problems and needs, and establish priorities in the context of humanitarian assistance. In this workflow, we will demonstrate how SurveyCTO can be used for a baseline survey of schools, water, and transport infrastructure in towns, from registering towns to managing infrastructure information. A case management system will facilitate this data flow, allowing you to register and close cases (i.e. towns), and manage the forms that need to be filled out for the completion of the case.

In this workflow, you will be able to:

	Register cases (i.e. towns)
	Assign forms to each case
	De-assign forms once they are completed
	Close cases once all forms are completed

2. Deploying the workflow #

Click below to view this workflow in the Hub and install it on your server.

Install Workflow

3. Understanding the workflow #

To be able to effectively test this workflow you can follow these outlined tasks:

Prepare SurveyCTO Collect to work on this workflow: Enable Manage Cases. To learn how, see Guide to case management part 3: Collecting data using case management, section On a mobile device. From the main menu of SurveyCTO Collect, open Get Blank Form, and download the forms related to this workflow (see under the section 4. Workflow components) Register one town: In SurveyCTO Collect, click on Fill Blank Form, open the form Ex 1: Town Infrastructure V1 – 01 Enrollment and complete it Enter the infrastructure information of that town: Open the Manage cases menu. Here, you should see the town that you just registered. Click on it and select a form to complete the town information either about schools, water pumps or transport stations. If you click on a newly registered town, you will see the 3 forms. Once you complete a form, it will be de-assigned. Manage the infrastructure information of that town: In the server console, you will see that the information collected is stored in separate datasets so that you can easily manage your towns, schools, water pumps, and transport stations’ data.

4. Workflow components #

This workflow has 4 forms, 1 cases dataset, and 3 server datasets. Below, you can find a diagram showing the relationship between these components, as well as a non-comprehensive list of all components, the correspondent files and main purposes.

5. Customization and improvements #

SurveyCTO has endless possibilities, so this workflow is only the beginning. Feel free to modify and expand on this workflow to fit your own needs. Here are some ideas on what you can add:

• Publish datasets in long format for easier GIS and data analysis: Currently, the Schools, Water Pumps, and Transport Stations datasets are published in wide format, where each row represents a single town. You could switch them to long format, where each row represents an individual infrastructure (e.g. single school), which can simplify GIS programming, automated reporting, and analysis when multiple entries exist per town.
• Add repeat infrastructure monitoring: You could expand the workflow to collect infrastructure information periodically, such as every few months. This would allow you to track changes in schools, water pumps, and transport stations over time, supporting trend analysis and more informed decision-making.
• Add conditional questions for more context: For example, you could ask whether a school or water pump is currently operational, under maintenance, or planned for upgrade. This can give a more nuanced picture of infrastructure functionality.

Do you have thoughts on this support article? We’d love to hear them! Feel free to fill out this feedback form.