Read the operator leaderboard: output, yield and cost per operator

The board is a read-only aggregation over all logged history — there is no built-in week or month window, so period questions belong in the labour analysis pivot, filtered by date, rather than here. It also knows nothing a log does not: an operator whose work is not logged simply is not on it.

The honest uses are comparative and procedural: spotting the station whose throughput lags its peers, the operator whose yield says the training did not land, the scrap pattern that follows one machine rather than one person. Pair it with the operator skills matrix — a low number from a Trainee on a hard station is a schedule finding, not a person finding. The dishonest use — monthly bonuses read straight off the ranking — teaches the floor to game the counts within a week.

The menu is missing — the Work Orders & Routing feature is off; the leaderboard exists only inside that layer.

An operator is absent from the board — no labour log carries their name; check they clock in as themselves rather than under a colleague's badge.

Numbers look inflated for one person — check for hand-typed logs alongside terminal ones, and whether their logs carry another station's easy operations.

The board disagrees with the payroll batch — the board sums all history while a batch froze one period; compare periods in the labour analysis, not here.