A Slack notification buzzes at 9:12 PM. You read it, tap out a two-sentence reply, and close the app. That took three minutes. Wednesday you stayed on a call until 5:20 PM. Friday your timesheet says 40.0 hours. Your own tally says 41.5.

Remote work didn’t kill the time clock. It scattered the punch points across your day. The law still requires an accurate count of every one of them.

Here is what the FLSA demands, which tracking methods hold up, and how to avoid a wage claim over moments that felt too small to log.

When does the remote employee time tracking day actually start?

In an office, the shift begins when you walk through the door. At home, the line is thinner. You open your laptop at 7:58 AM to check the calendar. You read a work message while the coffee brews. The company never told you to do either.

The Fair Labor Standards Act has required accurate records of hours worked since 1938. The obligation does not shrink because the employee works from a spare bedroom. The U.S. Department of Labor has never carved out remote workers. If the employee is non-exempt, the employer must record the time.

The harder question is knowing what the employee did. The law holds the company responsible for all time it “suffers or permits,” whether it asked for the work or not. A remote setup makes that harder to see and easier to get wrong.

FLSA recordkeeping for remote employee time tracking

The FLSA’s recordkeeping requirements are location-blind. For every non-exempt employee, the firm must keep:

  • Name, address, Social Security number, sex, occupation
  • The workweek start day and time
  • Hours worked each day and each week
  • Regular hourly rate, straight-time earnings, overtime earnings
  • Additions to or deductions from wages
  • Total wages paid each pay period and the date of payment

Payroll records stay for three years. Time cards, wage rate tables, and work schedules stay for two. No format is mandated. Paper, a spreadsheet, a web clock, a mobile app: all are fine, provided they are accurate.

The DOL has never required a physical punch clock. A browser-based tool or a phone app can work. But if a dispute lands in court, the enterprise carries the burden of proving the records are correct.

Which tracking method fits a distributed team?

Two approaches show up most often. A third is common but risky.

Web-based time clocks. The employee logs into a browser, clicks a button to punch in and out. The server records the timestamp. Works on any device with internet.

Mobile apps. The employee clocks in on a phone. GPS can optionally tag the location. That helps field staff, but requiring location tracking on a personal device raises privacy questions in states like Illinois (under BIPA) and California.

Productivity monitoring software. Tools that track keystrokes, mouse movements, screenshots, and app usage. These are not time clocks. They measure activity, not hours worked. An employee reading a PDF for 20 minutes may show zero keyboard activity. The software calls it idle. The FLSA calls it work. Using monitoring data as the sole basis for pay invites trouble.

The cleanest approach: a simple punch clock, web or mobile, that captures when the employee starts and stops. It is legal, it is straightforward, and it sidesteps the surveillance problems that monitoring software creates.

Does a three-minute after-hours email count as remote employee time tracking?

The FLSA defines “hours worked” as all time the employee is “suffered or permitted to work.” That includes:

  • Logging into company systems and beginning tasks
  • Checking and replying to work email
  • Participating in Slack or Teams conversations about work
  • Thinking through a job-related problem, if the enterprise expects it

The rule: if you are doing something for the outfit, and it knows or should know you are doing it, the time counts.

The de minimis doctrine carves out very short periods that are irregular and hard to record. Courts have not drawn a bright line. A minute or two once a week may qualify. Five minutes of after-hours email every night almost certainly does not.

Can a late-night email trigger a wage claim?

An employee reads a message from the couch at 9:15 PM and fires off a reply. Nobody asked them to. Does the company owe pay?

Under the “suffer or permit” standard, if the employer knows or has reason to know the employee is working, the time is compensable. When the reply lands in the inbox, the employer knows. When the Slack timestamp appears, it knows. Silence is not a defense.

The practical answer: either prohibit after-hours work entirely and enforce the ban, or pay for the time. A policy that says “no after-hours work” but is ignored by both sides will not hold up.

For the employee: keep your own log. If you send an email at 9:15 PM, note it. If it happens regularly, raise it with your manager.

Is productivity monitoring a payroll system for remote employee time tracking?

Monitoring software tracks keystrokes, clicks, and active-window time. A time clock records the span between punch-in and punch-out. They answer different questions.

An employee might read a printed document, think through a design problem, or take a work call. None of those actions move a mouse. If the business docks pay because the software showed 12 minutes of inactivity, it is on thin legal ground.

Use productivity tools for coaching and process improvement. Keep them away from payroll. Let the employee clock in and out. Use the activity data only to spot training needs or workflow bottlenecks.

Whose overtime rules apply when the team is scattered across states?

A company is based in Texas. The employee works remotely from California. Which overtime rules govern?

The law of the state where the work is performed controls. If the employee sits down in California, California’s daily overtime triggers apply: time-and-a-half after 8 hours, double time after 12. The company’s Texas address does not matter.

This creates compliance complexity. The operation must track not only hours but the employee’s location on each workday. States with stricter rules than federal include California, Oregon, Colorado, Alaska, and Nevada. Others, such as Florida, Texas, and Georgia, largely follow the FLSA.

If an employee splits time between two states, the picture gets murkier. A common approach: apply the stricter state’s rules to all hours to reduce litigation risk. Consult an attorney who practices in the employee’s home state.

Best practices for the employer: policy, training, audit

  1. Write a remote work time policy. Define what counts as work: email, Slack, calls, document prep. State when employees must clock in and out. Require prior approval for after-hours work and enforce the rule.

  2. Use contemporaneous records. The strongest evidence is a timestamp captured when work starts and stops. A web or mobile punch clock provides that. An end-of-week spreadsheet that says “I think I worked 42 hours” is weak evidence in a wage claim.

  3. Train managers. A manager who texts an employee at 7 PM with a “quick question” has just created compensable time. Managers must understand the suffer-or-permit standard.

  4. Audit after-hours activity. Run a report of late-night or weekend clock-ins and email timestamps. If you see patterns, address them: pay the time or stop the activity.

  5. Keep records for three years. This covers time cards, payroll records, and any communication about hours worked.

Best practices for the employee: log it or lose it

You have the right to keep your own record of hours worked. Exercise it.

  • Use a simple app or a notebook. Record the start and end of every work session, including brief after-hours tasks.
  • If the company’s time clock shows different hours than your log, flag it in writing. Email is best. Ask for a correction.
  • If you regularly work after hours without pay, keep a detailed log. That log is evidence if you need to file a wage claim.

The FLSA entitles you to pay for all hours worked. A contemporaneous personal log shifts the burden of proof in your favor.