Question Types

Presents a list of coded options and captures exactly one selection from the respondent. The most common question type in survey scripts. The answer is stored as the selected option code (integer).

Allows the respondent to select one or more options from a list. Each selected option is independently flagged. Use numberofresponse[] to count selections.

Captures free-text input from the respondent. The response is stored as a string. Use lengthof[] to check character count or substrof[] to inspect specific characters.

Captures a single numeric value from the respondent. Supports integer and decimal input with optional MIN:/MAX: range constraints. The response can be used directly in arithmetic comparisons.

Asks the respondent to rank a list of items in order of preference. Each item receives a rank number (1 = first/most preferred). Use valueof[Qx.n] where n is the item code to retrieve its assigned rank.

Displays a still image (JPEG, PNG, etc.) to the respondent as a visual stimulus without capturing a response. The image filename is specified in double quotes after *PICT. Typically placed immediately before a related question to ensure the respondent views the stimulus before answering.

Presents a matrix where each row is a statement or attribute and the respondent selects exactly one column option per row. Column options are defined once using *GRIDLIST and then referenced in any grid question with *USEGRIDLIST. Use valueof[Qx.n] to access a specific row's response.

A grid where each row allows multiple column selections (multi-select per row). Unlike Single Grid, the respondent is not restricted to one choice per row. Use numberofresponse[] to count total cells selected.

Displays a video stimulus to the respondent without capturing a response. The video filename is specified in double quotes after *VIDEO. The respondent must click the play button to watch the video before proceeding to the related question. Used to expose respondents to advertisement or product videos as stimuli.

Captures multiple open-text responses in a numbered list format using *ALPHALIST. Each numbered slot is presented as a separate text entry field. Commonly used for unaided recall questions where the respondent lists reasons, brands, or items one by one. Use *MANDATORY on a response slot to force the respondent to fill in at least that entry before advancing.

Captures multiple numeric values in a fixed-label list format using *NUMLIST. Each numbered slot has a predefined label and accepts a single numeric entry. Commonly used for expenditure breakdowns, allocation questions, or any scenario where the respondent must enter a number against each of a fixed set of categories. Use *MANDATORY on any slot to force an entry for that row. Use sumof[] to total all entries or valueof[Qx.n] to access a specific slot.

Captures a calendar date from the respondent using a date picker. The response is stored internally as an integer in YYYYMMDD format (e.g. 20260908 for 8 September 2026). Use datevalueof[] to extract the year, month, or day component individually for use in come-logic, check conditions, or validation rules.

Captures a time value (HH:MM) from the respondent using a time picker. The response is stored in HH:MM format. Commonly used to capture daily routine times (wake-up, sleep, commute) or to record interview start and end times for duration measurement. Use timediffof[] to calculate the elapsed minutes between two *TIME questions.

CAPI-only question type that activates the device camera and captures a photo directly within the survey. The captured image is stored as a file reference attached to the submission. Commonly used for shelf audits, outlet photos, product visibility checks, or any fieldwork task requiring visual evidence. No scripting expression is available as the response is an image file, not a numeric or text value.

Captures a list of numeric entries where one designated slot acts as the enforced total of all other entries. Each category slot accepts a numeric value with optional *MIN/*MAX range constraints. The Total slot is marked with *NMUL to make it exclusive and auto-calculated — the respondent cannot edit it directly. The system validates that the category entries sum correctly to the Total slot value before the respondent can advance.

A single-response question rendered as a text field with autocomplete suggestions. Suitable for large option lists (brands, cities, products). Stored value is the option code, identical to a standard *SR.

A single-response question rendered as a dropdown/select box. Functionally identical to type 1 (*SR); TYPE:DROPDOWN only changes the UI presentation. Preferred for long option lists.

A *GRIDSR variant where columns are numeric scale points (e.g., 0–10 for NPS). Each row stores the selected scale value. Supports maxvalueof[] and maxvalueindexof[] for identifying top-rated items.

Best-Worst Scaling exercise where the respondent selects the most and least important item from rotating attribute sets. Stored per-task. No direct scripting expressions are supported.

CAPI-only type that captures the device GPS coordinates (latitude and longitude) at the point the question is reached in the interview. Coordinates are stored as metadata attached to the submission. When two *GPS questions are placed at different points in the script — typically one at the start and one at the end — the system automatically calculates the distance (in metres) between the two captured locations. This distance is used in geo-validation reports to detect whether the interviewer moved significantly during the interview, which may indicate a data quality issue.

Groups multiple sub-questions onto a single screen. Each sub-question has its own label and is referenced independently in expressions. Useful for collecting related data in one interaction.

Displays static text, instructions, or piped content to the respondent without capturing a response. Used for section introductions, consent text, or mid-survey messages.