Menus that reach students
Menu reminders arrive during the student’s day, before they head to the mess.
Mess Intelligence
Before the meal is served,connect the people behind it.
Bring weekly menus, daily notifications, meal opt-outs and entry records together for students, mess managers and kitchen teams.
A personalised 30-minute campus walkthrough.
A connected campus workflow
- 01
Plan the week
The mess manager uploads the weekly menu.
- 02
Inform the student
7 am breakfast, 12 pm lunch and 7 pm dinner notifications.
- 03
Prepare & serve
Review participation and record meal entry through face recognition or QR.
Your university defines the rules and responsibilities.
Connected roles
- Mess managers
- Kitchen teams
- Students
- Hostel administration
What this connects
The work. The people. The complete picture.
Participation before preparation
Students can opt out of meals; the mess team reviews participation information for planning.
Meal access & choice
Record meal entry. Where multiple vendors are offered, students can choose, book and pay for their preferred mess.
Explore the workflow · Interactive examples with sample data
Meal planning board
Three inputs. One preparation count.
Start with Lunch — the declaration window is open. Use the timeline below to see how student skips and guest approvals change the live count.
Preparation count inputs
Eligible diners
2,847Declared skips
− 287Approved guests
+ 14Kitchen prepares for
2,574Declaration window open — count updating live
Each skip or guest approval updates the count in real time
Illustrative data · sample campus
Why this matters for the kitchen
Without declarations
Kitchen prepares for all eligible residents. Students on leave, skipping, or absent create waste that's invisible until after service.
With FretBox declarations
The kitchen receives a calibrated count before service. Declarations give the kitchen a better basis for preparation. Waste is measurable and reducible.
After service: the learning
Planned vs prepared vs attended — three numbers that explain operational efficiency and inform next week's menu planning.
Guest meal management
In this example, approved guest meals are included in the preparation count. Guest eligibility and approval rules follow the campus setup.
Rahul K. requests 2 guest meals for lunch
Approved→ Kitchen count updated: +2
Declaration-to-service timeline
Watch the count change as events happen
Select events below. "Student skips lunch" reduces the preparation count. "Two guests approved" increases it. The count above updates live — switch to Lunch to see it.
Live preparation count
LunchEligible diners2,847
Declared skips− 287
Approved guests+ 14
Kitchen prepares for2,574
Illustrative data · sample campus
Configured for your campus
Start with your university’s rules.
Agree the scope with the people who own the work. Fretbox supports configuration, role-specific training and adoption.
See implementation & supportBring these to the discussion
- Meal schedules and notification times
- Menu ownership, opt-out windows and meal eligibility
- Entry devices and any campus-specific mess vendor choices
Does opting out of a meal automatically create a refund?
Meal opt-out records the student’s intention not to eat and helps participation planning. Refunds or credits are not implied; any financial treatment must be agreed with the institution.
The next connection
Continue across the campus operation.
From an example to your campus
Let’s walk through your mess intelligence.
Bring the workflow, the teams involved and your existing systems.