qualtrics-opslisted

# Qualtrics Live-Survey Operations ## Instructions ### 1. When to use This skill covers **operating** a survey already built and imported into Qualtrics — publishing, quotas, flow routing, live text patches, panel-vendor integration, security options — on an instrument that is or will be fielding real respondents. It is not survey design or QSF construction; assume the survey definition already exists and the question is how to change it without breaking what respondents currently see. ### 2. Non-negotiables **Backups first, always.** Pull and save the survey definition (and flow and options as separate JSON) before any write. Qualtrics version restore exists but is coarse and carries data-risk caveats; your pre-change snapshot is the only *precise* recovery path, and the only one that covers objects (quota counters, options) outside version history. **Verify by read-back, never by absence of error.** A 200 response proves the API accepted the request, not that respondents will see the result. After every write, GET the changed object back and confirm it matches intent. **The version list is the proof a change is live**, not the publish-state flag. Question/block writes create no version-history entry, so publish-state can report "in sync" while the live version still lags behind your edit. The standard: your publish call created a NEW published version entry carrying your own description — and, because a description proves provenance rather than content, pair it with