Menu system · reviewed 29 July 2026 · build 7c00f13
Review & redesign proposal
We reviewed the Food4Life menu, nutrition, production and inventory system end to end,
then designed a replacement on Taher’s own Food4Life brand. Everything here is
browsable — the written findings, the running screens, and the design system underneath.
30 / 9,234
ingredients carry the crediting data every compliance number depends on
19
weekly USDA metrics tracked — presented today as three chips
0
mobile surfaces, for work done standing in a walk-in freezer
What we propose, in three moves
Document 3 sets these out in full. Everything else follows from them.
Make the week the thing you work on
Almost everything in this domain is keyed by date, yet one week of one school is scattered
across five screens today. It should be one surface: each day’s plan, what was
produced, and what was counted.
Make compliance prescriptive
Today the system says “weekly grains 1.25 of 5.00” and stops. It should say which
recipe on which day closes the gap — and what that does to sodium.
Fix the catalogue, in the right order
Nobody needs to credit 9,234 ingredients. They need the ones that reach a tray. Triaged that
way, the quiet emergency underneath everything else becomes a finite job.
Start anywhere
Three ways in, depending on what you want.
Scope. Everything here concerns the
Food4Life menu system —
menus, nutrition, compliance, production records and inventory. Taher’s separate legacy
financial platform,
WBA, is a different application; the two share domain
vocabulary but not a codebase, and this review found no shared database. Our May 2026 WBA
assessments were delivered and are
archived — WBA is being rebuilt
rather than remediated.