A metric can be consistent and still measure the wrong thing—or omit the conditions that produced the result.
A score looks objective because it has decimals, thresholds, and trend lines. But the score may combine customer bias, equipment failures, difficult assignments, protected leave, staffing shortages, or work the system does not measure. The useful question is not whether the score exists. It is what the score actually means.
The Missing-Context Problem
Two workers can receive the same productivity target while one has functioning equipment and a stable territory and the other spends hours resolving system outages or handling harder assignments. A comparison that ignores those conditions may be precise and misleading.
Interrogate The Metric
A performance score may combine speed, quality, customer ratings, attendance, acceptance rate, idle time, sales, location, or other inputs. Identify the formula or available description, weighting, comparison group, measurement period, and what happens when data are missing. A metric can be consistent while still measuring the wrong thing. Look for changes in the metric after a new vendor, policy, accommodation, leave, territory, assignment, or staffing pattern.
Capture Context The System Omits
Productivity data may not account for equipment failure, training, disability-related limitations, protected leave, safety compliance, difficult assignments, customer bias, or work performed outside the tracked channel. Preserve specific context rather than relying on a generalized objection to technology. Supervisors may override, annotate, or selectively enforce scores. The exception and review process can reveal the true decision system.
Connect Output To Legal Harm
The same score can affect multiple rights: unpaid time when workers perform hidden tasks to meet quotas, discrimination when biased inputs shape outcomes, accommodation when limitations are ignored, retaliation when scrutiny increases after a complaint, or safety when speed pressure discourages compliance. Each underlying right belongs in its own analysis; the technology page supplies the common operational map.
Records Behind The Score
- Score definitions, dashboards, screenshots, and trend data.
- Raw input records where available.
- Thresholds, warning rules, and automated notices.
- Override, annotation, appeal, and human-review records.
- Assignment, territory, equipment, staffing, leave, and accommodation context.
- Pay and schedule changes tied to the score.
Where The Analysis Can Break Down
- A poor score can reflect real performance.
- Correlation between a complaint and metric decline requires examination of intervening facts and system changes.
- Vendor secrecy may limit pre-litigation access.
- Automated scheduling and pay rules vary across jurisdictions and contracts.
What To Do Next
- 1. Save score history and definitions, not only the final warning.
- 2. Record known input errors and correction attempts.
- 3. Compare assigned conditions, not just employee outcomes.
- 4. Route complaint-related changes to Retaliation.org and wage effects to the wage center.