Become a certified partner

To become a certified partner:
  1. Make sure you meet all certification requirements:
  2. Fill out the application form and wait for a response from the Toloka expert panel.

If all the aforementioned conditions are met and the Toloka expert panel has no issues with the skills provided, the Toloka team confirms your certification and you'll find yourself in the list of certified partners.

General certification conditions

Scalability

Toloka is growing and developing rapidly. New features and functions are being added, and each day we see hundreds of new users and dozens of new requesters joining. We want our partners to maintain high quality standards for responses, attract new requesters, and enhance collaboration with existing ones. When evaluating this indicator, we take into account the amount paid to performers for completed tasks or the amount of rewards. By the time you apply for partner status, it must be at least $500 over the past year.

Project rating

Toloka is a two-way platform. We value user opinions about the tasks they complete and about their interaction with task requesters. That's why we believe that a project's rating in Toloka is one of the main indicators of a requester's competence. The project rating is the total score given by performers in four categories:

  • The intention to complete similar tasks.

  • Whether instructions are easy to understand.

  • Task interface usability.

  • Communication with the requester.

We expect the average rating of projects launched by a partner over the past month to be no less than 4.6 points.

There are no widespread complaints

Toloka is based on the crowdsourcing principle. This means that hundreds or thousands of performers may complete your task. It's important to us that requesters post tasks responsibly. Toloka partners must be able to:

Make sure our support team doesn't receive a large number of complaints from performers about technical errors in the tasks you post, unfair rejection of responses, lack of feedback, or anything else. We consider the number of complaints to be large if we receive more than 10 complaints per month and find at least 80% of them justified.

Guidelines for tasks

In Toloka, you can publish any tasks that require analyzing or creating content. It's important that your tasks meet the terms and conditions of the Requester agreement. Our partner warns a requester that a task isn't appropriate for Toloka if the task:

  • Involves creating or viewing illegal materials.

  • Is aimed at advertising and promoting websites (for example, the performer has to follow links to specified websites or enter specific search queries, view advertising materials, or leave a review or comment on websites).

  • Implies certain actions in social networks (for example, the performer has to post, distribute and evaluate posts, participate in polls, or make comments).

  • Contains personal data of third parties or grants them access to a user's account in Toloka.

If a task requires special software, get the Toloka administrator's approval.

Compliance with recommendations

Requesters can always count on support, assistance, and friendly advice in Toloka. Our administrators check each project once it's launched, detect errors, and give recommendations for configuring and improving the project. We hope that projects created by partners won't contain technical errors and inconsistent quality control rules, or run without filters.

We expect Toloka partners to follow our recommendations:

  • Task content. To achieve better results, try to divide a large task into several simple ones and create separate projects for each project stage. If a task is too complex and cumbersome, it takes longer to complete and costs more and it's more difficult to ensure high quality and consistency of responses.

  • Task interface. Make your task interface simple and user-friendly, use keyboard shortcuts and response validation. Check the performance of projects and their display on computer and mobile device screens. Use the sandbox to tune a task.

  • Instructions. Make sure your tasks have clear instructions. Describe all possible situations the performer may face. Use concise wording and simple sentences. Add pictures and screenshots with examples. Use lists and formatting to make the text easier to read. If you review completed assignments using non-automatic acceptance, list the evaluation criteria.

  • Selection of performers. Create a training pool and a test to select performers. Assign them skills depending on whether their responses are correct.

  • Task price. Set a fair price: the more complicated the task is and the more time the performer spends, the higher the price should be. Use dynamic pricing to motivate diligent performers.

  • Time for task completion. Allow enough time for completing tasks. Rushing results in lower quality. So make sure performers have sufficient time.

  • User filters. Make sure to specify the language of the task instruction and text using filters. Add a filter by skill and the Speed/quality balance slider so that only performers with a high rating can participate in the project. For tasks to be completed in mobile apps, set the Client = Mobile Toloka filter.

  • Quality control. Choose the optimal set of rules for each project. When quality control is set up correctly, you get more accurate responses. You can also disable tasks for performers who make too many mistakes, submit responses that don't match the majority opinion, or respond too fast.

  • Staying in touch with performers. Proper communication with performers keeps them interested in the project and lets you quickly detect any issues with the tasks. Answer questions in private messages.