For the complete documentation index, see llms.txt. This page is also available as Markdown.
Task Queue
Assign, claim, prioritize, filter, and start individual work.
Task Queue is where workflow state becomes executable work. What a user sees depends on the project, stage, role, assignment, filters, and item status.
Before you make the change
Confirm the intended workflow stage and role.
Know the assignment strategy and priority policy.
Define how unassigned, skipped, rejected, invalid, or reopened work is handled.
Task Queue with stage and action controls
Read the queue as an operating view: stage and filters define the population; assignment and priority define order; task actions change ownership or state.
Understand the product behavior
The Task Queue is a two-pane operational surface.
Stage rail
one row per visible stage in the bound workflow;
tinted stage-type icon and stage name;
copyable stage identifier;
live item count;
selected stage persisted in the URL.
The Project entry stage is not shown as a work queue even though it anchors routing.
Task table
select checkbox;
inline numeric Priority editor for managers;
media thumbnail and short task ID;
derived Status;
Assigned to;
Actions.
The default order is highest priority first. The explicit row action is Open, which launches the correct native editor in the Workbench while preserving queue scope. Assign and Release live in the Assigned-to dropdown. Moving work between stages is a bulk action, not a casual per-row shortcut.
When one or more tasks are selected, the bulk action bar offers Priority, Move, Unassign, and Assign. Bulk Move first calculates a plan and asks for confirmation.
Data Groups appear as one mixed work item with group name, tile count, aggregate status, assignee, and priority. Their member tiles do not appear as duplicate tasks.
Manager/admin users can view and manage all stage queues according to permission. Member-family users see only stages for which their annotator/reviewer position is eligible and only work that is assigned, claimable, or intentionally visible as unassigned.
Task queues answer operational questions:
What work is waiting at each stage?
Which tasks are unassigned?
Who owns the oldest or highest-priority items?
Which modality or dataset is causing a backlog?
How much work was rejected back to annotation?
Operate the individual backlog
1
1. Select the stage
Open the queue population that corresponds to the current responsibility.
2
2. Apply filters
Resolve status, source, assignee, modality, issue state, or other cohort criteria.
3
3. Review priority and ownership
Confirm the order and whether items are unassigned, assigned to self, or assigned elsewhere.
4
4. Assign or claim
Use the configured operating model; avoid side-channel assignment.
5
5. Start the task
Open the Workbench and confirm the same project, stage, and item context.
6
6. Reconcile after action
Check the task moved to the expected owner or next stage.
Decisions that affect production
Decision
Production guidance
Self-claim
Useful for elastic workforces when stage eligibility and fairness controls are clear.
Manual assignment
Useful for specialists, calibrated cohorts, or explicit ownership.
Priority
Document the business rule and review for starvation or hidden overrides.
Unavailable action
Check role, stage, assignment, selection, task status, and processing state.
Continue the operating flow
Use saved queue views for recurring operational questions.
Inspect Batch Queue when processing context is missing.
Escalate stalled or orphaned cohorts to the workflow owner.
