Disposition Codes
Every participant in a field has a so-called disposition code which describes their status in the field. This records, for example, whether participants have already been invited and whether they have already begun the survey or completed it. The field statistics, which builds on these statuses, gives you extensive information on the status of your field, i.e. your survey, at any time. The disposition codes have two digits. The areas are defined as follows:
10s: before the survey
20s: during the survey
30s: after the survey
The disposition codes are mutually exclusive: Any person can have only one disposition code at any given time. Therefore, the status variable can only assume one of the above characteristics at a time. The majority of disposition codes is assigned automatically and changed depending on the progress of the survey.
Disposition code | Status | Comment |
---|---|---|
10 | Consent seen | This status is set when an anonymous survey is started and the consent form is displayed, but the participant does not give consent or reject the consent prompt. |
11 | Not yet invited | The participant has not yet been invited. |
12 | Invited | The link has not yet been used. |
13 | Inactive | Only on EFS Panel installations: If you change the panel status |
14 | E-mail could not be delivered | Assigned automatically if the mail server does not accept a mail repeatedly or if it is not possible to connect to the mail server at all repeatedly. Per default, four attempts are made. The number can be configured. |
15 | Cannot be reached | This code is used in order to mark participants that cannot be reached. You will be notified that mails could not be delivered by a means outside the EFS system:
In all of these cases the assignment of the code must be done manually. You can use the trim participants function. |
16 | Reserved 1 | Corresponds to status 12, but can be customized and used for further differentiation. |
17 | Reserved 2 | Corresponds to status 12, but can be customized and used for further differentiation. |
18 | Custom unavailable 1 | Corresponds to status 15, but can be customized and used for further differentiation. |
19 | Custom unavailable 2 | Corresponds to status 15, but can be customized and used for further differentiation. |
Only in anonymous projects: 20 | Not yet started | The first page of an anonymous project has been called or delivered (pop-up window) and cancelled. To find out what evaluation options this special disposition code involves |
21 | Currently responding | The participant is answering the survey at the moment.
|
22 | Suspended | At least 30 minutes of inactivity have been observed.
The value is customizable. Please ask the Tivian support team, if you want to customize it. |
23 | Resumed | The survey has been resumed after an interruption. |
31 | Completed | The survey has been successfully completed. |
32 | Completed after break | The survey was interrupted during its course, but has been resumed and successfully completed. |
33 | Custom completed 1 | Corresponds to status 32, but can be customized and used for further differentiation. |
34 | Custom completed 1 | Corresponds to status 32, but can be customized and used for further differentiation. |
35 | Rejected at login (quota full) | Is set for respondents in personalized projects who want to use the link from the invitation mail to log into the survey after a quota has been closed. |
36 | Rejected (quota full) | Status 36 and 37 are set in a project with quotas when an intermediate final page has been reached. The survey administrator can use these codes to mark respondents as rejected (i.e. screened out by quota; there are already enough participants with the respective features) or screened out (= unsuitable). The status to be set is manually specified by the administrator at the intermediate final page. |
37 | Screened out | Status 36 and 37 are set in a project with quotas when an intermediate final page has been reached. The survey administrator can use these codes to mark respondents as rejected (i.e. screened out by quota; there are already enough participants with the respective features) or screened out (= unsuitable). The status to be set is manually specified by the administrator at the intermediate final page. |
38 | Custom screen out 1 | Corresponds to status 37, but can be customized and used for further differentiation. |
39 | Custom screen out 2 | Corresponds to status 37, but can be customized and used for further differentiation. |
40 | Custom screen out 3 | Corresponds to status 37, but can be customized and used for further differentiation. |
41 | Quota full | If a quota is full, this status will be assigned to all participants, who match the quota condition, but nevertheless have not started with the survey yet. If one of these participants tries to log in, then he will be rejected and the disposition code will be set to 35. |
42 | Consent rejected | The processing of personal data (GDPR) was not agreed. |
43 | Personal data deleted | The processing of personal data (GDPR) was initially agreed. After participation in the survey, the consent was withdrawn and the personal data deleted. |
Access to the disposition code of the survey participants is protected with the “show_dispcode” right. If you hold read rights to “show_dispcode”, you can view, use, or export the disposition code in various places of EFS.
© 2024 Tivian XI GmbH