What this is
What is an infectious disease response plan?
What is an infectious disease response plan?
It is the site-level plan for handling an outbreak among the workforce: how symptoms get reported, when someone is excluded from work, how the area gets cleaned, and how the business keeps running while people are off. It is written once and reviewed on a set cycle rather than raised per event.
What is the difference between this plan and an exclusion record?
This plan sets the rules in advance: the criteria, the triggers, the roles. The exclusion record is what happens when those rules are applied to one named person on one occasion. A site can have a strong plan and still fail if the exclusion record it produces contradicts the plan's own criteria.
What counts as a cluster for this plan's response section?
A cluster is two or more cases that share a plausible common source or timeframe, which is different from isolated illness handled under exclusion alone. The plan should set a numeric or time-based trigger for when isolated cases get escalated to a cluster investigation and public health liaison.
Scope
When is an infectious disease response plan required?
This plan sets the rules a site follows during an outbreak. It is not the record of a single case, and it is not the outbreak investigation itself — those are separate templates this one links to.
Use this template when
- The plan is being written or reissued for a site, or its annual review is due
- Occupational health needs to sign off a new or revised exclusion or cluster-recognition criterion
- A new business continuity risk (supplier, haulier, critical role) needs to be reflected in the plan
- You are running the Wellbeing and Mental Health programme and this plan is one of its standing controls
- The plan has been tested or exercised and the outcome needs recording against it
Do not use it for
- Illness Exclusion Record, which records one worker's exclusion decision and clearance to return, not the site-wide rules that decision was made against.
- Outbreak Investigation Record, which investigates an actual cluster once it happens, including case definition, timeline and exposures.
- Wellbeing Program Plan, which covers psychosocial risk and workload rather than infection control.
- Absence Trend Review, which looks at absence patterns generally, not this plan's specific reporting and exclusion triggers.
- Anything outside KnowHealth, such as a general business continuity or emergency plan not specific to workforce illness.
Compliance mapping
Which ISO 45001 cl.8.2 requirements does this satisfy?
ISO 45001 cl.8.2 covers emergency preparedness and response; the fields below map its intent onto reporting, response, continuity and communication rather than to sub-clauses the standard does not itemise this specifically.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.8.2 — Emergency preparedness and response | Define reporting and exclusion criteria before an outbreak occurs, not during one | Reporting and exclusion |
| ISO 45001 cl.8.2 — Emergency preparedness and response | Set a cluster-recognition trigger and a public health liaison route | Response |
| ISO 45001 cl.8.1 — Operational planning and control | Identify critical roles and confirm cross-training supports absence | Continuity |
| ISO 45001 cl.5.4 — Consultation and participation | Review the plan with occupational health, not just the site lead | Header |
| ISO 45001 cl.7.4 — Communication | Communicate the plan to the workforce and confirm managers are trained on it | Outcome |
| ISO 45001 cl.9.1 — Monitoring, measurement, analysis and performance evaluation | Confirm the plan has been tested or exercised, not just written | Continuity |
| ISO 45001 cl.10.2 — Incident investigation, nonconformity and corrective action | Raise and track an action when the plan is found deficient at review | Outcome |
What it does not cover
- Reporting route available out of hours, which without it a Saturday-night symptom onset waits until Monday to be reported, defeating the point of early exclusion.
- Pay arrangements do not discourage reporting, which if unmet means the criteria on paper are routinely ignored by workers protecting their pay.
- Cluster recognition trigger set, which left undefined turns every early cluster into a set of unconnected sick days until it is too large to contain quietly.
- Plan tested or exercised, which without it leaves every other field an assertion rather than a demonstrated capability.
- Applies to contractors and visitors, which if narrowed to employees only leaves a site's most common outbreak vector — a visiting driver or contractor — outside the plan entirely.
Global
Infectious Disease Response Plan requirements by country
The plan itself is generic, but the exclusion duty it references is not: what is discretionary guidance in most workplaces is a binding food-safety obligation on a site that handles food, and that gap is where most of the friction lives.
Food Standards Agency guidance under the Food Safety Act 1990 / Food Hygiene (England) Regulations
Food handlers with diarrhoea, vomiting or jaundice must be excluded from food handling; the FSA sets the symptom list the plan's criteria should mirror.
A UK food site's exclusion field must match the FSA symptom categories exactly, not a shortened in-house version.
FDA Food Code, Chapter 2-201 (Employee Health)
Food establishments must restrict or exclude employees reporting specified symptoms or diagnoses, with the person-in-charge responsible for applying the criteria.
The 'decision made by trained person' control matters here: Chapter 2-201 puts the duty on a named person-in-charge, not on self-exclusion.
Codex Alimentarius, General Principles of Food Hygiene (CXC 1-1969), personal hygiene and health status
Sets the baseline that food handlers known or suspected of a disease transmissible through food should not work in food handling areas.
For multi-country operators this is the common floor to build to before layering on the stricter UK or US detail above.
How to complete it
How to complete an infectious disease response plan, step by step
Four judgement calls decide whether this plan will hold up when it is actually invoked, rather than just when it is reviewed.
Symptoms rarely announce themselves during office hours. If the reporting route depends on a manager who is not on site nights or weekends, the field can be marked yes while the practical answer is no.
An exclusion criterion is only as good as the incentive not to hide symptoms. If sick pay for excluded days is worse than statutory minimum or discretionary, treat the whole plan as unproven regardless of how the other fields score.
A name in a cross-training register is not the same as that person having covered the role recently. Continuity fields should reflect recent practice, not a training matrix nobody has checked against actual absence.
A tabletop discussion with the site lead is not the same as an exercise that involves the people who would actually report, decide, and cover. Score 'plan tested or exercised' against the latter.
What auditors find
Most common infectious disease response plan findings
Reviewers repeatedly find the same gaps between what the plan states and what would actually happen during a live outbreak.
| Finding | Clause | What fixes it |
|---|---|---|
| Exclusion criteria are defined but not shared with the workforce in plain language | ISO 45001 cl.7.4 | Add a one-page plain-language version of the exclusion symptom list to induction and break-room communication, separate from the plan document itself. |
| Cluster recognition trigger is a vague 'if numbers seem high' rather than a number or timeframe | ISO 45001 cl.8.2 | Set an explicit trigger, for example two or more cases with a shared exposure within 72 hours, and record it as the field value rather than leaving it to judgement on the day. |
| Continuity plan reference is left blank because the site continuity plan is owned by a different team | ISO 45001 cl.8.1 | Record the linked continuity plan ID even when it is owned elsewhere; the link exists so an auditor can trace the two plans together. |
| Managers trained on the plan is marked yes based on a single briefing years ago | ISO 45001 cl.7.4 | Tie this field to a refresh cadence — annually, or whenever the plan itself changes — rather than a one-off historical event. |
| Applies-to-contractors field is marked yes with no visitor sign-in symptom check in practice | ISO 45001 cl.8.2 | Add a symptom question to the visitor and contractor sign-in process itself, so the field reflects an actual control rather than an intention. |
| Plan tested or exercised is marked yes citing a discussion at a management meeting | ISO 45001 cl.9.1 | Require a specific exercise record — date, scenario, participants, outcome — before this field can be marked yes at the next review. |
Case in point
Case in point: the plan that only worked on paper
A packing site scored full marks on exclusion criteria and cluster recognition every year. When a norovirus cluster hit, the reporting route ran through a supervisor off that weekend, and two affected workers came in anyway because excluded days were never checked against payroll, which docked their pay.
The fix did not touch the plan's criteria — they were correct. It added a weekend on-call number and put excluded pay on the same basis as other sick leave. Both changes came from fields the annual review had treated as formalities.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- HLT-051
- Archetype
- Plan
- Record ID
- IDP-2026-000
- Scoring
- Plan current
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.8.2
- Links
- Links Illness reporting, Business continuity
- Tags
- Infection control
- Sections
- 5
- Fields
- 43
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 3
Header
11 fieldsPlan ID*
Auto sequence. Format IDP-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Version*
Issue Date*
Next Review Due*
Plan Owner*
Approved By*
Reviewed With Occupational Health*
- Yes3 pts
- Partly1 pt
- No0 pts
Food Sites Carry An Exclusion Duty
Most workplaces send people home as a courtesy. A food site is legally required to exclude certain symptoms, and people will not comply if it costs them a day's pay.
Reporting and exclusion
6 fieldsSymptoms Requiring Reporting Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Exclusion Criteria Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Return Clearance Criteria Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Reporting Route Available Out Of Hours*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Pay Arrangements Do Not Discourage Reporting*
- Yes3 pts
- Partly1 pt
- No0 pts
Applies To Contractors And Visitors*
- Yes3 pts
- Partly1 pt
- No0 pts
Response
6 fieldsCase Definition Process Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Cluster Recognition Trigger Set*
- Yes3 pts
- Partly1 pt
- No0 pts
Public Health Liaison Route Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Enhanced Cleaning Protocol Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Product Risk Assessment Triggered*
- Yes3 pts
- Partly1 pt
- No0 pts
Communication Plan Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Continuity
6 fieldsCritical Roles Identified*
- Yes3 pts
- Partly1 pt
- No0 pts
Cross Training Supports Absence*
- Yes3 pts
- Partly1 pt
- No0 pts
Remote Working Where Possible*
- Yes3 pts
- Partly1 pt
- No0 pts
Supplier And Haulier Impact Considered*
- Yes3 pts
- Partly1 pt
- No0 pts
Vaccination Offered Where Appropriate*
- Yes3 pts
- Not applicable3 pts
- No0 pts
Plan Tested Or Exercised*
- Yes3 pts
- No0 pts
Outcome
14 fieldsPlan Current*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Communicated To Workforce*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Managers Trained On It*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Linked To Business Continuity*
- Yes3 pts
- Partly1 pt
- No0 pts
Continuity Plan ID
Links to ENV-046 Plan ID
Next Review Due*
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Occupational Health*
Signature*
Site Manager*
Second Signature*
HLT-051 · record IDs look like IDP-2026-000 · Links Illness reporting, Business continuity
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The plan is easy to write and easy to let go stale. The work that actually protects a site is keeping the reporting route live and the continuity arrangements current between reviews.
Holds the plan against its review cycle, flags when occupational health sign-off has lapsed, and keeps the linked exclusion and investigation records visible from the same view.
Surfaces the plan alongside the site's other emergency preparedness controls, so a reviewer isn't checking infection response in isolation from the rest of the safety management system.
Tracks the plan against the jurisdiction-specific exclusion duty that applies to the site, and raises the gap when local requirements change ahead of the next scheduled review.
Coordinates the review with occupational health, drafts the corrective action when a field falls short, and holds every write for your approval before it touches the plan.
This template lives in KnowHealth — employee wellbeing. Exposure monitoring, health surveillance, case management and return to work.
Meet KnowHealth→Glossary
Infectious Disease Response Plan definitions and key terms
- Exclusion
- Temporarily removing a worker from food handling duties, or from site altogether, on health grounds, until they meet defined clearance criteria to return.
- Cluster
- Two or more illness cases sharing a plausible common source or timeframe, distinct from isolated cases handled individually under exclusion.
- Public health liaison
- The defined route and contact for notifying the relevant public health authority when a cluster or notifiable disease is suspected, rather than deciding case by case whether to call.
- Business continuity
- The arrangements — cross-training, remote working, supplier contingency — that keep operations running when a portion of the workforce is excluded at the same time.
- Notifiable disease
- A disease that public health authorities require to be reported by law, independent of whether the site chooses to exclude the affected worker.
FAQ
Frequently asked questions about infectious disease response plan
What is the infectious disease response plan template based on?+
It is built against ISO 45001 cl.8.2, which covers emergency preparedness and response. The clause does not itemise infection control specifically, so the plan interprets it against reporting, exclusion, cleaning and continuity.
What sections does the plan contain?+
Five sections: Header, Reporting and exclusion, Response, Continuity, and Outcome, covering 43 fields in total, most of them required.
How often is the plan reviewed?+
Written once and reviewed yearly, with an additional review recommended after any outbreak response so lessons from a live event get folded back in immediately rather than waiting for the next cycle.
Does this plan cover the actual handling of an outbreak once it happens?+
No. This plan sets the rules in advance. The linked Illness Exclusion Record and Outbreak Investigation Record are where an actual case or cluster gets handled and documented.
Why does a food site need an exclusion duty other workplaces don't?+
Food safety regulation in most jurisdictions requires excluding food handlers with specific symptoms, such as gastrointestinal illness or jaundice, from food handling areas — a legal duty, not a discretionary wellbeing measure.
Can the plan template be changed?+
Yes. Every field, option, score and conditional rule is editable, and its links to the exclusion and investigation records travel with it. Most sites install it as-is, run it for a cycle, then adjust.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Wellbeing and Mental Health
Wellbeing Survey
Asks workers about workload, support, stress and how they are coping
Psychosocial Risk Assessment
Assesses workplace factors that affect mental health, including demand, control, support and change
Workload Review
Reviews whether workload, hours and staffing are sustainable for a team
Wellbeing Program Plan
Sets out what wellbeing support is available and how people access it
Support Referral Record
Records that a worker was pointed towards support services, without recording why
Fitness for Duty Assessment
Assesses whether a worker is currently able to perform their role safely
More in Infection Control
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 cl.8.2 — Emergency preparedness and response
- ISO 45001:2018 cl.8.1 — Operational planning and control
- FDA Food Code, Chapter 2-201 — Employee Health
- Codex Alimentarius CXC 1-1969 — General Principles of Food Hygiene
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.