Garland Independent School District in Garland, Texas built a structured student-feedback engine into its menu planning. Chef Kevin Jenkins leads culinary development, and the district's Menu Advisory Council (MAC) meets four times per school year to turn student voices into specific menu changes.
The Menu Advisory Council
The MAC pulls together students, parents, teachers, and school nutrition staff. Meeting quarterly keeps the council close to what's actually happening on the lunch line, rather than reacting months later to stale feedback. Students share what they liked, what flopped, and what they'd want to try. Parents and teachers weigh in on what they're seeing at home and in classrooms. Nutrition staff bring the operational reality: what's feasible given equipment, procurement, and prep time.
Chef-led recipe development
With the MAC's direction in hand, Chef Jenkins designs new recipes to test. Having a chef on staff means the district can move from student feedback to a viable recipe without waiting on outside consultants. That shortens the feedback loop considerably and makes the whole process feel collaborative rather than bureaucratic.
Staff training as part of the rollout
Each new menu concept comes with a staff development session. The team learns the prep techniques, timing, and portioning needed to make the recipe work at scale. This matters. New menu items that staff aren't confident preparing tend to drift in quality or get quietly dropped after a few cycles.
What made it work
Two ingredients, consistently applied: a feedback structure students took seriously, and the operational capability (both culinary leadership and staff training) to actually act on what they heard. Menu changes stopped feeling top-down and started feeling like the natural output of a process everyone was invested in.