When the Meal Cannot Be the Same: The Special-Diet and Referral Record MBG Needs

MBG Watch · 2026-09-26

The premise

MBG is built as a mass feeding program. That is not a flaw by itself. A national public meal has to be planned in batches, cooked in kitchens, moved on routes, and checked against standards that can be repeated.

The problem begins when one standard tray is treated as proof that every body has been safely included.

BGN’s public record now shows three things at once. First, MBG menus are described as built around the Ministry of Health’s Angka Kecukupan Gizi standard, with macro- and micronutrient balance, local food adaptation, nutritionist involvement, and periodic evaluation. Second, BGN has published operational detail showing different AKG percentages and energy references by school level and by the 3B group — pregnant women, breastfeeding mothers, and toddlers. Third, MBG is no longer only a school-lunch problem. BGN’s own technical page for mothers and non-PAUD toddlers says success depends on accurate beneficiary data from BKKBN, periodic updating, cadres, community-level stakeholders, monitoring and evaluation, and openness to feedback.

Those are necessary foundations. They do not yet answer the special-diet question.

A pregnant woman with a clinical restriction, a toddler with a suspected allergy, a child whose disability affects swallowing or meal access, a beneficiary whose religion forbids an ingredient, a student with acute illness, and a child who needs referral after repeated symptoms are not asking MBG to become personalized medicine. They are asking the program not to confuse average nutrition design with safe inclusion.

This is the narrow crossing with the wider health-care shift toward more model-guided and personal care. MBG should not borrow the glamour of personalization. It should borrow the discipline of exception handling: who noticed, what category of exception applied, what safe action was taken, who was responsible, and how the case moved back into ordinary service or into health care.

Earlier MBG Watch pieces have asked for adjacent records: the measurement loop for mothers, toddlers, and 3T nutrition; the travel record when care does not move through schools; the warning against proving MBG through metabolic sensing; disaggregated validation rather than aggregate claims; language and literacy controls; and a parent-understandable menu record. This piece is the missing joint between them. If the meal cannot be the same, the public does not need the child’s diagnosis. It needs proof that the program has a safe, private, timely way to act.

What the evidence supports

The public evidence supports a basic claim: BGN is building visibility around menus, nutrient standards, production reporting, complaints, and the 3B route.

BGN’s January 2026 menu statement says MBG menus are required to refer to national AKG standards under the 2026 MBG governance technical instruction. It says menus consider carbohydrates, protein, fat, vitamins, and minerals; that target groups include students, pregnant women, breastfeeding mothers, and toddlers; that local food may be used if it still meets the nutritional standard; and that nutrition experts and periodic evaluation are part of quality control.

A February 2026 BGN release from an SPPG in Agam adds operational detail. It says meals undergo organoleptic checks — texture, taste, and color — before distribution, samples are kept cold for 2x24 hours for possible further checking, and energy references vary by group: 328 kcal for TK/PAUD at 20–25 percent AKG, 368.8 kcal for lower primary, 531 kcal for upper primary, 719 kcal for junior secondary, 762.5 kcal for senior secondary, 818 kcal for pregnant and breastfeeding women, and 342 kcal for toddlers.

For 3B beneficiaries, BGN’s technical-document page says the program for pregnant women, breastfeeding mothers, and non-PAUD toddlers depends on collaboration between BGN, BKKBN, the Ministry of Health, local government, cadres, and community stakeholders. It names accurate and periodically updated beneficiary data as the basis of targeting, and says monitoring, evaluation, field findings, and feedback should feed improvement.

For menu visibility, BGN has launched Radar MBG. Its portal asks the user to choose province, district/city, subdistrict, village, and institution to see “menu hari ini” and the SPPG provider. BGN’s August 2026 press release says Radar MBG is meant to let parents, schools, local governments, agencies, and the public see schools receiving MBG, the menu served, nutrient content, food photos, and the producing SPPG. It also says about 85 percent of SPPGs had filled digital reporting at that point, with BGN pushing all kitchens to report production more consistently.

For complaints, BGN’s SAGI 127 release says Call Center 127 operates 24 hours as a complaint and nutrition-consultation channel for students, parents, schools, catering providers, and the public. BGN’s own site also points users to SP4N-LAPOR and a WhatsApp contact.

This is enough to make a special-diet record possible. It is not enough to show that one exists.

The public pages I retrieved did not show a clear national record for allergy declarations, religious or clinical substitutions, disability-related meal modifications, temporary exclusions from a meal, referral triggers, or how schools, posyandu, puskesmas, parents, cadres, kitchens, and complaint channels coordinate when one beneficiary cannot safely receive the standard item.

That gap matters because food allergy and special-diet management is not theoretical. Indonesia’s Ministry of Health page on food allergy in children describes food allergy as an adverse health effect from a specific immune response, notes that perceived food allergy is not the same as confirmed allergy, and lists major allergen groups including milk, egg, peanut, tree nuts, shellfish, fish, wheat, and soy. The FDA’s public food-allergy page makes the same operational point from another system: food allergic reactions can range from mild symptoms to life-threatening anaphylaxis; avoiding the food and managing allergen hazards, ingredient labeling, cross-contact, and undeclared allergens are central controls.

The lesson for MBG is plain. A special-diet system cannot be built only around calories and menu photos. It needs the controls that stop the wrong food reaching the wrong person.

What ordinary menu variation can handle

Some differences belong inside ordinary menu planning.

Ordinary variation can handle:

• local ingredient substitution that still meets the nutrition standard;
• age- or target-group energy differences already reflected in the menu standard;
• routine menu rotation to prevent monotony;
• culturally appropriate menu planning where the whole service population shares the constraint;
• clear parent-readable descriptions of the menu, nutrient content, and producing SPPG.

Radar MBG is well suited to this layer. It can show what was planned, what kitchen produced it, what nutrient standard it claims to meet, and what the meal looked like.

But ordinary variation is not enough when the risk sits in the individual relationship between a beneficiary and an ingredient, texture, clinical condition, disability, or acute symptom. The same peanut, egg, milk, fish, wheat, soy, shellfish, or texture may be safe for most children and unsafe for one. A public menu photo does not solve that.

What requires a safe substitution

A safe substitution is needed when the beneficiary can still participate in the meal service, but one item or feature must change.

The record should not publish names or diagnoses. It should publish aggregate and operational proof that substitutions exist and are governed.

At minimum, each SPPG or institution-level public record should show:

• the number of approved substitutions that day or week;
• the reason category, not the diagnosis: allergy or intolerance; medical dietary restriction; pregnancy or lactation need; toddler texture or feeding need; disability-related access need; religious or ethical dietary constraint; temporary illness; other approved category;
• whether the substitution stayed within the nutritional target or required a documented exception;
• the responsible actor who approved the category: parent/guardian declaration, school health staff, puskesmas or posyandu route, cadre, nutritionist, or other defined officer;
• the safe alternative used, at category level: protein replacement, texture modification, non-dairy option, halal-compliant alternative, allergen-free packed item, or meal withheld pending referral;
• the handoff point: kitchen, school, cadre, parent, posyandu, puskesmas, or complaint channel.

USDA’s school-meal disability guidance is from a different legal system, but it is useful here because it separates the practical layers MBG also needs: meal modifications, medical statements, records management, declining or accepting requests, reimbursement or cost handling, food allergies, portion sizes, meal-service modifications, tracking dietary intake, procedural safeguards, and training. MBG does not need to import U.S. law. It needs the operational insight that substitution is not a favor by a kitchen worker on a busy morning. It is a controlled service pathway.

What requires referral or exclusion from a particular meal

Some cases should not be handled by improvising a replacement tray.

Referral or temporary exclusion is needed when:

• a child or mother develops symptoms after eating and the cause is unclear;
• the family reports severe allergy or prior anaphylaxis and the kitchen cannot verify cross-contact controls;
• the required texture or feeding support is beyond what the meal route can safely provide;
• pregnancy, breastfeeding, toddler health, disability, or acute illness creates a clinical question beyond menu planning;
• repeated complaints or missed meals suggest the beneficiary is not being safely reached;
• the requested substitution would make the meal nutritionally inadequate unless health staff approve a plan.

This is where MBG’s school and 3B routes have to meet Indonesia’s existing care pathways. Schools, UKS functions, posyandu, puskesmas, BKKBN-linked data updating, cadres, and parents do not need a public diagnostic registry. They need a simple referral record: what category triggered referral, who was notified, how fast, whether the beneficiary was protected from the unsafe item in the meantime, and whether the case returned to ordinary service, a substitution plan, or continued clinical follow-up.

A parent calling SAGI 127 because a child repeatedly cannot eat the meal should not be told only that the menu meets AKG. A kitchen receiving a list of allergies should not have to guess whether a parent’s note, a school health note, or puskesmas confirmation is enough. A cadre carrying food to a 3B beneficiary should not become the private holder of sensitive health information without a boundary.

The public record should make the system legible without exposing the person.

What not to publish

BGN should not publish child-level or mother-level special-diet profiles.

This is not only a matter of taste. Indonesia’s Personal Data Protection Law framework treats health information and children’s data as specific personal data. A special-diet system that publicly exposes names, diagnoses, disability details, pregnancy risks, religious identity, or household vulnerabilities would solve one accountability problem by creating another.

The public should not see:

• a named child’s allergy;
• a pregnant woman’s clinical condition;
• a disability-linked feeding need attached to a person;
• a household’s religious or ethical dietary record;
• complaint narratives that identify a beneficiary;
• geolocated micro-records that make a small group identifiable.

The safe public layer is aggregated, categorical, and operational. The private care layer can hold the identifiable information needed to protect the person, but access should be role-based and limited to those who need it: parent or guardian, school or cadre, health worker, SPPG nutritionist, complaint handler, and the relevant program officer.

MBG should also avoid a second mistake: claiming individualized nutrition outcomes because it can record exceptions. A substitution ledger does not prove a child’s nutritional status improved. It proves that the program did not knowingly serve an unsafe or unusable meal without a response. Outcome proof still belongs in the measurement loop, disaggregated validation, and referral follow-up record.

The least-harm record

The least-harm path is not a personalized MBG. It is an exception-and-referral ledger with a privacy wall.

The public version should be published at the SPPG, institution, district, and national levels. It should be easy enough for parents to understand and structured enough for auditors to test.

The core fields should be:

1. Menu exposure

   • planned menu;
   • known major allergen categories present;
   • texture form where relevant for toddlers or disability access;
   • SPPG provider;
   • time the menu became visible to schools, parents, cadres, and complaint channels.

2. Exception category

   • ordinary menu variation;
   • approved safe substitution;
   • meal withheld or excluded for safety;
   • referred to health worker;
   • unresolved or awaiting confirmation.

3. Reason category

   • allergy or intolerance;
   • clinical dietary restriction;
   • pregnancy, lactation, or toddler feeding need;
   • disability-related access or texture need;
   • religious or dietary constraint;
   • acute illness;
   • complaint-triggered review;
   • other, with controlled internal detail.

4. Responsible actor

   • SPPG nutritionist;
   • school or UKS contact;
   • parent or guardian;
   • cadre;
   • posyandu or puskesmas contact;
   • district program officer;
   • SAGI 127 or SP4N-LAPOR complaint handler.

5. Action taken

   • safe substitution delivered;
   • alternative protein or ingredient used;
   • texture modified;
   • meal held pending confirmation;
   • referral issued;
   • parent notified;
   • complaint closed with correction;
   • recurrence flagged.

6. Timeliness

   • when the exception was known;
   • whether the kitchen knew before cooking, before packing, before delivery, or only after service;
   • whether the parent, school, cadre, or health worker received notice in time to act.

7. Correction loop

   • whether the same exception recurred;
   • whether the menu record was corrected;
   • whether the SPPG changed procurement, labeling, packing, or handoff steps;
   • whether the beneficiary missed the meal and whether a safe replacement was provided.

This ledger would give MBG Watch, parents, schools, local governments, health workers, and BGN a more honest denominator. Not only how many meals were served, but how many meals could not be safely served as planned — and whether the system knew what to do.

The public claim BGN could make

If BGN builds this record, the defensible claim is modest and valuable:

MBG cannot make every meal individually designed. It can make every known exception traceable, private, and acted on before harm is normalized.

That claim would be stronger than a personalization slogan. It would also be more protective than silence.

The test is simple. On any given meal day, a parent should be able to see the menu early enough to recognize a problem. A school or cadre should know where to send the warning. A kitchen should know whether it is allowed to substitute, must withhold, or must refer. A puskesmas or posyandu route should receive the case when it becomes clinical. A complaint channel should be able to see whether the fix happened. The public should see the categories and counts. The person’s private health information should stay private.

That is not a large-data dream. It is a basic safety record.

What remains unknown

The evidence retrieved for this piece is strong on BGN’s stated menu standards, group expansion, Radar MBG visibility, production reporting ambitions, sample retention, organoleptic checks, 3B continuity, and complaint channels.

It is thin on the exception layer.

I did not find, in the public sources retrieved, a national special-diet protocol showing how MBG handles allergies, religious constraints, disability-related meal access, toddler texture modifications, acute illness, clinical dietary restrictions, or health-worker referrals. I also did not find a public aggregate report showing how many substitutions, exclusions, or referrals have occurred, how fast they were handled, or whether complaint channels are linked back to kitchen practice.

That does not prove the system is absent. It means the public cannot yet see it.

Until that record exists, MBG should be careful with two claims. It should not claim individualized nutrition outcomes from a standardized meal. And it should not claim safe inclusion from aggregate meal counts alone.

The middle path is available: publish the special-diet and referral record, keep the person-level data private, and make the one-size meal accountable for the moments when one size is not safe.