Reviewing labeled assets
This page explains how reviewers can access and review labeled assets within a configured workflow.
For an overview of how workflow steps and transitions work, refer to the Workflow Configuration page
How assets reach the review step
When a workflow includes a review step, labeled assets can automatically move to it:
- After completion of the Labeling or a prior Review step
- Based on configured rules (e.g., random sampling)
Once transitioned, the asset status changes to the review step and becomes available for reviewers assigned to that step.
How to get assets to review
As a reviewer, you can access assets in two ways:
1. Start Reviewing (Automatic Assignment)
Click Start reviewing.
Kili automatically serves you the next asset based on:
- Assignment rules
- Prioritization settings
- Workflow configuration
This is the fastest way to process assets in queue.
2. Search and select manually
You can manually search for assets using filtering options (status, priority, author, metadata, external ID etc.) and open the one you want to review.
This approach is useful when:
- You need to review a specific subset
- You are investigating a particular case
Reviewing assets outside the sampling rules
If random sampling is enabled, some labeled assets may not automatically move to the review step.
If you still need to review one of these assets:
- Open the asset
- Click Take for review
The asset will move into the review step and become reviewable.
Submitting a Review
Once reviewing an asset, you can:
Review
Click Review to submit your review.
- You may edit annotations before submitting
- A new label is created as part of the review step
The asset will then move to the next step defined in the workflow.
Send Back
Click Send back to request corrections.
Before sending the asset back, you can create issues to explain what needs to be fixed:
- Annotation-level issues – attached to specific annotations
- Global issues – related to the asset as a whole
This helps the corrector clearly understand what must be updated.
Once sent back, the asset moves to one of the previous steps, according to the workflow configuration, so it can be corrected by the responsible user.
Updated 5 days ago