Buyer guides

    Buyer guides for schools

    The questions to ask before you choose school transport software, plan a lunchroom rollout or pick a school management system, and what a good answer looks like.

    Who it’s for: school directors, head teachers, bursars and transport managers.

    School transport software

    Choosing school transport software

    A practical guide for school leaders comparing transport records, route visibility and parent communication.

    Why it matters

    Every school office knows the morning calls: has the bus left yet, and did my child get off at the right stop? Good transport software answers those questions from a record, not from memory. It should show who boarded, where and when, show where the bus is, and tell parents before they need to call.

    What to look for

    • Start with boarding, drop-off and exception records your team needs every day.
    • Ask how the school sees the journey and what parents are told.
    • Understand which devices, connectivity and support are required.
    • Review how a record can be found after the journey ends.

    What a transport rollout involves

    1. 1Scope buses, routes, student numbers and responsibilities.
    2. 2Prepare student and parent records, including information and consent before biometric enrolment.
    3. 3Configure devices, assignments and biometric enrolment.
    4. 4Train staff and check verification, records, messages and exception procedures.
    5. 5Launch and review the operation.

    Questions to ask any supplier

    • How is each student identified when they board and get off, and what happens if that check doesn’t work?
    • Is every boarding and drop-off saved with the time and place?
    • What do parents receive, and do they need an app to get it?
    • Can we see where each bus is during a journey, separately from each student’s boarding record?
    • What equipment goes on each bus, and who looks after charging, placement, SIM and data?
    • Can staff find a student’s journey history days later, by student, bus, time or place?
    • Who controls the student data, and when is consent collected for biometric enrolment?
    • What’s included in the quote, and what is quoted separately, such as field trips, CCTV or telematics?

    What a good answer looks like

    • You’re shown a complete journey record, from boarding to drop-off, not just a bus on a map.
    • There is a supervised procedure for when verification fails, agreed with your school and walked through with staff before launch.
    • Parents get updates on any phone, or the supplier is clear about when an app is needed.
    • Devices, warranty, connectivity and support are set out in the written proposal.
    • Your school is the data controller, with a written agreement covering consent, access and retention.

    How Osprey Edge handles it

    Transport Pro verifies each student by fingerprint as they board and get off, records the time and place, and sends parents an automated SMS, so no app is needed. Live GPS shows each bus during active journeys, and journey history can be filtered by student, bus, event, time and location. Transport Core uses a lower-cost device where the bus minder records the register, and parents get in-app notifications.

    School lunch management

    Preparing a lunchroom rollout

    A practical starting point for schools organising meal eligibility, service records and reconciliation.

    Why it matters

    The bursar and caterer need to know exactly how many meals were served, to whom, and which weren’t registered. The person serving needs a student’s recorded allergies in front of them before a meal is handed over. A lunchroom rollout works when those rules are agreed before the first student reaches the counter.

    What to look for

    • Define eligibility and the service points involved.
    • Agree how staff record meals and supervised exceptions.
    • Give catering, finance and operations a shared review process.
    • Plan staff training and support before launch.

    A sensible order for your rollout

    1. 1Map the lunchroom workflow.
    2. 2Confirm student data and school rules.
    3. 3Configure devices and menus.
    4. 4Train staff.
    5. 5Run a measured pilot.
    6. 6Review a wider rollout with catering and administration.

    Questions to ask any supplier

    • How is each student checked at the counter, and what is the fallback if that check isn’t available?
    • What happens when a student isn’t registered for a meal? Can we set our own policy?
    • How are recorded allergies checked against the meal being served?
    • How are second servings and guest meals handled and recorded?
    • Are allergy blocks and exceptions kept separate from the count of meals served?
    • Can the bursar see meals by day, campus and serving point, and export them for reconciliation?
    • What notices, consent and alternatives are agreed for students who don’t use biometrics?

    What a good answer looks like

    • Not registered doesn’t automatically mean no meal. Your school chooses a grace meal, approval, an individual charge or another policy, and a served meal stays visible for review.
    • An allergy conflict blocks that meal, not the child, and your food-safety procedure takes over.
    • Every fallback still applies the meal and allergy checks.
    • Records export to Excel or CSV, and any connection to your school information system is scoped with your IT team.
    • A measured pilot is reviewed with catering and administration before a wider rollout.

    How Osprey Edge handles it

    Lunchroom Access Control checks each student at the counter against your meal register, with facial verification first, fingerprint as a backup and RFID as a fallback. Staff tag allergens on each meal, and the screen tells them not to serve a meal that conflicts with a recorded allergy. The bursar gets a daily meal ledger, with unregistered meals, repeat servings, guest meals and exceptions shown separately.

    School management system

    Choosing a school management system

    What school directors and finance teams should look for when comparing school management software.

    Why it matters

    Your school management system holds the records the bursar, administrators and teachers rely on every day: fee balances, staff records, the register and parent updates. The right system shows who is following up each balance, request and absence. The wrong one becomes another place to check.

    What to look for

    • Check that HR, accounts, fee collection and parent communication are genuine parts of the system.
    • Ask what records AI assistance can use and how answers are presented for review.
    • Look for clear roles, data preparation, training and support.
    • Choose a walkthrough that demonstrates useful questions rather than an empty text box.

    What a good rollout looks like

    1. 1Understand: agree the first module and who does what, with the people who will use it.
    2. 2Prepare: set up records from your existing data and give each role the access it needs.
    3. 3Practise: work through everyday tasks before going live, so everyone knows what happens next.

    Questions to ask any supplier

    • Can the bursar see outstanding balances by class and term, and who is following each one up?
    • Does billing stay in our control, with payments recorded by our own team?
    • Where do staff records and leave requests live, and who reviews them?
    • How is the class register recorded, and how are absences followed up?
    • Can parent updates be prepared and reviewed before they’re sent?
    • If AI is offered, is it optional? Which records does it use, and does a person review each answer before it’s shared?
    • How will our records move from our current system, and when?
    • Can we start with one module and add the rest later?

    What a good answer looks like

    • Each function is shown working with example records, not described on a slide.
    • Every balance, leave request and absence has a named owner and a recorded outcome.
    • AI, if offered, is optional, and every answer can be checked against the records it came from.
    • The move from your current system is planned around when your contract ends.
    • Set-up and staff training are included in the quote.

    How Osprey Edge handles it

    Osprey Edge School Management covers fees and billing, accounts, HR and staff, parent communication and attendance. Run it on its own or together with Student Movement Visibility, and start with the module your team needs most. AI assistance is optional: staff can ask a question, get an answer from the relevant school records and review it before sharing.

    Before you compare suppliers

    Three things to ask every supplier

    Ask to see a record

    Ask the supplier to show one example from start to finish, from the moment something is recorded to the moment someone reviews it, including what isn’t covered.

    Ask what’s included

    Before you compare prices or claims, find out what set-up, configuration, manual exceptions, equipment, connectivity and responsibilities are included, and what is quoted separately.

    Ask who controls the data

    Under Kenya’s Data Protection Act, 2019, people can ask for access to, correction or deletion of their data. With Osprey Edge, your school is the data controller and Osprey Edge is the processor, under a written agreement, and consent is completed before any biometric enrolment.

    Read how we protect student data

    Book a demo

    Bring this checklist to a demo.

    We’ll answer each question around how your school actually runs.
    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
    Interested in (optional)

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