Productivity Monitoring as the Basis for Discipline: “The System Flagged Him” Is Not a Defense

“We told them about it in the handbook” is the line that does the least work in the lawsuit.

Productivity monitoring software — keystroke logging, screen capture at intervals, idle-time scoring, application-use tracking — has moved into small-business operations. A subscription is affordable, the vendor’s deployment is quick, and the handbook gets an updated paragraph notifying employees that “activity may be monitored.” The employer believes the notice did the legal work.

The break point is the moment the monitoring output gets used as a basis for discipline or termination. A remote employee is fired for “low productivity.” The employee is in a protected category — disability, leave from CFRA, pregnancy, age — or has recently engaged in protected activity. The plaintiff’s lawyer asks how the productivity number was generated, what the scoring algorithm weights, and whether the same standard was applied consistently across similarly situated employees.

At that point, the handbook notice is no longer the issue. The issue is whether the employer can articulate the criteria, prove consistent application, and identify whether any aspect of the scoring disproportionately disadvantages employees in a protected category. Under FEHA, a facially neutral practice with disparate impact requires job-relatedness and consistency with business necessity. Under NLRB doctrine, monitoring that chills protected concerted activity — employees discussing pay, scheduling, or working conditions — is its own exposure even in non-union workplaces.

The proof pressure is the unexplainable score. If the employer cannot explain how the number got generated, and cannot show that the standard was applied across similarly situated employees, the score becomes a credibility problem, not a productivity finding. The plaintiff’s pattern is to subpoena the vendor’s documentation and depose the manager who relied on it. The manager who answers “the system flagged him” is the witness who proves the case.

Disability accommodation runs through the same fact pattern. An employee with an accommodation that includes flexible breaks, intermittent leave, or reduced cognitive load on certain tasks will show up on a monitoring dashboard as low-output. Disciplining on the dashboard score, without re-running the accommodation analysis, is what makes the monitoring tool the cause of the failure, not the defense to it.

The corrective frame is not to stop monitoring. It is to separate the input from the decision. Monitoring outputs may be useful diagnostically. They are not standalone disciplinary records, and the moment a manager treats them as standalone is the moment the legal exposure crystallizes.

Looking at how the dashboard output enters the discipline chain — and where a manager could pause it — is the cleaner audit.

This post shares general information based on common patterns I see in California workplaces. It is not legal advice, does not create an attorney-client relationship, and outcomes depend on specific facts — no lawyer can guarantee a result. Past results do not guarantee or predict future outcomes. AI may have been used to create this post. All content reviewed by a CA attorney before publication. This post may be attorney advertising.