SchoolOrbits is not a suite of products you buy separately. Attendance knows which class a student is in, fees know which term you are collecting for, and report cards know which subjects that class took — because it is all one record.
Every student gets one attendance record a day: a gate check-in and an optional check-out. Teachers can mark a register by class, or let the kiosk at the gate do it. Absences and late arrivals are visible on the dashboard the moment they happen, not at the end of the month.
A stateless recognition engine turns a face into a 512-dimension embedding and matches it against the enrolled student in milliseconds. The match threshold is tuned per school rather than hard-coded.
Set up a fee structure per class and academic year, generate invoices in bulk, and let parents pay online through your own payment gateway account. Part payments, discounts, fines and cash at the counter are all first-class, and every payment prints a receipt.
Define exam terms and the subjects each one covers, enter marks subject by subject, and let the grade scale you configured do the grading. Report cards render for a single student or an entire class, ready to print.
Bring your student list across from Excel in one upload; the importer previews every row and tells you what will fail before anything is written. Parent details sit on the student record, so siblings resolve to one guardian without any extra setup.
Add staff individually or by import, assign them as class teachers, and grant module-level permissions so a fees clerk never sees exam marks. Admin, teacher, student and guardian roles come built in.
Classes carry a grade, a section and an academic year, with an optional class teacher. Subjects are a school-wide catalogue linked to the classes that take them — so a subject list is maintained once, not per class.
Lay out a schedule per class and month: a weekly pattern, or periods pinned to dates for exam weeks and events. Start from a spreadsheet or copy last month’s — or last year’s — forward. A teacher cannot be put in two classes at once and a room cannot be double-booked, so the timetable you publish is one the school can actually run. When a teacher is away, the day view lists every period left empty and suggests who can cover it: someone who teaches that subject first, then whoever has the lightest load.
A parent signs in with the phone number on the student record and reaches every child carrying that number. Check-in and check-out alerts go out as they happen, which is usually the single feature parents notice first.
The dashboard answers the questions a principal asks before 9:30am: who is in, who is missing, which classes are short, and what came in at the fee counter. Everything behind it exports.
Every record carries a tenant, and every query is scoped to it, so two schools in the same trust never see each other. A group administrator switches between campuses from a single sign-in.
A register gets signed in bulk. A card gets handed to a friend. A face does neither — so the number on your dashboard is the number of children actually on campus, and nobody had to call out 1,200 names to get it.
Capture a few clear photos of each student, once. The school confirms parental consent before it enrols anyone.
A kiosk at the gate turns each face into a 512-dimension embedding and matches it against the enrolled student in milliseconds.
Attendance is marked, late arrivals are flagged, and the parent gets a check-in alert — before the child reaches the classroom.
Consent sits with the school. Face data of a minor is a special category under GDPR and needs verifiable parental consent under India's DPDP Act. Schools obtain it from parents before enrolling a face, as our privacy policy sets out, and card or PIN attendance is always available as a fallback.
Book a demo and we will import a sample of your student list live on the call, so you can see your own school in it before you decide.
Questions first? A 20-minute demo, and we will import a sample of your data live.
