Step 1 of 5
Understanding Annotation
Learn the fundamentals of data annotation — tasks, roles, actions, and how to communicate with the team.
Welcome to Data Annotation
This guide will walk you through the fundamentals of working on annotation tasks. Whether you're brand new to data annotation or just new to this platform, read through each section before starting your first task.
01What Is Data Annotation?
Data annotation is the process of labeling, rating, or improving information so that AI systems can learn from it. Think of it as quality work done by humans to help machines understand the world better.
Small, individual pieces of work that you complete one at a time. Each task has clear instructions and a defined scope.
Groups of related tasks with a shared goal — like improving a chatbot's answers or evaluating AI-generated code. In many projects, contributors focus on one active task at a time.
02How Tasks Are Assigned
Platform-specific: The screenshots and workflow below are from the annotation-platform-henna platform. The core concepts (task queues, claiming, Start Tasking) apply broadly, but the exact UI and steps may differ if you are working on a different tool.
Tasks are assigned to you based on your skill level and the projects you are qualified for. When a task is ready for you, click the Start Tasking button to begin working on it.
The Tasks section in the left sidebar gives you a full view of your assigned and available work across all projects. Click it to open the task management area.
Inside the Tasks view, you will find two areas: My Tasks (tasks you have claimed or that were sent back to you) and Available Tasks (the shared queue you can browse and claim from).
From the dashboard, you can also click Browse Tasks below any project card to open a quick-access panel showing pending tasks for that specific project.
About task timing
Each task type has a set time allocated to it, defined by the project. This is the amount of time you are expected to spend on that task — and it also determines your pay for completing it.
Tasks are matched to your expertise level — it is normal not to see certain task types immediately.
03The Two Roles: Attempter & Reviewer
Every task goes through a two-step pipeline. Two different people work on each task — one after the other.
You are the first person to see the task. You read the instructions, complete the work, and submit your response. You are responsible for the first version.
A second person checks the attempter's work. They look for quality issues, make corrections if needed, and give a final approval or revision.
Task Pipeline
You may be assigned as an attempter on some tasks and as a reviewer on others, depending on the project and your qualifications.
04Basic Actions in the Platform
There are three core actions you'll use on every task:
Start Tasking
Click this to begin a work session. Your next assigned task will open right away.
Submit Task
When you have finished a task and are confident in your work, click Submit to send it forward. Once submitted, the task moves to the next step in the pipeline.
Release (Unclaim)
If you receive a task that you are not confident completing — for example, it requires knowledge you don't have — use Release to send it back to the queue so someone else can take it.
Save
Saves your current progress without submitting. Use this before closing the page if you need to take a break.
05Instructions & Learning Materials
Platform-specific: How and where instructions are delivered varies by platform. On annotation-platform-henna, guides and courses are accessible from within each project. On other tools (Feather, etc.), instructions may appear differently — always check your project's onboarding materials for the exact location.
Each project comes with its own set of instruction documents and sometimes short tutorials or courses. These explain exactly what is expected from you.
Critical — Read Before You Start
Always read the project instructions before starting your first task. Not reading them is the most common reason for poor-quality work and failed reviews.
Instructions Will Tell You
- What the task is asking you to do
- How to format your response
- What counts as a good or bad answer
- Any specific rules for that project
If something is unclear, re-read the instructions before asking for help. The answer is usually already there.
06Slack — Team Communication
Slack is the app we use to communicate as a team. Think of it like a group chat, but organized and built for work. It is where you will receive announcements, ask questions, and stay up to date with what is happening across projects.
Getting access
Once you join the team, you will typically receive an email invitation. Open the link, create your account, and follow your project onboarding instructions. Setup details may vary by team. You do not need to download anything right away — Slack also works in your browser.
Channels
Inside Slack, conversations are organized into channels. Each channel is a separate space dedicated to a specific topic, so discussions stay structured and easy to follow.
General channel
A shared space for all team members across projects
Project announcements
Automated updates and important notices for a specific project
Project general
Open discussion for everyone working on a project
Reviewers channel
Private channel for reviewers only
You do not need to read every message in every channel. Just keep an eye on the ones relevant to your work, and check back regularly for any important announcements.
Screenshots are taken directly from the platform. Diagrams are illustrative — your workspace may look different.