Fast responses

This rule is necessary to filter out cheating Tolokers who complete tasks too quickly and carelessly. You can also use it to provide protection against robots that can distort the final results in the pool.

When to use

Restrict the pool access for Tolokers who respond too quickly to:

  • Restrict access for Tolokers who cheat in their responses. In this case, set the time required to complete a task suite when giving random task responses.

  • Provide anti-robot protection. In this case, set twice as little time for task suite completion.

To estimate the time required to complete a task suite:

How to configure

Recent task suites to useThe number of recent assignments submitted by the Toloker.

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

If the field is filled in, the corresponding number of task suites is used. The rule takes into account the task suites from both this pool and other pools where this field is filled in.

To learn more about how this field works, go to Parameter "Remember values".
Minimum time per task suiteThe task suite completion time (in seconds). Everything that is completed faster is considered a fast task suite response.

A condition for performing the action in the then field:

  • number of task suite responses — The number of the Toloker's recent task suite responses (less than or equal to the number in the Recent task suites to use field).

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

To add multiple conditions, click .


Action to perform for the If condition:

  • assign skill value — Assign a fixed value to the Toloker's skill.

  • accept all assignments from this Toloker in the pool — Requires the manual review option to be set.

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

  • suspend — Suspend the Toloker'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 Toloker's responses is not saved after the ban is lifted. The skill level is calculated based on the new responses.


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 Tolokers who complete tasks too quickly.

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


The assignments submitted by banned Tolokers will be taken into account if you don't reject them using manual review. They can be reassigned by setting up the Recompletion of assignments from banned users rule.

Blocking for fast responses

Correct settings
Incorrect settings

A Toloker 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 Toloker 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.

For developers


What is the right time limit for the task completion?
Should I create a skill for every pool?
Can I use a skill beyond a particular pool or project and apply it to other projects as well?
Is the time specified per task suite in the fast response settings?
How can I ban a Toloker and reject all their responses?
Contact support

Last updated: July 26, 2023

Getting started
Important tips
Useful recommendations
Working with Toloka
Project analysis
Toloka settings
Task interface
Template Builder
HTML/CSS/JS editor
Help and support