You fire off a quick text at 9 p.m. — "Can you resend the client file tonight?" Your employee answers in four minutes, and you both move on. No timecard entry, no overtime math, no second thought. Here is the expensive part: under the Fair Labor Standards Act, those four minutes are compensable work time if you knew or had reason to believe they happened. Multiply that by a team, by every evening, by two or three years of lookback — and your casual texting habit has quietly become a wage claim.
This is not a corner case. In fiscal year 2025, the Department of Labor's Wage and Hour Division recovered more than $259 million in back wages for nearly 177,000 workers, and the year before it topped $273 million. A large share of that money comes from ordinary hours-worked disputes: time that was worked, suffered, or permitted — and never paid. If your people answer messages after hours, this article is about your exposure and how to close it.
The Rule That Makes You Liable: "Suffered or Permitted"
The FLSA does not only require you to pay for work you requested. Federal regulation 29 CFR 785.11 states the broader standard: work not requested but suffered or permitted is work time. Section 785.12 extends that rule to work performed at home or away from the job site. The trigger is knowledge — if you know or have reason to believe the work is being performed, the time counts as hours worked. The reason the employee kept working is immaterial.
Apply that to after-hours messages and the logic is unforgiving:
- You sent the text. You obviously know the reply happened. Knowledge is established by your own outbox.
- You received the answer. An email timestamped 10:42 p.m. is constructive knowledge sitting in your inbox. "I never looked at the clock" is not a defense.
- Your managers expect fast replies. If supervisors routinely message hourly staff at night and praise the quick responders, you have reason to believe the work is happening — you built the culture that produces it.
- The employee volunteered it. Enthusiasm changes nothing. An employee who answers "just to be helpful" without being asked is still suffered or permitted to work.
The one structural exception is classification. These rules protect nonexempt employees — generally hourly workers and salaried workers who fail the duties or salary tests for exemption. Genuinely exempt salaried employees receive a flat salary that covers all hours, including the 11 p.m. email thread. But that shield only works if the classification is correct: the duties must fit an executive, administrative, or professional category, and the salary must clear the federal floor — currently $684 per week ($35,568 per year), back at its 2019 level after a federal court vacated the Labor Department's 2024 increase. Misclassify a nonexempt worker as exempt and every after-hours message becomes unpaid overtime on top of an already broken classification.
Which After-Hours Contact Actually Counts as Work?
Not every ping is equal. The question is always whether the employee performed compensable work — and for nonexempt staff, the bar is low.
Almost certainly counts:
- Answering a substantive question ("What did the client decide on pricing?")
- Resending files, looking up records, checking a system
- Troubleshooting a problem a coworker or customer raised
- Joining a call, even a short one
- Reviewing a document you sent "for tomorrow" tonight
The waiting itself is a separate question. Federal rules distinguish being "engaged to wait" — stuck at the workplace or so restricted that personal life is effectively impossible, which is paid — from "waiting to be engaged" — leaving word where you can be reached while living your evening, which is not. A vague "keep your phone on" usually falls in the unpaid second bucket. But the moment the employee picks up and does something, that responsive work is compensable regardless of how the waiting time was classified. The gray zone is the tight-leash arrangement: stay within ten minutes of the shop, answer within two rings. The Labor Department judges those case by case, and the tighter the restrictions, the more likely the whole period counts.
Bottom line for owners: stop asking whether the message was "really work." If a nonexempt employee spent time serving your business at your implicit or explicit direction, budget it as work.
The "It Was Only Two Minutes" Defense Is Narrower Than You Think
Many owners assume tiny increments of time can be ignored. There is a real doctrine for that — the de minimis rule in 29 CFR 785.47 — but it covers far less than people hope.
The regulation lets employers disregard only insubstantial or insignificant periods beyond scheduled hours that cannot as a practical administrative matter be precisely recorded. The Labor Department's own guidance sharpens the test: it applies to a few seconds or minutes of uncertain, indefinite duration, where the failure to count the time is justified by industrial realities. And it draws a hard boundary: you may not arbitrarily skip any part of an employee's fixed or regular working time, or any practically ascertainable period the employee regularly spends on assigned duties — however small.
Three reasons smartphones destroy this defense:
- The time is precisely recorded. Every text, email, and call carries a timestamp. Nothing about a 9:04 p.m. reply is "uncertain or indefinite" — your phone logs prove exactly when it happened.
- Regular beats small. Courts and the Department consistently hold that time which recurs regularly must be counted even when each instance is brief. Four minutes every evening is not a trifle; aggregated over a year, it is roughly 24 hours per employee.
- Tracking is trivially easy now. The doctrine excuses time that cannot practically be recorded. When the record creates itself in your messaging app, "impractical to track" is a difficult argument to make with a straight face.
Some states go further and reject the federal de minimis cushion for regularly occurring work altogether. Treat the doctrine as covering genuinely one-off seconds — a single accidental pocket-dial callback — and pay for everything else.
Timekeeping Traps That Manufacture Violations
Most off-the-clock liability is not a policy decision. It is plumbing. Four common setups quietly generate unpaid time:
1. Rounding that only rounds one way
Neutral rounding — say, to the nearest five minutes or quarter hour — is permitted only if it averages out over time and does not systematically shortchange employees. A system that rounds 8:07 down to 8:00 but never rounds 4:53 up to 5:00 is not neutral; it is a pay cut wearing a timekeeping costume. Audit a month of punches: if the rounding errors skew consistently in your favor, fix the configuration before an investigator does the same math.
2. Automatic lunch deductions plus working lunches
Auto-deducting 30 minutes for lunch is common and legal — until employees keep answering messages through lunch. Every "quick question" handled over a sandwich converts that half hour back into compensable time. If your team cannot actually take an uninterrupted meal break, either enforce a real break (phones down, coverage assigned) or stop auto-deducting and pay reported time.
3. "No overtime without prior approval" as a payment policy
You are allowed to require advance approval for overtime, and you are allowed to discipline employees who work unapproved hours. What you may not do is refuse to pay for overtime that was worked. The rule is pay first, discipline separately. A written policy that says unapproved overtime "will not be paid" is a confession in the employee handbook — it documents a practice of exactly what the statute forbids.
4. Edited, shaved, or manager-rounded time entries
Hours must reflect hours actually worked. Adjusting entries to match schedules, trimming a few minutes "to keep it clean," or requiring employees to get manager sign-off that discourages reporting extra time all create the same paper trail problem: your records show compliance while your message logs show work. Keep the two honest with each other — investigators will compare them.
What It Costs When You Get It Wrong
The arithmetic of an hours-worked violation surprises owners because the wages are the smallest line item:
- Back pay with a long tail. Employees can recover underpayments going back two years, or three if the violation was willful — meaning you knew or recklessly disregarded the risk. Each shorted paycheck starts its own clock.
- Liquidated damages that double the bill. The statute adds an equal amount on top of the unpaid wages. The only way out is proving you acted in good faith with reasonable grounds for believing you complied — a defense courts construe narrowly.
- The other side's legal fees. A prevailing employee recovers attorney fees and court costs from you, which is why small individual claims attract representation: a $1,200 wage dispute can carry multiples of that in fees.
- Civil penalties per violation. The Department can assess civil money penalties for repeated or willful minimum-wage and overtime violations — a per-violation figure adjusted annually for inflation, recently in the roughly $2,500 range. Across a team with nightly messages, violations multiply fast.
- Retaliation claims on top. Firing, demoting, or cutting the hours of someone who complains — or cooperating with an investigation — creates a separate claim with its own damages. Complaints to the Department are kept confidential, so you may not even know who triggered an inquiry.
And remember that federal law is the floor. Several states require daily overtime past eight hours, mandate itemized wage statements that make discrepancies easy to spot, or add steeper penalties. Employees always get the protection of whichever law is more generous. There is currently no federal "right to disconnect" law limiting after-hours contact itself — the legal question is not whether you may text, but whether you paid for the reply.
A Practical Compliance Playbook for Small Employers
You do not need a legal department. You need five habits:
1. Get classification right first
Audit every role against the duties tests and the $684-per-week salary floor. Anyone close to the line should be treated as nonexempt until you are certain. One misclassified employee answering nightly texts is two violations stacked: bad classification plus unpaid overtime.
2. Write an after-hours communication policy — and a reporting channel
Spell out who is expected to respond after hours and who is not. Give nonexempt employees a simple, no-retaliation way to report all time worked, including message replies: a timekeeping app entry, a weekly email to a supervisor, a shared form. The policy that saves you is not "don't work off the clock" alone — it is "report everything, and here is exactly how."
3. Make timekeeping capture small increments
Your system must record to the minute, and managers must be trained that a two-minute reply is reportable time, not a favor. Review message timestamps against time entries monthly; the first time they diverge, you have found your leak while it is still cheap.
4. Train managers that speed has a price
The costliest after-hours work is manager-driven: the supervisor who texts "ASAP??" at 10 p.m. and rewards instant replies. Teach leads to batch non-urgent messages for the morning (scheduled send exists for a reason), to mark genuinely urgent items explicitly, and to never punish a delayed reply from nonexempt staff. Culture is a payroll control.
5. Pay first, discipline separately, keep records for years
When unapproved overtime shows up on a timesheet, pay it — then address the policy violation through coaching or discipline, in writing, without touching the paycheck. Keep payroll records for at least three years and time records for at least two; they are your evidence that the system worked.
Run this audit quarterly. Pull one week of after-hours message logs, match them against time entries, and fix every gap the same pay period. A fifteen-minute review beats a two-year lookback.
Overtime You Can't See Still Hits Your Books
Here is the bookkeeping angle owners miss: unrecorded after-hours time does not just create legal exposure — it corrupts your labor-cost data. If replies happen off the books, your job costing understates the true cost of serving the clients who generate the messages, your overtime premium never lands in the right expense account, and your staffing decisions rest on hours that never happened on paper. Accurate time capture is what lets you price work, schedule coverage, and spot the client whose "quick questions" consume five unpaid hours a month.
That is a records problem as much as a legal one. Track after-hours time in the same system as everything else, post overtime premium to its own line so you can see it grow, and review labor-cost reports monthly — a rising premium line is often the first sign that after-hours expectations are drifting. If you keep your books in plain-text accounting, explicit version-controlled entries make that audit trail trivial to inspect; the docs cover getting started with structured transaction records, and the dashboard gives you a visual read on where labor dollars actually go.
Keep Your After-Hours Habit From Becoming a Wage Claim
Your 9 p.m. text is not the problem. The missing time entry is. The FLSA's suffered-or-permitted standard means knowledge is liability: if you knew or should have known nonexempt employees were answering, you owe them for the time — down to the minute, at time-and-a-half past forty, with doubled damages and the other side's legal fees waiting if you guessed wrong. The de minimis cushion will not save regularly occurring message time in an era when every reply timestamps itself.
The fix is unglamorous and cheap: classify correctly, write the policy, capture every minute, train your managers, and audit the logs against the timesheets every quarter. Do that, and after-hours messages go back to being what they should be — a minor cost of doing business, recorded, paid, and forgotten — instead of a quiet liability compounding in everyone's pockets.
Simplify Your Financial Management
As you tighten up timekeeping and payroll compliance, keeping clean, auditable financial records makes every audit — internal or government — dramatically easier. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready, so your labor costs, overtime premium, and payroll liabilities are always traceable to the source. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
