# SierraTec Survey Launch Checklist

Use this checklist before publishing a survey. Adapt it to the risk, audience, jurisdiction, and approval requirements of your organization.

## Purpose and ownership

- [ ] The survey supports a clearly written decision or research objective.
- [ ] The intended respondents and inclusion criteria are defined.
- [ ] A business, research, or program owner is accountable for the survey.
- [ ] A response-review and action owner is assigned.
- [ ] The launch, monitoring, close, analysis, and deletion dates are documented.

## Questions and logic

- [ ] Every question supports the objective or a required operational need.
- [ ] Questions use clear, neutral, audience-appropriate language.
- [ ] Each question asks one concept at a time.
- [ ] Answer choices are balanced, distinct, and sufficiently complete.
- [ ] Required questions are limited to what is genuinely necessary.
- [ ] Logic, branching, piping, scoring, quotas, and outcomes have safe defaults.
- [ ] All logic paths and boundary values were tested.

## Respondent experience

- [ ] The introduction explains purpose, expected time, and responsible organization.
- [ ] Privacy, consent, and contact information are accurate and readable.
- [ ] Desktop, mobile, tablet, zoom, reflow, and keyboard behavior were tested.
- [ ] Labels, instructions, validation, errors, and focus order are accessible.
- [ ] Each language version was reviewed independently.
- [ ] Arabic and other right-to-left content was tested for reading order and layout.
- [ ] The completion page and any redirect are accurate.

## Collection settings

- [ ] Anonymous, confidential, or identified status is described accurately.
- [ ] Opening date, closing date, timezone, response limit, and quota rules are set.
- [ ] Duplicate and automated-response controls are proportionate to the risk.
- [ ] Public, email, SMS, QR, embed, kiosk, or authenticated collectors were tested.
- [ ] Reminder frequency and opt-out handling are approved.
- [ ] Test responses are excluded from production reporting.

## Data, security, and integrations

- [ ] Only necessary personal and sensitive data are collected.
- [ ] Roles, response access, export rights, and team membership were reviewed.
- [ ] Retention, deletion, legal hold, and backup expectations are documented.
- [ ] Integrations use approved accounts, minimal scopes, secure secrets, and owners.
- [ ] Webhooks, automations, alerts, and recovery workflows were tested.
- [ ] Export formats and destination security were reviewed.

## Final approval and monitoring

- [ ] The final survey version and translations are approved.
- [ ] A complete test response was reviewed in the response table and report.
- [ ] Early-response monitoring is assigned for quality, abuse, and technical issues.
- [ ] Support and incident escalation paths are documented.
- [ ] Stakeholders know when and how results will be shared.
