Input | Description |
---|---|
Survey name | Name of the survey. This will be used as the display name on the web app and for labelling dashboards, emails etc. E.g., ADP 2.0 Agriculture. |
Survey ID | Unique identifier for the survey. The naming convention is survey name + round name e.g., adp_ag_r2. Spaces are not allowed. |
Project name | (Optional) Can be used for grouping multiple rounds of data collection for a single project e.g., ADP. |
Survey description | (Optional) Brief description to provide more context about your survey e.g., “ADP 2.0 Agriculture is a survey being conducted in 8 states of India for collecting data from agriculture extension agents about supply of fertilizers to farmers”. |
Survey method | Whether the survey is an in-person, phone, or mixed mode (in-person + phone) survey. |
Survey start date | The start date from which your team will start using SurveyStream after configuration. From this date until your Survey end date the SurveyStream back end will be Active , meaning that it will regularly pull in your data from SurveyCTO and perform other actions you’ve configured like sending messages or updating your monitoring dashboards. Set this field to a couple of days ahead of the data collection start date for the purpose of testing the systems. This field can be edited. |
Survey end date | The date until which the SurveyStream back end will be Active . This field can be edited during the survey as per changing survey requirements. The end date must be chronologically after the Survey start date . |
What criteria will be used to map supervisors to surveyors?
Available options are:
What criteria will be used to map supervisors to targets?
Available options are: