I'd be happy to help! Our projects sometimes deal with interviewing the residents of a city with respect to health, mosqitoes etc.
Here's a typical scenario:
A surveyor has already visited a particular area on Day1. The first question is the House number which is unique throughout the city. The process is to open the form, enter the House number first, and then attempt to interview the resident. The second question in the form is if the residents are available for interview. If yes, it is followed by the other survey questions. If not, the form exits after recording that interview was not possible. The data is submitted to the server on a live basis and is available for download through an API endpoint.
On Day2, the process continues with the same Surveyor or a different one. Ideally, as soon as a House number is entered into Question1 of the form, it should pull the data which has already been submitted till now using the API endpoint (as a CSV file) and should display various columns which show the status of this House number. Whether it has been visited before, when & who visited, was it a successful visit, etc.
This feature will provide the following benefits:
- Surveyors will not waste time trying to interview residents who have already been interviewed previously
- We can programmatically prevent someone from visiting a house a second time if the visit was a success
- We can encourage the surveyor to try harder for the interview if the previous visits were unsuccessful.
Other (ideal) requirements and notes:
- It should be possible to pull data from a variety of sources, even google sheets which someone can keep updating at the back-end with any other kind of information required.
- If the data pull doesn't work for any reason (eg. bad data connection, API is down etc), it should still be possible to proceed on the form. It would be best if the data pull status can be captured in a variable, so that we can make the form logic according to that.
How we are managing currently:
- We provide a Google sheet doc link containing updated visit information which each surveyor can check for the status of each house, but practically it doesn't happen because either the back-end person forgot to update the file, or the surveyor is not savvy enough to do a search within the sheets etc.
- Actually many of our surveyors spend a lot of time ringing doorbells, waiting for responses, etc. only to find that the interview has already happened before.
Hope it is clear, if any other info is required please let me know.