What is an employee health policy?

An employee health policy is the written program a food establishment uses to keep sick food handlers from contaminating food. It defines the symptoms and diagnoses a food employee must report, who they report to (the person in charge), and the response (restriction or exclusion from work). This is food handler illness reporting in practice: a standing duty, not a one-time form.

A few terms matter on first read:

• Food employee. Anyone who works with unpackaged food, food equipment or utensils, or food-contact surfaces.
• Conditional employee. A job applicant who has been offered a position but has not started yet. The Food Code covers them because a covered diagnosis disclosed during pre-employment screening can block a start date.
• Person in charge (PIC). The individual present at the establishment who is responsible for the operation at the time, and who receives illness reports.
• Food Employee Reporting Agreement. The signed-and-dated form acknowledging the duty to report.

The reason this matters is not abstract. CDC found that 1 in 5 food service workers reported working at least once in the prior year while sick with vomiting or diarrhea. Infected food workers cause about 70% of reported foodborne norovirus outbreaks from contaminated food, per the CDC Vital Signs report on preventing norovirus outbreaks. And the policy itself is often the weak point. CDC found one in three restaurant sick-worker policies failed to specify the symptoms that should keep a worker home, and most omitted jaundice and sore throat with fever, both Food Code triggers. See the CDC guidance on managing sick workers.

A policy that lives in a binder nobody re-signs is not a program. The health inspector does not ask "do you have a policy." They ask "show me the signed reporting agreement for this employee." The paper binder loses the signed-and-dated form. That is the gap this page sells against.

Regulatory framework

The FDA Food Code is the regulatory baseline for the employee health policy. The relevant provisions sit in Chapter 2, Management and Personnel, specifically sections 2-201.11 through 2-201.13. The map to HACCP (Hazard Analysis and Critical Control Points) is direct: an ill food handler is a recognized biological hazard, and the reporting program is the control. See the definition of HACCP in the Xenia learning center.

Per the 2022 FDA Food Code, Chapter 2:

• 2-201.11, Responsibility. The reporting provision. Food employees and conditional employees must report to the person in charge, in a verifiable manner, information about their health as it relates to diseases transmissible through food. The permit holder must require this reporting.
• 2-201.12, Exclusions and Restrictions. Defines when the person in charge must exclude (remove from the establishment) versus restrict (limit to non-food-handling duties) a food employee.
• 2-201.13, Removal, Adjustment, or Retention. The return-to-work provision. It sets the conditions for coming back, including symptom-free windows and, for diagnosed illnesses, medical documentation or regulatory-authority approval.

The signed agreement comes straight from the FDA. The FDA Retail Food Protection: Employee Health and Personal Hygiene Handbook provides the model Food Employee Reporting Agreement. Its stated purpose is to inform employees of their duty to notify the person in charge, and to demonstrate to the regulatory authority that an Employee Health Program is in place. State and county health departments publish near-identical versions.

One enforcement reality to plan around. The Food Code is a model regulation. State and local health departments adopt and enforce it, with their own return-to-work windows. Your jurisdiction's adopted version governs, not "the FDA inspects your restaurant." For vomiting or diarrhea without a diagnosis, your jurisdiction sets the window (commonly 24 hours symptom-free, and CDC recommends 48 hours for norovirus risk). Do not assume a single universal number across a multi-state footprint.

One honest limit: Xenia is not a HACCP-certification platform and does not auto-file reports with health authorities. The audit trail is there. Submission and return-to-work clearance stay operator-driven and health-authority-governed.

Report, restrict, or exclude: the five symptoms and the Big 6

A food employee must report five symptoms and six diagnoses (the Big 6). Some trigger restriction (moved off food handling). Others trigger exclusion (sent home). Getting this decision right, and documented, is the core of food handler illness reporting.

The five reportable symptoms, reported to the person in charge before or during a shift:

1. Vomiting
2. Diarrhea
3. Jaundice (yellowing of the skin or the whites of the eyes)
4. Sore throat with fever
5. Infected cut or wound on the hand or wrist that cannot be effectively covered

The Big 6 reportable illnesses are the highly infective pathogens easily transmitted by food workers:

1. Norovirus
2. Hepatitis A virus
3. Shigella spp.
4. Shiga toxin-producing E. coli (STEC)
5. Salmonella Typhi (typhoid fever)
6. Nontyphoidal Salmonella

Two definitions make the decision extractable. Restrict means the employee stays at work but moves off any task that touches exposed food, clean equipment, or food-contact surfaces. Exclude means the employee is removed from the establishment entirely while food is prepared or served.

| Condition | Action | Notes |
|---|---|---|
| Vomiting or diarrhea (active symptoms) | Exclude | Cannot be in the establishment while food is prepared or served |
| Jaundice | Exclude | Report to regulatory authority. Medical clearance needed to return |
| Diagnosed Big 6 illness (symptomatic) | Exclude | Hepatitis A, STEC, Shigella, Salmonella Typhi, nontyphoidal Salmonella |
| Sore throat with fever | Restrict | Move off food handling. Exclude if serving a Highly Susceptible Population |
| Infected, uncoverable cut or wound on hand or wrist | Restrict | Keep off exposed food until effectively covered or healed |
| Exposure without symptoms (household member diagnosed, or ate outbreak-linked food) | Restrict or monitor | Per Food Code exposure provisions |

A Highly Susceptible Population (HSP) is a group more likely to suffer severe foodborne illness, served in facilities like hospitals, nursing homes, assisted living, preschools, and childcare. HSP establishments face stricter exclusion thresholds. A condition that only triggers restriction in a standard restaurant can trigger full exclusion in an HSP facility. That is why the policy is not one-size-fits-all across a portfolio that mixes a hospital cafeteria contract with QSR units.

Return to work follows 2-201.13. For vomiting or diarrhea without a diagnosis, the worker stays out until symptom-free for the jurisdiction's window (commonly 24 hours, with CDC recommending 48 hours for norovirus risk). For diagnosed Big 6 illnesses and jaundice, return requires medical documentation and/or approval from the regulatory authority.

How does Xenia handle employee health reporting agreements?

Xenia broadcasts the written employee health policy to every food handler, captures a required acknowledgment and signature per employee, and re-collects the signature every time the policy is revised. The compliance-evidence trail sits in the system instead of a binder. This is food safety compliance software doing the part paper cannot: tracking a current signed agreement per person, at scale.

Here is how the pieces fit:

• Announcements with acknowledgment and signature. The standing policy goes out as an announcement that requires acknowledgment and signature. Broadcast the policy update, capture acknowledgment and a signed acknowledgment per food handler, and the auditable trail of who saw the policy and when sits in the system. When the policy is revised, a new jurisdiction adoption or an updated return-to-work window, the re-broadcast collects a fresh signature. This is not a notarized DocuSign-grade signature. It is documented compliance evidence.
• Follow-up questions with required photo, plus corrective action workflows. When a food handler reports a symptom (during an opening health check or a reporting form), the answer triggers a follow-up: which symptom, onset date, exposure. The reported symptom then creates a restrict-or-exclude task routed to the person in charge with sign-off. The corrective action workflow tracks it to closure and escalates to the DM if the decision is not logged. This is the same closure discipline covered in corrective action tracking from audit to closure.
• Location hierarchy with scoped permissions. A DM sees acknowledgment status across their district. Corporate sees the rollup across all units. "47 of 50 units have a current signed reporting agreement from every food handler" is one view, not 50 binders.
• Issues-first dashboards. Surface units with missing signatures and open restrict or exclude tasks, not just a completion percentage.

This is where the distinction from an allergen rollout matters. Broadcasting a new allergen SOP as a one-time rollout answers "did everyone see the new rule." The employee health policy answers a different question: "do we have a current signed agreement from every food handler that proves they know their reporting duty." Same signature capability, different operational job. One is a broadcast. The other is a standing program with a per-employee agreement on file. The scoring discipline that ranks critical food-safety items over cosmetic ones is covered in weighted audit scoring with critical-item thresholds.

Across a footprint at Dave's Hot Chicken scale (321 locations), proving every food handler has a current signed reporting agreement is the part paper cannot keep up with.

Where do operators see results?

Operators see results in three places: a current signed reporting agreement on file for every food handler, faster and documented restrict-or-exclude decisions, and an inspection-ready audit trail when the health inspector asks for proof.

The compliance-evidence win is the headline. When the inspector asks "show me the signed reporting agreement for this employee," the answer is one tap, not a binder search. This is the same compliance-evidence pattern Power Market runs across 360 C-store locations with QR deployment and bilingual checklists, where the rollout went live across all 360 locations and drove 40% faster task resolution. The mechanics are food-safety here, but the proof point is the same: signed acknowledgment captured and findable at multi-location scale.

The accountability win closes a documented gap. CDC found that half of sick food workers said their managers knew their symptoms, and managers rarely asked. A reporting form that fires a restrict-or-exclude task closes that communication gap with a documented decision. The manager is not relying on memory or a hallway conversation. There is a logged choice with a name and a timestamp.

The multi-unit win is one rollup view instead of fifty. With location hierarchy, acknowledgment status across the portfolio is a single screen, not a phone-around to fifty store binders. For restaurant operators running this across a growing footprint, the same pattern shows up in restaurant task management at multi-unit scale. The numbers that matter here are not a vanity percentage. They are "how many units have a current signed agreement" and "how many open restrict-or-exclude tasks are unresolved."

How to set up an employee health policy in Xenia

Setting up an employee health policy in Xenia takes five steps: load the policy, broadcast it with required signature, build the symptom-reporting form, wire the restrict-or-exclude task, and review acknowledgment status on the dashboard.

1. Load the written policy. Start from the FDA Employee Health Handbook model agreement or your jurisdiction's adopted version. Upload the SOP PDF and the AI Template Agent converts it into a digital form with the required acknowledgment fields. The agent transforms an existing SOP. It does not write the policy from scratch.
2. Broadcast with required acknowledgment and signature. Send the policy as an announcement to every food handler and conditional employee. Each one acknowledges and signs. Set it to re-trigger on every policy revision so the signed agreement on file is always current.
3. Build the symptom-reporting form. Create the reporting form covering the five symptoms and the Big 6, with a follow-up question for onset date and exposure. Make it accessible at shift start (tie it to the opening checklist) so the report happens before the shift, not after.
4. Wire the restrict-or-exclude corrective task. Configure the follow-up so a reported symptom auto-creates a corrective task routed to the person in charge: restrict or exclude, with manager sign-off and a deadline. Escalate to the DM if the decision is not logged.
5. Review acknowledgment status on the dashboard. Use the issues dashboard and location hierarchy to confirm every unit has a current signed reporting agreement from every food handler, and to clear open restrict or exclude tasks.

For the broader regulatory map this program sits inside, see the guide to food safety regulatory frameworks across FDA, FSMA, and HACCP, the HACCP checklist template, and the playbook for allergen control and cross-contamination. The full set of cluster guides lives on the food safety operations hub.