The 48-hour rule, explained and automated

Anyone who has run a kitchen knows the rule: a food handler who has been vomiting or has diarrhoea stays away from work until they have been free of symptoms for 48 hours. It is simple to state and surprisingly hard to apply.

Where it goes wrong

The rule is usually applied by whoever picks up the phone. At 5am that is a shift manager with a delivery to check in. The caller says "I've got a bug" or "I think it's flu". The manager writes "sick" on a pad. Nobody asks which symptoms, or when they last occurred, and so nobody knows when the person can safely come back.

Two things then happen. Some people come back too early, which is a food safety risk. Others are kept away for 48 hours with a cold, which is a shift you did not need to lose.

What the rule actually covers

Most food businesses exclude for vomiting, diarrhoea, jaundice, a confirmed food-borne illness, and a fever together with a sore throat. A cold does not count. Nor does a sore throat on its own, or a fever on its own.

The clock starts when the person was last sick, not when they rang in. Someone who was ill at 2am on Tuesday and has been fine since can work from 2am on Thursday.

How our AI handles it

When someone rings the absence line, the AI asks what is wrong. If the answer is vague, it asks a follow-up:

"Sorry to hear that. Was that vomiting or diarrhoea? I ask because of the food safety rules."

If an excluding symptom is present, it explains the rule, asks when the symptoms last occurred, and works out the earliest return. The report the restaurant receives a few minutes later shows the food safety risk in red, with the date.

If the caller pushes back and says they will come in anyway, the AI does not argue. It records it, and the report is flagged for a manager.

One detail we learned the hard way

Company sickness policies are often written loosely: "vomiting, a fever, diarrhoea or anything similar". An AI that reads the policy literally will send someone home for 48 hours with a temperature. We now treat the precise list of excluding symptoms as a setting, separate from the policy text, so the rule is applied the same way on every call.

The 48-hour rule is a good example of something a busy person on a phone does inconsistently and a well-instructed AI does the same way every time.