Introduction to BergFlow

BergFlow is BergAi’s annotation workspace. Teams use it to get through labelling work faster without letting quality slip.

This guide is for managers, reviewers, and annotators. It takes you from the invite email through delivery. It is not an engineering wiki.

The four objects

These names show up all over the product:

• Project. A long-lived container for a body of work. It holds the task template (input and output columns), guidelines and ground truth, and settings such as how many annotations a task needs and how long one should take.
• Batch. One upload of source data into a project (CSV or Excel, and a ZIP of images if you need one). Each row becomes a task.
• Task. One unit of annotation work. You open it, fill the output fields, and submit it for review.
• Delivery batch. A curated bundle of completed tasks you hand to the client. You can export it as CSV and, if you want, freeze those tasks as completed.

How work moves

Typical path: invite, then sign in, then project, then batch, then annotate, then review, then (optional QC), then delivery.

Who should read what

• New to BergFlow: start with roles and access, then layout and dashboard.
• Managers setting up work: projects, batches, teams, delivery.
• Annotators and reviewers: tasks and annotation.