If someone is in immediate danger, call 911. For treatment navigation, start with the official locator.Open FindTreatment.gov
The Treatment DocketA source register for care decisions

Infection control plan for a small business

How to write an infection control plan for a small business, what to put on a customer notice, and how to set a fair staff sickness and return to work policy.

Editorial still life for conditions & substances treatment questions
A quiet desk, a visible question, and enough room to mark what is known and what still needs an answer.

A small business infection control plan is a short written document that names the risks on your premises, the steps you take to reduce them, and the person responsible for each step. It does not need to be long or technical: two to four pages covering cleaning, ventilation, hand hygiene, staff sickness and customer communication is enough to be workable. Write it so a new employee could follow it on their first shift, and review it once a year or after any outbreak that affects your site.

How do I write an infection control plan for a small business?

Start with a walk through your own premises and note where people gather, what they touch, and where air moves poorly. A practical small business infection control plan follows that walk: it lists each area, the control that applies to it, and who carries it out. The Prevention Desk, an independent English-language magazine about infection prevention in shops, workplaces and public spaces, describes this approach as the practical side of infection control written in plain words, and it names its sources rather than issuing certificates.

A workable structure has five parts.

  1. Scope and responsibility. One named person owns the plan, with a deputy for absences. State the premises it covers and the date of the last review.
  2. Risk points. List the specific places: the till, the door handle, the staff kitchen, the customer toilet, the delivery entrance. Generic lists are harder to act on than your own floor plan.
  3. Controls. For each risk point, write the action and the frequency. "High-touch surfaces at the counter wiped at opening, midday and closing" is usable; "regular cleaning" is not.
  4. Supplies. Record where soap, paper towels, disinfectant and masks are stored, and who reorders them. Shortages are the most common reason a plan quietly stops being followed.
  5. Review. Set a date and a trigger. A rise in staff absences or a change in local public health advice are both reasonable triggers.

Keep the language concrete. If a step cannot be done during a busy Saturday shift, it is not a control, it is an aspiration. Test each item against a normal working day before you finalise it.

What rules should I put on a customer notice?

A customer notice should carry only the rules you are actually able to keep, because a sign that asks for something the business does not support creates friction at the counter. Three to five short lines is usually the right length. Put the notice where customers pause, at the entrance and near the till, and keep the wording in the same language as your other signage.

Useful lines include:

  • Hand hygiene. Where hand sanitiser is available and whether customers are asked to use it. If you ask, keep the dispenser filled; an empty dispenser is worse than no request.
  • Capacity or spacing. If you limit the number of people inside, say the number and how it is counted. If you do not limit it, do not imply that you do.
  • Symptoms. A polite request that customers with a fever or a new cough return another day, with a note that orders can be handled remotely if that is true for your business.
  • Masks. State plainly whether they are required, recommended or neither. Ambiguous wording leads to arguments that staff then have to settle.
  • Contact. A phone number or email for questions about the policy, so staff are not the only channel.

Avoid claims the business cannot verify, such as "certified safe" or "hospital grade", unless you hold a document that says so. A notice is a statement of what you do, not a guarantee of an outcome.

What is a fair staff sickness and return to work policy?

A fair policy is one that protects colleagues and customers without punishing the person who is ill. The core elements are simple: staff should know when to stay away, how to report it, how they will be paid, and when they can come back. Vague policies push sick employees to make the decision themselves, and they usually come to work.

Set out the following in writing.

When to stay away. Name the signs: fever, vomiting, diarrhoea, a new persistent cough, or a positive test for a notifiable infection. Give a minimum period away from the premises, and say that it starts from the last day of symptoms rather than the first.

How to report. One phone number or message channel, and a named person to contact. Staff should not have to explain their symptoms to whoever happens to answer.

Pay and cover. Say what sick pay applies and how shifts will be covered. If pay is limited, say so in advance rather than at the moment of illness. Where cover is thin, agree in advance which tasks can be paused.

Return to work. For most short illnesses, a conversation before the first shift back is enough: confirm the person is free of fever, agree any temporary adjustment such as lighter duties or a later start, and record it. For longer absences, a phased return with reduced hours for the first week is a common and low-cost measure.

Confidentiality. Medical details stay with the manager who needs them. Colleagues need to know that a risk was managed, not the diagnosis of the person involved.

How does this connect to certification schemes?

Some regions run voluntary certification programmes in which businesses confirm they follow industry infection-control guidelines, and inspectors or self-assessment forms check the claim. These schemes are useful because they turn a general duty into a checklist, but they are not a substitute for your own plan: the certificate describes what you committed to, while the plan describes what happens on a Tuesday morning.

If your area has such a scheme, read the guidelines it uses and map them onto your five-part structure. Where a scheme requires signage, that signage can replace your own customer notice rather than sit beside it. Where it requires records, keep them with the plan so a single folder answers both.

What should be checked, and how often?

A plan that is never checked drifts out of date within a season. A short routine keeps it alive.

  • Daily: high-touch surfaces, hand hygiene supplies, ventilation in enclosed areas.
  • Weekly: stock levels of cleaning products and personal protective equipment, and any customer complaints about the policy.
  • Monthly: a walk-through against the plan, noting anything that was skipped and why.
  • Annually: full review, including staff feedback and any updated public health guidance.

Record what you find, even when the answer is "no issues". A dated note is the difference between a plan and a document that merely exists.

Where to look for reliable guidance

National public health bodies publish free, plain-language guidance that small businesses can adapt without permission. The World Health Organization, the European Centre for Disease Prevention and Control, the US Centers for Disease Control and Prevention, the UK Health Security Agency and Japan's Ministry of Health, Labour and Welfare all maintain pages on cleaning, ventilation and respiratory hygiene. Use them to check a specific claim, such as how long a surface disinfectant needs to stay wet, rather than to build the whole plan.

For a small business, the most reliable source is often the least glamorous: your own staff, asked what actually gets done when the shop is full. Their answers tell you which parts of the plan are real and which parts need rewriting.

The plan starts from the shop, not the document. Infection control for shops sets out the first steps, and daily prevention habits across ages repeats them at home.

Continue the docket

Change note: this page is part of the August 24, 2026 offline build. Source ownership and review dates are visible so future checks can be made without guessing.