This is a general summary of publicly available legislative patterns for informational purposes, not legal advice; state law changes frequently and a company monitoring employees across multiple states should confirm current requirements with counsel before launch.
The states with the clearest specific notice requirements
Connecticut's electronic monitoring law requires employers to give prior written notice to employees before engaging in electronic monitoring of their activity, with the notice posted in a conspicuous, accessible place or delivered individually. New York has a similar requirement, mandating written notice at the time of hiring and posted notice thereafter, specifically covering monitoring of phone, email, and internet usage. Delaware's law closely parallels New York's, also requiring both individualized written notice and a general electronic notice acknowledgment.
- Connecticut -- prior written notice required, posted or individually delivered
- New York -- written notice at hiring, plus posted notice, covering phone/email/internet monitoring
- Delaware -- individualized notice plus an acknowledgment requirement
- California -- broader data disclosure and access rights under state privacy statutes, less monitoring-specific but still relevant
States without a specific monitoring notice statute still have applicable law
The absence of a monitoring-specific notice statute in most other states doesn't mean monitoring is unregulated there -- general wiretap statutes (many states require at least one-party consent to record communications, and a smaller number require all-party consent) and common-law privacy torts still apply to workplace monitoring even without a dedicated statute. A small number of states, including a few with all-party consent wiretap requirements, create meaningfully different constraints on monitoring that captures audio or communications content specifically, separate from the states with express written-notice statutes for general electronic monitoring.
No state-specific notice statute doesn't mean no applicable law -- it usually means the older, more general wiretap and privacy framework is what applies instead.
The multi-state employer's practical problem
A company with employees across several states faces a genuine compliance design choice: build state-specific notice and monitoring configurations for each jurisdiction, or adopt a single, uniform policy built to satisfy the strictest applicable state's requirements across the entire workforce. The second approach is administratively simpler and is the more common practical choice among multi-state employers, even though it means employees in states with lighter requirements receive a more protective notice than their state technically mandates -- a reasonable tradeoff against the complexity of maintaining separate configurations.
Keeping the policy current as more states legislate
This is an active area of state legislation, with additional states introducing monitoring-notice bills in most recent legislative sessions, which means a policy built to be compliant today can fall out of date within a single year without anyone noticing until a new law takes effect. Assigning a specific, recurring review point -- annually at minimum -- to check current state legislation against the existing monitoring policy is a low-cost way to avoid drifting out of compliance as the legal landscape shifts. Readers comparing this approach with a commercial implementation can review read more here from Monitask.
A specific compliance gap that a growth-stage company discovered late
A software company headquartered in Texas built its monitoring notice and rollout process around Texas requirements, which include no state-specific electronic-monitoring notice statute, and treated that as the baseline for its entire remote workforce. When the company later hired a small team of New York-based employees, nobody flagged that New York's written-notice-at-hiring requirement hadn't been incorporated into the standard onboarding process, because the onboarding template had been built once, around the company's home-state requirements, and never revisited as the company's remote hiring footprint expanded into other states. The gap was caught during a routine HR policy review roughly a year later, at which point the company had to retroactively provide the required notice to employees who should have received it at hiring -- a correctable but avoidable gap that a state-by-state review triggered by each new hiring location, rather than a one-time policy built around headquarters, would have caught immediately.
A practical trigger for catching this kind of gap
A workable safeguard is tying a monitoring-notice compliance check directly to the hiring workflow itself -- any time a new hire's work location is entered into the HRIS, an automated or manual check confirms whether that state has specific monitoring notice requirements and, if so, that the required notice is included in that employee's onboarding packet. Building this check into the hiring process itself, rather than relying on a periodic, manually-triggered policy review, catches new-state requirements at the point they actually become relevant, which is the point a company's compliance posture is most likely to have a gap. For an independent reference, consult OECD AI Principles.
Local ordinances beyond state law
Beyond the state-level statutes discussed in the main article, a smaller number of US cities and counties have introduced their own local ordinances touching on workplace technology and monitoring, layering a third jurisdictional level -- city, on top of state, on top of federal -- onto an already complex compliance picture for employers with operations in those specific localities. These local ordinances are less commonly tracked than state-level legislation, partly because there are simply more of them to potentially monitor across a large multi-city footprint, which makes them an easy layer to miss even for organizations that are otherwise diligent about state-level compliance.
Organizations with a significant physical or hiring footprint in specific major cities should specifically check, as part of their periodic compliance review, whether any local ordinance beyond state law applies to their monitoring practices in that city, rather than assuming state-level compliance is automatically sufficient everywhere within that state.
Finally, when a new state law is identified during the periodic review discussed earlier, treat updating the monitoring notice as the higher-priority task compared to updating internal training materials -- the notice is what creates or closes a compliance gap directly, while training materials, though important, are a secondary concern that can reasonably follow shortly after.
The patchwork described throughout this article isn't likely to simplify soon -- more states, not fewer, are expected to introduce their own monitoring-notice requirements in the coming years, which makes an ongoing review habit more valuable than a one-time compliance push.