What Should a Retail Food Employee Illness Policy Include?

A retail food employee illness policy should tell workers what to report, tell the person in charge how to respond, and leave a clear record of the decision. It should be short enough to use before a shift, specific enough to prevent an ill employee from handling food, and aligned with the rules adopted by the state or local authority for each site.

Where TapTick fits: TapTick can help connect routine checks, exceptions, corrective actions and supporting evidence. It does not replace the employee illness policy, the manager's decision under local rules, or any HR and privacy process.

1. What changed in the 2026 Food Code

FDA released the 2026 Food Code on September 17, 2026. Among its changes is a model requirement for food establishments to maintain a written employee illness policy and make it available. The accompanying public-health guidance explains that the policy should set out employee reporting duties, management responsibilities, exclusion or restriction decisions, tracking and return-to-work criteria.

This matters to convenience stores, travel centers, quick-service restaurants, grocery foodservice counters and other retail food establishments. A verbal instruction such as “tell us if you are sick” is too vague. Employees need to know which conditions trigger a report, and the person in charge needs a repeatable way to decide what happens next.

The federal Food Code is FDA's model for safeguarding food offered at retail and in food service. Jurisdictions may adopt it in full, adopt an earlier edition, amend it or use their own code. A September 2026 release therefore does not mean every US establishment immediately has a new legal duty. An operator should confirm:

• which food code edition and amendments the regulatory authority has adopted;
• the effective date for the relevant establishment;
• whether local reporting, exclusion or reinstatement rules differ from the model; and
• what the inspector or permitting authority expects to be available on site.

This is a retail food control. It is not a new FSMA rule for food manufacturers. A business that operates both retail establishments and manufacturing or distribution facilities should map the requirements separately instead of applying one label to every operation.

2. What the written policy should contain

A useful policy answers seven questions without making an employee or shift manager interpret the entire food code.

1. Who is covered?

Identify food employees, conditional employees such as job applicants or new hires, and the person in charge. Include temporary, agency and contract workers when they perform covered food work. Make clear which manager receives reports outside normal office hours.

2. What must an employee report?

Use the current list in the locally adopted code. The 2026 model materials address symptoms including vomiting, diarrhea, jaundice, sore throat with fever, and infected cuts or lesions on the hands, wrists or exposed parts of the body. They also address diagnoses and specified exposures involving foodborne pathogens.

Do not copy a list from another state and assume it is complete. The model code names conditions such as norovirus, hepatitis A, Salmonella Typhi, Shigella species, Shiga toxin-producing Escherichia coli and nontyphoidal Salmonella, but a jurisdiction can change reporting details or add requirements.

3. When and how is the report made?

Require reporting before the employee starts work and immediately if a symptom, diagnosis or exposure arises during a shift. Give one primary contact and a backup. State the approved reporting channels, what information is needed and what the employee should do while waiting for instructions.

4. How will the person in charge decide?

Give managers a jurisdiction-specific decision guide. It should distinguish:

• exclusion — the person does not work in the food establishment;
• restriction — duties are limited so the person does not work with exposed food, clean equipment, utensils, linens or unwrapped single-service items; and
• normal duties — permitted only when the adopted rule and the facts support that decision.

Do not let a staffing shortage rewrite the decision. The guide should also tell the manager when to isolate affected food, stop a task, start a vomiting or diarrheal-event cleanup procedure, and escalate uncertainty.

5. When must the regulatory authority be notified?

List the events that require notification under the locally adopted rule, the agency's contact details and the person authorized to make the call. If the establishment operates after the health department's normal hours, include the correct after-hours route or the next action specified by that authority.

6. What allows a return to normal duties?

Use the exclusion, restriction and reinstatement criteria in the applicable code. Some decisions depend on the symptom, diagnosis, time since symptoms ended, medical documentation or regulatory approval. Avoid an improvised blanket rule such as “return after 24 hours.” The correct decision can vary by condition and jurisdiction.

7. How will the policy be communicated?

Explain the policy at hiring, revisit it when the code or job changes, and make it accessible in the languages and formats the workforce needs. FDA's annex guidance recommends employee reporting agreements and other reference tools. A signature can acknowledge receipt, but it does not prove that the employee understands when or how to report.

3. A practical shift-level workflow

The policy becomes operational when a manager can follow the same sequence every time:

1. Receive the report. Make it easy for an employee to report before arriving or discreetly during the shift.
2. Confirm only the relevant facts. Ask the policy's questions about symptoms, diagnosis, exposure, dates and food duties. Avoid collecting unrelated medical details.
3. Apply the local decision guide. Exclude, restrict or permit duties using the code adopted for that site. Escalate if the facts do not fit the guide.
4. Protect food and the environment. If work may already have been affected, identify the food, equipment and surfaces involved. Follow the establishment's contamination-event and disposition procedures.
5. Notify when required. Contact the regulatory authority or other designated party when the applicable rule calls for it.
6. Record the action. Document the operational decision, its basis, the manager and any corrective action without turning the food-safety record into a general medical file.
7. Control the return. Verify and record that the applicable reinstatement criteria were met before normal duties resume.

Managers should know who can answer a difficult case. That may be the regulatory authority, an employee-health contact or the company's food-safety lead. The policy should identify the route rather than leaving a shift supervisor to search for it during service.

4. What to document

The 2026 Food Code's annex offers practical guidance rather than a single mandatory national record format. Suggested tools include employee reporting agreements, an exclusion and restriction guide, pathogen references, medical-referral forms, an illness log and reinstatement criteria.

For each reported event, an operational record can include:

• the employee identifier, site and role;
• the date and time reported;
• the policy trigger reported, using limited categories rather than unnecessary clinical detail;
• the decision to exclude, restrict or permit duties;
• the code, decision guide or authority instruction used;
• any food isolation, disposal, cleanup or other corrective action;
• any required regulatory notification and reference number;
• the decision-maker; and
• the return-to-work decision, date and basis.

Keep the written policy and current decision tools readily available at the establishment. Control access to illness records, retain them according to applicable company, employment and privacy requirements, and avoid displaying personal medical information on general shift boards or shared checklists.

5. How multi-site operators should manage differences

A national or regional operator can use one core policy, but each site needs the rules that actually apply there. Build a jurisdiction appendix or site profile containing the adopted code edition, local amendments, authority contact, notification triggers and effective date.

Use version control so managers can tell whether their decision guide is current. A simple register can show:

• site and permitting authority;
• adopted food code or local code reference;
• policy and decision-guide version;
• date last verified with the authority's published information;
• manager training status; and
• open actions from an inspection, incident or code change.

When a jurisdiction adopts the 2026 Food Code, update the affected site's appendix and training evidence. Do not announce a nationwide effective date or assume that a neighboring county uses the same rule.

6. How to test whether the policy works

A policy is useful only if workers report and managers act consistently. Test it with short scenarios:

• An employee calls before a 5 a.m. opening shift after vomiting overnight. Who receives the report and what happens?
• A deli worker develops diarrhea midway through a shift. How are their duties stopped, and how is potentially affected food assessed?
• A cashier has a covered cut on a hand and sometimes helps with food-to-go. Which duties are permitted under the local rule?
• A worker reports that a household member has a diagnosed foodborne illness. Does the jurisdiction require restriction, exclusion, monitoring or another action?
• A manager wants the employee back because two people have called out. Can the return criteria be demonstrated?

Review the results across sites. Repeated late reports may signal that employees do not know the policy, cannot reach a manager or fear the consequence of reporting. Repeated manager uncertainty may point to an unclear decision guide. Fix the workflow, not just the wording.

A practical final check

Before treating the policy as ready, ask:

• Does it name every locally required symptom, diagnosis and exposure?
• Can every employee report before or during any shift?
• Can the person in charge distinguish exclusion from restriction?
• Are notification and return-to-work rules tied to the correct jurisdiction?
• Is the current policy available at each establishment?
• Are illness records appropriately limited and protected?
• Can the business show when the site-specific rule was last checked?

If any answer is no, that is the next corrective action. The best illness policy is not the longest document; it is the one an employee can use early and a manager can apply correctly under pressure.