Does a Food Establishment Need a Written Employee Illness Policy?

Under the 2026 FDA Food Code model, yes: a food establishment would need a written employee illness policy and would have to make it available on request. But the Food Code is a model, not a nationwide rule. A convenience store, travel center, restaurant or food-to-go operator must first check which code edition and amendments its state, county, city, tribal or territorial authority has adopted—and when those rules take effect.

TapTick can help operators put site routines, checks, exceptions and corrective actions into a consistent daily workflow. It does not decide whether an employee must be excluded or restricted, and it does not replace the adopted code or instructions from the local health department.

What changed in the 2026 Food Code?

The FDA released the 2026 Food Code on September 17, 2026. New section 2-501.11 says the permit holder should provide a written employee illness policy and make it available on request. The section is marked as a “Priority Foundation” item in the model code.

The written policy is meant to turn the employee-health rules into a usable system. In the model provision, it must address:

• reporting by food employees, conditional employees and the person in charge;
• reporting to the regulatory authority when the code requires it;
• symptoms including vomiting, diarrhea, jaundice, sore throat with fever, and an infected wound or cut;
• diagnoses including norovirus, hepatitis A, Shigella, typhoid fever, nontyphoidal Salmonella and Shiga toxin-producing E. coli;
• restriction or exclusion from work when required; and
• reinstatement after the condition is resolved.

This is different from a vomit-and-diarrhea cleanup plan. The cleanup plan controls contamination after an event in the establishment. The employee illness policy controls reporting, work restrictions, management decisions and return to work when a worker is ill, diagnosed or otherwise covered by the applicable employee-health rules. A robust operation needs both.

Why the model-versus-law distinction matters

The FDA Food Code is offered to jurisdictions as a model for retail and food-service regulation. It does not become enforceable everywhere on publication day. States and local authorities may adopt a different edition, amend it, phase it in or use their own language.

That means a chain can face different requirements at different locations. One county might adopt the 2026 model provision with no change; another might still use an earlier Food Code; a city might add a reporting form or impose a different clearance process. The operator should not use a national document as a substitute for the law that actually applies at the site.

For each location, record:

• the regulatory authority and contact route;
• the adopted food code edition and local amendments;
• the effective date of the current rules;
• which conditions trigger exclusion, restriction or regulator notification;
• whether the operation serves a highly susceptible population; and
• what evidence is needed before an employee returns to normal duties.

The 2026 Food Code is about retail and food-service establishments. It should not be confused with the FDA Food Safety Modernization Act rules that apply to manufacturers and other covered entities. A business with both retail operations and a manufacturing or distribution activity may need separate analyses.

What should the written policy cover?

1. Who has to report

Do not write the policy only for cooks. It should cover food employees, conditional employees such as applicants or incoming hires, and each person in charge. Consider cashiers who handle open food, beverage-station staff, temporary workers, agency workers, delivery staff who perform food tasks and managers who step into production during busy periods.

2. What has to be reported

Use plain language for the symptoms and diagnoses in the applicable code. The 2026 model provision names the five symptoms and six diagnoses listed above. The wider employee-health rules and FDA explanatory material also address relevant exposures. The local code controls the exact list and reporting deadlines, so avoid shortening it from memory.

Workers need to know when and how to report before arriving for a shift, during a shift and outside normal management hours. A policy that says only “tell your manager if you are sick” leaves too much room for inconsistent decisions.

3. What the person in charge must do

The policy should lead the person in charge through a decision, not merely collect a message. Depending on the condition, duties, population served and adopted code, the response may be exclusion from the establishment, restriction from particular work, reassignment, regulator notification or another control.

Do not turn a short symptom list into a universal decision chart. The right action can differ by diagnosis, symptom, exposure history, recovery stage and whether the establishment serves a highly susceptible population. Base the decision guide on the rule in force at that location and give managers an escalation route when facts are uncertain.

4. How return to work is decided

Define who can lift a restriction or exclusion and what evidence is required. The answer may involve elapsed time, symptom resolution, medical documentation, regulatory approval or a combination of these. CDC advises food workers with norovirus symptoms to stay home while sick and for at least 48 hours after symptoms stop, but that public-health guidance does not replace a jurisdiction’s legal return-to-work conditions.

5. How the establishment will keep operating

A reporting policy fails if staff believe they must work sick to protect their hours or keep the store open. The CDC has found that written policies and staffing practices affect whether sick workers report illness and stay home. Include backup staffing, an on-call route, cross-training and a rule against pressuring an ill worker to remain on food duties.

A workable shift-level process

A practical process can be short enough for a busy shift while still producing a defensible decision trail:

1. Receive the report. Give workers a named primary and backup contact for every shift. Accept reports before arrival and during work.
2. Protect food immediately. If illness is reported during a shift, stop the affected work and prevent further handling while the person in charge assesses the situation.
3. Use the site-specific decision guide. Check the symptom, diagnosis or exposure against the adopted local rule, the worker’s duties and whether a highly susceptible population is served.
4. Restrict, exclude or reassign as required. Record the action and who authorized it. Do not improvise a return date.
5. Notify the regulatory authority when required. Keep the correct phone number and after-hours route with the policy.
6. Control any contamination. If there has been vomiting, diarrhea, bare-hand contact or another contamination event, activate the relevant cleanup, disposal and sanitation procedure as a separate corrective action.
7. Manage reinstatement. Confirm the applicable criteria before the employee resumes restricted duties.

For a 24-hour travel center or convenience store, the overnight supervisor needs the same route as the day manager. “Call head office tomorrow” is not an adequate response when an employee becomes ill during food preparation at 2 a.m.

What records should an operator keep?

Section 2-501.11 requires the written policy to be available on request. The FDA’s explanatory annex also describes useful supporting documentation such as signed reporting agreements, illness logs and records of restriction, exclusion and reinstatement. Those examples are helpful evidence, but they should not be presented as universally mandatory unless the adopted code or local authority requires them.

A proportionate record can capture:

• location, date and time of the report;
• the relevant symptom, diagnosis or exposure category without unnecessary medical detail;
• the duties the employee was performing;
• the restriction, exclusion, reassignment or other immediate action;
• the manager or person in charge who made the decision;
• any health-department contact and instructions;
• the basis and authorization for reinstatement; and
• related contamination controls or corrective actions, where applicable.

Limit access to sensitive information and collect only what the operation needs for food-safety, employment and regulatory purposes. Coordinate the policy with HR and legal advisers where disability, privacy, paid-leave or other employment requirements apply.

How should multi-site operators roll it out?

A single corporate policy can set the reporting culture and minimum process, but it needs location-specific supplements. Build a jurisdiction register and assign an owner to monitor adoption dates and amendments. Link each site to the correct decision guide, authority contact and return-to-work requirements.

Then test the system across real operating conditions:

• day, night and weekend shifts;
• company employees, temporary staff and new starters;
• stores with made-to-order food, self-service beverages and packaged food;
• sites serving hospitals, schools, care settings or other highly susceptible populations;
• workers who need the policy explained in another language; and
• locations operating under different state or local codes.

Train people on the reporting route when they start and reinforce it regularly. The FDA annex recommends training at hire and annually, but operators should verify whether their authority sets a different training or documentation requirement. Managers should practice short scenarios so they can recognize when to stop work and escalate.

What should be ready for an inspection?

If the 2026 model provision has been adopted for the location, an inspector may ask for the written policy. Even before adoption, the policy can help show that the establishment manages a major foodborne-illness risk deliberately.

Keep the current approved version accessible to the person in charge. They should be able to explain:

• how an employee reports illness before and during a shift;
• where the five symptoms and six diagnoses are listed;
• how the manager identifies the correct restriction or exclusion decision;
• when the health department is contacted;
• how reinstatement is authorized;
• how temporary and overnight staff are covered; and
• how the site records action without over-collecting medical information.

Do not rely on a policy stored only at head office if the site cannot produce it or use it. Availability and manager understanding are separate controls, and both matter.

Implementation checklist

• Confirm the regulatory authority, adopted code edition, amendments and effective date for every site.
• Draft a written policy covering reporting, management action, regulator notification and reinstatement.
• List the symptoms, diagnoses and exposure rules exactly as the applicable code requires.
• Create a primary and backup reporting route for every shift.
• Provide site-specific exclusion, restriction and return-to-work guidance to each person in charge.
• Plan backup staffing so workers are not pushed to work while sick.
• Keep the illness policy separate from, but connected to, contamination and vomit/diarrhea cleanup procedures.
• Define proportionate records and protect sensitive employee information.
• Train new, temporary and existing workers in language they understand.
• Review the policy whenever a jurisdiction changes its code or the operation changes its food activities.

A written employee illness policy should make the safe action easier at the moment a worker reports a problem. For multi-site operators, the strongest approach combines one clear reporting culture with local rule mapping and a usable shift-level decision route.

TapTick helps teams make recurring controls and follow-up actions visible across locations. See TapTick features for the current product scope.

Primary sources

• FDA: FDA Releases 2026 Food Code (September 17, 2026)
• FDA: Food Code 2026
• FDA: 2026 Food Code, sections 2-501.11 and 2-201
• FDA: Summary of Changes in the 2026 FDA Food Code
• FDA: Employee Health Policy Tool
• CDC: Restaurants Can Manage Sick Workers to Help Prevent Outbreaks
• CDC: Norovirus Fact Sheet for Food Workers

Important: This article explains the 2026 FDA Food Code model and general operational good practice as of October 26, 2026. The Food Code is not automatically law nationwide. Check the food code, amendments, effective dates and health-department instructions that apply to each establishment. This is not legal, medical or employment advice.