Request details

7 min

A request is one annotation order inside a project: a set of scenes, an annotation instruction, a workflow, and a workforce. The request page is where you follow its progress and act on it.

Prerequisites

You open a request from the Requests list on the project's Overview tab. You need the workspace role Annotation manager, Project manager, Developer or Admin. See Roles & permissions.

The tabs Summary, Inputs, Tasks and Workforce are shown to all of these roles. Which phase tabs you see, and what you can do inside each tab, depends on your organization's request role, shown in the page header:

Request role	What it means
Producer	Your organization produces the annotations. You see every phase and manage tasks and workforce
Owner	Your organization ordered the request. You see progress and the client-facing phases. In Tasks and Workforce you see only what belongs to those phases
Client QA Contributor	Your organization takes part in Client QA. You see the Client QA phase and the inputs sampled for it

See Request Access Management for how request roles are assigned.

What the page shows

The header shows the request name, the project it belongs to and your organization's request role.

Below the header, one tab per area:

Tab	What it is for
Summary	Progress across the workflow, productivity and quality estimates, processing errors
Inputs	Every scene in the request, its workflow stage and task state, with batch actions such as send for review, skip correction and delete
Tasks	Every task created in the request. Assign, reassign and expire tasks, filter by member, state or date
Workforce	Who works in the request, their workflow stages and how tasks are allocated to them
One tab per phase	The phase's progress, decisions and inputs. Which phases you see depends on the workflow, see Workflow phases
Review Monitoring	Classic Workflow only. Round-based review statistics. Classic workflows were deprecated in September 2025 and cannot be chosen for new requests

Start production

Automatic allocation decides whether the platform hands out tasks on its own. Click Activate automatic allocation at the top of the page once the request is configured and the workforce is added. From then on, workforce members with automatic allocation get tasks according to their workflow stages, and a task becomes assigned to them when they pick it up. Tasks you assign manually in the tab work regardless of this setting: members can see and work on them even when automatic allocation is off. Inactivate automatic allocation stops the automatic distribution; manually assigned tasks are not affected.

The button is disabled until you have completed the request configuration. If it stays disabled, contact your Kognic contact. See Guide: Automatic task allocation for how distribution works.

Actions

The other buttons at the top right of the page. Producers see all of them; other roles see the ones their request role allows.

Action	What it does
Settings	Opens Request settings: name, workflow, request roles, annotation instruction and phase settings
Use as template	Creates a new request in the same project with the same input type, workflow and error type groups. You can include this request's scenes and reuse its instruction. See Guide: Create a request
Reuse scenes...	Copies this request's scenes into another request with the same scene type. Scenes already in the target are skipped. Pre-annotations are not copied
View scene addition errors...	Lists scenes that could not be added to the request and why: input creation, scene creation, pre-annotation or health check failed
Archive request...	Hides the request from the project's request list and from My Tasks. Can be undone with Unarchive request
Copy request UUID	Copies the request's identifier, for API use or support

Common questions

If your organization is not the producer, the Tasks and Workforce tabs are limited to the tasks, members and workflow stages of the client-facing phases, such as Client QA. The production phases and their tasks belong to the producing organization. In Workforce you also see only members from your own organization and from organizations your organization has workforce access to, see Workforce access. See Request Access Management.

You see only the phases your request role has access to. Owners see client-facing phases such as Client QA; producers see all. On the Summary tab, phases you cannot see are folded into the Production group as two rows without phase names, Not started and Ongoing.

It was replaced by the Requests list on the project's Overview tab, which also filters by status, active phase and Client QA verdict.

Summary, where to start when you open a request

Workflow phases, what each workflow phase tab contains

Request settings, the configuration behind the request

Guide: Create a request, how a request is set up from the start

Request details

Prerequisites

What the page shows

Start production

Actions

Common questions

Why do I see only some tasks and workforce members?

Why is a phase tab missing?

Where did the Annotation Requests tab go?

Request details

Prerequisites

What the page shows

Start production

Actions

Common questions

Why do I see only some tasks and workforce members?

Why is a phase tab missing?

Where did the Annotation Requests tab go?

Related