Multi-group workflows

Overview

Multi-group workflows extend the standard multi-step review workflow with an additional layer: work groups. Instead of a single Label step feeding into a shared set of Review steps, a project is split into several work groups, each with its own Job Scope, its own Label and Review steps, and its own team assignments.

This is useful when different parts of your ontology require different expertise or different levels of quality control — for example, a specialized team reviewing one category of jobs more thoroughly than another, within the same project.

Core concept: work groups

A multi-group workflow is composed of one or more work groups, executed sequentially — one group's steps don't run in parallel with another's.

Each work group has:

• A defined Job Scope — the jobs it covers
• Exactly 1 Label step
• 0 to N Review steps
• Its own team assignments

For everything related to how Label and Review steps behave individually — sampling, reviewer assignment, statuses — see Workflow configuration; that content applies the same way inside each work group.

Scoping and send-back rules

• Each work group's Job Scope can be as broad or as narrow as needed, and scopes can overlap across groups when your ontology calls for it.

• Each Review step sends rejected assets back to exactly one step, set in Send back to. You can choose:

  • any previous step of the same work group;
  • the first step of any previous work group.

  By default, assets are sent back to the work group's Label step.

Team assignment & visibility

• Labelers and reviewers are assigned per step, within a work group — there's no default or inherited assignment across groups.
• Depending on your project's annotation visibility setting, users may see only annotations within their own group's Job Scope, or see other groups' annotations in read-only mode.
• In all cases, users can only create, edit, validate, or send back annotations within their own group's scope.

Example: reviewing a multi-section contract

Consider a document project where each contract is split into sections that call for different expertise and different levels of scrutiny:

• Work group "Clauses" — Job Scope: clause-type, obligation, defined-term. Labeled by a legal-trained team, with 2 Review steps given the importance of getting contractual language right.
• Work group "Signatures" — Job Scope: signature-block, date, witness. Labeled by an operations team, with 1 Review step.
• Work group "Appendices" — Job Scope: appendix-reference, attachment-type. 1 Label step, no Review step, since this content carries lower risk.

Each group runs its own Label → Review sequence, with its own assigned team, before the next group's steps begin.

Setting up a multi-group workflow

From the Workflow editor:

1. Click Add work group, then name the group in its card header.
2. In Labeling jobs, select the jobs the group covers. The row shows Any jobs when the group covers all jobs, or a count such as 3 jobs.
3. Configure the group's steps:
   • In the Label step, select labelers in Labeler.
   • Add Review steps as needed. In each one, select reviewers in Reviewer, then choose where rejected assets go in Send back to.
   • Set the share of assets sent to review in the sampling card between two steps.
   • To add consensus or honeypot to a step, open the step's … menu.
4. Repeat for each additional work group. Groups run in the order they appear.
5. Click Apply changes.

Group names, step names and sampling rates can be edited inline.