Do you need an employee illness policy in writing?
Under the 2026 Food Code, yes: the written policy is now part of the code itself. FDA released the 2026 edition on September 17, 2026, and its summary of changes retitles Part 2-5 "Policies and Procedures for Employee Illness Management" and makes § 2-501.11 "Employee Illness Policy Documentation." Law-firm commentary on the release describes it as a requirement that permit holders keep a written policy and have it available for the regulator on request. The model inspection form even has a line for it, now called "Illness Documentation."
One caveat before you rewrite anything: the Food Code is a model code, not a federal rule. It binds you only once your state, county or city adopts it, and many still enforce an earlier edition. Call your health department and ask which edition applies to you and when that changes. A written policy is worth having either way, because earlier editions already expect your staff to know the rules and the person in charge to act on them.
What the policy should cover
A health department fact sheet that follows the Food Code breaks the policy into three parts: management tells employees about the policy and trains them, employees learn to recognize symptoms and know they must report them, and management has a plan to restrict or exclude anyone with symptoms, a diagnosis or an exposure. Turned into a one-page policy, that means writing down:
- What to report. Vomiting, diarrhea, jaundice, and sore throat with fever. The fact sheet also lists infected cuts or burns on the hands or arms.
- Which diagnoses to report. The Food Code lists specific illnesses, including norovirus, hepatitis A virus, Shigella, Shiga toxin-producing E. coli and Salmonella. Copy the exact list from the edition your regulator uses.
- Who to tell, and how. The person in charge, before the shift starts, by a phone number or channel everyone actually has.
- What happens next. Whether the employee is excluded from the establishment or restricted from certain tasks, and who decides. Many jurisdictions also require the person in charge to notify the health authority about certain diagnoses, so check yours. Keep a record of each case: our Employee Illness Report & Exclusion template is built for that.
- Exposure. What an employee should do if someone at home has one of the listed illnesses. FDA's decision tree handles exposure differently from symptoms, so write down what you will do.
- When they come back. See the next section.
When can a sick employee return?
This is the part managers most often guess at. A state health department summary of the Food Code's symptom rules says an employee excluded for symptoms can return after being symptom-free for at least 24 hours, or with written medical documentation that the symptom comes from a noninfectious condition. For diagnosed illnesses the rules are stricter, and the 2026 edition changes how clearance works: reinstatement can now rest on two consecutive negative results from a validated test run by an accredited laboratory, not just stool cultures (§ 2-201.13). Your health authority has the final say, so put "check with the health department before bringing back anyone with a diagnosed illness" in the policy.
Vomiting and diarrheal events
The 2026 code moved the cleanup requirements for these events into a new section, § 2-502.11, under a new subpart on contamination event response. Your policy doesn't need to repeat the procedure, but it should say where the written cleanup procedure is and who is responsible for running it. A Vomit & Diarrheal Event Cleanup template gives each incident a dated record of who did what.
Getting every employee to acknowledge it
A policy nobody has read doesn't protect you in an inspection. Have each employee acknowledge it when they're hired and again whenever you change it, and keep a record of who acknowledged it and when.
Does the acknowledgment have to be signed? We didn't find wording in the Food Code summaries we read that requires an employee signature. What the code asks for is that the policy exist in writing and be available to the regulator. Signed records are still common practice: FDA's model Form 1-B in Annex 7, a reporting agreement for food employees and conditional employees, has signature and date lines for the employee and the permit holder. If your health department hands out its own form, use it, and ask whether they expect a signature.
On paper that means a binder of signed sheets that goes missing when a manager leaves. On a phone it can be a short checklist: the employee scans a QR code, reads the policy, answers the questions and signs or initials in a signature field, and the record is saved with the date and time. They don't need an account or an app, which matters for a seasonal hire on their first day.
A free starting point
Our free restaurant temperature log kit includes an Employee Illness Policy Acknowledgment template alongside the cold-holding, cooling and sanitizer logs and a daily person-in-charge check. You get printable PDFs and QR-ready versions, and you can edit them to match your own policy and your local rules. The Employee Illness Report & Exclusion and Vomit & Diarrheal Event Cleanup templates are available too once you sign up free. If you're also tightening up your temperature records, our post on a cold-holding log that holds up covers the rest.
What this does and doesn't do
A written policy and a record of acknowledgments help you show what you told your staff and when. They don't guarantee a clean inspection, and they don't replace the Food Code text, your local regulator's requirements, or food protection manager training. Rules on exclusion, restriction and return to work vary by jurisdiction and by the illness involved, so confirm the details with your health department before you finalize the policy.
a7reports.com is not affiliated with the FDA or any health department.