School meal software built by Syfo
LunchLog is a software platform built by Syfo to simplify school meal ordering and administration.
- users
- 3,500+users
- schools
- 35+schools
The problem
A lot of people, a lot of information.
A school meal programme looks simple from the outside. In practice it involves parents, pupils, classes, schools and meal suppliers, all of whom need different information at different times.
Every day, someone has to know which pupils are having which meal, which class they're in, what dietary requirements apply, and what the supplier needs to prepare. Done with paper, email and spreadsheets, that coordination takes time and leaves room for mistakes — and with dietary requirements, mistakes matter.
The solution
One system for everyone involved.
LunchLog brings the whole process into one system. Parents, schools and suppliers each work from the same information, with access to the parts that are relevant to them.
Orders, pupils, classes, meal options and dietary requirements are managed centrally, so the information supplier and school staff rely on is current and consistent.
- Parents
- Schools
- Suppliers
One shared system
- Meal ordering
- Pupils
- Classes
- Meal options
- Dietary requirements
- Administrative information
- Supplier workflows
Who uses it
Parents, schools and suppliers.
Parents
Order meals for their children and keep dietary requirements up to date.
Schools
See pupils, classes and orders in one place, without compiling lists by hand.
Suppliers
Receive the order information they need to prepare and deliver meals.
What the software handles
The whole process, in one place.
- Meal ordering
- Pupils
- Classes
- Meal options
- Dietary requirements
- Administrative information
- Supplier workflows
Current scale
Used every school day.
LunchLog is used by 3,500+ people across 35+ schools.
Building a production product
Not a prototype.
LunchLog is not a prototype. It is production software that people depend on every school day — which means it has to handle everything real software has to handle.
Authentication
Secure sign-in for every user.
Different user roles
Parents, schools and suppliers each see and do different things.
Data management
Pupils, classes, meals and orders kept accurate and consistent.
Business logic
The rules of how ordering, menus and deadlines actually work.
Responsive interfaces
Designed to work on the phones parents actually use.
Production hosting
Running reliably, every school day.
Ongoing improvements
Developed continuously as schools and suppliers use it.
Have a process or idea like this?
LunchLog started as a real operational problem. Tell us about yours.