User Manual
Help Center/User Manual/Labor: How Performance Numbers Are Worked Out

Labor: How Performance Numbers Are Worked Out

Last updated 2026-11-01

How Labor works out achievement and on-time rates: each kind of work is judged against its own due time with its own denominator, full records are counted with nothing cut off, and the dashboard shows how many days in a row someone has been below target.

Performance numbers only feel fair when everyone can see how they are worked out. This page explains the rules behind the achievement % on Labor → Operators and the needs-coaching list on Labor → Dashboard — the same rules for every operator, every warehouse, every day.

On-time rate: each kind of work against its own due time#

  • Each kind of work is judged against its own due time. The on-time rate for a kind of work is: of the finished tasks of that kind that had a due time, how many finished by it. Kinds are never mixed into one shared denominator.
  • A person who does several kinds of work gets a clean rate per kind — doing a lot of one kind does not dilute or inflate the rate of another. The overall rate only adds up the kinds that have due times, task by task.
  • Some kinds of work have no due time at all (receiving, for example). Those show no on-time rate — an empty space, not a zero and not a guess.
  • Nothing is cut off in the background: the full record for the period you pick is counted, however long the list gets, so a busy month cannot quietly drop people or tasks from the numbers.

“Days below target in a row” on the needs-coaching list#

  • The dashboard’s needs-coaching list shows how many days in a row an operator’s achievement has been below the target line — counted day by day backwards from the day you are looking at.
  • The count stops at the first day the operator was at or above target — and also at the first day with no record at all. A day off or a day with no standard set does not stretch the streak, and does not erase it either; it simply stops the counting there.
  • New starters get a fair runway: during the first 14 days after joining, an operator does not appear on the needs-coaching list at all. Their numbers are still recorded and visible — they are just not judged against the target yet.
Read speed and quality together. Achievement and on-time rates say how fast the work went; errors and damage sit on the same operator record so a fast-but-messy pattern is visible at a glance. A coaching conversation goes better with both halves on the table.

Docklify features used in this article#

  • Per-operator achievement and quality record — Labor → Operators (/labor/operators)
  • Needs-coaching list with days below target in a row — Labor → Dashboard (/labor/dashboard)
  • Engineered standards the achievement % is measured against — Labor → Standards (/labor/standards)