Skipped assignments

Restrict access to pool tasks for performers who skip several task pages in a row.

  1. Rule settings
  2. Rule example

Rule settings

Field

Description

If
A condition for performing the action in the then field:

  • task pages skipped in a row — The number of task pages skipped in a row.

then

Action to perform for the condition:

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

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

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

    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.

Field

Description

If
A condition for performing the action in the then field:

  • task pages skipped in a row — The number of task pages skipped in a row.

then

Action to perform for the condition:

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

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

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

    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.

Rule example

Suspending performer's access to the pool for skipping tasks


A performer who skips 2 task pages in a row is restricted from accessing the pool and can't complete your tasks for 5 days.