Remote work has a way of making employment rules feel less local than they really are. A company may be headquartered in Chicago, a manager may sit in Dallas, payroll may run out of another state, and yet the employee doing the work may be logging in every day from a home office in Ann Arbor. Michigan’s current earned sick time framework matters in that setting because the state’s Earned Sick Time Act, as amended, took effect on February 21, 2025 and now governs sick time rights for a broad range of employees working in Michigan. For employers and employees around Ann Arbor, that means remote-work questions are no longer edge cases. They are now central compliance questions, especially for multistate businesses, hybrid teams, professional services firms, startups, and employers that have quietly built a Michigan workforce without revising their leave policies to match. ⁵
The core principle is more straightforward than many people expect. Michigan’s guidance says the Earned Sick Time Act applies to employees who are physically located in Michigan, regardless of where the employer is based. In practical terms, an employee living in Ann Arbor and working remotely from a Michigan home office for an out-of-state company will generally be entitled to Michigan earned sick time protections. The statute also states that an employer must provide earned sick time to the employer’s employees in this state, which reinforces that the legal focus is on the employee’s work presence in Michigan, not merely on where corporate leadership, payroll, or human resources happen to sit. ¹ ³
That physical-location rule is especially important around Ann Arbor because the region is full of work arrangements that blur old assumptions. Some employees live in Ann Arbor but report to teams elsewhere. Some split time between a home office and periodic travel. Some are recruited by out-of-state employers precisely because remote work makes geography feel interchangeable. Michigan’s current guidance cuts through that ambiguity by treating physically Michigan-based work as covered work. The law also recognizes a second category that matters in the Ann Arbor market: employees whose employment is based in Michigan and who are then sent out of state for assignments. Those employees continue to accrue, and use earned sick time while away. The takeaway is that a Michigan-based remote arrangement does not fall outside the statute simply because the employer’s operations cross state lines. ¹
Coverage is broad, but it is not unlimited. The statute defines an employee as an individual engaged in service to an employer in the business of the employer, and Michigan’s labor agency notes that ordinary employee-status questions are analyzed under the state’s economic reality framework. That matters because some remote workers are labeled as contractors when, in practice, they function like employees. At the same time, the act excludes certain categories, including individuals employed by the United States government, unpaid trainees or unpaid interns, and certain youth workers. It also excludes a narrow category of workers whose employer policy lets them schedule their own hours and bars adverse action if they do not schedule a minimum number of hours. For remote teams, that means the title “flexible” does not automatically remove someone from coverage. If the employer still controls the schedule in a meaningful way, the exemption may not
fit. ¹ ²
The small-business distinction is another issue employers around Ann Arbor need to understand with precision. Michigan’s guidance says an employer is a small business if it employs 10 or fewer employees, and the count includes full-time, part-time, temporary, and certain staffing-agency workers across the United States or its territories. That count is not limited to the Michigan branch or the Ann Arbor office. A business with a small Michigan footprint may still be outside the small-business category if its total national headcount is higher. The distinction matters because, under the current law, small businesses generally may cap use at 40 hours of paid earned sick time per year, while other employers generally may cap use at 72 hours. It also mattered for timing, because small businesses were given until October 1, 2025 to begin the required accrual or frontloading obligations that applied earlier to larger employers. ¹ ³ ⁵
For covered employees, the accrual rule is simple in formula even if it becomes messy in administration. Employees accrue at least one hour of paid earned sick time for every 30 hours worked. Employers can use the accrual method, or they can frontload the required amount at the beginning of the benefit year. For a small business, that generally means at least 40 hours for immediate use if frontloading is chosen. For other employers, it generally means at least 72 hours for immediate use. If the employer uses accrual rather than frontloading, unused time must generally carry over from year to year up to the statutory limits, although the employer can still cap annual use at 40 hours for a small business or 72 hours for other employers unless it voluntarily offers more. For remote workforces, those choices are not just technical payroll preferences. They decide whether the employer must track accruals with precision and whether managers can administer leave consistently. ¹ ³
Remote work also puts pressure on hour-counting rules that employers once took for granted in a physical office. Hourly employees working from home present obvious tracking questions, but salaried employees do as well. Michigan’s guidance states that an employee exempt from overtime under federal law is presumed to work 40 hours per week for accrual purposes unless the employee’s normal workweek is less than 40 hours, in which case accrual is based on that lower normal schedule. That rule is significant for the many professional employees in and around Ann Arbor who are salaried and hybrid. Employers cannot simply assume that a remote salaried employee is outside the accrual system. They still need to know whether the employee is treated as exempt, whether the normal workweek is full-time or part-time, and whether the policy is set up to frontload or accrue. Sloppy assumptions in those areas are one of the fastest ways to create inconsistent balances across a remote team. ¹
The timing of use matters just as much as accrual. Michigan’s guidance says that, for covered employers other than small businesses, employees who were already employed on February 21, 2025 began accruing and could use accrued earned sick time immediately. For new hires under an accrual-based system, an employer may require the employee to wait until the 120th calendar day after starting work before using accrued earned sick time. That waiting period does not erase accrual; it only delays use. Employers that frontload time may allow immediate use, and some do so to reduce the administrative friction of managing partial accrual banks for newly hired remote employees. In a remote environment, that timing rule needs to be written clearly because employees often onboard digitally may never receive an in-person handbook explanation and may rely entirely on what appears in the online HR portal. If the written policy is vague, managers and employees can easily begin operating under different assumptions. ¹ ³
What can the time be used for? The answer is broader than a simple “staying home sick” model. Michigan’s law covers the employee’s own mental or physical illness, injury, health condition, diagnosis, treatment, or preventive care, and it also covers those same needs for a family member. It further covers leave connected to domestic violence or sexual assault, including medical care, counseling, victim services, relocation, legal services, and participation in civil or criminal proceedings. The statute also reaches meetings at a child’s school or place of care related to the child’s health or disability, or the effects of domestic violence or sexual assault on the child. In addition, the law applies in certain public-health-emergency situations, such as closures of the employee’s workplace or a child’s school or place of care, and when exposure to a communicable disease makes the employee’s or family member’s presence in the community a health risk. For remote employees, that breadth matters because many qualifying uses arise even when the employee is already working from home. ¹ ⁴
The family-member definition is also important in real-world administration. Michigan’s guidance includes biological, adopted, and foster children, stepchildren, legal wards, children of domestic partners, parents, foster parents, stepparents, adoptive parents, legal guardians, grandparents, grandchildren, siblings, and domestic partners, among others. That means an Ann Arbor employee who works remotely and needs time to assist a grandparent, a sibling, or a child of a domestic partner may still be invoking a protected use under the act. Employers that cling to a narrow, older definition of family leave can misclassify a valid earned sick time request as unexcused. Remote work can make this worse because requests are often sent quickly through chat, email, or a leave platform without much conversational context. A policy that uses outdated family definitions can therefore generate avoidable denials and, with them, legal risk. ¹ ²
Notice rules under the act are designed to separate foreseeable leave from unforeseeable leave, and that distinction matters even more in remote settings where managers sometimes expect instantaneous digital responsiveness. If the need for leave is foreseeable, an employer may require advance notice of up to seven days before the leave begins. If the need is not foreseeable, the employee must give notice as soon as practicable, or in accordance with the employer’s written policy if the policy meets the statute’s requirements. Michigan’s guidance emphasizes that, for unforeseeable leave, the policy must allow notice after the employee becomes aware of the need for time off. In other words, an employer cannot write a rigid notice rule that effectively defeats emergency use. For remote employees, that is crucial. A parent working from home in Ann Arbor whose child becomes sick two hours before a scheduled video-heavy workday is not stripped of protection simply because the employer’s normal scheduling culture expects more lead time. ¹ ⁴
Documentation rules are similarly bounded. Michigan’s guidance says that if an employee uses earned sick time for more than three consecutive days, the employer may require reasonable documentation showing that the leave was used for a permissible purpose. The employee then has up to 15 days after the employer’s request to provide that documentation. The employer may not require the documentation to describe the illness or the details of violence, and if documentation is required, the employer must pay the employee’s out-of-pocket expenses incurred in obtaining it. Just as important, the employer cannot delay the start of leave while waiting for the paperwork. These guardrails matter for remote employees because the digital workplace often encourages over-documentation. A manager who would never ask an in-office employee for a detailed medical explanation may casually request it in a remote chat thread. The statute is designed to stop that drift, and it also bars employers from requiring an employee to find a replacement worker as a condition of using earned sick time. ¹ ⁴
Payment rules under the act deserve attention because they affect budgeting, wage statements, and leave-bank design. Michigan’s guidance states that earned sick time must be paid at the greater of the employee’s normal hourly wage or base wage, or the Michigan minimum wage then in effect. At the same time, the law does not require employers to include overtime premiums, holiday pay, bonuses, commissions, supplemental pay, piece-rate pay, tips, or gratuities in that calculation. This is one reason multistate employers should resist the temptation to treat Michigan earned sick time as interchangeable with every other paid leave rule on their books. A national policy that works in one state may not align cleanly with Michigan’s pay-rate requirements. For remote teams around Ann Arbor, this becomes especially relevant when employees have variable compensation structures or when payroll is centralized in another state that uses different leave formulas. ¹ ³
Existing paid time off policies can satisfy the statute, but only if they truly match what Michigan requires. The labor agency says an employer does not have to create a separate sick-time bank if an existing PTO policy provides at least the same benefits, may be used for the same purposes, under the same conditions, and accrues at an equal or greater rate than the statute requires. That is a useful compliance option, particularly for remote-first employers that want one leave bank rather than several. But it is not a free pass. A general PTO policy can fail Michigan’s standard if it restricts qualifying uses, applies a stricter notice rule than the statute allows, accrues too slowly, or does not preserve carryover rights when required under an accrual model. Around Ann Arbor, many remote employees work for sophisticated employers with polished PTO systems, yet sophistication alone does not guarantee compliance. The decisive question is whether the policy functions like the Earned Sick Time Act in practice, not whether it looks modern in the handbook. ¹ ³ ⁴
The law becomes especially concrete when applied to a common Ann Arbor scenario: a Michigan resident working remotely for an out-of-state employer. Under Michigan’s guidance, an employee who lives in Michigan and works remotely from a Michigan home office is entitled to earned sick time accrual and use even if the employer is located elsewhere. That means an employer based in Illinois, Ohio, Indiana, Texas, or California cannot assume that its own home-state leave policy is the only one that matters. If it has an Ann Arbor employee working from Michigan, the employer must analyze Michigan law. For businesses that hire nationally, this can come as an unwelcome surprise because Michigan becomes part of the compliance map the moment the company places a covered employee in the state. The employee’s residence and actual work location, not the address on the employer’s letterhead, drive the answer. ¹
The reverse situation also matters. An employee who lives outside Michigan but accepts a Michigan-based job around Ann Arbor may be covered while working on that Michigan assignment, regardless of residency. Michigan’s guidance gives the example of an out-of-state construction worker taking a Detroit project lasting several months and treating that employee as covered during the Michigan assignment. By contrast, an out-of-state employee who is generally based elsewhere and only travels into Michigan from time to time may not be covered unless 50 percent or more of the employee’s compensation is earned for time spent working in Michigan. That distinction matters in southeastern Michigan, where regional businesses may send sales staff, field technicians, drivers, consultants, or project employees across state lines. A company should not assume that every trip into Ann Arbor creates Michigan earned sick time obligations, but it also should not assume that cross-border work defeats coverage. The right answer turns on where the work is based and how much of the employee’s compensation is derived from Michigan work. ¹
Because remote work makes location analysis more fact-specific, recordkeeping becomes a frontline compliance task. Michigan’s guidance says employers must keep records documenting hours worked and earned sick time taken for at least three years. The same guidance also says employers must provide written notice of employee rights under the act at the time of hiring or by the applicable statutory date. For a traditional office employer, that may once have meant posting a notice in a break room and handing out a paper policy. For remote employers, it means something more deliberate. They need systems that identify where employees actually work, not just where they were hired. They need onboarding packets and digital acknowledgments that include Michigan-specific notice language when Michigan law applies. And they need timekeeping and payroll tools capable of distinguishing Ann Arbor-based remote employees from otherwise similar workers in other states. When those systems are missing, a company may be violating the law without realizing it. ¹ ⁵
Employers should also pay attention to what happens when a worker transfers, separates, or returns. Michigan law provides that if an employee transfers to a different division, entity, or location but remains employed by the same employer, the employee retains accrued earned sick time. If the employee separates from employment and is rehired by the same employer within two months, previously accrued unused earned sick time must generally be reinstated, unless the employer paid out that accrued time at separation. At the same time, the statute does not generally require payout of unused accrued earned sick time when employment ends. Those rules matter in remote organizations because internal transfers are common. An employee may move from an Ann Arbor home office arrangement to a Chicago office role, or from one business unit to another, without a clean break in employment. Sick-time balances should not disappear merely because the org chart changed. ¹ ³
In practice, many mistakes arise not from hostility to leave rights but from using the wrong frame of reference. Some employers focus on the employee’s manager location. Others focus on the company headquarters. Others ask where the laptop was issued, where payroll is processed, or whether the employee is remote “for convenience.” Those may be relevant business facts, but they are not the controlling legal question under Michigan’s current guidance. The first question is whether the employee is physically working in Michigan or is otherwise in a Michigan-based job relationship covered by the act. From there, the employer has to ask the ordinary statutory questions: whether the worker is a covered employee, whether the business qualifies as a small business, how accrual or frontloading is administered, whether notice and documentation rules are compliant, and whether existing PTO language actually matches Michigan requirements. ¹ ³ ⁴
For employees living or working around Ann Arbor, the practical lesson is equally clear. A remote arrangement does not cause Michigan sick-time rights to vanish. If the employee is physically working in Michigan, the employer is out of state, and the leave request otherwise falls within the statute, Michigan law may still require accrual and protected use of earned sick time. For employers, the safest approach is not to rely on assumptions imported from older leave laws or from another state’s handbook. It is to identify where the employee actually works, decide whether Michigan’s statute applies, and then align the policy, payroll settings, manager training, and onboarding documents accordingly. In a labor market where, remote work has made Ann Arbor part of national hiring pipelines, that is no longer a niche issue. It is ordinary compliance. ¹ ³ ⁴ ⁵
This article is intended for general informational purposes and should not be taken as legal advice for any specific workplace or leave dispute.
Contact Tishkoff
Tishkoff PLC specializes in business law and litigation. For inquiries, contact us at www.tish.law/contact/. & check out Tishkoff PLC’s Website (www.Tish.Law/), eBooks (www.Tish.Law/e-books), Blogs (www.Tish.Law/blog) and References (www.Tish.Law/resources).
Footnoted Sources
1-Michigan Department of Labor and Economic Opportunity, “Earned Sick Time (ESTA) FAQ,” accessed April 16, 2026. https://www.michigan.gov/leo/bureaus-agencies/ber/wage-and-hour/frequently-asked-questions/wage-and-hour/earned-sick-time-faqs
2- Michigan Legislature, MCL 408.962, “Earned Sick Time Act — Definitions,” accessed April 16, 2026. https://www.legislature.mi.gov/Laws/MCL?objectName=mcl-408-962
3- Michigan Legislature, MCL 408.963, “Earned Sick Time to Be Provided by Employer; Alternatives; Accrual; Use; Carry Over; ‘Year’ Defined; Workweek; Compliance; Pay Rate; Replacement Worker Not Required,” accessed April 16, 2026. https://www.legislature.mi.gov/Laws/MCL?objectName=mcl-408-963
4- Michigan Legislature, MCL 408.964, “Earned Sick Time; Permissible Uses; Advance Notice; Incremental Use; Documentation; Disclosure; Other Purposes,” accessed April 16, 2026. https://www.legislature.mi.gov/Laws/MCL?objectName=mcl-408-964
5- Michigan Department of Labor and Economic Opportunity, “Earned Sick Time Act — Effective Feb. 21, 2025,” accessed April 16, 2026. https://www.michigan.gov/leo/bureaus-agencies/ber/wage-and-hour/paid-medical-leave-act