There are things in the nursery that are redone every year from scratch, without anyone ever really deciding it. The menu is one of these: a file that someone reopens every week, manually adjusts, prints, and hangs up. Then, next to it, on the kitchen wall, there's the sheet with the names of the children who eat differently.
It works, as long as it works. But it's a repetitive job and a piece of information that lives outside the system. The seasonal menu serves to close both gaps: it is built once, covers months, and special needs stop being a footnote.
The problem is not the menu, it's recreating it every time
Anyone coordinating a 0-6 facility knows this: the effort of the menu does not lie in deciding what to eat. That is usually already established and validated with the relevant authorities. The effort lies in maintenance: copying, updating, reprinting, responding to families asking what is on the menu this week, remembering that for one child the first course is different.
It is identical work to itself and, precisely because it is repetitive, it is the first to be rushed on Friday afternoon. Building the menu as a structure, and not as a document to be rewritten, simplifies everything else.
Start with the dishes, not the menu
In Easy.School, the menu is not written: it is composed. The first step is to catalog the dishes by food category, and it is from that list that selections are made each time.
It seems like an extra step, and yet it is what saves time later. Once the dishes are in the system, composing a week becomes a selection rather than a writing task. And when a dish changes name or is removed from rotation, it is corrected in one place only.
The typical week is the building block
From the list of dishes, the weekly menu is built: the days, the meals, dish by dish. It is the building block with which everything else is constructed, so it is worth doing it calmly just once.
The practical advice is to prepare a few complete typical weeks, rather than many almost identical variations. They will serve for months, and each additional week is one more to keep updated.
The seasonal menu: a cycle that lasts until the end
This is where the change that truly alters the work comes in. The seasonal menu organizes the typical weeks into a cycle within a defined time frame: a start date, which must be a Monday, and an end date, which must be a Sunday. Within that period, you can set up to nine weeks of rotation.
Translated: you set the cycle at the beginning of the season, indicate when it ends, and the system knows what is eaten every single day until that date. There is no longer a week to prepare at the last minute for Monday. The Monday-Sunday constraint is not a formality: it serves to align the rotation with the actual weeks of the calendar, so the third week of the cycle always falls where you expect it to.
When the season changes, you do not rewrite anything: you create a new seasonal menu with different typical weeks and another time frame. The previous one remains in the system, ready for the following year.
Allergies and special diets: a menu assigned to the child
This is the part that usually lives on paper, and it is also the one where paper helps the least.
The seasonal menu in Easy.School is not generically assigned to the facility: it is associated with one or more specific children. This means that a child with a different dietary need does not have an asterisk next to their name on a hanging sheet: they have their own seasonal menu in the system, with their dishes, their cycle, and their dates.
The advantage is especially evident during ordinary moments when information usually gets lost: a substitution in the kitchen, an educator covering a shift that is not theirs, a return after a closure, a child moving to another section. In all these cases, the information does not depend on who was there yesterday, because it is written where everyone looks for it.
A necessary clarification: the management system organizes and preserves the information, it does not determine what a child should eat. Special diets, certifications for allergies and intolerances, and dietary tables remain the responsibility of the pediatrician and the relevant health authority, according to the guidelines of their region. Easy.School ensures that once that indication arrives, it is readable by anyone who needs it and does not get stuck in a handover.
The surrounding data — who issued the certification, the expiration date, useful contacts — finds its place in the child's profile, which has customized fields specifically for the information that each facility manages in its own way. And when something changes, an internal communication with a read status indicates which colleagues have actually opened it: it is not a check, it is knowing if the message has arrived.
The expected menu and the meal actually consumed
A menu, no matter how well constructed, tells what was expected. What happens at the table is another piece of information, and it is necessary.
Lunch, snack, and nap are recorded every day for each child: it is noted how much they ate, how much they slept, what was served. This is the data that comes in handy when a family asks how the week went, or when preparing for a meeting and wanting to talk about facts rather than memories.
To prevent it from becoming another burden for educators, recurring recordings are automated: the rule is set for section, day of the week, and time slot, and the entries fill in automatically. Those in the section only need to correct the exceptions, which is the only part that makes sense to do manually.
At the end of the month, the lunch report lines up the numbers: how many meals, for which enrolled children, on which days. It serves the kitchen for quantities, serves the administration for reporting, and serves the coordinator when someone asks for accountability for a period.
Bringing the menu out of the kitchen
A well-constructed menu is of little use if it stays within the management system. There are two paths, both already ready:
- The PDF of the daily menu, to be displayed at the entrance or handed out to those who ask for it. It is generated from the system menu, so it is always aligned: no more old prints from three weeks ago on the bulletin board.
- The Easy Family app, from which families can consult the menu from their phones, without having to ask for it at pick-up.
In the same logic fall the consumables: the prepaid supplies associated with the child, from diapers to snacks, which are automatically deducted with each use. Another notebook of tally marks that disappears from the changing table. And those managing multiple locations work the same way at each site, without duplicating files.
The menu is just one of the points where paper accumulates: if you are working on the overall organization, you may also find it useful to refer to the guide on how to digitize a nursery and the one on school-family communication.
In summary
Building a seasonal menu is a half-day job that saves you half an hour every week for months. The process is always the same:
- Catalog the dishes by food category: it is the list from which everything originates.
- Compose a few typical weeks, but complete.
- Create the seasonal menu with a start on Monday, end on Sunday, and up to nine weeks of rotation.
- Assign the menu to the children: those with different needs have their own, not an asterisk on a sheet.
- Record lunch, snack, and nap every day, automating recurring entries.
- Share with the daily PDF and the Easy Family app.
Easy.School is a cloud management system designed for the 0-6 segment, developed in Rome since 2010 and used by over 1000 facilities. The plan starts at 25 euros per month, or 250 euros per year, plus VAT for the first 20 children with 4 GB included; each additional child costs 0.60 euros per month and adds 0.2 GB.
If you want to see how the seasonal menu works for the children in your facility, you can try it directly: Try Easy.School for free.
