Survey applications

Respondents, lists and deployments

Survey Respondents are separate from system users. Lists select the respondents who may receive a deployment. A deployment chooses a survey form, time window, list and repeat-submission policy. Anonymous deployments have no list and accept public responses only during their configured window.

Response tables and data integrity

Each deployment owns a response table with deployment, list, respondent, form, timestamps, completion status and form fields. The table is created when the deployment is created or changed while it has no data. Once responses exist, the deployed form is protected from structural changes.

Progress and completion

Pagination can submit progress after a validated next step. In-progress and completed states are stored with the response. A completed submission can resume the latest response when resubmission is allowed; otherwise the policy limits the participant to one response.

Identity and assistance

Local respondents can reset a password. Google and Facebook external identities can complete eligible public deployments; their external provider ID is stored as the respondent identifier. Survey assistants and administrators can open an assisted session without signing in as the respondent.

See mobile notifications, security and deployment, and forms.