Summary
Activity monitoring sees the device. It does not see the sales call taken on a mobile, the two-hour workshop in a meeting room, the site visit, the phone interview, the whiteboard session or the forty minutes spent reading a printed contract. For roles where that is a small share of the week, the gap is an annoyance. For account managers, field engineers, recruiters, consultants and most managers, it is a third to a half of the job, and a dashboard that reads it as idle time produces figures that are wrong by that much. This guide explains how to account for non-computer work: what the software can pull in automatically from calendars and call systems, where a light manual layer is unavoidable, how to set idle rules so that real work is not counted as absence, and which roles should be measured on output rather than activity at all.
E-Monitor's calendar and call integrations fill the gaps automatically, and employees can tag the rest from their own dashboard. Book a demo →
The Size of the Gap by Role
Before designing anything, measure how much of a role's week is off the device. A two-week comparison of scheduled hours against recorded active hours, with meetings and calls from the calendar overlaid, gives the number quickly. Typical shares of non-computer work in knowledge-work roles:
| Role | Share of week off the device | Main forms |
|---|---|---|
| Software developer | 10 to 20% | Stand-ups, design discussions, thinking |
| Customer support (chat and ticket) | 5 to 15% | Team huddles, coaching |
| Inside sales | 25 to 40% | Phone calls, video demos counted only if on the device |
| Field sales and account management | 40 to 60% | Client visits, travel, calls |
| Recruiter | 30 to 50% | Phone screens, interviews, events |
| Consultant | 30 to 60% | Client workshops, on-site days |
| Field engineer | 60 to 80% | Site work, travel |
| Manager | 40 to 60% | Meetings, one-to-ones, walking the floor |
Above about 30 percent, device activity on its own is the wrong primary measure and the role should be managed on output with activity as context. Below it, filling the gaps makes the activity data usable. The offline work guide covers the narrower case of the software's behaviour when the device is disconnected; this guide is about work that is never on the device at all.
What Can Be Filled In Automatically
Three sources cover most non-computer work without anyone typing anything.
Calendar integration. Accepted meetings in Google Calendar or Microsoft 365, with their duration, overlaid on the activity timeline. An idle period that coincides with a calendar entry is reclassified as meeting time rather than idle. This single integration resolves the largest gap for most office roles and is the first thing to switch on.
Call and telephony logs. Diallers, softphones and mobile call logs that sync to the CRM record call start, end and contact. For sales, support and recruiting roles, calls are reclassified as productive time by the same overlay. Where the dialler runs on the device it is already captured; the integration matters for mobile and desk phones.
Location and site check-ins. For field roles, a check-in at a job site or client address from the mobile app, or a geofenced arrival where the policy permits it, records site time. This is the most privacy-sensitive source and should be limited to working hours and to the sites the role visits; the field service guide covers the configuration and disclosure.
Together these typically close two-thirds of the gap for a mixed role. E-Monitor's attendance tracking and integrations handle the overlay; the remaining third needs the next section.
The Manual Layer, Kept Light
Some work has no system of record: the whiteboard session, the printed document, the corridor conversation that resolved a blocker, the hour of thinking before writing. For this a light manual layer is unavoidable, and the design principle is that it must cost the employee seconds, not minutes.
The form that works: when the activity timeline shows an idle gap over a threshold, the employee's own dashboard offers that gap with a one-tap tag, such as meeting, call, site, reading, thinking or break. Tagging a gap takes two seconds and happens at most a few times a day. Timesheets, by contrast, ask for the whole day from memory on Friday and are wrong by a third.
Two rules keep the manual layer honest. Tags are the employee's statement and are taken at face value unless a pattern contradicts them; a manager who audits every tag has recreated the timesheet. And untagged gaps are reported as untagged, not as idle, so the figure the manager sees is honest about what it does not know. The employee's guide to the dashboard explains the tagging step to the person doing it.
Idle Rules That Do Not Punish Real Work
Most false readings of non-computer work come from the idle threshold. A rule that marks any five minutes without input as idle turns every call, every read and every conversation into absence, and it is the rule most often responsible for employees buying mouse jigglers.
- Threshold by role: five minutes may suit a data-entry role; fifteen to thirty suits anyone whose job includes thinking, calls or meetings
- Calendar and call overlays applied first, so that known work is never idle
- Idle inside scheduled hours reported as "no device activity", which is what it is, rather than as "idle" with its implication
- No idle alerts to managers at all for roles above 30 percent non-computer work; the figure is context, not a signal
- Employee self-view of idle periods so that the person can tag or explain before anyone else sees a number
The idle time guide covers thresholds in detail, and the jiggler guide explains what happens when they are set wrong.
Roles That Should Be Measured on Output Instead
For roles where non-computer work exceeds a third of the week, activity data is the wrong primary measure however well the gaps are filled. The honest approach is to measure the role on what it produces and use activity as supporting context.
| Role | Primary measure | Activity data used for |
|---|---|---|
| Field sales | Pipeline progressed, revenue, visits logged | Admin load, CRM hygiene, after-hours work |
| Recruiter | Screens, interviews, offers, time to fill | Tool switching, sourcing time |
| Consultant | Billable hours delivered, deliverables, client rating | Billable versus internal split |
| Field engineer | Jobs completed, first-time fix rate, site hours | Reporting and admin time |
| Manager | Team outcomes, one-to-ones held, decisions closed | Meeting load, focus time for own work |
The productivity metrics guide shows how to define output measures per role, and the sales productivity guide works through the field-sales case in detail.
Telling Employees How Gaps Are Treated
The policy should say, in one paragraph, what happens to time the device does not see: that calendar meetings and logged calls are counted as work automatically, that employees can tag other gaps from their dashboard, that untagged gaps are reported as unknown rather than idle, and that for roles with substantial off-device work, output is the measure and activity is context. That paragraph removes the fear that drives most objections to monitoring in mixed roles, and it is a sentence a recruiter can say in an interview. The policy guide shows where it goes.
A Worked Example: The Account Manager Who Looked Idle
An account manager at a logistics firm showed 46 percent active time in her first month of monitoring, lowest on a team of nine. The team lead, new to the dashboard, raised it in a one-to-one. She had spent eleven days of the month at client sites and on the phone, which was the job.
Three changes followed. Calendar integration was switched on, which reclassified fourteen hours a week of client meetings from idle to meeting time. The CRM's call log was connected, adding six hours of calls. The idle threshold for the account-management role was moved from five minutes to twenty, and the dashboard was set to show untagged gaps as unknown. Her figure the following month was 81 percent active or in known work, with four percent untagged, and the team lead's view switched to the measures that mattered for the role: pipeline progressed and renewals closed, where she had been top of the team all along.
Frequently Asked Questions
1. How does monitoring software handle work that is not on a computer?
It does not see it directly. The gaps are filled by calendar integration for meetings, call-log integration for phone work, site check-ins for field roles, and a light one-tap tagging layer on the employee's own dashboard for everything else. Untagged gaps should be reported as unknown, not as idle.
2. Does idle time mean an employee was not working?
No. Calls, in-person meetings, reading, thinking and site work all show as no device activity. Apply calendar and call overlays first, set the idle threshold by role, and report remaining gaps as no device activity rather than idle.
3. Which roles should not be measured on activity data?
Any role where more than about a third of the week is off the device: field sales, recruiters, consultants, field engineers and most managers. Measure those on output, such as pipeline, hires, billable deliverables, jobs completed and team outcomes, with activity data as context.
4. Should employees fill in timesheets for non-computer work?
A full timesheet from memory is wrong by about a third and resented. A one-tap tag on idle gaps the dashboard surfaces takes seconds, is far more accurate, and is the employee's own statement, taken at face value unless a pattern contradicts it.
5. What integrations fill the gaps automatically?
Google Calendar or Microsoft 365 for meetings, CRM and telephony call logs for calls, and mobile site check-ins or geofenced arrivals for field roles, limited to working hours and the sites the role visits. Together they usually close two-thirds of the gap.
6. What should the monitoring policy say about off-device work?
That calendar meetings and logged calls count as work automatically, that employees can tag other gaps from their dashboard, that untagged gaps are reported as unknown rather than idle, and that roles with substantial off-device work are measured on output with activity as context.
The whole job, not just the screen E-Monitor overlays calendar and call data on the activity timeline, lets employees tag the rest in seconds, and reports what it cannot see as unknown rather than idle. Sign up →