Case study: reporting a fictional food recall and outbreak alert

What to take away

The scenario below is fictional and teaches workflow, not current safety advice.
Product scope and consumer action lead the first report.
Epidemiology, traceback, and testing are labeled as separate evidence streams.
A recall does not make every illness part of the outbreak.
Each update changes the prominent facts, not just the final paragraph.

At 9:10 a.m., a fictional state health department posts an investigation notice about six laboratory-confirmed illnesses. At 9:35, fictional producer North Valley Kitchens announces a recall of two 12-ounce salad kits with named lot codes. No real company, product, case, or notice is described here.

9:15 a.m.: open an evidence ledger

The desk copies the state notice, records the page time, and creates four columns: confirmed, reported, inferred, and unknown. Confirmed facts include six cases meeting the notice's definition, three hospitalizations, illness-onset dates, and interviews that found five people ate packaged salad. Unknowns include the ingredient, contamination point, full distribution area, and whether additional illnesses will meet the case definition.

The reporter does not write "salad caused six illnesses." A common exposure reported by patients supports a hypothesis, not a completed source finding. The evidence-verb discipline follows the health alerts and medical news guide.

CDC describes a multistate foodborne investigation as a seven-step process that can have several steps underway at once. The CDC investigation sequence distinguishes detecting a possible outbreak, defining and finding cases, generating and testing hypotheses, confirming the source, controlling the outbreak, and deciding when it is over. It also identifies epidemiologic, traceback, and food or environmental testing as three evidence types used to confirm a source.

9:40 a.m.: reconcile the product notice

The producer's fictional announcement lists:

Field	Fictional detail
Product	North Valley Garden Crunch salad kit
Package	12 ounces
Lots	NV271A and NV272A
Use-by dates	February 4 and February 5, 2027
Distribution	Stores in three named states
Action	Do not eat; discard or return to place of purchase

The desk checks every character twice. It does not shorten the headline to "North Valley salads recalled" because other products may be unaffected. It asks the company and regulator whether the action is voluntary, whether a recall class has been assigned, and whether retailers have received notices. Reading the notice fields in order follows how to read a public health notice.

10:05 a.m.: publish the first brief

The opening names the two lots, three-state distribution, and discard-or-return instruction. The second paragraph states that officials are investigating whether the recalled kits are connected to six illnesses. The story says the connection is under investigation and gives illness-onset dates.

The desk withholds a claim that the kits caused the illnesses. It also avoids saying all six patients ate the product because the fictional notice says five reported packaged salad and investigators are still collecting brand information. Before the post goes out, the health alert reporting checklist is marked line by line.

12:20 p.m.: add the regulator's record

The fictional regulator posts the company notice but has not yet assigned a recall class. The update says that plainly. Posting a notice is not described as endorsement or independent confirmation of every company statement.

FDA's consumer explanation of product recalls says a recall can involve correction or removal and explains where consumers can find public warnings and classified entries. It also notes that when a company announces a recall, market withdrawal, or safety alert, FDA typically posts the announcement as a public service and does not endorse the product or company. That distinction guides the wording of this fictional update.

Day 2: the evidence changes

Investigators report that traceback records point to one processor and that an outbreak strain was found in an unopened kit. The desk can now describe a stronger link, while attributing the finding and naming the exact product tested. It still does not claim that every illness with similar symptoms belongs to the outbreak.

The case count rises to nine because three older reports now meet the case definition. The story explains that the increase does not necessarily mean three people became ill that day. Reporting and classification can lag symptom onset.

Day 4: the scope narrows

Testing identifies one ingredient supplied during a limited production window. Officials say other lots are not included. The desk rewrites the headline and action box to retain the exact affected codes and adds a dated note describing the narrower scope. It does not say all other salad products are proven safe. A parallel desk drill for a utility advisory is the drinking water advisory case.