The exact-match query create qualtrics survey describes a task, not a product, so the useful answer is a sequence: open the platform, start a project, build the question set, test it, then publish. Qualtrics itself publishes support documentation covering the Survey tab, the Survey Builder, blocks, question types, survey flow, and publishing, and that documentation is the structural basis for the steps below.
What a Qualtrics survey project contains
A project is the container that holds everything a respondent eventually sees. Inside it sit questions, and questions sit inside blocks. Blocks group related items so a long instrument stays readable and so page breaks fall in sensible places. Survey flow sits above the blocks and controls the order in which they appear, which is where branching and randomisation live.
Three supporting layers sit alongside the question set. Look and Feel controls theme, logo, and layout. Survey Options controls behaviour such as back-button use and progress display. The Data & Analysis and Results areas hold responses once collection starts. A project is therefore not just a list of questions; it is a question set plus presentation plus logic plus a results destination.
For anyone in Malaysia building a first instrument, the practical implication is that planning the block structure before typing questions saves rework. A block per topic, with flow logic added afterwards, keeps the build readable and makes later edits far less disruptive.
How to create qualtrics survey projects in the builder
The creation path is short and mostly linear. The steps below follow the sequence described in Qualtrics support documentation and in university user guides that walk through the same flow.
- Sign in to the Qualtrics account. Institutional users typically sign in through single sign-on with a university or organisation login rather than a personal email address.
- Select the option to create a new project from the account dashboard.
- Choose the project type. Qualtrics separates survey, questionnaire, and form style projects, and the choice affects the starting template.
- Confirm the selection to open the setup screen.
- Name the project and set the available options, then create it.
- Add questions inside the default block, or add further blocks first if the instrument has clear sections.
- Configure question types, answer choices, and any display or skip logic the instrument needs.
- Use the preview function to test the survey as a respondent would see it.
- Publish the survey so changes go live. Edits made after publishing are not visible to respondents until the survey is published again.
Two details in that sequence cause most first-build confusion. The first is that a project can exist in a draft state indefinitely; nothing is visible to respondents until publishing happens. The second is that multiple users can edit the same survey, so on shared institutional accounts it is worth confirming who holds edit rights before a build begins.
Question types, blocks, and survey flow
Qualtrics documentation groups question types into families rather than a single flat list. Multiple choice, text entry, matrix table, and scale formats such as Likert and Net Promoter Score cover the majority of business and academic instruments. Constant sum, rank order, and side-by-side formats appear where comparative judgement matters. The right choice depends on what the analysis needs to do later, not on what looks best in the builder.
Blocks do three jobs. They group related questions, they create natural page breaks, and they give survey flow something to route between. A short customer satisfaction instrument might need one block. A multi-section employee survey might need five, with a screening block at the front and a demographics block at the end.
Survey flow is where the instrument stops being a static list. Branches send respondents down different paths based on earlier answers. Randomisers shuffle question or choice order to reduce position bias. Embedded data fields carry values into the response record, which matters when the same survey is distributed through several channels and the source needs tracking. Quotas cap how many respondents land in a given segment.
The trade-off is straightforward. Every branch, randomiser, and quota adds a path that must be tested. A survey with heavy logic needs a longer preview cycle, and a broken branch is usually discovered by a respondent rather than by the builder.
Free account limits and what changes on paid plans
Qualtrics maintains a free account tier, and its own support documentation devotes a page to free account usage limits, features, and restrictions. That page is the authoritative place to check current response caps, survey counts, and inactivity rules, because those terms change and are not fixed for the life of the product.
What the documentation structure makes clear is the shape of the restriction rather than the exact numbers. Free accounts carry usage limits on responses and on how many surveys can be created and distributed. Certain features are restricted, and custom code, advanced branding, and some analytics capabilities sit behind paid licensing. Free accounts created before November 2019 are treated separately from newer ones, which means two users on the same tier may not have identical capabilities.
Upgrading happens from the Plans area of the account, and deactivation is also a documented option. For a Malaysian SME or a student running a single research project, the free tier is usually enough to build and test an instrument. The constraint appears when response volume grows or when the analysis needs crosstabs, advanced text analysis, or integrations that the free tier does not include.
Pricing for paid tiers is not reproduced here. Qualtrics publishes its own plan comparison, and any figure quoted second-hand should be verified against that source before it is used in a budget.
Distributing a survey and reading results
Distribution options in Qualtrics cover anonymous links, direct email invitations, and SMS, with the choice affecting how responses can be tracked. An anonymous link is the simplest route and the least traceable. Email distribution through the platform allows reminders and response tracking per contact. For panel-based or quota-controlled research, distribution is tied to the quota logic configured in survey flow.
Results land in the Data & Analysis area and in the Results dashboard. The dashboard handles visual reporting and PDF export; Data & Analysis handles response editing, export to formats such as CSV, Excel, and SPSS, and the statistical work that precedes reporting. Reports can be shared with people who do not hold an account, which matters when findings need to reach a client or a department head.
One practical constraint applies to every distribution method. Changes made in the builder after publishing do not reach live respondents until the survey is published again, so a mid-collection edit can split the dataset between two versions of the instrument. Where comparability matters, the safer route is to close collection, revise, and treat the change as a new wave.
What to check before the first response arrives
Preview the survey on a mobile screen, not only on desktop. Confirm that required questions behave as intended and that skip logic does not strand a respondent on an empty page. Check that the closing message tells respondents what happens next. Confirm the export format matches whatever analysis tool will receive the data. These checks take minutes and prevent the most common post-launch repairs.
Where the build fits into a wider data workflow
Survey data rarely stays inside the survey platform. It usually feeds a reporting process, a CRM, or a decision cycle, and the quality of that downstream work depends on how the instrument was structured at build time. Consistent coded values, stable question wording across waves, and a clear block structure all make later analysis cheaper.
Blackstone Intelligence, a Kuching-based AI systems and digital growth agency operated by Blackstone Consultancy Sdn Bhd, works across AI automation, dashboards, reporting, and content systems for Malaysian SMEs, ecommerce brands, education providers, and institutional teams. That work sits downstream of data collection rather than inside it, which is the relevant boundary here: the survey platform handles collection, and the surrounding systems handle what happens to the responses afterwards.
For teams running repeated surveys, the useful discipline is to treat the instrument as a versioned asset. Record what changed between waves, keep coded values stable, and store the export alongside the questionnaire. That record is what makes a year of responses comparable instead of merely numerous.
