Working Sick and the Customer Home

Why this matters

A tech who comes to work with the flu does not stay in the shop. They spend the day in six or seven kitchens, basements and bedrooms, shaking hands, touching thermostats and faucets, and standing a foot from customers who may be 85 years old, on chemotherapy, or holding a newborn. In-home service carries an infection exposure an office job does not, and the trades have a strong culture of working through it. That culture is reinforced by pay structures that make a sick day cost the tech money. This card covers why techs work sick, what it costs the customer and the crew, what paid sick leave law requires (which depends on where you are), and the policy shape that makes staying home actually possible. The day-to-day procedure is a sibling SOP.

Presenteeism, and why techs do it

Presenteeism means showing up to work while ill enough that you are less productive, more error-prone, or a risk to others. It is the mirror image of absenteeism, and in most workplace research it costs employers more, because it is invisible and common.

Techs work sick for reasons that are entirely rational from where they stand:

• No paid sick time, or not enough. A tech paid hourly with no sick leave loses a day's pay. A tech on commission or flat-rate pay loses the tickets. That is a real, immediate cost against a vague, future one.
• The board. They know their calls get dumped on someone else, or customers get pushed, and nobody wants to be the reason.
• Points and suspicion. Attendance systems that count a sick day as an occurrence, or a manager who rolls their eyes at a call-in, teach people not to call in.
• The toughness code. The same culture that keeps people quiet about pain keeps them quiet about a fever. A sibling card covers that language (see related).
• Not knowing they are contagious. Many people believe that once a fever is down, they are safe. With some illnesses that is roughly true; with others it is wrong.

None of this is solved by telling techs to stay home when sick. Every one of those reasons survives the instruction.

The customer home is a different exposure

A tech's workday is a string of close-contact visits to households you know nothing about. On any given day, some fraction of them include someone at high risk from a common infection: the elderly, people with heart or lung disease, people who are immunocompromised from cancer treatment or a transplant, pregnant people, and infants. In residential HVAC and plumbing, the share of service calls to older customers is often high, because older homeowners call for help more and are more likely to be home during the day.

Contact points are routine and hard to avoid: the thermostat, door handles, faucet handles, the customer's pen or tablet for a signature, the kitchen counter where the tech sets a tool bag. Respiratory droplets carry in close-quarters work in small rooms. And for gastrointestinal illness, the bathroom and kitchen are often exactly where the work is.

What the shop gets in return for a tech working sick is a few completed tickets. What it risks is a customer hospitalized with an infection traced, rightly or not, to the tech who coughed through their furnace tune-up, and a review that says so.

How common illnesses travel, and when a person is safe to return

Return markers here follow current CDC guidance as of 2026. Public-health guidance on respiratory illness changed in 2024 and may change again; re-check the CDC's current respiratory virus guidance before writing it into policy.

The trap in that table is the fever marker. A tech who takes a fever reducer in the morning can feel well enough and read normal on a thermometer while still running the illness. "Fever-free" means without the medicine.

What the law requires: a state and local layer over almost no federal floor

Federal floor. There is no general federal law requiring private employers to provide paid sick leave. The Family and Medical Leave Act (29 CFR Part 825, enforced by the U.S. Department of Labor) gives up to 12 weeks of unpaid, job-protected leave for a serious health condition, but only at employers with 50 or more employees within 75 miles, for employees who meet the hours and tenure requirements, so it misses most shops in this audience and does not cover a two-day flu anyway. Federal contractors are the exception: Executive Order 13706 requires paid sick leave for workers on covered federal contracts.

State layer. As of 2026, roughly 18 states plus Washington, DC require private employers to provide paid sick leave, and the number moves almost every year. California, Washington, Oregon, Arizona, Colorado, New York, New Jersey, Massachusetts, Illinois, Minnesota and Michigan are among them. Missouri passed a mandate by ballot in 2024 and its legislature repealed it in 2025, which shows how fast this changes. The details that vary state by state:

• Accrual rate. One hour of paid sick time per 30 hours worked is the most common rate, but not universal.
• Annual cap on use. California, for example, requires employers to allow at least 40 hours or five days a year.
• Which employers are covered. Some states cover an employer with a single employee; others start at a headcount. Connecticut, for example, is phasing its coverage down to small employers over 2025 to 2027.
• Permitted reasons. Your own illness, a family member's, medical appointments, and in many states safe time for domestic violence. Illinois and a few others require paid leave usable for any reason.
• Documentation. Many state laws bar requiring a doctor's note for short absences. Washington, for example, lets an employer require verification only for an absence of more than three consecutive days; New Jersey's rule is similar.
• Retaliation. Every state law bars penalizing a worker for using covered leave, which means a point-based attendance policy counting protected sick days can itself be a violation.

Local layer. Cities and counties add their own ordinances in states that allow it: New York City, Chicago and Cook County, Philadelphia, Minneapolis, San Francisco and Seattle among them, sometimes with higher accrual or broader coverage than the state. Other states have passed preemption laws that forbid local sick-leave ordinances. A shop serving several cities can owe different rules to techs based on where they work, not just where the shop is.

Your state labor department's website is the place to check your own obligations. This is not legal advice, and an employment attorney is the person to see before writing a leave policy for a multi-state or multi-city crew.

Worked example: one tech, one flu

A twelve-tech HVAC shop in a state with no paid sick leave mandate. The shop has no paid sick days. Tech Andre wakes up Monday with a fever and body aches, takes a fever reducer, and comes in, because a missed day is a day's pay.

His day: seven calls. Two of the households include someone over 80; one has an infant. He coughs through a furnace tune-up in a small utility closet at the second of them.

The illustrative spread. Say Andre passes it to two coworkers on Monday at the morning huddle and in a shared van at lunch. Both get sick by Thursday. Andre himself crashes on Tuesday and misses three days anyway. Now count tech-days lost: Andre's 3, plus 2 coworkers at 3 days each, so 3 plus 6, or 9 tech-days, in a week the shop was already short. Had Andre stayed home Monday and Tuesday and come back once fever-free without medicine, the shop would have lost perhaps 2 to 3 tech-days and nobody else.

That trade, roughly 9 against 3, is three times the lost capacity, before counting the customer side. Those numbers are illustrative; how many people one sick tech infects varies widely by illness and by how close the crew works. The shape is the point: working sick saves the shop one day, and on a contagious illness it often costs several.

What changes the answer. A cold with no fever, no vomiting, and a tech willing to mask and wash hands between calls is a different case; most shops reasonably let that tech work, perhaps off calls to the highest-risk households. The line the policy needs is fever, vomiting or diarrhea, or a draining infection. A cold is not a flu.

The policy that makes staying home possible

Whatever your state requires, a shop that wants techs to stop working sick needs four things, and each one answers one of the reasons people come in:

1. Paid time that covers a short illness. At least enough to cover two or three days without pay loss. For a flat-rate or commission tech, pay sick time at an average daily rate, not the base hourly rate, or the leave still costs them.
2. No penalty for using it. Sick days do not count as attendance occurrences, and nobody gets a sigh on the phone.
3. A coverage plan that is the shop's job, not the tech's. The tech reports; dispatch reassigns. If the sick tech has to arrange their own coverage, they will come in.
4. A clear, simple stay-home rule: fever, vomiting, diarrhea, or a draining infection means stay home, with return markers written down so nobody has to guess. The sick-tech SOP turns this into steps (see related).

Owners worry that paid sick days will be abused. In practice, the shops that pay sick time and track it see patterns quickly, and the pattern conversation is a management task covered by its own card (see related). The cost of an occasional abused day is small next to the cost of one flu working its way through a crew.

References

• CDC, Respiratory Virus Guidance (updated March 2024)
• U.S. FDA Food Code, employee health exclusion provisions for gastrointestinal illness
• U.S. Department of Labor, Family and Medical Leave Act (29 CFR Part 825) and Executive Order 13706 paid sick leave for federal contractors
• See related: The Sick Tech Policy SOP
• See related: A Strong Tech Keeps Calling In on Mondays