A client pays for an engineer’s undivided attention from 9 a.m. to 1 p.m. The engineer delivers the weekly assignment on time. On Tuesday, though, a production alert goes unanswered for forty minutes. The team lead suspects the engineer was working a second job. The engineer says she was helping the same client by phone. A screenshot taken at 10:15 would show an idle desktop in either case.
The client is entitled to the coverage it bought. The engineer is entitled to have her explanation checked. Start with the promise you need to verify. Hours worked, availability, quality of work and an exclusive commitment are four different promises. No single activity score proves all four.
Define what the client or employer is buying
For an hourly assignment, specify how to record actual time, including calls, preparation and work away from the keyboard. For coverage, agree on the time zone, the channel to watch, the response expected and who covers breaks or conflicting client duties. For a deliverable, name the person who will accept it and what makes it usable. Finishing the assignment early is fine when the agreement buys an outcome. It does not release somebody from a separately agreed coverage window.
If exclusive dedication matters, explain what that means before the assignment starts. Does it mean no work for another customer during specified paid hours? A duty to disclose conflicts? A restriction involving a particular client or its data? An evening assignment outside the agreed window and billing two clients for the same exclusive hour are different situations. HR or counsel should check any proposed restriction for the worker’s location and type of engagement. On a staffing assignment, the agency and client should also agree who approves time, who may review which records, and who handles a dispute.
Use records that answer the question
- Hours billed. Use a time-entry system with project codes, worker corrections, approval history and a named reviewer. Reconcile exceptions with tickets, service calls or handoffs. A timesheet records a claim; a ticket can corroborate part of it. A ticket opened at nine and closed at five does not establish eight hours of effort.
- Coverage promised. Use the shift roster, alert delivery and acknowledgement times, incident calls and documented handoffs. Check that alerts reached the right person and that backup coverage worked. A green status light answers none of those questions.
- Productivity and quality. Review accepted work, defects, rework and blocked dependencies with the person who uses the result. A short weekly report can cover what was finished, what is blocked and which decision is needed. A senior engineer who prevents a bad release may close fewer tickets than the colleague making the repairs.
- Overlapping commitments. Ask workers to flag conflicts and confirm that time submitted meets the agreed terms. Investigate specific discrepancies in records the organization is authorized to use. A second professional affiliation, an unanswered chat or a quiet laptop cannot establish double billing.
Time verification should also catch work the employer owes money for. U.S. Department of Labor guidance explains that, for covered employees, employers must count compensable remote work they know or have reason to believe occurred. Give employees a practical way to report unscheduled work without discouraging accurate entries. Keep a client invoice dispute separate from the obligation to pay for compensable work. U.S. Department of Labor, Field Assistance Bulletin 2020-5.
What about keylogging, screenshots, browsing and chats?
Keystrokes and mouse activity. For ordinary time or performance review, leave raw keylogging off. It can capture passwords and private text. Even a tool that only counts keystrokes measures input volume. A person reading a specification, tracing a diagram on paper or speaking with a customer may generate almost none. An activity count is a poor basis for docking pay or accusing someone of working elsewhere.
Screenshots and recordings. A worker-initiated recording of a reproducible error in a test environment can be justified: there is a concrete problem, a reviewer and a point at which recording ends. Random desktop screenshots collect whatever happens to be open, including customer data, and show only selected moments. Continuous video or audio can also capture household members. For routine attendance, choose a shift check-in and a handoff record. Keep home cameras, microphones and personal devices outside that process.
Internet navigation. A security team investigating a specific alert on a managed device may need a relevant domain and timestamp. A manager verifying a Tuesday shift rarely needs a week of URLs, search terms or page contents. An open tab does not establish who was using it, for how long, or for whose benefit. Keep access to security logs tied to their stated purpose.
Chats. An agreed incident channel can show when someone accepted a handoff. Read that exchange if it resolves the question. Searching private conversations for signs of insufficient dedication sweeps in unrelated material and can intrude on protected employee discussions. Covered U.S. employees have rights to discuss wages with colleagues, including in writing. National Labor Relations Board guidance.
Investigate the disputed forty minutes
The team lead can open privately: “The roster shows you on duty. The alert reached the queue at 10:05 and was acknowledged at 10:45. You mentioned a client call. Can we match it to the service record and work out who was covering alerts?” Check time zones, routing and the existing call record before requesting anything more personal. If the call is confirmed, the engineer was working. The unanswered alert still needs an owner. The remedy may be a backup responder when the primary takes a client call.
If the record conflicts with the explanation, describe exactly what remains unresolved and let the worker correct or supplement it. HR or the designated reviewer can authorize a narrowly scoped check for those dates. If evidence establishes overlapping billing, reconcile the affected client entries and address the conduct under the applicable agreement and policy. If the only established failure is missed coverage, address missed coverage. Give the worker the outcome and a way to challenge a factual error.
Set the limit before switching on a tool
Monitoring becomes disproportionate when the extra detail cannot reasonably distinguish the explanations that matter, or when a less intrusive record already answers the question. Before collection, write down its purpose, device and hours covered, data collected, authorized viewers, deletion date and review process. Tell workers what the tool actually does. Check applicable law, client permissions and notice or consent requirements before enabling it. For example, New York specifies prior notice for certain electronic monitoring by covered employers. The UK Information Commissioner separately addresses necessity and proportionality under UK rules. A signed device policy alone cannot settle every jurisdiction’s requirements. New York Civil Rights Law § 52-c and UK ICO monitoring guidance.
This applies the Signal vs. Noise practice from The Vitaver Playbook. Before buying a monitoring tool, have the manager finish this sentence: “If the record shows X, I will do Y; if it shows Z, I will do something different.” In the missed-alert example, the call record could change the decision. A thousand screenshots of the same quiet desktop could not.