There’s a strange gap between how carefully we track our own time at home and how little most of us know about what the law actually says about it. You log in, answer messages, maybe run a quick errand mid-day, catch up on Slack after dinner — and somewhere in that blur, the question sits: which of these minutes count? Under the Fair Labor Standards Act, every hour an employer “suffers or permits” work is compensable regardless of location — no remote carve-out exists, which means your kitchen table is legally the same as a cubicle, even when it doesn’t feel that way.
Employee Rights Wage & Hour Law Time Tracking
Heads up — this post may include links to things I use or like, and I might earn a little something if you shop through them. Doesn’t cost you anything extra, and I only mention stuff I’d actually recommend.
The Same Rules, Just a Different Address
The principle sounds simple enough: federal employment law doesn’t distinguish between your home office and a company building. The Fair Labor Standards Act covers minimum wage, overtime eligibility, and recordkeeping — and every word of 29 CFR Part 785, which defines hours worked, applies identically at home. No special carve-out for remote workers exists, and the Department of Labor’s Fact Sheet #22 makes clear that “hours worked” includes all time the employer knows or has reason to know about — authorized or not.
What trips people up is the practical gap between that rule and how remote work actually feels. In an office, the shift has a start and end. You badge in, you badge out. At home, the boundaries dissolve. A message arrives at 7:42 PM. You answer it in under a minute. That minute is compensable time under federal law — and the employer who saw the reply has constructive knowledge that work happened. The rule doesn’t bend for convenience, and it doesn’t depend on whether you asked permission first.
The most common assumption I hear is that if work wasn’t scheduled or approved, it doesn’t need to be paid. That’s exactly backward. The “suffered or permitted” standard means the employer’s duty to pay attaches when they know work is happening — regardless of whether they wanted it to happen. The right response to unauthorized after-hours work is discipline, not wage theft. The distinction matters, and many remote workers don’t realize they’re on the winning side of it.
What Counts as “On the Clock” at Home
The details matter more at home because the cues that used to separate work from not-work have disappeared. A few common scenarios give a sense of where the lines fall.
Booting Up and Logging In
A 2025 federal ruling from the Southern District of Ohio — Lott v. Recker Consulting LLC — clarified that a few minutes spent turning on a computer, typing credentials, and launching applications at the start of a shift are generally not compensable. Those actions count as “preliminary activities” under the FLSA. The analysis flips, though, if your employer requires hardened equipment with a lengthy security boot process or an extensive pre-shift checklist. If you’re spending fifteen minutes running through mandatory startup steps before your first email, that time likely should be on the clock.
After-Hours Messages and On-Call Response
This is where most disputes live. A manager sends a Slack at 8:30 PM. You reply at 8:32. That’s two minutes of work — and it’s compensable. The employer saw the reply; they have actual knowledge. If your status shows as “active” after hours, that’s constructive knowledge. Under the DOL Field Assistance Bulletin 2020-5, an employer who has a clear reporting procedure and an employee who uses it has met the “reasonable diligence” standard — but the employer cannot implicitly or explicitly discourage accurate reporting. A manager saying “don’t put that on your timesheet” or “we don’t pay for quick replies after hours” destroys that defense and creates personal liability for unpaid wages plus liquidated damages.
Mid-Day Personal Errands
If your employer allows a flexible schedule — work 7–11 AM, take a long lunch for an appointment, return 1–5 PM — the personal errand window is unpaid because you’re completely relieved from duty. Most flex policies make this explicit. The catch: if you answer a single work email or take a quick call during that window, the entire break may become compensable. The rule from 29 CFR §785.19 is clear — a meal period is unpaid only when you’re fully relieved from duty. Eating while monitoring your inbox is not fully relieved.
Meal Breaks, Rest Breaks, and the Kitchen-Desk Problem
Federal law doesn’t mandate meal or rest breaks — that’s left to the states. But when breaks are provided, the FLSA draws a bright line between short rest breaks (5–20 minutes, always paid under 29 CFR §785.18) and bona fide meal periods (30+ minutes, unpaid only when fully relieved under 29 CFR §785.19).
At home, the “fully relieved” test gets messy. Your kitchen is ten steps from your desk. It’s tempting to eat while scrolling email or to answer a quick Teams message during lunch. But that message makes the entire meal period compensable — and if it happens regularly, you may be owed back pay. The law doesn’t care that your kitchen is close. It cares whether you were actually free from work duties.
- Log every break, even short ones. If your time-tracking system has a break function, use it. If not, keep a separate note with start and end times for every meal period longer than 20 minutes.
- Physically step away from the workspace during lunch. Leave the room. Close the laptop. The spatial separation reinforces the legal boundary and makes it harder to accidentally slip into compensable time.
- Document interruptions when they happen. A quick note — “12:34 PM, answered Sarah’s question about the Q3 report, 2 minutes” — turns a vague memory into evidence if a dispute arises later.
When Monitoring Crosses a Line
Employers have more tools than ever to track what remote workers do — keystroke logging, mouse movement tracking, webcam screenshots, productivity scoring. The legal question isn’t whether these tools exist; it’s how they’re used and what the worker has consented to.
Under federal law, the Electronic Communications Privacy Act generally permits monitoring on company-owned systems when there’s a business purpose and the employee has been notified. A clear, acknowledged policy serves both purposes — it documents consent and establishes the business rationale. On personal devices, the analysis is harder. Mandating monitoring software on a worker’s own laptop raises consent issues, privacy claims, and potential statutory violations in states that require written notice before electronic surveillance.
Several states — Connecticut, Delaware, and New York — have statutes requiring written notice before monitoring electronic communications. New York’s law, effective 2022, covers email, internet usage, and phone. Connecticut’s notice requirement reaches keyboard and mouse logging. In Texas, case law has established similar warnings about consent limits on personal devices. If your employer hasn’t disclosed what’s being tracked, the monitoring may be unlawful.
The pattern I see most often isn’t the tracking itself — it’s tracking that reaches into spaces with a reasonable expectation of privacy. Bathrooms, bedrooms, off-hours communications on personal accounts, and home camera feeds when the worker is off shift. No business-purpose exception covers those spaces. An employer who monitors a worker’s bedroom via webcam or records personal calls during lunch is creating real legal exposure for themselves and a potential claim for the worker. Timekeeping doesn’t require keystroke-level surveillance. A simple clock-in and clock-out with break tracking is fully compliant with federal rules — everything beyond that is a choice, not a requirement.
The important distinction: timekeeping and productivity surveillance are different legal animals. Timekeeping records start, stop, and lunch for FLSA compliance. Productivity surveillance infers what you did every minute — it has no statutory pedigree. Defensible timekeeping doesn’t require keystroke-level data, and an employer who insists on that level of detail may be creating liability rather than avoiding it.
State Laws Change the Math
Federal law sets the floor. State law stacks on top, and the differences matter enormously for remote workers. If your employer is based in one state and you live in another, the law of the state where you physically perform your work generally governs wage and hour requirements — not the state on the company letterhead.
California Labor Code §510 requires time-and-a-half after 8 hours in a single day and double-time after 12 — exceeding the FLSA weekly standard. Meal and rest break rules survive the move to remote work: a 30-minute uninterrupted meal break by the 5th hour, and a 10-minute paid rest break for every 4 hours worked. Labor Code §2802 requires employers to reimburse all necessary business expenses, including a portion of home internet and phone bills. These obligations don’t disappear just because your manager is in another state.
New York has higher minimum wages in NYC and surrounding counties, wage theft prevention notices, and strict final paycheck timing rules. Illinois requires written notice of pay rates and paydays, has a strong Equal Pay Act that prohibits salary history inquiries, and mandates equal pay certifications for larger employers. Texas follows the federal minimum wage floor and operates under at-will employment, but still requires compliance with the Texas Payday Law for wage claims. Each state also has its own record-retention window — California requires 4 years for many wage records, New York 6 years — which matters if a wage claim arises months after you’ve left the role.
That’s probably wrong. The state where you perform work generally controls wage and hour requirements, leave entitlements, meal and rest break obligations, and termination procedures. Exceptions exist for workers’ compensation and unemployment insurance, which can involve both states, but for daily wage and hour compliance, your physical location is the anchor. If your employer pushes back, it’s worth consulting an employment attorney in your state — and keeping your own time records in the meantime.
What to Do When Your Records Don’t Match
Disputes over hours happen. Your log says you worked 44 hours; the employer’s system says 40. The gap might be after-hours messages, a few minutes of pre-shift setup, or a lunch period you didn’t actually get to take. When records disagree, federal case law gives the worker a significant advantage.
In Anderson v. Mt. Clemens Pottery Co. (1946), the Supreme Court held that when an employer’s records are inaccurate or inadequate, the burden shifts to the employer to disprove the employee’s reasonable estimate of hours worked. Your contemporaneous log — kept day by day, not reconstructed from memory — carries weight. A simple notebook, a spreadsheet, or a timekeeping app on your phone that records clock-ins, breaks, and after-hours interruptions with timestamps creates a paper trail that can shift the burden in a wage claim.
If you’re in a dispute, a few steps matter:
Compare every stub to your log
Five minutes per pay period catches almost every error before it compounds. Look for consistent patterns — exactly 40 hours every week, zero entries for after-hours exchanges you know happened, or missing overtime in weeks with heavy evening work.
Document interruptions as they happen
A short note for every after-hours Slack ping, weekend email, or on-call response — timestamp, duration, who pinged you. That note turns a vague memory into evidence. Save export copies of your log every pay period.
Use the employer’s system first
The DOL’s reasonable diligence standard means if your employer has a clear reporting procedure and you use it, their obligation is met. If you bypass the system and only keep your own log, courts may refuse to hold the employer liable for hours you didn’t report through their process. Use both — report through their system and keep your independent record as backup.
Bring it up directly if the pattern is clear
If you notice a recurring gap — say, your Friday afternoon messages regularly go unlogged — say something. A sample line: “I’ve noticed my timesheet doesn’t reflect the after-hours responses I’ve been logging on my end. Could we walk through the time-tracking process to make sure I’m using it correctly?” That frames it as a process question, not an accusation, and puts the employer on notice.
✦
Here’s what I’ve come to think: the legal framework for remote time tracking is clearer than most of us assume, but enforcement depends entirely on documentation. The FLSA gives you the right to be paid for every hour your employer knows or should know you worked. That right doesn’t enforce itself. A contemporaneous log, a habit of comparing stubs, and a willingness to ask clarifying questions — those are the tools that turn a legal right into something you can actually use.
If you’re unsure where your state falls on a specific issue — meal break requirements, expense reimbursement, monitoring notice — the DOL’s state labor law guide is a solid starting point. For anything that touches a specific dispute or potential violation, an employment attorney in your state is worth the call. The law is on your side, but it expects you to keep receipts.
Your rights under federal and state wage laws don’t weaken when you work from home. The same protections apply — but proving them requires a habit of documentation that most remote workers don’t have. Start a log this week. Compare your first stub to it. You’ll either catch an error or confirm things are correct. Either way, you’ll know where you stand.