Queue and editor
With thecontribute rung on a project you can open the Queue, claim or start the next task, draw and correct labels with the editor’s tools, save drafts, submit, and, when the pipeline routes a review task to you, accept, correct or reject someone else’s work. A Submit that records labels writes a commit under your name, and finishing a review writes one too. Both appear on the project’s Versions tab, on its Commits and branches page, so do not share an account or a credential.
Outcome
An annotator opens an assigned item, understands what must be labeled, does the work, and submits it without learning version-control vocabulary. A reviewer sees the previous and proposed labels, who or what authored them, and records a verdict that binds exactly what they looked at. External contributors need a visibly limited scope, a rung on the projects they work and nothing else. A plain member with no rung opens no project at all.Task flow
- Open Queue. The Tasks you can take list shows what you can take, and Start next takes the Next up row. To pick a task yourself, open its row to see its brief, then press Claim and open (Claim and continue when the row is your own draft). Take work from picks the stages that Start next and the list draw from: everything, the stages you tick, or nothing while you pause.
- The editor opens on the task’s Source with the taxonomy the project bound. Confirm the category list and the instructions before drawing.
- Draw or correct with the toolbar: cursor, brush, contour, threshold, 2D box, point, measure, 3D box. Drafts save as you go and survive a reload for seven days.
- Leave a comment on the task when your work departs from the instruction or from a model proposal. Comments anchor to the task and can be marked as needing attention.
- Press Submit. The session’s pending labels are committed first, then the task closes; a retry of the same press replays the same commit rather than writing a second one. A task submitted with no labels and no answers closes and writes no commit.
- Depending on the pipeline, your work goes to a review stage or straight on. A rejection comes back to you as a rework task.
If you release a task, skip it, or the lease runs out, the uncommitted events are checkpointed as a
handback commit and the task returns to the queue. Nothing you drew is lost, and nothing you drew is counted as finished.
What a reviewer sees
A review task opens the same editor on the revision the annotator submitted. The reviewer sees the source, every annotation at the hash it was submitted with, who authored each one (a person, a model Agent, or a correction), the bound instructions, and the comments on the task.
The reviewer’s verbs are accept, reject and correct per row, each bound to the annotation’s hash, and Accept all and finish for the task. A correction is the reviewer’s own edit during the hold; the corrected annotation is shown as corrected, not accepted. Finishing over a standing rejection needs a reason, closes the review and sends a rework task to the original annotator.
Next step
Read Release a dataset to create a Dataset Version from committed annotations.| Plans | All plans |
|---|---|
| Last verified | 2026-09-28 |