The deferred term
tag specifies a point in the survey where respondents should be terminated, rather than have them terminate immediately. This allows the survey to collect additional data before terminating respondents.
app config
deferred term: end_of_screener
start group: SCREENER
GEN. Are you...
type: radio
1. Male
2. Female
3. Rather not say {term: y}
AGE. How old are you?
type: integer
range: 0-99
termif: $QAGE<18
end group: SCREENER
label: end_of_screener
show text: INTRO
text: Congratulations, you have qualified for our survey!
In the example above, respondents who select "Rather not say" at QGEN and/or who enter a number less than "18" at QAGE will terminate after the screener, before seeing the "Congratulations" message.
Details
- The
deferred term
point must be defined in theapp config
section of the survey. - The
deferred term
point can be a label, page label, question, table, or group name. - The
deferred term
will apply to all terminations unless specifically overridden. - If a terminate is placed after the deferred termination point specified in the
app config
, it will result in an immediate termination.
Tip! If only some of the defined terminations should be deferred until a later point in the survey, it may be easier to use the term after
method.
Additional examples
Immediate termination using 'goto: term'
While deferred termination is in effect, you can still immediately terminate a respondent by using goto: term
. Either question below will terminate immediately if the respondent meets the specified condition.
app config
deferred term: end_of_screener
GEN. Are you...
type: radio
1. Male
2. Female
3. Rather not say {term: y} {goto: term}
AGE. How old are you?
type: integer
range: 0-99
termif: $QAGE<18
goto: term
condition: $QAGE < 18
Comments
0 comments
Please sign in to leave a comment.