At the Kitchen Tap: Why MBG Food Safety Needs a Public Water and Wastewater Readiness Record

MBG Watch · 2026-08-14

The narrow question

MBG’s food-safety debate has moved in the right direction. BGN is no longer treating hygiene and sanitation as a secondary administrative matter. In January 2026, BGN said new SPPG kitchens must obtain a Sertifikat Laik Higiene Sanitasi, or SLHS, within one month of operation, and that each SPPG must have wastewater treatment through an IPAL. In March, BGN suspended 1,256 SPPG in eastern Indonesia for not registering SLHS and not having IPAL. In April, it said roughly 1,780 of 26,800 SPPG had been temporarily stopped for missing IPAL, missing SLHS registration, or delayed certification. In August, BGN gave kitchens operating without SLHS a 10 August deadline and said kitchens found not hygienically and sanitarily fit could be permanently closed.

That record matters. It is also incomplete.

The question now is narrower than “is the kitchen certified?” It is: what evidence can an SPPG kitchen show, kitchen by kitchen and batch by batch, that the water used for washing ingredients, cooking, handwashing, utensil washing, cleaning, ice, and wastewater handling remains safe in ordinary operation and after heavy rain, flooding, coastal inundation, or water-supply interruption?

MBG should not stop meals because rain exists. Indonesia is an archipelagic, wet, coastal country; weather is an operating condition, not an exceptional excuse. But the same kitchen that is safe on a dry day may need a different menu, a different treatment step, a delayed dispatch, or a temporary pause when source water is interrupted, a washing tank is contaminated, floodwater reaches the preparation area, or wastewater backs up.

The missing layer is a public water and wastewater readiness record.

Why water belongs inside the food-safety chain

Food safety is often discussed through visible controls: cooking temperature, storage time, delivery delay, and whether food is consumed within the safe window. Those are necessary controls. MBG Watch’s earlier pieces — “Food Safety Crisis in MBG Rural Rollout,” “The First Thousand,” “Heat at the Kitchen Door,” “Hourly Heat, Not Daily Heat,” “Weather at the Dispatch Door,” “The Power Behind the Plate,” and “Not the Panel, the Cold Chain” — each approached the same operating problem from a different side: safe meals depend on inspectable systems, not assurances.

Water is one of those systems.

WHO’s meeting report on water used in food production and processing states the principle plainly: water is a major input in food from primary production through consumption; it can contact food directly or indirectly; and it is used to maintain hygiene and sanitation throughout the food chain. PAHO’s publication of WHO’s “Golden Rules” makes the kitchen-level version even simpler: safe water is as important for food preparation as for drinking; if there is doubt about the water supply, water should be boiled before being added to food or used to make ice.

For MBG kitchens, this means water cannot sit outside the safety record. It is not only an input. It is the medium through which hands are washed, utensils are cleaned, vegetables and fruit are handled, surfaces are wiped, cooked food containers are rinsed, and waste is moved away from the kitchen. A failure in water or wastewater control can turn an otherwise correct cooking process into a contaminated service process.

The wastewater side matters for the same reason. BGN’s own SLHS and IPAL language already recognizes that kitchen sanitation and wastewater are not separate from food safety. IPAL is not a decorative compliance asset. It is part of keeping kitchen waste, standing water, drains, pests, and nearby environmental contamination from returning to the preparation chain.

What the current incident record does and does not show

Recent poisoning reports should be read carefully. They do not justify claiming that rain or kitchen water caused MBG poisoning events in general. The public record is not strong enough for that.

What it does show is enough to justify a stronger water-control record.

In Seruyan, Kompas reported that 156 students were poisoned after consuming MBG meals distributed by SPPG Seruyan Hilir Kuala Pembuang I. BGN said laboratory results received on 1 August 2026 found bacteria in a number of food samples, and the SPPG was temporarily stopped. The reported evaluation covered SLHS, water quality, IPAL, and other administrative requirements. That does not prove water caused the event. It does show that, after an incident, water quality and wastewater controls are part of the repair list.

In Jepara, Betanews reported laboratory testing after an MBG incident at SPPG Bandengan 5. Food samples were positive for several bacteria, and a clean-water sample taken from a washing tank was reported positive for coliform bacteria. The report also said the SPPG was suspended for at least two weeks. This is closer to the water question, but it still should be handled with care: a positive water sample from a washing tank is a serious control signal; it is not, by itself, a complete causal chain for every illness.

That distinction matters. MBG Watch should not invent causality. The honest conclusion is operational: poisoning reports often do not publish a complete water/pathogen/timing chain. Therefore, a kitchen-level water and wastewater readiness record is needed before incidents, not reconstructed after them.

Rain, coastal water, and supply interruption are operating stresses

The weather signal is also specific enough to matter, but not specific enough to overstate.

On 10 August 2026, Antara reported BBMKG Region III’s warning of potential coastal flooding, or rob, in six coastal areas of Bali from 11–17 August, linked to lunar perigee and the new moon, with possible effects on ports, coastal settlements, salt ponds, and inland fisheries. Jakarta’s Dinas Sumber Daya Air separately warned that north Jakarta coastal areas could face rob from 8–13 August, with the highest tide projected at 0.57 metres above mean sea level around 20.00 WIB and vulnerable locations including Muara Angke, Muara Baru, Pasar Ikan, Ancol Marina and JIS, Tanjung Priok and Kali Baru, and Marunda. Kompas TV reported BMKG warnings for moderate to heavy rain in several provinces on 14–15 August 2026, with strong-wind warnings across others.

These reports do not say MBG kitchens were contaminated. They should not be used that way.

They do say that water stress is not hypothetical. Coastal inundation can affect access routes, drainage, standing water, ports, fishery areas, and coastal settlements. Heavy rain can affect roads, water turbidity, drains, handwashing access, delivery timing, and whether wastewater systems overflow. Supply interruption can push kitchens into informal water sourcing unless the fallback is pre-approved.

That is why the water record should be local. A national weather warning is not a kitchen decision by itself. A kitchen decision needs to know whether the SPPG’s source water, storage tank, washing station, handwashing points, drains, and IPAL are still functioning safely at that hour.

The readiness record each SPPG should keep

The least-harm path is not a broad pause. It is a visible stop-go record that lets verified kitchens keep serving and isolates only the unsafe or uninspectable point.

At minimum, each SPPG should keep and, where appropriate, publish a simple water and wastewater readiness record with these fields:

1. Source water status: piped water, well, tanker, bottled or treated supply, including the provider and whether the source changed that day.

2. Latest water-quality test: date, testing body, sample point, result, and whether the test covered the water actually used for food contact and washing, not only a remote source.

3. Treatment or fallback method: filtration, chlorination, boiling, bottled water, tanker supply, or temporary menu substitution, with the condition that triggers it.

4. Handwashing water availability: number and location of functioning handwashing points, with soap, during the production and packing window.

5. Utensil and container washing protocol: water source, detergent/sanitizing step, drying/storage condition, and whether clean and dirty flows are separated.

6. Food-contact water rule: whether water used for washing raw produce, making ice, diluting ingredients, or final rinsing must meet drinking-water quality or a stated “fit-for-purpose” standard.

7. Wastewater and IPAL status: whether IPAL is present, operating, inspected, and not overflowing; where wastewater goes when IPAL is down; and whether drains are blocked or backflowing.

8. Rain, flood, rob, and overflow exception: a short field saying whether heavy rain, floodwater, coastal inundation, sewage overflow, or access-route contamination touched the kitchen, storage area, water source, washing area, drain, or dispatch path.

9. Stop or substitute threshold: named conditions that require menu substitution, treatment escalation, delayed dispatch, batch disposal, route pause, or kitchen pause.

10. Corrective-action trail: who found the issue, what was done, who verified the fix, and when the kitchen returned to normal operation.

This record should be short enough to use. It should not become another binder that looks clean only during inspection. The test is whether a school, district health office, BGN supervisor, or parent can answer one practical question: was the water chain safe for this batch, at this kitchen, on this day?

What this adds to SLHS and IPAL

SLHS remains essential. IPAL remains essential. But both are structural controls. A certificate says a kitchen passed a standard at a point in time. A wastewater installation says a control exists. Neither automatically says the washing tank was uncontaminated today, the handwashing water was available during the packing window, the drain did not backflow after heavy rain, or the kitchen used the approved fallback after a supply interruption.

This is the same logic MBG Watch has applied to heat, power, and dispatch. A cold chain is not proven by owning a refrigerator. Heat risk is not captured by a daily temperature average. Weather-aware dispatch is not a forecast pasted into a chat group. The control has to be visible at the operating point.

Water readiness should be treated the same way.

The least-harm path

The practical standard is simple.

Keep serving where water and wastewater controls are verified.

Substitute menus, delay dispatch, treat water, replace water, or dispose of a batch where a specific control is unsafe.

Pause only the kitchen, route, or batch whose water or wastewater controls are unsafe, failed, or not inspectable.

That approach protects children without making weather an excuse for either negligence or blanket shutdown. It also protects honest kitchens. A kitchen with a clean record should not be treated the same as a kitchen whose water source changed without testing, whose washing tank is contaminated, or whose wastewater system overflowed.

What I am uncertain about

First, the public MBG incident record remains incomplete. Some reports name bacteria in food samples; fewer publish complete sample locations, timing, water test results, pathogen matches, or chain-of-custody details. That limits causal claims.

Second, public reporting does not yet show a consistent national SPPG water-quality dataset. BGN’s SLHS and IPAL enforcement is visible, but routine water-test frequency, sample points, result thresholds, and post-rain exception rules are not yet visible in the public record reviewed for this piece.

Third, local weather and coastal warnings show plausible operating stress, not direct kitchen contamination. The connection should be made through controls: source water, washing, handwashing, wastewater, drainage, and dispatch routes.

Those uncertainties are the reason to build the record, not a reason to wait for the next incident.