How do you track a borehole repair from report to resolution?
Define a workflow type with the steps your repair process actually has (report, verify, assign, repair, verify the fix, close) and deploy it to the supervisors and technicians who do the work. Each repair then becomes a tracked case with a responsible person and a record at every step.
Most functionality data tells you what is broken, not whether anyone fixed it. That gap is why downtime figures look bad even where teams are working hard: the repair happened, but nothing recorded who did it or when. Running repairs as workflows turns maintenance into data you can manage, including how long verification takes, which technicians are overloaded and which water points fail repeatedly, and it gives regulators evidence that service standards are being met.
How to do it
Choose an existing workflow type for the process, such as water point repair, or create your own with the steps and roles you use.
Deploy the workflow type to the relevant people, for example office supervisors and field technicians.
Let the workflow start where the problem is found. A technician can launch it from the app, and it can also be triggered automatically by a survey response reporting a broken pump.
Configure the actions on each step, such as filling in a survey with repair details, assigning the case to a technician, or notifying a manager.
Add automations to move cases forward and escalate them, so an overdue repair surfaces instead of going quiet.
Require a verification step before closing, so a case only closes once someone has confirmed the water point works again.
Review the workflow data in the Portal to see open cases, time to resolution and repeat failures by site.