Fast responses

This rule is necessary to filter out cheating performers who don't pay attention to what they're doing and complete tasks too quickly. You can also use it to provide protection against robots that can distort the final results in the pool.

If you need additional protection from robots, use captchas.

When to use

Restrict the pool access for performers who respond too quickly to:
  • Suspend access for performers who cheat in their responses (in this case, set the time required to complete a task suite when giving random responses).

  • Provide protection from robots (in this case, the time for completing the task suite should be 2 times less).

To estimate the time required to complete a task suite:

Rule settings

Field

Overview

Recent values to use

The number of recent assignments submitted by the performer.

To calculate pages from all project pools, fill in the field in the rule for each pool.

If this field is not filled in, the calculation includes only task suites that contain tasks from the pool to which the rule applies.

Minimum time per task suite

The task suite completion time (in seconds). Everything that is completed faster is considered a fast response.

If

A condition for performing the action in the then field:
  • number of responses — The number of the performer's recent responses (less than or equal to the number in the Recent values to use field).

  • number of fast responses — Allowed number of fast responses (out of the recent ones).

To add multiple conditions, click .

then

Action to perform for the condition:

  • assign skill value — Assign a fixed value to the skill.

  • accept user's answers — Requires the non-automatic acceptance option to be set.

    Useful if the performer completes most tasks well. Example: The Toloker completed more than 80% of the tasks correctly and you are satisfied with this result. The rule will work automatically and accept all responses in the pool.

  • suspend — Suspend the performer's access to the pool for the specified number of days. Only the requester can view the reason.

  • ban — Block access to the project or all of the requester's projects for the specified number of days. Only the requester can view the reason.

    If access to tasks is blocked temporarily (for example, for 7 days), the history of the performer's responses is not saved after the ban is lifted. The skill value is based on new responses.

Examples of rules

Task: you noticed that the pool closed too quickly and the final result was unsatisfactory. To prevent this from happening again, you decided to filter out performers who complete tasks too quickly.

Examples are provided for simple classification. There are 10 tasks per page.

Attention. Responses submitted by the banned user before the ban won't be automatically rejected and will be paid for. However, they can be reassigned by setting up the Recompletion of assignments from banned users rule.
Blocking for fast responses


A performer who completes a task suite in less than 10 seconds will be banned and won't be able to access your tasks.

Suspension in the pool for fast responses


A performer who completes two task suites in less than 20 seconds is suspended from accessing the pool and can't complete your tasks for 10 days.

Troubleshooting

What is the right time limit for the task completion?
Try completing the tasks yourself. Ask your colleagues and friends to complete them. Find out average completion time and add 50% to it.
Should I create a skill for every pool?

It is better to use one skill in a project. You can choose the way to calculate the skill:

  • 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.

Can I use a skill beyond a particular pool or project and apply it to other projects as well?

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.

Is the time specified per task suite in the fast response settings?

Yes, the fast response settings specify the time per task suite.

How can I ban a user and reject all their responses?

You can't automatically reject the responses of a banned performer.

But you can do it yourself if you want. When downloading the results, select the option Exclude assignments by banned users to delete the responses of performers who were banned at the moment of downloading. You can also forward all the assignments from banned users to other performers using the Re-completion of assignments from banned users rule.