Remote Employee Time Tracking: Hours Worked, Breaks and Monitoring Limits

Remote employee time tracking works the same way legally as in-office tracking: the employer must keep an accurate record of hours worked each day and each week for every nonexempt employee, wherever they sit. What changes is how you capture that time and how far you can go in watching it. The answer is to track hours, not keystrokes.

This article covers what counts as hours worked at home, how to handle breaks and interruptions, where overtime risk hides, and what limits apply to monitoring. It is general information, not legal advice. Several states regulate employee monitoring and wage rules differently, so check with counsel or your state labor department.

The rules do not change at home

A nonexempt remote employee is covered by the FLSA like anyone else. You must record hours worked, pay at least the minimum wage ($7.25 federal, higher in many states and cities), and pay 1.5 times the regular rate for hours over 40 in a workweek. Recordkeeping follows 29 CFR Part 516: payroll records for 3 years and time cards for 2 years, with longer periods in many states. See FLSA timekeeping requirements.

The FLSA does not dictate a method. A mobile or web time clock is perfectly acceptable if it is complete and accurate. What does not work is a weekly "I worked about 40" email, because it hides the daily pattern and shows nothing in an audit.

What counts as hours worked at home

Work that is suffered or permitted counts, even if nobody asked for it (29 CFR Part 785). That includes answering a customer message at 9 p.m., finishing a report after the shift, and logging in early to fix a connection problem. If a manager knows or should know the employee is working, the time is compensable.

Time spent waiting also counts if the employee cannot use it freely. Starting the computer, opening required software and waiting for a VPN to connect are pre-shift tasks that belong on the clock when they are necessary to the job. Read what counts as hours worked for more examples.

Breaks, interruptions and meal periods

Short rest breaks of 5 to 20 minutes are paid under 29 CFR 785.18. A bona fide meal period, usually 30 minutes or more and fully relieved of duty, can be unpaid under 785.19. At home, the line blurs: an employee who eats lunch while watching the inbox is not relieved of duty, and the time should be paid.

The simplest policy is to ask employees to clock out for a real meal break and back in when they return, and to tell them to report any interruption. Federal law has no meal or rest break requirement, but states such as California do, with premium pay for violations. Check your state before setting a policy.

Where overtime hides in remote work

Remote work blurs the end of the day, so overtime grows quietly. Suppose an employee earns $22.00 per hour, works 40 hours Monday to Friday, and answers messages for 30 minutes on four evenings. That is 2 extra hours. Math: 2 x $22.00 x 1.5 = $66.00 of overtime pay owed for the week, on top of the $880.00 for the 40 regular hours (40 x $22.00).

That is a small number once, and a large one over a year and a team. If you also lack a record of those evening minutes, the claim becomes the employee's word against yours, and a court can accept a reasonable estimate. Unauthorized work is still work you must pay. Learn more in unauthorized overtime.

Employees accept tracking more easily when the purpose is clear. Explain that the record exists to pay every minute worked and to protect both sides in a dispute, and that you are not measuring how busy someone looks. A one-page policy that says what is recorded, who sees it and how long it is kept is enough for most small teams. See how to write a timekeeping policy.

What monitoring is reasonable

You need to know when work starts and ends. You do not need to capture screens, keystrokes or webcam images to meet the FLSA. Heavy monitoring adds privacy, morale and legal risk, and some states require notice. New York, for example, requires written notice of electronic monitoring since 2022.

A lighter approach captures hours at clock-in and clock-out, plus GPS only at those moments if location matters. There is no general federal law on GPS tracking, but location captured at punch is far less intrusive than continuous tracking. Whatever you choose, tell employees in writing what you collect and why. See GPS tracking of employees.

Exempt remote employees

Exempt employees do not earn overtime, but exemption depends on the salary basis and duties tests, not on job titles or on working from home. The federal salary threshold is $684 per week ($35,568 per year), and several states set higher levels, so verify before relying on a number.

Some employers ask exempt remote staff to log hours too, for workload or project reasons. That is allowed, but the record should not become a way to dock pay for partial days, which can threaten salary basis. Keep it separate from payroll deductions unless you have taken advice.

Common remote tracking mistakes

The first mistake is relying on self-reported weekly totals. An employee who enters "8 hours" every day produces a record that looks neat and proves nothing. A court or investigator will ask for the real start and end times, and a copied number is easy to attack.

The second mistake is ignoring time zones and split days. A remote employee who works 7 a.m. to 11 a.m. and 3 p.m. to 7 p.m. has worked 8 hours across two blocks. The workweek, not the calendar, decides overtime, so fix the workweek start (a fixed, recurring 168-hour period) in writing and apply it to every employee.

The third mistake is leaving corrections undocumented. When an employee forgets to clock out, the manager should adjust the entry with a note and the employee should confirm it. See missed punches and timesheet corrections. Review exceptions weekly, not at year end.

How SimpleWorkshift Helps Remote Teams

SimpleWorkshift lets remote employees clock in and out from the iOS or Android app or from the web, with GPS location attached to each entry. Managers see time entries and exceptions in real time, so an employee who forgot to clock out is caught the same day, not at payroll.

Work schedules per employee, shift changes, time bank and PTO tracking sit in the same account, and overtime is calculated automatically. Custom reports and payroll closing turn the week into clean totals. Try it for 30 days, with no contracts, at simpleworkshift.com.