Work TimeTimekeeping · Monitoring · Evidence

Timekeeping & the Law

Timekeeping for Remote and Hybrid Staff

Section
Timekeeping & the Law
Written
2026-08-06
Last checked
2026-08-06
Law and programme rules in this area change. This article states the position at the time of writing and is revised when it moves. It is general information, not legal advice.

The legal obligations are identical for remote and on-site staff. Every hour worked is recorded, every hour is paid, the same records are kept for the same periods.

Monitask provides a product-oriented overview of remote workforce management software.

Federal wage-and-hour guidance is maintained by the U.S. Department of Labor Wage and Hour Division.

What changes is that nobody observes the start and end of the day, so the failure modes are different — and quieter.

General information, not legal advice. Multi-state remote work raises additional obligations; take advice.

The failure modes

Fragmented work. Twenty minutes before breakfast, a fix after dinner, a message answered at 10pm. None of it feels like a shift, so none of it is recorded. All of it is compensable if the employer knew or should have known.

No natural boundary. On-site, the commute marks the ends of the day. At home there is nothing, and the day expands.

Availability creep. A non-exempt employee who keeps the messaging app on their phone is subject to an expectation, and answering is working time. See off-the-clock work.

Breaks not taken or not recorded. Meal periods eaten at the desk while working. Where the state requires a duty-free meal period and premium pay for missing one, this is a direct liability.

Retroactive timesheets. Filled in on Friday from memory. Not contemporaneous, less accurate, and materially weaker if ever challenged.

Records that only capture the "main" block. A system that records 9 to 5 while the actual pattern is 8 to 12, 2 to 4, and 9 to 10pm is not an accurate record.

What to put in place

Say plainly that all time must be recorded. Including the five minutes at 10pm. Employees frequently believe small increments do not count, or that recording them will look bad.

Set a schedule, even for flexible work. Not to constrain the person, but to define what is normal and to make deviation visible. "Core hours 10 to 3, flexible either side, all hours recorded" is workable. "Work whenever" is not a timekeeping arrangement.

Set an availability policy for non-exempt staff. Either they are not expected to respond outside recorded hours, or that time is recorded and paid. Leaving it to individual judgement produces unpaid work and inconsistency between managers.

Make recording frictionless and mobile. If recording twenty minutes takes two minutes of navigation, people will not do it. This single point causes more incomplete records than any policy failure.

Require contemporaneous entry, daily rather than weekly.

Handle breaks explicitly. Recorded, and in states requiring duty-free meal periods, treated as such — the employee genuinely relieved, not eating while monitoring messages.

Never use automatic meal deduction for remote staff. You have no way of knowing whether a break was taken, and an automatic deduction with no visibility is a mechanism for producing unpaid work.

The temptation to monitor instead

The instinct when you cannot see people is to watch them. It is worth naming why this is the wrong response.

It does not solve the timekeeping problem. Activity monitoring records activity, not hours worked. It will not tell you whether the employee answered a message at 10pm, and it will not produce a compliant record.

It creates new obligations. Notice requirements in several states, and additional questions where the device is personal. See employee monitoring: what is lawful and monitoring on personal devices.

It costs more than it returns. See productivity surveillance.

A timekeeping problem is solved by making recording easy and expected. It is not solved by observation.

The multi-state problem

This is the part remote work created and most employers have not fully worked through.

An employee's work state generally determines which rules apply — not where the employer sits.

Depending on the state, remote employees can bring:

  • A higher minimum wage
  • A higher salary threshold for exempt status. California's is roughly double the federal figure, which means an employee correctly classified as exempt in one state can be non-exempt in another at the same salary
  • Daily overtime, not only weekly. California pays overtime after eight hours in a day
  • Mandatory meal and rest periods, with premium pay for missed ones
  • Different rules on rounding. California, Washington and Oregon have all narrowed or effectively removed it. See rounding time entries
  • Different final pay deadlines on termination
  • Paid sick leave entitlements
  • Pay transparency and wage statement requirements
  • Registration and payroll tax obligations for the employer in that state

Know where every remote employee actually works, and keep it current. An employee who moves without telling anyone creates a compliance gap that nobody discovers until something else goes wrong.

Decide which states you are willing to employ in, and say so. "Remote — US, in these states" is a normal formulation and prevents the problem at hire.

Hybrid adds a wrinkle

On-site days may involve compensable travel in some circumstances — particularly where an employee is required to travel to a location that is not their regular workplace. See travel, training and on-call time.

Do not run two timekeeping systems for the same person depending on where they are. One record, all days.

Watch the pattern. Employees who work longer on remote days than on-site days are common, and the extra time is frequently unrecorded.

A short check

  • [ ] Every remote employee's work state is recorded and current
  • [ ] Requirements checked for each of those states, not only the employer's
  • [ ] Exempt classification re-tested against each state's threshold
  • [ ] All hours recordable, including short fragments, from a phone
  • [ ] Entry is daily, not weekly
  • [ ] No automatic meal deduction
  • [ ] Availability expectations for non-exempt staff stated in writing
  • [ ] Managers trained that discouraging recording creates liability rather than saving cost

The last item is the one that fails most often, and it fails for the same reason everywhere: a manager measured on overtime spend, with no measure of unrecorded work, is being paid to create the problem.