Lead

Who is moving, and who quietly stopped

Cohort progress by belt, with the conditions that flag somebody written down rather than left to whoever happens to be looking.

Book a demo
4
belts
White to Black
70%
exam pass mark
the same for everyone
3
flag conditions
written, not judged
Staff only
access
learner detail is role-gated

Cohort view

Progress by belt, at a glance

For each belt: how many people are in the cohort, how far through they are on average, and how many have finished. The written summary sits beside the numbers so a manager reads the pattern rather than reconstructing it.

Sample data/org/training

White

24 learners · 76% average

Yellow

18 learners · 63% average

Green

11 learners · 49% average

Black

4 learners · 31% average

Who needs attention

Falling behind is a written rule

A learner is flagged when they have not passed and any one of these is true. Printing the rule matters: a dashboard that flags people by an undisclosed method is one nobody argues with and nobody trusts.

1

Seven days without activity

The exam is not passed and nothing has moved for a week.

2

3 attempts, none passed

Three recorded attempts and no pass. More practice is not the answer here.

3

Under 30% after fourteen days

Enrolled a fortnight ago and less than a third of the way in.

Section-level analytics

Find the section that slows the cohort

How many people completed each section, and how long it took them. When a cohort stalls it is usually one section doing it, and an average across the whole course hides exactly that.

Sample data/org/training
Process mapping92% · 12 min
Measurement systems81% · 18 min
Capability analysis64% · 29 min
Hypothesis testing52% · 34 min

Who can open it

A staff surface, gated as one

The training view carries learner names and email addresses, so it is restricted by role rather than simply left out of the menu.

Two things this page is not

Exams are not timed. The pass mark is 70% and the clock is not part of the test.

Learning is planned by belt, not by job title. There is no role-based path, and the page does not suggest one.

See it run with your own team

Bring the process you use today. Thirty minutes is enough to see it as a governed project with the decisions recorded.

Book a demo

How SigmaForge governs the work