Exact meal counts, day by day
Every student is checked against your meal register, so you know how many meals were served each day, and to whom.
Lunchroom Access Control
Lunchroom Access Control checks every student at the counter against your meal register, so the bursar and caterer know exactly how many meals were served, to whom, and which weren’t registered. It also checks recorded allergies against the meal before it’s handed over.
Who it’s for: bursars, kitchen teams, lunchroom supervisors, head teachers and parents.
Facial verification first. Fingerprint backup. RFID fallback.
See how serving works, step by step.
Student verification
Face · fingerprint · RFID fallback
Decision for the server
Meal, allergy and serving rule
What your school gets
Every student is checked against your meal register, so you know how many meals were served each day, and to whom.
A meal served to an unregistered student stays visible for the bursar to review. Billing stays in your school’s control.
Each student’s recorded allergies are checked against the meal before it’s handed over.
Records and reporting
Example
| Time | Student or pass | Campus · serving point | Meal | Status | Serving | Outcome |
|---|---|---|---|---|---|---|
| 12:04 | Amina K. | North Campus · Point 1 | Pilau and kachumbari | Registered | First | Served |
| 12:11 | Zawadi N. | North Campus · Point 1 | Groundnut stew and rice | Registered | First | Blocked · allergy |
| 12:18 | Baraka M. | North Campus · Point 2 | Pilau and kachumbari | Unregistered | Exception | Served · review |
| 12:26 | V-204 | North Campus · Point 2 | Pilau and kachumbari | Guest pass | Guest | Served |
| 12:31 | Kiprono R. | North Campus · Point 1 | Pilau and kachumbari | Registered | Repeat | Pending policy |
Scroll sideways to see every column.
3
meals served
1
blocked for an allergy conflict
1
awaiting the seconds policy
Export to Excel or CSV for reconciliation
Connecting to your school information system is scoped with your IT team.
Allergy checks at the counter
Staff schedule menus and tag allergens. When a student’s recorded allergy conflicts with the selected meal, the screen tells staff not to serve it, and your food-safety procedure takes over. The block applies to that meal, not to the child.
How serving works
Verify the student or approved guest
Check the meal, allergies and earlier servings
Show the person serving a decision
Record the outcome for review
Select a situation to see what staff are told and what is recorded.
Example
Registered student: SERVE. First serving. Hand the meal to the student.
Selected situation
Registered student
SERVE
First serving. Hand the meal to the student.
Recorded as: Served · first serving
Unregistered meals
Rollout
Your serving points, meal rules and reporting needs.
Student data, allergy records and your serving policies.
Configure the devices, schedule menus and tag allergens.
Including the fallback and food-safety procedures.
Reviewed with catering and the office, then we decide together how to extend it.
Your school is the data controller and Osprey Edge is the data processor. Before launch, we agree notices, consent and permissions; retention and authorised access; alternatives for students who don’t take part; fallback and food-safety procedures; and each side’s data responsibilities.
Read how we protect student dataStart with Lunchroom Access Control as a single module, with a written quote before anything is installed. See packages
Founding schools work directly with our team on their lunchroom, and help shape what we build next. Become a founding school
Read the lunchroom guideFAQ
Your school chooses the policy: a grace meal, approval, an individual charge or another agreed route. If the meal is served, it stays visible against the student for the bursar to review.
Staff tag allergens on each meal. When a student’s recorded allergy conflicts with the selected meal, the screen tells staff not to serve it and your food-safety procedure takes over. The block applies to that meal, not to the child.
Facial verification first, with fingerprint as a backup and RFID as a fallback. Your school agrees how each fallback is supervised, and the meal and allergy checks still apply.
Yes. A previous serving is recognised and sent to an authorised operator to approve or decline. Visitors can use a time-limited pass, and guest meals are logged separately without biometric enrolment.
Yes, if your school switches that policy on. It’s optional.
Yes. Meal records export to Excel or CSV for review and reconciliation. Connecting to your school information system is scoped with your IT team.
Book a demo