Grocery Illness and Injury Daily Log
Track employee illness reports, exclusion decisions, and work-related injuries in one daily grocery log. Use it to document FDA Food Code health actions and OSHA recordkeeping follow-up before the next shift starts.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Grocery Retail · Foodservice · Supermarket Operations · Prepared Foods / Deli · Retail Safety
Overview
This template is a daily grocery store log for two related events: employee illness reports that may require exclusion or restriction from food handling, and work-related injuries or incidents that may require OSHA follow-up. It gives the person in charge a single place to capture who reported what, when symptoms started, what decision was made, and what corrective action or escalation followed.
Use it when an employee reports vomiting, diarrhea, fever, jaundice, sore throat with fever, infected wounds, or a known exposure that could affect food safety, and also when a slip, cut, strain, burn, or other workplace injury occurs during the shift. The log is especially useful in stores with deli, bakery, meat, seafood, produce, and stockroom operations where both food safety and employee safety decisions happen fast.
Do not use this as a substitute for formal medical documentation, HR case files, or OSHA recordkeeping forms. It is not the right tool for unrelated customer complaints, product quality issues, or routine sanitation checks. It also should not be used to guess at diagnoses; record only what the employee reported, what was observed, and what action the PIC took. The value of the template is in creating a clear, defensible shift record that supports food code employee health decisions, injury follow-up, and next-step accountability.
Standards & compliance context
- The illness section supports employee health controls aligned with FDA Food Code expectations for excluding or restricting ill food employees.
- The injury section helps document events that may feed OSHA general industry recordkeeping and incident review processes.
- If your store has a formal food safety program, this log can support ISO 9001-style corrective action tracking by linking the event, root cause, and follow-up.
- For stores with written safety programs, the injury follow-up fields also support ANSI/ASSP Z10-style hazard correction and management review.
- If an injury involves sanitation chemicals, hot equipment, or other exposure concerns, use the log to trigger the appropriate safety and exposure review under applicable workplace standards.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Shift & Inspector Information
This section anchors the record to one date, shift, and responsible PIC so every illness or injury entry has clear ownership.
-
Log Date
Date this daily log is being completed.
-
Shift
Select the shift being covered by this log entry.
-
Person-In-Charge (PIC) Name
Full name of the manager or PIC completing this log (FDA Food Code §2-101.11).
-
Department / Work Area
Primary department or area covered (e.g., Deli, Bakery, Produce, Front End).
Employee Illness Report
This section captures the employee-reported symptoms and exposure details needed to decide whether food handling should continue.
-
Did any employee report illness symptoms at or before the start of this shift?
Includes vomiting, diarrhea, jaundice, sore throat with fever, or infected skin lesions per FDA Food Code §2-201.11.
-
Reporting Employee Name(s)
List the name(s) of employee(s) who reported illness. Enter 'N/A' if no illness reported.
-
Reported Symptom(s)
Select all symptoms reported by the employee(s). These are the Big 5 reportable symptoms under FDA Food Code §2-201.11.
-
Symptom Onset Time / Duration
When did the employee's symptoms begin? Note approximate time or duration (e.g., 'started last night', 'since this morning').
-
Has the employee been diagnosed with or exposed to a reportable pathogen?
Reportable pathogens include Norovirus, Hepatitis A, Shigella spp., Shiga toxin-producing E. coli (STEC), or Salmonella Typhi per FDA Food Code §2-201.11(A)(1).
Exclusion & Restriction Decision
This section documents the actual control action taken and why it was chosen, which is critical for food safety accountability.
-
Exclusion/Restriction Decision
Select the action taken for the reporting employee. Exclusion = removed from facility. Restriction = limited to non-food-contact duties. No Action = symptoms do not meet exclusion/restriction criteria.
-
Basis for Exclusion or Restriction Decision
Describe the specific reason for the decision (e.g., 'Employee reported vomiting — excluded per §2-201.12(A)', or 'Infected lesion on hand — restricted from bare-hand contact with RTE foods').
-
Was the employee informed of the exclusion/restriction decision and the reason?
PIC must communicate the decision and the applicable food safety policy to the employee.
-
Was the employee's manager / HR notified of the exclusion or restriction?
Notify store management and HR as required by store policy for any exclusion or restriction event.
-
Return-to-Work Clearance Requirement Communicated
Was the employee told what is required to return to work (e.g., symptom-free for 24 hours, medical clearance, negative test result per FDA Food Code §2-201.13)?
Work-Related Injury Report
This section records the injury facts, severity, and recordkeeping trigger so workplace incidents do not get lost in shift notes.
-
Did any work-related injury or incident occur this shift?
Includes cuts, slips, falls, strains, chemical exposures, or any other injury occurring in the course of employment.
-
Injured Employee Name
Full name of the injured employee. Enter 'N/A' if no injury occurred.
-
Nature and Location of Injury
Describe the injury type (e.g., laceration, sprain, burn) and body part affected (e.g., right hand, lower back).
-
Injury Severity / Treatment Required
Select the level of treatment provided or required. OSHA 29 CFR 1904.7 defines recordability based on treatment beyond first aid.
-
Was an OSHA 301 Incident Report initiated for a recordable injury?
OSHA 29 CFR 1904.29 requires a completed OSHA Form 301 (or equivalent) within 7 calendar days of a recordable injury.
-
Hazard or Root Cause Identified
Briefly describe the hazard or condition that contributed to the injury (e.g., wet floor without signage, box cutter used without cut-resistant gloves, improper lifting technique).
Corrective Actions & Follow-Up
This section closes the loop by assigning immediate fixes and next-step actions before the next shift begins.
-
Were immediate corrective actions taken for any illness exclusion or injury this shift?
Examples: area cleaned and sanitized after ill employee contact, hazard corrected, PPE issued, wet floor sign placed.
-
Description of Corrective Actions Taken
Describe all corrective actions completed this shift. Include who performed the action and when.
-
Are any follow-up actions pending for the next shift or management review?
List any open items requiring follow-up (e.g., awaiting medical clearance, OSHA 300 log update, maintenance repair request).
-
Follow-Up Actions Required
Describe pending follow-up items, responsible party, and target completion date.
-
PIC Signature
Person-In-Charge signature confirming accuracy of this daily log.
How to use this template
- 1. Enter the log date, shift, PIC name, and department or work area at the start of the shift so the record is tied to one responsible supervisor and one operating area.
- 2. Record any employee illness report immediately, including the employee name, reported symptoms, onset time or duration, and any known diagnosis or exposure relevant to food safety.
- 3. Document the exclusion or restriction decision, the basis for that decision, and whether the employee and manager or HR were informed before the employee returns to duty.
- 4. If a work-related injury or incident occurs, describe the injury, body location, severity, treatment needed, and whether an OSHA 301 Incident Report was initiated when required.
- 5. Note the hazard or root cause, list immediate corrective actions taken, and assign any follow-up actions needed for the next shift or management review.
- 6. Finish by signing as PIC only after the record is complete and any return-to-work or handoff instructions have been communicated.
Best practices
- Record symptoms and onset timing exactly as reported instead of translating them into a diagnosis.
- Separate food safety exclusion decisions from injury treatment notes so the basis for each action stays clear.
- Flag any employee with vomiting, diarrhea, jaundice, or a reportable exposure for immediate manager review before food handling continues.
- Document who was notified and when, because verbal handoffs are easy to lose during shift changes.
- Capture the hazard or root cause for every injury, even when the injury seems minor, so repeat conditions can be corrected.
- Use observable language such as cut on left index finger or slip on wet floor near dairy cooler rather than vague phrases like hurt hand or unsafe area.
- Assign follow-up actions to a specific person or role before closing the log so the next shift knows what remains open.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this Grocery Illness and Injury Daily Log used for?
This template documents employee illness reports, exclusion or restriction decisions, and work-related injuries during a grocery shift. It helps the person in charge record what was reported, what action was taken, and what follow-up is needed. It is especially useful when a store needs a single daily record that connects food safety employee health decisions with workplace injury tracking.
Who should complete this log?
The person in charge, shift supervisor, department lead, or another designated manager should complete it. In many stores, the PIC is the best fit because they can make immediate exclusion or restriction decisions and notify management or HR. If an injury occurs, the supervisor may add details, but the log should still reflect the shift-level decision and follow-up.
How often should this template be used?
Use it every shift, or at minimum once per day for each store location. A daily cadence works best because illness reports and injuries need to be captured close to the time they occur, while details are still fresh. If your store runs multiple shifts, separate entries help avoid missed handoffs and unclear return-to-work instructions.
Does this template replace OSHA injury logs or incident reports?
No. This template is a shift-level daily log, not a substitute for formal OSHA recordkeeping forms or your internal incident reporting process. It can note whether an OSHA 301 Incident Report was initiated for a recordable injury, but you still need to follow your organization’s recordkeeping workflow. Think of it as the operational record that supports those filings and reviews.
How does this relate to FDA Food Code employee health requirements?
The illness section supports employee health decisions tied to food safety, including exclusion and restriction when symptoms or reportable exposures are identified. That makes it easier to show that the store acted on reported illness before the employee returned to food handling. It also creates a clear record of the basis for the decision and whether return-to-work clearance was communicated.
What are the most common mistakes when using this log?
Common mistakes include recording vague symptoms without onset timing, failing to document the reason for exclusion or restriction, and not noting who was informed. Another frequent issue is treating an injury like a minor note and skipping root-cause follow-up or OSHA incident initiation when needed. The template works best when each entry is specific, time-stamped, and tied to a clear action.
Can this template be customized for different grocery departments?
Yes. You can tailor the department or work area field for produce, deli, bakery, meat, seafood, front end, or stockroom. Some stores also add fields for manager name, witness, temporary reassignment, or return-to-work documentation. The core structure should stay the same so illness and injury records remain consistent across shifts.
How does this fit with other store systems or integrations?
This log can be paired with incident reporting, HR case management, food safety checklists, and corrective action workflows. Many teams use it alongside a digital task system so exclusion decisions, cleaning follow-up, and injury investigations are assigned immediately. It also works well as a source document for management review and trend tracking.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
See how MangoApps helps manufacturers and distributors collaborate in real time — sharing product updates, market intel, and goals on one unified platform.
-
Intranet file naming conventions that improve search, reduce clutter, and help employees find the right document fast.
-
Learn how MangoApps Community Suite captures, votes on, and implements customer ideas — turning community feedback into product decisions at scale.
-
On-premise intranet explained: control, security, and compliance benefits for regulated organizations and IT teams.
Ready to use this template?
Get started with MangoApps and use Grocery Illness and Injury Daily Log with your team — pricing built for small business.
