Lunchroom Access Control

    Every meal accounted for.

    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.

    Example Serving point 1

    Student verification

    Face · fingerprint · RFID fallback

    Decision for the server

    Meal, allergy and serving rule

    Amina K. · Pilau and kachumbari · no allergy conflict SERVE

    What your school gets

    Meal numbers that add up, with allergies checked at the counter.

    1

    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.

    2

    Unregistered meals visible, not lost

    A meal served to an unregistered student stays visible for the bursar to review. Billing stays in your school’s control.

    3

    Allergy checks before every plate

    Each student’s recorded allergies are checked against the meal before it’s handed over.

    Records and reporting

    Every serving in one ledger the bursar can reconcile.

    Blocked meals are recorded as events, not meals served, so they don’t count towards your serving totals.

    Example

    Example meal ledger
    TimeStudent or passCampus · serving pointMealStatusServingOutcome
    12:04Amina K.North Campus · Point 1Pilau and kachumbariRegisteredFirstServed
    12:11Zawadi N.North Campus · Point 1Groundnut stew and riceRegisteredFirstBlocked · allergy
    12:18Baraka M.North Campus · Point 2Pilau and kachumbariUnregisteredExceptionServed · review
    12:26V-204North Campus · Point 2Pilau and kachumbariGuest passGuestServed
    12:31Kiprono R.North Campus · Point 1Pilau and kachumbariRegisteredRepeatPending policy

    Scroll sideways to see every column.

    3

    meals served

    1

    blocked for an allergy conflict

    1

    awaiting the seconds policy

    Reports for finance, catering and operations

    • Meals by day, campus and serving point
    • Registered and unregistered meals
    • First and repeat servings
    • Guest meals and exceptions
    • Allergy blocks
    • Each student’s meal history

    Export to Excel or CSV for reconciliation

    Connecting to your school information system is scoped with your IT team.

    Allergy checks at the counter

    Allergy checks before every meal is served.

    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.

    • Menus are scheduled for each serving point.
    • Permission to serve an unregistered meal can’t override an allergy block.

    How serving works

    Staff know what to serve before anything is handed over.

    1. 1

      Verify the student or approved guest

    2. 2

      Check the meal, allergies and earlier servings

    3. 3

      Show the person serving a decision

    4. 4

      Record the outcome for review

    Six lunchtime situations, one clear answer each time

    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

    Student or guest
    Amina K. · registered lunch entitlement
    Verification
    Face match complete
    Selected meal
    Pilau and kachumbari
    Rule applied
    No recorded allergy conflict

    First serving. Hand the meal to the student.

    Recorded as: Served · first serving

    Fallbacks, second servings and guests, handled your way

    • Identification: fingerprint backs up face. RFID is a credential fallback, not biometric proof of identity. Your school agrees how each fallback is supervised.
    • Second servings: an earlier serving is recognised, and an authorised operator approves or declines.
    • Guests and visitors: an approved, time-limited QR pass, with guest meals logged separately and no biometric enrolment.
    • Verification unavailable: pending isn’t a pass. Whichever fallback is used, the same meal and allergy checks apply and the outcome is recorded.

    Unregistered meals

    Your policy for unregistered meals, applied at the counter.

    Not registered doesn’t automatically mean no meal. If the meal is served, it stays visible against the student for the bursar to review.
    • Allow a grace meal, require approval, record an individual charge, decline, or apply another agreed policy.
    • An optional email to parents about an unregistered meal, if your school switches it on.
    • Billing stays in your school’s control.

    Rollout

    Start with a pilot, then extend it across the school.

    1. 1

      Map the workflow

      Your serving points, meal rules and reporting needs.

    2. 2

      Confirm data and rules

      Student data, allergy records and your serving policies.

    3. 3

      Set up devices and menus

      Configure the devices, schedule menus and tag allergens.

    4. 4

      Train staff

      Including the fallback and food-safety procedures.

    5. 5

      Pilot and review

      Reviewed with catering and the office, then we decide together how to extend it.

    Student data responsibilities

    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 data

    Start 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 guide

    FAQ

    School lunchroom questions

    What if a student isn’t registered for lunch?

    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.

    How do allergy checks work?

    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.

    How are students identified at the counter?

    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.

    Can it handle second servings and visitors?

    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.

    Can parents be emailed about an unregistered meal?

    Yes, if your school switches that policy on. It’s optional.

    Can the bursar export the records?

    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

    Give your bursar a meal count that adds up.

    Show us your serving points, meal rules and reporting needs. We’ll help define a focused pilot for your school.
    1. 1We get in touchBy phone or WhatsApp, to understand your school and what you want to see.
    2. 2A demo around your schoolYour routes, your lunchroom or your gate, not a generic tour.
    3. 3A written quoteAgreed before anything is installed.
    I’d like

    Prefer to talk? WhatsApp us or call +254 711 716 622