RSS2.0

Meal Zoning - An Antiquated Model

Monday, November 24, 2008

Every UMBC student with a meal plan has encountered "meal zoning." That's the little system that prevents you from using your meal at lunchtime if you had breakfast too late. Why does this policy exist? Is there any real reason for it? Why, if a student buys, say, a ten-meal plan, can't they choose when to use them?


The answer to this question is clouded by myths, two of which I would like to address here.


Myth #1: Meal plans are priced assuming that students will not use all of their purchased meals, and the meal zones are designed to facilitate missed meals.

Fact: This is not the case. Meal plans are priced according to how many meals could potentially be used. When you buy a ten meal plan, you are paying for ten meals whether you use them or not.


Myth #2:
Meal zoning is specified in the food services contract, and therefore cannot be eliminated.

Fact: The food services contract specifies a list of "minimum requirements" that the contractor must meet. At the very least they must provide meals during the kinds of zoning rules UMBC has always had. There is nothing to say that these rules could not be superseded by a superior system.


I see no reason for UMBC to cling to an outmoded system that most other schools have long since abandoned. Some progress has been made with the so-called "unlimited" meal plan, but why not go all the way and allow students to use meals whenever and wherever is most convenient?

I propose that students be able to use their meals at any time of the day, dining hall or Commons, restricted only by the number of meals they are allotted each week. A student with a ten meal plan could use five meals on Monday, one meal each on Tuesday, Wednesday,and Thursday, and two on Friday.

The infrastructure is already in place; all that would have to be done is to lift the frustrating time restrictions. There is really no strong reason not to - it's time UMBC's food services moved into the modern era.