HN Debrief

Michigan bill would bar employers from requiring after-hours coms with workers

  • Labor
  • Regulation
  • Startups
  • Developer Tools

The story is about Michigan’s proposed Workplace Boundaries Act, which would bar employers from requiring employees to handle work communications outside their assigned hours unless that time is treated as paid work. The bill is aimed less at obvious emergency on-call rotations and more at the everyday creep of off-hours demands like coverage texts, executive messages at night, and "quick" follow-ups that quietly turn free time into unpaid standby time.

If your company relies on informal evening Slack pings, ad hoc schedule changes, or unpaid on-call expectations, assume that practice is getting political and may become a compliance issue. The practical fix is to make after-hours availability explicit, narrow, and paid instead of treating it as a fuzzy cultural expectation.

Discussion mood

Mostly supportive of the bill’s intent, with frustration at commenters treating their own high-autonomy tech jobs as universal. The biggest concerns were draft ambiguity, enforceability, and whether employers would route around the rule, but the dominant mood was that unpaid after-hours availability is real and should be treated as paid labor when it is effectively required.

Key insights

  1. 01

    Required availability is already on-call work

    The useful line is not whether a task only takes five minutes. It is whether the employer expects a response and can punish you for ignoring it. Once an evening inbox check or late-night message becomes mandatory, the employee is no longer off duty in any meaningful sense. That reframes the bill away from banning contact and toward forcing employers to admit when they are buying standby time.

    Audit every role that includes "just keep an eye on things" outside normal hours. If nonresponse has consequences, convert that expectation into a defined on-call window with explicit pay and response rules.

      Attribution:
    • quadrifoliate #1 #2
    • beAbU #1
  2. 02

    State laws can reset competition norms

    The strongest answer to the "businesses will be less competitive" objection was that labor standards often work like speed limits. If everyone in a jurisdiction has to absorb the same constraint, no single employer is uniquely punished for not squeezing extra unpaid time out of staff. State-level laws also tend to be how US labor rules start before federal cleanup happens later.

    Do not assume a state rule is just a local nuisance. If enough states copy it, your operating model becomes the outlier, so build policies that can survive wider adoption.

      Attribution:
    • gwbas1c #1
    • cadamsdotcom #1
  3. 03

    On-call compensation changes incentives

    Several concrete examples showed why separate on-call pay matters beyond fairness. Google paying different rates for different response windows forces teams to justify whether a five-minute commitment is truly necessary. Other comments described the opposite pattern, where companies folded on-call into salary, then kept expanding expectations because the marginal cost became invisible. Paying explicitly makes managers feel the cost of operational chaos and usually reduces bogus urgency.

    Price response-time commitments separately from base salary. Once managers see the real cost of a five-minute pager or weekend standby, many services will suddenly stop needing it.

      Attribution:
    • KennyBlanken #1
    • al_borland #1
    • tarellel #1
    • Analemma_ #1
    • siliconc0w #1
  4. 04

    Personal devices are part of the boundary fight

    A surprisingly practical subthread tied after-hours work to bring-your-own-device expectations. If employers require a proprietary MFA app, Duo, Microsoft Authenticator, or other work software on a personal phone, they are already eroding the wall between work and private time. Commenters pointed to YubiKeys, FIDO tokens, TOTP-compatible alternatives, and employer-provided devices as cleaner options. The device policy shapes how easy it is for work to spill into off-hours life.

    Review your BYOD and MFA setup as part of work-boundary policy. If employees need personal phones to stay reachable or authenticated, you are making after-hours separation harder than it should be.

      Attribution:
    • childofhedgehog #1
    • brendoelfrendo #1
    • tassadarforaiur #1
    • bluefirebrand #1
    • nekusar #1
  5. 05

    Tech workers are badly sampling the labor market

    The most valuable meta point was that people with leverage keep mistaking their experience for the baseline. A developer who can ignore messages, run two phones, or negotiate comp for pager duty is not representative of workers in restaurants, retail, education, hospitality, or admin roles. That blind spot makes labor stories look like edge cases when they are often just happening to people outside the usual tech bubble.

    When evaluating labor-policy risk, do not use senior engineering culture as your model employee. Look at support staff, hourly workers, assistants, and lower-leverage functions first, because that is where informal pressure usually bites hardest.

      Attribution:
    • roughly #1
    • quadrifoliate #1
    • siliconc0w #1
    • BoxFour #1

Against the grain

  1. 01

    Managers can still imply pressure off the books

    The sharpest objection was that a manager does not need to write "required" in Slack to make an expectation real. Employers can tell investigators that off-hours responses were voluntary while workers still understand missed replies will count against them. That means the bill may clean up the obvious cases while leaving the hardest ones in the gray zone of implied retaliation.

    If you want this kind of policy to work inside a company, pair it with written escalation rules and protected reporting channels. Otherwise managers can preserve the same pressure while changing only the wording.

      Attribution:
    • oatmeal1 #1
    • throwaway85825 #1
  2. 02

    Portable roles may move elsewhere

    Some commenters argued that jobs with easy geographic substitution like assistants, support work, and some tech roles could simply be shifted to states or countries with looser rules. They were not denying abuse. They were warning that labor protections bite differently in roles employers can relocate quickly, especially where cost pressure is already pushing work offshore.

    If your business depends on distributed support or on-call-heavy roles, model location strategy before laws like this spread. If you are a policymaker, expect stronger results in place-bound sectors than in highly portable back-office work.

      Attribution:
    • ElProlactin #1 #2
    • hintymad #1

In plain english

Duo
A commercial authentication product often used by organizations for login approval and multi-factor authentication.
FIDO
Fast Identity Online, a set of standards for secure passwordless or hardware-based authentication.
MFA
Multi-Factor Authentication, a broader term for using multiple ways to verify identity when logging in.
on-call
A work arrangement where someone must be reachable and ready to respond outside normal hours if needed.
Slack
A workplace messaging app commonly used for team communication.
TOTP
Time-Based One-Time Password, a standard that generates short-lived login codes in an authenticator app or device.

Reference links

Primary sources

Authentication and device boundary tools

  • Duo
    Mentioned as an example of a proprietary MFA system that can force work onto personal phones.

Research and context

  • MIT WEIRD problem resource
    Used to support the point that a homogeneous community can mistake its own experience for the general case.
  • The Cost of Regulation
    Cited by a skeptic arguing that extra business regulation creates drag and cost.

Prior Hacker News references