HR & Legal •

Employee Monitoring During a Performance Improvement Plan: Building the Evidence File Legally

Wrongful termination claims cost U.S. employers an average of $40,000 to defend even when the employer wins — and $400,000+ when they lose. The primary driver of that exposure is inadequate documentation. Monitoring data, collected correctly, is the most objective evidence available.

A performance improvement plan (PIP) is a formal HR process that establishes specific, measurable performance objectives and a defined timeline for an employee to meet them — typically 30, 60, or 90 days. When an employee fails to meet PIP objectives and termination follows, that termination must be defensible: supported by objective evidence that the performance deficiencies were real, consistently documented, and not a pretext for discrimination or retaliation.

Employee monitoring data is the most objective documentation available to HR. It doesn't rely on manager memory or subjective observation. It produces timestamped, verifiable records of actual work activity that either support or contradict the performance narrative in the PIP. Used correctly, monitoring data transforms a PIP from a bureaucratic formality into a legally defensible evidence record.

This article provides HR and legal information, not legal advice. Consult qualified employment counsel before initiating or documenting any PIP proceeding, particularly in unionized workplaces or jurisdictions with robust wrongful termination protections.

Why Does Objective Documentation Matter So Much in PIP Proceedings?

The legal risk of a poorly documented PIP termination is not abstract. A 2023 analysis by Littler Mendelson found that wrongful termination claims have a plaintiff success rate of approximately 67% when they reach jury trial — and the median jury award in employment discrimination cases in federal court exceeds $200,000. The cases that reach juries are disproportionately those where employer documentation was inconsistent, vague, or appeared retaliatory.

Subjective manager notes — "employee seemed disengaged," "I observed reduced effort," "attitude was not meeting expectations" — are the weakest possible documentation. They invite counterclaims of bias and are difficult to defend because they are inherently contestable. Objective digital activity records are a different category of evidence: they show exactly how much time was spent in which applications, when the employee was active versus idle, and whether specific work-related tool usage met the targets set in the PIP.

The combination of monitoring data plus manager documentation plus formal PIP review records creates a three-layer evidence file that is substantially more defensible than any single element alone.

Three requirements must be met for monitoring data to be legally usable in a PIP proceeding:

Requirement 1: The Monitoring Policy Must Predate and Be Independent of the PIP

Monitoring that begins or is intensified specifically because an employee is placed on a PIP is legally problematic in two ways. First, it may not satisfy disclosure requirements in states like Delaware, Connecticut, and New York (see our home monitoring legal guide for state-specific notice requirements) if the employee did not receive adequate prior notice of monitoring. Second, it creates the appearance that the monitoring is designed to build a case rather than to apply an objective workplace standard — which courts and juries find troubling.

The monitoring data used in a PIP should come from a monitoring program that applies to all employees in the same role, operating under a policy disclosed at hiring or during the monitoring program's rollout. If your organization is deploying eMonitor for the first time during an active PIP, pause, roll out the monitoring program to the full team first with proper disclosure, then apply the resulting data to the PIP going forward.

Requirement 2: Monitoring Must Be Applied Consistently to Peers

Applying monitoring more intensively to a PIP employee than to their peers — increasing screenshot frequency, adding application tracking categories not applied to others, or setting lower idle-time thresholds — creates selective enforcement exposure. If the employee's attorney can show that monitoring was heightened specifically for their client, the entire monitoring evidence file may be challenged as pretextual.

The standard: the monitoring configuration for the PIP employee should be identical to the configuration applied to their peers in the same role. If you need to document specific behaviors relevant to the PIP objectives — say, confirming CRM usage because the PIP targets pipeline activity — ensure the same CRM usage tracking applies to the entire sales team.

Requirement 3: The Data Must Align with PIP Objectives

The most useful monitoring data in a PIP evidence file is data that directly measures the performance objectives articulated in the PIP itself. If the PIP states "employee must log 6+ hours of active productive time per workday," then daily active time records from time tracking are directly relevant evidence. If the PIP states "employee must use the CRM for client communication," then CRM application usage data is directly relevant.

Monitoring data that is tangential to the PIP objectives — information about the employee's internet browsing habits when the PIP targets output quantity, for example — adds volume to the file without adding defensibility. Include monitoring data that measures what the PIP measures.

What Monitoring Data Should Go Into the PIP Evidence File?

A well-constructed PIP evidence file from monitoring data includes the following categories of records, organized by PIP review period:

Daily Active Time and Login Records

For any PIP that includes work hours or attendance objectives, daily records of login time, logout time, total hours, and active productive time are foundational documentation. These records are objective, timestamped, and not subject to the manager-perception challenge that weakens subjective notes. They answer the specific factual question: "Did this employee meet the hours-worked requirement in the PIP, or didn't they?"

eMonitor's daily summary reports generate per-employee activity records that include active time, idle time, login/logout timestamps, and weekly totals — all exportable for HR file inclusion in PDF or CSV format.

Application Usage Data Relevant to Role Objectives

For PIPs that target tool engagement — requiring a developer to spend minimum time in their IDE, a salesperson to spend minimum time in CRM, or a customer support agent to use the ticketing system rather than alternative channels — application usage analytics provide direct evidence of whether those targets were met.

The documentation approach: include weekly application usage reports for the PIP employee alongside the same period's data for two or three peers in the same role. This contextualizes the PIP employee's usage (showing whether it deviates from norms) and demonstrates that the same tracking applies to peers.

Productivity Trend Data Over the PIP Period

Trend data — showing whether productivity metrics improved, deteriorated, or remained flat over the course of the PIP — is particularly valuable for the termination decision documentation. A PIP that required improvement and shows a productivity trend line that is flat or declining over 90 days, despite documented coaching and support, is a strong foundation for a performance-based termination.

Include the 90-day productivity trend chart alongside the review meeting notes from each PIP check-in. The combination shows both the objective data trajectory and the subjective coaching record — the two elements that together demonstrate good-faith effort to support the employee's improvement.

What Should You Not Do When Monitoring a PIP Employee?

Several monitoring practices during PIPs create legal exposure significant enough to undermine an otherwise well-documented case:

Do Not Increase Monitoring Intensity Only for the PIP Employee

Increasing screenshot frequency, reducing idle-time thresholds, or adding application tracking categories specifically because an employee is on a PIP — without applying the same changes to their peers — is selective enforcement. Employment attorneys routinely request monitoring configuration settings as part of discovery in wrongful termination cases to identify exactly this pattern.

Do Not Use Monitoring to Find Pretextual Evidence

Monitoring data used in PIP proceedings should document the performance deficiencies identified in the PIP — not search for additional grounds for termination. An employer who uses PIP monitoring to discover and then rely on unrelated policy violations (non-work browsing, personal phone use) that were never the subject of the PIP creates the appearance of pretext: that the real reason for termination is different from the stated performance reason.

Do Not Monitor for Protected Activity

This is the most serious risk in PIP monitoring. Monitoring that captures an employee's communications about potential union organizing, workers' compensation claims, FMLA-related discussions, harassment complaints, or whistleblowing activity — even as incidental captures within a broader monitoring program — can transform a performance termination into a retaliation claim. Under the NLRA, FMLA, and various whistleblower protection statutes, retaliation claims carry remedies that substantially exceed ordinary wrongful termination damages.

The practical safeguard: ensure HR counsel has reviewed the monitoring data for protected activity exposure before the termination decision is finalized. This review is not about excluding the evidence — it's about identifying whether there are claims that need to be addressed independently before the performance proceeding concludes.

Union Employees on PIPs: Different Rules Apply

For employees covered by a collective bargaining agreement, PIP procedures — including monitoring during PIPs — are subject to the CBA and the NLRA's duty to bargain over terms and conditions of employment. Several issues arise specifically in unionized contexts:

Weingarten rights: Under NLRB v. Weingarten, Inc. (1975), union employees have the right to request union representation at any investigatory interview they reasonably believe may result in discipline. PIP review meetings where monitoring data is discussed and discipline is possible likely trigger Weingarten rights. Failing to honor a Weingarten request is an unfair labor practice that can invalidate the entire PIP proceeding.

Past practice: If monitoring has not historically been applied to employees in the bargaining unit at the level you are proposing for the PIP, implementing it for the first time during a PIP may constitute a change in working conditions requiring bargaining notice.

Grievance procedures: CBA grievance procedures may require specific documentation steps and timelines that interact with PIP monitoring evidence. Consult labor counsel before conducting any PIP proceeding for a union-represented employee.

Building the Complete HR Documentation File

The most defensible PIP termination package combines three independent evidence streams into a coherent, mutually supporting record:

  1. The PIP document itself: Specific, measurable objectives; documented support provided; review meeting dates; and the final assessment. The PIP document is the framework against which all other evidence is measured.
  2. Monitoring data records: Exported from eMonitor for the PIP period, showing active time, application usage, and productivity metrics aligned with PIP objectives. Accompanied by configuration documentation showing the same monitoring applies to peers.
  3. Manager notes and meeting records: Contemporaneous documentation of each PIP review meeting, coaching conversations, feedback provided, and employee responses. These records humanize the process and demonstrate that the employer made genuine efforts to support improvement — not just to document failure.

Have employment counsel review the complete package before executing any termination decision. Counsel will assess whether the evidence supports the stated performance basis, identify any gaps in documentation, and flag any discrimination or retaliation risks in the record that should be addressed before the termination is finalized.

How eMonitor Supports HR Investigation and PIP Documentation

eMonitor's evidence export function generates structured activity reports for specified employees and date ranges, formatted for HR file inclusion. The platform maintains tamper-evident activity logs with access records — essential for establishing chain of custody when monitoring data is used in litigation or arbitration.

The role-based access control system ensures that monitoring data for a PIP employee is accessible only to authorized HR personnel and the employee's management chain — limiting the discovery exposure that arises when monitoring data is broadly accessible within an organization.

For organizations building their first formal HR monitoring policy, eMonitor's compliance documentation includes jurisdiction-specific monitoring policy templates and the disclosure language required by Delaware, Connecticut, New York, and other states with specific monitoring notice requirements. Starting at $3.50/user/month, the platform is accessible to organizations of all sizes — including those for whom the cost of a single wrongful termination defense would exceed the monitoring investment many times over.

Build a Monitoring Program That Protects Your Organization

eMonitor generates the objective, tamper-evident activity records that make HR proceedings defensible. Trusted by 1,000+ companies. Starting at $3.50/user/month.

Start Free Trial

7-day free trial. No credit card required.

Frequently Asked Questions

Can you use employee monitoring data during a performance improvement plan?

Yes. Monitoring data from an existing, disclosed policy is admissible documentation in PIP proceedings. Three requirements: the monitoring predates the PIP and applies to all employees in the role (not just the PIP employee), the monitoring scope is consistent with peers, and the data measures the specific objectives defined in the PIP itself. Data collected under these conditions is objective, timestamped, and substantially more defensible than subjective manager notes.

What makes monitoring during a PIP legally defensible?

Three elements: (1) the monitoring policy predates and is independent of the PIP — not created to build a case; (2) monitoring scope and intensity are identical to what applies to peers — selective intensification creates discrimination exposure; and (3) the monitoring criteria align with the measurable PIP objectives. Broader monitoring, applied unequally, will be challenged in any tribunal or litigation proceeding.

Should you tell an employee they are being monitored more closely during a PIP?

If the monitoring is standard policy applying to all employees, no separate PIP-specific disclosure is needed. If you are intensifying monitoring specifically for the PIP employee — adding screenshot frequency, new tracking categories — that intensification must be disclosed in writing, justified in the PIP documentation, and applied consistently to peers. Undisclosed intensification creates both legal exposure and an evidentiary problem if contested in litigation.

What monitoring data is most useful in a PIP evidence file?

Data that directly measures PIP objectives: daily active time records showing hours worked versus claimed, application usage showing time in role-relevant tools, output metrics where applicable, and attendance and login records. Include the same data for 2-3 peers to contextualize the PIP employee's metrics and demonstrate consistent application. Trend data over the full PIP period showing whether performance improved, held flat, or declined is particularly valuable for the termination decision file.

Can a PIP employee challenge monitoring data in an employment tribunal?

Yes. Common challenges include: monitoring policy not disclosed before PIP; monitoring applied more intensively to the PIP employee than peers; broken chain of custody for monitoring records; or selective presentation excluding periods where metrics were met. Maintaining complete, unaltered monitoring records with documented access logs addresses the chain-of-custody challenge. Employment counsel review before termination identifies the other challenge vectors before they become litigation issues.

What should you NOT do when monitoring an employee on a PIP?

Do not: increase monitoring scope only for the PIP employee without written justification and peer-consistent application; conduct monitoring not disclosed in the pre-existing policy; use monitoring data as the sole termination basis without corroborating manager documentation; share monitoring data beyond the authorized HR and management chain; or use monitoring to identify evidence of protected activity — union organizing, whistleblowing, or FMLA-related communications — which can convert a performance proceeding into a retaliation claim.

How does union membership affect PIP monitoring?

Unionized employees on PIPs have Weingarten rights (the right to request union representation at investigatory meetings that may result in discipline), and intensifying monitoring may constitute a change in working conditions requiring bargaining notice under the NLRA. Past practice matters: if monitoring has not historically applied to bargaining unit members at the proposed level, implementing it during a PIP without bargaining notice may be an unfair labor practice. Consult labor counsel before any PIP proceeding for a union-represented employee.

Can monitoring data prove an employee met PIP objectives?

Yes — and this benefits both parties. Monitoring data showing an employee consistently meeting PIP productivity targets is evidence of success, creating a fair record rather than a one-sided evidence file. This bidirectional objectivity is actually one of monitoring's strongest arguments for legal defensibility: if the data could show improvement as readily as failure, it is less vulnerable to the claim that it was selectively gathered to support a predetermined outcome.

What is the eMonitor audit trail and how does it support PIP documentation?

eMonitor maintains tamper-evident activity logs with access records showing who viewed, exported, or modified any monitoring data. This chain-of-custody audit trail is essential for PIP evidence files: it demonstrates the data was not selectively extracted or modified after the fact. The evidence export function generates structured reports for a specified employee and date range, formatted for HR file inclusion and compliant with EEOC records retention requirements.

Should HR counsel review monitoring data before a PIP termination?

Always. Employment counsel should review the complete file — monitoring data, manager notes, PIP objectives, review records — before any PIP-based termination. Counsel will assess consistent monitoring application, whether data supports stated deficiencies, whether discrimination or retaliation risks exist in the record, and whether the documentation is sufficient to defend a wrongful termination claim. This review is not optional: wrongful termination defense costs $40,000+ even when employers win.

Objective Evidence for Every HR Decision

eMonitor provides tamper-evident activity records, exportable evidence reports, and role-based access control — the infrastructure for legally defensible HR proceedings. Starting at $3.50/user/month.

Book a Demo View Compliance Resources