Remote work monitoring has become one of the most discussed โ and most misunderstood โ topics in the WFH era. Employees worry about Big Brother surveillance; managers want accountability. The reality of what most employers actually monitor, and how, is more nuanced than either extreme suggests.
What Employers Can Monitor (and Commonly Do)
Presence and Activity Signals from Communication Platforms
The most universal form of remote monitoring isn't invasive software โ it's the built-in presence detection in the tools you already use. Microsoft Teams, Slack, and Zoom all show when you were last active, how long you've been Away, and when you're on calls. These signals are visible to managers and IT administrators in ways that go beyond what you see on your own screen.
In Microsoft Teams, administrators with the right permissions can pull presence reports showing each user's availability status over time. Slack's enterprise tier includes analytics on message activity, response times, and active hours. None of this is secret โ it's part of the product offering that companies pay for.
This is why keeping your status active matters beyond just appearing available for colleagues. In companies that track presence data, a pattern of frequent Away status during work hours can surface in manager or HR dashboards without anyone actively spying on you.
Endpoint Monitoring Software (The More Invasive Tier)
Some employers โ particularly in financial services, legal, healthcare, and highly regulated industries โ deploy dedicated employee monitoring software on company devices. Common examples include Teramind, ActivTrak, Hubstaff, and Veriato. These tools can capture:
- Screenshots at configurable intervals (every 1โ10 minutes is common)
- Application usage logs showing which programs were open and for how long
- Website visit history during work hours
- Keystroke counts (not necessarily content, but volume)
- Idle time detection, often overlapping with but separate from Teams presence
If monitoring software is installed on your company device, it typically runs as a background service and isn't easily visible. In most jurisdictions, employers are legally required to disclose that monitoring software is in use โ this is usually buried in your employment agreement, acceptable use policy, or company handbook.
Network-Level Monitoring
If you work through a corporate VPN, your network traffic passes through your employer's infrastructure. IT teams can see which websites and services you're connecting to, the volume of data transferred, and connection timing. They typically cannot read the content of encrypted traffic (HTTPS), but they can see the destinations.
This is why IT departments know when employees are accessing streaming services or personal email heavily during work hours, even without endpoint software. DNS logs are often enough.
What Employers Typically Can't See
Activity on personal devices: Your employer has no visibility into your personal laptop, phone, or tablet. They can only monitor devices they manage and control. If you use your work laptop for work and your personal phone for personal things, those remain completely separate.
Content of encrypted personal communications: HTTPS web traffic, encrypted messaging apps (WhatsApp, Signal), and personal email sent via browser (Gmail, Outlook.com) โ even if your employer can see you're visiting Gmail, they cannot read the content of your messages.
Activity when not on VPN: If you're working directly on your home network without a VPN, your employer's network monitoring doesn't apply. Endpoint software on your device still operates, but network-level surveillance doesn't.
Browser activity on personal profiles: If your work laptop has both a work Chrome profile and a personal Chrome profile, and corporate management only applies to the work profile, browsing in the personal profile is not visible to your employer's admin tools (though endpoint screenshot software may still capture it).
The Teams Status Question
One of the most practical monitoring concerns for remote workers is Teams presence data. The key fact: Teams presence is visible to your entire organization by default โ not just your manager. Anyone who messages you can see when you were last active. More importantly, team administrators and IT can pull historical presence reports.
What a typical Teams presence report shows: time spent in each status (Available, Away, Busy, In a meeting, Offline) per day, per week. For a remote employee with a lot of Away time during core hours, this can become a performance conversation topic regardless of how much work is actually getting done.
A keep-awake tool addresses this specific concern directly. It keeps your status green during focus work, reading sessions, phone calls, and other legitimate work activities where you're present but not touching your keyboard. It doesn't fake activity โ it accurately represents that you're at your desk and available.
Legal Considerations
Employee monitoring laws vary significantly by country and, within the US, by state. California, New York, and Connecticut have specific workplace monitoring notification laws. In the EU, GDPR places significant constraints on what data employers can collect and how long they can retain it. In most jurisdictions, monitoring is legal as long as it's disclosed and limited to company devices/networks โ but the specifics matter and are worth understanding for your location.
The Practical Takeaway
Most employers aren't running keystroke loggers or watching screenshot feeds. The monitoring that actually affects remote workers day-to-day is presence data from communication tools โ Teams status, Slack activity, response times. This is built into the tools you already use, visible without any additional software, and often informally watched by managers assessing remote worker availability.
The solution isn't to game this system โ it's to accurately represent your actual availability. When you're working at your desk but not typing, a keep-awake tool ensures your status reflects reality rather than the assumption of your idle timer.