Skipped assignments
Restrict access to pool tasks for performers who skip several task suites in a row.
Performers can skip task suites that seem too large or complex and choose easier tasks. They get paid in the same way. For example, the performer is evaluating medical articles for whether they contain prescriptions, dosage, and mentions of specific medications. They might decide to skip long texts and label only short ones that take 10-20 seconds to read.
You can set up this rule to restrict performer access to a pool.
Before you enable skipping tasks, we recommend that you read the section Tips for designing tasks.
When to use
- Tasks are different in volume and performers might skip large tasks in order to only perform short ones.;
- Tasks must be performed in order and skipping tasks may affect the quality. In this case, don't forget to enable Keep task order.
- Don't use it if:
-
- There aren't very many tasks in the pools. For example, if a task is a survey on a single page and the performer skips this page, they will no longer be able to perform tasks in the pool, which means there is no need to ban them.
- Tasks are the same in volume.
- The task complexity can't be estimated, which means the performers won't be willing to skip tasks in search of easier ones.
Rule settings
| Field | Overview |
|---|---|
| If | A condition for performing the action in the then field:
|
| then | Action to perform for the condition:
|
| Field | Overview |
|---|---|
| If | A condition for performing the action in the then field:
|
| then | Action to perform for the condition:
|
Rule example
Task: you're conducting an opinion poll. For the results to be accurate, the performer must answer most of the questions.
-
A performer who skips 2 task suites in a row is restricted from accessing the pool and can't complete your tasks for 5 days.
If a performer skips 2 task suites in a row, all their responses will be accepted automatically.
With this setting, a performer who skips less than 2 task suites in a row is restricted from accessing the pool and can't complete your tasks for 5 days.
Troubleshooting
Calculate the skill for each pool separately. The current skill value is the value of the skill in the pool the user completed last. This option is convenient if:
The pools are intended for different groups of performers (for example, there are filters by city or country).
Pools are started one by one and you don't want to take into account the responses in the previous pools to calculate the skill in the current pool.
This calculation method is used by default when adding a quality control rule to a pool. For the control tasks block, leave the Recent values to use field empty.
Calculate skill based on all tasks in a project This option is good if the pools are small and you don't need to have skill calculated for each pool.
This option is available only for skills on control tasks. To use it, fill in the Recent values to use field in quality control rules in pools.
It is better to use one skill in a project. You can choose the way to calculate the skill:
Yes, of course — you can use the same skill for different projects. But most often, a skill is intended for a specific project. If the performer completes a certain task well, this doesn't mean that they will complete other ones successfully. Another disadvantage is that if you filter by skills that were set long ago, you will artificially limit the number of available performers.
Yes, unfortunately, this can happen. This is why we recommend that you offer a training task or exam before the main task. In this case, only those people who showed good performance at the previous stage are selected for the main pool.
If the user already got paid for the tasks, the money can't be refunded to you.
