Use Case: HR and People Operations
Employee Monitoring Data in Performance Improvement Plans: Objective Evidence That Protects Both Sides
PIPs (Performance Improvement Plans) are legally sensitive documents — and wrongful termination claims often turn on whether performance issues were documented with objective evidence. eMonitor activity data provides the timestamped, system-generated records that transform a manager's subjective impression into verifiable workplace documentation.
7-day free trial. No credit card required.
What Is the Role of Employee Monitoring Data in a Performance Improvement Plan?
Employee monitoring data in a performance improvement plan functions as objective, system-generated evidence of work patterns that supplements manager observations with verifiable behavioral records. A PIP (performance improvement plan) is a formal HR document that identifies specific performance deficiencies, establishes measurable improvement targets, and defines a timeline for achieving them — typically 30, 60, or 90 days. When monitoring data is integrated into this process, it replaces or supplements subjective impressions with timestamped activity records: daily active work session durations, application usage breakdowns, idle time ratios, and pattern changes over time.
The legal significance of monitoring data in PIPs is substantial. Wrongful termination claims — the most common employment litigation employers face — frequently hinge on whether the employer can demonstrate that performance issues were real, documented before the termination decision, and applied consistently across similarly situated employees. Activity monitoring data, when collected under a disclosed policy and applied without discriminatory intent, provides exactly the objective documentation record that courts and administrative agencies look for when evaluating the legitimacy of termination decisions. Organizations at higher monitoring program maturity levels have the systematic baselines and consistent processes that make PIP evidence most defensible.
This page is not legal advice. Organizations should work with qualified employment counsel when designing PIP processes and when monitoring data will be used in formal disciplinary proceedings. The frameworks described here represent general HR best practices and are not a substitute for jurisdiction-specific legal guidance.
Why Monitoring Data Changes the PIP Dynamic for Both Parties
PIPs without objective measurement have a fundamental credibility problem: the employee knows performance is being judged by a manager who may have subjective biases, and the employer knows that any termination following the PIP will be judged retrospectively by people who were not present for the performance issues. Monitoring data changes this dynamic. When both parties can see the same timestamped, system-generated activity records, the conversation shifts from "I don't think you're working hard enough" to "our data shows your average active work session time was 2.8 hours per day over the past six weeks, compared to a team average of 5.4 hours." The second conversation is more honest, more actionable, and far more defensible.
How to Use Historical Monitoring Data to Establish a Performance Baseline
Establishing a performance baseline from historical monitoring data is the foundation of using activity data effectively in a PIP. The baseline answers the question: what did normal look like for this employee before performance concerns emerged? Without a baseline, monitoring data from the performance concern period has no context — a daily active time of 4.2 hours might be below the team average but above this employee's own previous average, or it might represent a significant decline from a prior baseline of 6.5 hours. The data means different things depending on context.
eMonitor maintains historical activity data for the full duration of the monitoring period. For PIP purposes, HR should request a 90-day lookback report covering the period before performance concerns were first raised. This report establishes the employee's personal baseline across the key metrics: average daily active time, application category distribution, idle time ratio, and session start/end patterns. This baseline becomes the anchor against which both the problem period and the PIP improvement period are measured.
What Baseline Data Reveals About Performance Pattern Changes
The most diagnostically useful pattern is a baseline that shows reasonable performance followed by a measurable decline correlated with a specific time period. An employee whose monitoring data shows 5.5 hours of daily active time for the first eight months of their employment, followed by a gradual decline to 3.0 hours over the following six weeks, tells a different story than an employee who has shown low active time since their first week. The first pattern suggests a change in engagement, motivation, or personal circumstances. The second may indicate a poor role fit or hiring decision. Both require different management responses, and monitoring data makes the distinction visible.
Absence of Baseline as a PIP Limitation
When monitoring was not in place before performance issues emerged, the baseline problem is significant. Initiating monitoring specifically at the start of a PIP creates no useful comparison point and is legally problematic — it can appear retaliatory. Organizations that implement monitoring after performance issues are identified have limited ability to use that data for historical comparison. This is one of the strongest operational arguments for implementing monitoring as a standard organizational practice rather than a reactive intervention: the value of monitoring data for PIPs depends entirely on data existing before the PIP was triggered.
How to Write Measurable PIP Goals Using Monitoring Data
The most common failure mode in performance improvement plans is setting goals that cannot be objectively measured — goals like "demonstrate improved engagement," "show greater commitment to your responsibilities," or "be more present during work hours." These goals are impossible to evaluate objectively and create exactly the kind of post-PIP dispute that monitoring data is designed to prevent. Activity monitoring data enables specific, quantifiable goals that both parties can verify independently.
Examples of Monitoring-Based PIP Goals
The following goal structures illustrate how activity monitoring data translates to measurable PIP targets. These are examples only and should be calibrated to the specific role, team norms, and the employee's historical baseline:
- Active work time target: "Maintain a minimum of 5.5 hours of active computer work time per day as measured by eMonitor activity monitoring, on at least 8 of every 10 consecutive working days over the 60-day PIP period."
- Role-specific tool engagement: "Spend a minimum of 60 percent of active computer time in job-designated applications [list specific tools] as measured by eMonitor application usage reports."
- Idle time reduction: "Reduce extended idle periods (uninterrupted inactivity exceeding 30 minutes) to no more than one occurrence per work day on average over the PIP period."
- Work schedule adherence: "Begin active computer work within 15 minutes of scheduled shift start at least 9 of every 10 working days as recorded by eMonitor session data."
The critical characteristic of effective monitoring-based PIP goals is that the employee can track their own progress using their personal eMonitor dashboard. This is not a minor procedural detail — it is ethically significant. Employees on a PIP who have real-time visibility into their own progress data can self-correct without waiting for manager check-ins. They know whether they are on track before the formal review meeting. This transforms the PIP from an adversarial process into a supported improvement structure.
Calibrating Goals to Role and Team Norms
PIP goals must be calibrated to reasonable expectations for the specific role. Active computer time goals should reflect the nature of the work: a software engineer working on complex architectural problems may legitimately show lower keystroke activity during deep thinking phases. A customer support representative handling tickets has a more direct correlation between active computer time and output quantity. HR teams should establish role-specific baselines before setting PIP targets, consulting with the employee's manager to understand what normal productive activity looks like for the specific role.
Legal Defensibility: How Monitoring Data Strengthens (and Complicates) PIP Documentation
Monitoring data strengthens PIP legal defensibility when it is collected under a properly disclosed policy, applied consistently across comparable employees, and presented as one component of a broader performance assessment rather than as the sole basis for employment decisions. It can complicate PIP defensibility when these conditions are not met. HR leaders should understand both dimensions before integrating monitoring data into formal disciplinary processes.
The Disclosure Requirement
Monitoring data is only legally usable in employment proceedings when employees received prior notice that monitoring was occurring. In the United States, the Electronic Communications Privacy Act (ECPA) permits employer monitoring of work devices and networks, but best practice — and in some states, legal requirement — dictates written notice to employees before monitoring begins. This notice should be part of the employee handbook, an onboarding acknowledgment form signed by the employee, and should describe what is monitored, how data is stored, and how it may be used. Without this documentation, monitoring data collected for PIP purposes is legally vulnerable.
Consistent Application Across Protected Classes
The EEOC (Equal Employment Opportunity Commission) prohibition on discriminatory application of workplace policies applies to monitoring. If monitoring data is used to support PIPs for some employees but not applied consistently across all employees in comparable roles, the inconsistency creates disparate treatment liability. HR must document that monitoring policies are applied to all employees in monitored roles without regard to race, gender, age, religion, national origin, disability, or other protected characteristics. The monitoring policy, data review thresholds, and PIP trigger criteria should be identical for all employees in the same role classification.
Monitoring Data as Corroboration, Not as the Sole Trigger
Employment law practitioners consistently advise that monitoring data functions best as corroboration of manager observations rather than as the independent trigger for a PIP. An employee whose manager has documented repeated performance conversations, missed deadlines, and declining quality output — and whose monitoring data also shows declining engagement patterns — has a well-documented performance case. An employee who receives a PIP citing monitoring data as the primary evidence, without a documented history of performance conversations, has a much stronger argument that the process was procedurally flawed. The sequence matters: manager concerns and documented conversations should precede monitoring data review in the disciplinary record.
Documentation Requirements for Admissible Evidence
If monitoring data will be used in an administrative proceeding (EEOC complaint, unemployment hearing, labor arbitration) or civil litigation, the following documentation is typically required to establish admissibility: (1) the monitoring policy signed by the employee, (2) records confirming that monitoring was active and operational during the data collection period, (3) a description of the methodology used to generate the reports presented, (4) records confirming that the same monitoring standards applied to other employees in comparable roles, and (5) chain of custody documentation showing the data was not altered after collection. eMonitor's exportable reports with timestamps and the ability to generate reproducible historical queries support this documentation framework.
WARN Act and Documentation Requirements for Monitoring-Informed Terminations
The Worker Adjustment and Retraining Notification (WARN) Act requires employers with 100 or more employees to provide 60 days advance notice before mass layoffs or plant closings. While WARN Act requirements apply to mass employment actions rather than individual terminations, the documentation requirements for individual terminations following a PIP touch adjacent legal terrain. Employment counsel should advise on whether the specific facts of a termination create any WARN Act exposure before an employment decision is finalized.
For individual termination documentation, the monitoring-informed PIP record should include: the initial PIP document with monitoring-based goals; weekly check-in records showing progress or lack thereof against those goals; eMonitor activity reports covering the full PIP period, exported and attached to the personnel file; and the final assessment documenting whether PIP goals were met, partially met, or not met. This complete documentation record demonstrates good-faith process administration that courts and administrative agencies expect to see in employment decisions.
Constructive Dismissal Risk When Monitoring Is Used in PIPs
A specific legal risk worth noting: if an employer initiates significantly more intensive monitoring specifically when a PIP begins — particularly if this monitoring includes screenshot capture, keystroke recording, or other intrusive methods not previously applied — the employee may have grounds for a constructive dismissal claim. The argument would be that the intensified monitoring constituted a fundamental change to working conditions that made continued employment intolerable. Avoid introducing new, more intrusive monitoring methods as part of a PIP initiation. The monitoring baseline should be consistent with what applied before performance issues arose.
How Not to Use Monitoring Data in a Performance Improvement Plan
The ways that monitoring data can undermine a PIP process are as important to understand as the ways it strengthens one. HR teams implementing monitoring for PIP support should be aware of the following failure modes that both erode employee trust and create legal exposure.
Using Monitoring as the Trigger for a PIP Without Prior Conversation
Initiating a PIP based solely on monitoring data — without prior documented performance conversations between the employee and manager — is procedurally problematic. Employees have a reasonable expectation that performance concerns will be raised in conversation before formal disciplinary action begins. An employee who receives a PIP stating "monitoring data shows your active time is below expectations" without ever having been told in a 1:1 that their work engagement was a concern has grounds to argue the process was unfair. Monitoring data should inform performance conversations that precede a PIP, not replace them. Our guide to coaching with monitoring data explains how to build this pre-PIP conversational foundation effectively.
Presenting Raw Session Logs Rather Than Aggregate Patterns
Presenting granular raw session logs in a PIP meeting — lists of every application opened, every website visited, every minute of activity — is counterproductive and potentially legally problematic. It signals disproportionate scrutiny, creates a punitive rather than improvement-oriented dynamic, and may reveal data collected under circumstances the employee finds intrusive. Present aggregate patterns: average daily active time, application category percentages, trend lines over time. The goal is to establish a pattern discussion, not to conduct a minute-by-minute accounting of the employee's day.
Different Monitoring Standards for Different Employees
If your organization applies different monitoring configurations to different employees in the same role — for example, more intensive screenshot monitoring for one employee under PIP while other employees in the role are not subject to screenshot monitoring — this creates significant disparate treatment risk. Monitoring configurations and data review thresholds must be standardized by role classification and applied consistently.
Frequently Asked Questions: Employee Monitoring and Performance Improvement Plans
Can employee monitoring data be used in a performance improvement plan?
Employee monitoring data is usable in performance improvement plans when employees received prior notice of monitoring through a disclosed workplace policy. Activity data provides objective timestamps, application usage patterns, and work session durations that supplement manager observations with verifiable, non-subjective evidence of performance patterns over time.
What monitoring data is most useful in a PIP?
The most useful monitoring data for a performance improvement plan includes daily active work session durations, application usage breakdowns showing time in job-relevant tools versus non-work applications, idle time ratios, and pattern changes over time. Baseline data from before performance issues emerged is particularly valuable for establishing what normal performance looked like for that specific employee.
Does monitoring data protect the employer in a wrongful termination claim?
Monitoring data strengthens employer legal defense in wrongful termination cases by providing objective, timestamped records of performance patterns that preceded the termination. Courts have accepted digital activity logs as evidence of performance issues when the monitoring policy was disclosed before data collection and applied consistently across similarly situated employees.
How should monitoring data be presented to an employee during a PIP?
Present monitoring data in a PIP as objective observations rather than accusations. Share aggregate patterns — average daily active time, tool usage ratios, trend lines over the relevant period — rather than granular session logs. Frame the data as establishing a measurable baseline against which PIP progress will be tracked, not as evidence of deliberate misconduct.
Can a PIP use monitoring data to set measurable goals?
Activity monitoring data enables specific, measurable PIP goals that eliminate subjectivity from progress assessment. Instead of "improve engagement," a PIP goal becomes "maintain a minimum of 5 hours of active work time per day as measured by eMonitor, for 8 of 10 consecutive working days." These goals are objectively verifiable by both parties, including the employee through their own dashboard.
What is the EEOC risk when using monitoring data in PIPs?
The primary EEOC risk is disparate application: using monitoring data to scrutinize employees in protected classes more aggressively than comparable employees outside those classes. HR must document that monitoring data is reviewed against the same thresholds and applied under the same procedures for all employees in similar roles, regardless of protected class membership.
Should monitoring be initiated when a PIP begins?
Initiating or intensifying monitoring specifically when a PIP begins is legally risky and produces no baseline data for comparison. Monitoring should be in place as standard organizational practice before any individual performance issues arise. Introducing significantly more intrusive monitoring at PIP initiation can create grounds for a constructive dismissal claim.
How long should monitoring data be retained for PIP documentation?
Monitoring data used in PIP documentation should be retained for the applicable statute of limitations for employment claims in your jurisdiction. In the United States, this is generally two to three years for federal claims and up to four years for some state-level claims. Consult employment counsel for jurisdiction-specific retention schedules and legal hold obligations.
Can monitoring data be used if an employee denies the performance issue?
Monitoring data is particularly valuable when employees dispute performance assessments, because it provides timestamped, system-generated records that are independent of manager interpretation. An employee cannot reasonably dispute activity logs showing an average of 2.3 active work hours per day over a six-week period, where the documented team average is 5.4 hours for the same role.
Does monitoring data in a PIP constitute an invasion of privacy?
Monitoring data collected from employer-owned devices and networks, with prior employee notice through a disclosed monitoring policy, does not constitute an invasion of privacy under US law in most circumstances. The ECPA permits employer monitoring of work systems with proper notice. Employees retain privacy interests in personal device usage and personal accounts accessed on personal networks outside work hours.
What documentation should accompany monitoring data in a PIP?
Monitoring data in a PIP should be accompanied by: the monitoring policy signed by the employee at onboarding, manager observations and documented performance conversations that pre-date the monitoring data review, a description of the baseline period and reporting methodology, and written confirmation that the same monitoring standards apply to all employees in comparable roles. Employment counsel should review PIP documentation before it is presented to the employee.
Can monitoring data help an employee succeed in a PIP?
Activity monitoring data benefits the employee in a PIP by making improvement targets concrete and self-trackable. When the goal is specific — increase active work session time to 5.5 hours per day — the employee can monitor their own progress through their personal eMonitor dashboard and self-correct between formal check-ins. Measurable goals with real-time feedback are more achievable than ambiguous behavioral expectations.
How does eMonitor support the HR documentation workflow for PIPs?
eMonitor provides exportable activity reports in PDF and CSV formats that attach directly to PIP documentation. Reports include date-stamped daily summaries, application usage breakdowns, work session durations, and trend analysis over user-defined date ranges. These exports create a permanent, reproducible record that can be produced in administrative proceedings or litigation without requiring live system access.
Related Use Cases and Resources
Monitoring Data in Workplace Investigations
Chain of custody, evidence preservation, and legal defensibility for monitoring data in formal investigations.
Learn more →Compliance and Legal Guides
Jurisdiction-specific monitoring law, GDPR considerations, and employer disclosure requirements.
Learn more →HR and People Operations Blog
Ethical monitoring frameworks, coaching with data, and performance management best practices.
Learn more →