Create, Test, Publish, and Share a Qualtrics Survey

To create, test, publish, and share a Qualtrics survey, build your questions in a project, preview and test the survey, then use the publishing controls to make the current version available. After publishing, distribute it with an appropriate link or other available channel, and check that responses are being recorded before inviting a wider audience.

Plan the survey before building it

Start by defining what you need to learn and who should answer. A short, focused survey is easier to complete and analyze than one that collects information without a clear purpose. Decide which answers you need, whether questions are required, and whether different respondents should see different questions.

• Write a specific goal, such as finding out which of three appointment times works best.
• Identify the intended audience and how you will reach them.
• Choose question types that fit the answers: for example, a multiple-choice question for fixed options or a text-entry question for open comments.
• Review sensitive or identifying questions and collect only what the project genuinely needs.

Qualtrics menus and available features can vary by account, organization, and product configuration. If a control named here is not visible, consult your organization’s Qualtrics administrator or the help resources available in your account.

Create a survey project

Sign in to your Qualtrics account and create a survey project using the project-creation options available to you. Depending on your account, you may be able to start from a blank survey or use a template. Give the project a clear name so collaborators can identify it; the project name is for management and is not necessarily the title respondents see.

In the survey editor, add questions and select a suitable question type. Enter the question text and answer choices, then check the order and wording. Keep response options mutually clear where possible, and include an “Other” or “Not applicable” choice only when it makes sense for the question. Use the editor’s settings to mark a question as required only if respondents must answer it to continue.

Organize related questions into blocks when that helps the survey flow. If the survey needs branching—for example, showing a follow-up question only to people who selected “Yes”—configure the relevant display or skip logic and test each path. Avoid assuming that a survey’s visual order alone determines what every respondent sees.

Configure survey flow and options

Before testing, review the survey flow and project options. Depending on the design, these may include block order, branching, end-of-survey behavior, a welcome or closing message, and settings that affect how responses are collected. Some account-level choices, such as access restrictions or distribution methods, may be managed elsewhere.

Check the respondent experience as well as the question content. Make sure instructions explain unfamiliar terms, answer choices do not overlap, and a respondent can tell how to proceed. If you use a progress indicator or page breaks, ensure they support rather than interrupt the flow. Consider accessibility: use plain language, meaningful labels, and a logical reading order, and do not rely on color alone to convey information.

Preview and test the survey

Use the survey preview feature to inspect the survey as a respondent would see it. Previewing is useful for catching layout and wording issues, but it does not replace a real test of the complete response process. Test on the devices and screen sizes your audience is likely to use, especially if the survey contains long answer choices, images, or complex branching.

1. Complete the survey once using a typical set of answers.
2. Test each branch, including answers that should skip questions or lead to a different ending.
3. Try boundary cases, such as leaving optional questions blank or selecting “Other,” if those options are present.
4. Check required-question messages, page navigation, and the final thank-you or completion screen.
5. Confirm that a test response appears in the project’s response or data area, if your account provides that view.

Do not use a public distribution link for testing unless you understand how those responses will be stored. Keep track of test entries so they are not mistaken for genuine responses; remove or exclude them using the options available in your account before analyzing results.

Publish and manage changes

When the survey is ready, use the publishing control in the editor to publish the current version. In Qualtrics, publishing is distinct from previewing: a preview lets you inspect the survey, while publishing makes a version available for respondents through distribution. The exact labels and prompts can differ as the interface changes.

After publishing, make a small verification pass using the intended respondent route. Confirm that the link opens, the questions display as expected, and a completed response is recorded. If you edit a survey after it has been published, review the change and publish the updated version where required; changes made in the editor should not be assumed to be live automatically.

Think carefully before changing a live survey. Rewording questions or altering answer choices while responses are already coming in can affect consistency in the collected data. If a change is necessary, document what changed and when, and consider whether responses gathered before and after the change should be analyzed separately.

Share the survey with the right audience

Open the project’s distribution or sharing area and select a method your account supports. A web link is a common option for sending through email, a website, or a message. Other options may be available depending on your organization’s setup. Follow the on-screen instructions, since access rules and distribution features are account-specific.

• Send the link only to the intended audience, and explain the survey’s purpose and expected time commitment.
• Check whether the survey is open to anyone with the link or restricted to particular people or groups.
• Use an invitation method that fits your needs if you must track invitations or manage a defined recipient list.
• Do not assume that sharing a project with a collaborator is the same as distributing the survey to respondents.

Before sending a broad invitation, open the distribution link in a private or signed-out browser session when practical. This can reveal access restrictions or sign-in requirements that you may not see while logged into your account. Avoid posting a link publicly if responses are intended only for a controlled group.

Common problems and useful checks

If respondents cannot open the survey, check that the current version is published, the link is correct, and the survey’s access settings match the audience. A link that works for the survey owner may still require authentication for other people. If a change does not appear, confirm that the edited version was published and that you are testing the current distribution link rather than an old preview or invitation.

If answers are missing, first check whether the respondent completed the survey and whether the question or branch logic behaves as intended. If test responses appear in the data, distinguish them from real submissions before reporting results. For a survey already in circulation, avoid deleting or changing response data without understanding the effect on the project and any connected workflow.

Frequently Asked Questions

Does previewing a Qualtrics survey publish it?
No. Previewing lets you inspect the respondent experience; publishing makes the current survey version available for distribution.

How do I get a link to share?
Open the project’s distribution or sharing area and choose a supported link-based method. Check the access settings and test the link from a respondent’s perspective before sending it.

Can I edit a survey after publishing?
Usually you can continue editing, but changes may need to be published before they appear to respondents. Test and publish the revised version, and consider how changes affect responses already collected.

How can I test branching logic?
Preview or test the survey using answers that trigger every branch. Verify both the questions shown and the destination at the end of each path.

Why can’t someone open my survey link?
Possible causes include an unpublished version, a restricted access setting, an incorrect or outdated link, or a sign-in requirement. Check the distribution settings and test the link while signed out.

Related

• One Punch Man Manga Break: Is It Two Months?
• All Star Tower Defense X Units Tier List and Tips
• AI Safety Evaluations: How Labs Decide to Release Models