Managing medical absences in remote teams when employees work across state lines

Improve employee attendance
November 2026
    Contents:

  1. Why medical absences are harder to manage in remote teams
  2. FMLA and remote workers
  3. State sick leave laws for distributed teams
  4. ADA accommodations for remote employees
  5. Building a remote sick leave policy
  6. Communication and reporting procedures
  7. Planning workloads around absences
  8. Tracking absences across locations
  9. FAQ

When a team shares an office, managing medical absences is straightforward. Someone calls in sick, their manager sees the empty desk, and the team adjusts. In a remote team, the process gets more complicated: the employee might work from a different state (or country), local sick leave laws might differ from where the company is headquartered, and the team may not realize someone is out until a deadline slips.

Tracking who is absent is the easy part. Staying compliant with the leave laws that apply where each employee actually works, while keeping projects on track when absences are less visible than they would be in an office, is where most remote teams struggle.

Why medical absences are harder to manage in remote teams

Three factors make medical absence management more complex for distributed teams:

Multi-jurisdiction compliance. A company based in Texas with remote employees in California, New York, and Colorado must comply with at least four different sets of leave rules. California requires 5 paid sick days. New York requires 40 or 56 hours depending on employer size. Colorado requires 48 hours. Texas has no state-mandated paid sick leave at all. The law that applies is generally determined by where the employee works, not where the company is incorporated.

Reduced visibility. In an office, absences are immediately apparent. In a remote team, an employee who is sick but does not report it may simply appear unresponsive on Slack for hours before anyone notices. This delay makes it harder to reassign work and meet deadlines.

Blurred boundaries between sick and working. Remote employees are more likely to work while sick because there is no visible cue (like leaving the building) to mark the transition from “at work” to “on sick leave.” This can extend recovery time and make absence records inaccurate.

FMLA and remote workers

The Family and Medical Leave Act provides up to 12 weeks of unpaid, job-protected leave per year. Remote employees are eligible if the company has 50 or more employees and the employee has worked at least 12 months and 1,250 hours.

The complication for remote teams is the 75-mile rule. Under FMLA, an employee must work at a location where the employer has 50 or more employees within 75 miles. For remote workers, the Department of Labor considers their “worksite” to be the office to which they report or from which their work is assigned. If a remote employee reports to a home office with 50+ employees within 75 miles, they are covered. If they report to a small satellite office with only 10 employees and no other company location within 75 miles, they may not be.

This means two remote employees doing the same job at the same company could have different FMLA eligibility based on which office they are assigned to in the company’s records. Employers with distributed teams need to review their reporting structures to make sure FMLA eligibility does not depend on an arbitrary office assignment.

Intermittent FMLA for remote workers

Intermittent FMLA leave allows employees to take leave in separate blocks of time for a single qualifying reason. For remote employees, this is common: a worker undergoing chemotherapy might need two days off every three weeks, or someone managing a chronic condition might need to reduce their hours on certain days.

Tracking intermittent leave in a remote setting requires clear reporting. The employer can require the employee to follow the company’s usual call-in procedures, but cannot require more frequent reporting than they would for on-site employees.

State sick leave laws for distributed teams

As of 2026, 18 US states plus the District of Columbia require employers to provide paid sick leave. For a company with remote employees in multiple states, the general principle is that the law of the state where the employee works governs their sick leave entitlements.

State Paid sick leave requirement Accrual rate
California 5 days (40 hours) per year 1 hour per 30 hours worked
New York 40 or 56 hours depending on employer size 1 hour per 30 hours worked
Colorado 48 hours per year 1 hour per 30 hours worked
Washington 40 hours per year 1 hour per 40 hours worked
New Jersey 40 hours per year 1 hour per 30 hours worked
Arizona 24 or 40 hours depending on employer size 1 hour per 30 hours worked
Illinois 40 hours per year 1 hour per 40 hours worked
Oregon 40 hours per year 1 hour per 30 hours worked

This table covers the states most commonly represented in remote workforces, but it is not exhaustive. Some cities (San Francisco, Los Angeles, Chicago, Minneapolis) impose additional requirements that exceed the state minimum.

The practical challenge for remote teams is that a single sick leave policy may not comply everywhere. A company offering 3 paid sick days meets zero state-mandated sick leave laws on the list above. One approach is to set your company policy at the highest applicable standard. If your most generous jurisdiction requires 48 hours, make 48 hours the company-wide minimum and you will comply everywhere.

ADA accommodations for remote employees

The Americans with Disabilities Act requires employers with 15 or more employees to provide reasonable accommodations for qualified employees with disabilities. For remote workers, this can include modified schedules, reduced hours, additional breaks, or ergonomic equipment for a home office.

One area that has shifted since the pandemic: courts are now more receptive to remote work itself as a reasonable accommodation. Before 2020, employers often argued that physical presence was an essential function of most jobs. That argument is harder to make when the same employee has been working remotely for years.

If a remote employee requests time off for medical treatment, the ADA interactive process applies just as it would for an on-site employee. The employer should engage in a good-faith discussion about what accommodation would allow the employee to perform their essential functions. This might mean a temporary schedule change rather than extended leave.

Building a remote sick leave policy

A sick leave policy for a distributed team needs to account for geographic variation without becoming unmanageable. The most practical structure has three layers:

Company-wide baseline. Set a minimum that meets or exceeds the most generous jurisdiction where you have employees. This gives you a single standard that is compliant everywhere, and you avoid tracking different entitlements by state.

Reporting procedure. Define how employees report a sick day (Slack message, email, leave management system), who they notify, and by when. For remote teams, the reporting time should be before the employee’s normal working hours, not after. A simple rule: notify your manager via the leave system before your scheduled start time.

Documentation requirements. Specify when a doctor’s note is required. A common threshold is absences of three or more consecutive days. Be consistent, and check state laws: some states restrict when employers can request medical documentation.

What to include

  • Sick leave entitlement (hours or days per year)
  • Accrual method or frontloading
  • Eligible uses (personal illness, family member care, medical appointments, mental health)
  • Reporting procedure and notification timeline
  • Documentation threshold
  • How unused sick leave is handled (carryover rules, payout rules by state)
  • Return-to-work procedures for extended absences
  • FMLA and state family leave interaction

Communication and reporting procedures

Remote teams need more explicit communication norms around absences because the physical cues of an office are missing. Three things need to be clear to every employee:

Where to report. Choose one primary channel. A leave management system is better than Slack or email because it creates a record and notifies the right people automatically. If you use a system like actiPLANS, the employee submits a leave request, the manager approves it, and the team calendar updates immediately.

When to report. Before the start of the workday in the employee’s time zone. For planned medical appointments, as early as possible.

What to share with the team. The team needs to know availability, not medical details. A calendar status showing “out sick, back Thursday” is enough. Specific diagnoses should only be shared with HR or the direct manager when documentation is required.

Handling time zone complexity

In a team spread across time zones, a sick employee in California might not report until 9 AM Pacific, but their colleague in New York already started work three hours ago and is waiting for a deliverable. Build your policy so that any handoff tasks have a backup contact identified in advance, not scrambled together after the absence is reported.

Planning workloads around absences

Medical absences become disruptive when they are not reflected in the team’s workload plan. In an office, a manager can reassign work in a five-minute conversation. In a distributed team, the reassignment happens asynchronously, which means it takes longer and is more likely to be incomplete.

Practical steps that reduce disruption:

  • Identify backup contacts for every recurring responsibility. Not a full backup plan for the entire role, just someone who knows where to find the files and who to notify if something is urgent.
  • Make work visible. If tasks and deadlines live only in someone’s head or a private to-do list, the team has no way to pick up the work when that person is out. Shared task boards and project management tools solve this.
  • Build buffer into estimates. The Bureau of Labor Statistics reports that US workers miss an average of 5.2 days per year due to illness or injury. For a team of 10, that is roughly one person out sick every other week. If your project plans assume 100% availability, they assume something that statistically never happens.

Tracking absences across locations

When employees work from different states or countries, absence tracking has to do more than count sick days. It needs to apply the correct entitlement per location, track accruals at the correct rate, and flag when an employee is approaching a leave threshold that triggers FMLA or state-specific protections.

A leave management system like actiPLANS handles this by letting you create separate leave types with location-specific rules. Set up a “Sick Leave (CA)” type that accrues at 1 hour per 30 hours worked with a 40-hour annual usage cap, and a “Sick Leave (CO)” type that accrues the same rate but with a 48-hour cap. Each employee is assigned the leave type that matches their work location, and the system tracks their accrual and balance automatically.

This matters for two reasons beyond compliance. First, it gives you accurate data about absence patterns across your distributed team. Second, when an employee who has been working from California moves to Texas, you can update their leave type and the system adjusts going forward.

actiPLANS is free for teams of up to 3 users. Paid plans start at $1.50 per user per month.

FAQ

Does FMLA apply to remote employees?

It can. FMLA eligibility for remote workers depends on the 75-mile rule: the employee’s assigned worksite must have 50 or more company employees within 75 miles. For remote workers, the DOL considers their worksite to be the office to which they report or from which assignments are made, not their home.

Which state’s sick leave law applies to a remote worker?

Generally, the sick leave law of the state where the employee performs their work. If an employee works from home in California for a company headquartered in Texas, California’s 5-day paid sick leave law applies to that employee.

Can I use a single sick leave policy for a distributed team?

Yes, if you set the policy at or above the most generous applicable standard. If your most generous state requires 48 hours of paid sick leave per year, offering 48 hours company-wide means you comply everywhere. The alternative is maintaining separate policies per state, which is more complex but gives you more control over costs.

Can I require a doctor’s note from a remote employee?

In most states, yes, but check local rules. Some states restrict when employers can require medical documentation. California, for example, does not require employees to provide a doctor’s note for paid sick leave. A common and generally compliant threshold is requiring documentation only for absences of three or more consecutive days.

How do I track sick leave when employees work in different states?

Use a leave management system that supports multiple leave types with different accrual rules. Assign each employee the leave type that matches their work location. This ensures correct entitlements and avoids manual calculations.

Enjoy a better way to
schedule work
Start Using actiPLANS