Skip to content
SchoolOS
Book a demo

Modules

Everything you need to run a school — and a straight answer on what is missing.

Eight categories, every module in the product, and a label on each one. Nothing on this page is a roadmap item dressed up as a feature; where something is not built, it says so.

36
Working todayAvailable

Working today. We will show it to you on a call.

4
Partly shippedIn build

Partly shipped, or shipped and connected to your own vendor account during implementation.

19
On the roadmapPlanned

On the roadmap, not available today. We will tell you the same thing on a call.

Academics

Classes, subjects and the timetable are the spine everything else hangs from — attendance, homework and results all resolve against them.

  • Classes & sections

    Class and section structure per academic year, with teachers and students assigned to each.

  • Subjects

    Subject lists per class, including electives and the teacher who takes each one.

  • Timetable

    Period-by-period timetable per section, visible to teachers, students and parents.

  • Homework

    Homework set per subject with due dates, visible to parents the same evening.

  • Classwork

    A record of what was covered in each period, so a returning student can catch up.

  • Academic calendar

    Terms, holidays and examination windows in one calendar the whole school reads.

Examinations

Marks entered once produce the result and the report card, with the grading scheme applied centrally rather than in each teacher’s spreadsheet.

  • Examinations

    Examination schedules per class with subjects, maximum marks and dates.

  • Mark entry

    Subject teachers enter marks against their own classes and nobody else’s.

  • Grading schemes

    Grade bands defined once and applied to every result computed from them.

  • Results

    Results computed from entered marks, held until an administrator publishes them.

  • Report cards

    Printable report cards generated from published results, per student or per section.

  • Certificates

    Planned

    Bonafide, transfer and character certificates issued from the student record.

People

One record per student and one per staff member. Everything else in the system points at these rather than keeping its own copy.

  • Student records

    Admission details, guardians, class history, attendance, fees and results on one record.

  • Parents & guardians

    Guardian records linked to their children, with their own sign-in and their own view.

  • Staff records

    Teaching and non-teaching staff, with roles, subjects and the classes they take.

  • Student attendance

    Daily and period attendance, marked by the teacher who took the class.

  • Attendance reports

    Attendance by class, by student and by date range, read from live records.

  • Staff attendance

    Attendance for employees, reported alongside leave.

  • Leave

    Leave applications and approvals for staff, with balances against the year.

  • Document vault

    Planned

    Birth certificates, transfer certificates and photographs held against the student record.

  • Bulk import & promotions

    Planned

    Importing a year group from a spreadsheet, and promoting a class at year end.

  • HR & payroll

    Planned

    Salary structures, deductions and payslips computed from attendance and leave.

Admissions

Enquiries arrive on the system rather than in a notebook. The pipeline that works them through to enrolment is the next release.

  • Enquiry capture

    In build

    Enquiries recorded with the family behind them and shown on the administrator’s dashboard.

  • Admission pipeline

    Planned

    Enquiry, visit, application, offer, enrolled — the stage held on the record.

  • Follow-ups & call logs

    Planned

    Scheduled follow-ups per enquiry, listed by who owes the call and when.

  • Conversion analytics

    Planned

    Enquiry-to-enrolment conversion by source, counsellor and stage.

  • Online application forms

    Planned

    A public application form, with documents, that writes straight into the pipeline.

  • Front office & visitors

    Planned

    Visitors, calls and gate passes logged at the desk they arrive at.

  • Enrol as a student

    Creating the student record directly, which is how admissions are enrolled today.

Finance

Fee structures are defined once per class and produce every invoice, receipt and outstanding report from the same figures.

  • Fee structures

    Heads, instalments and due dates per class, with the year built from them.

  • Invoices

    Invoices raised per student from the structure that applies to their class.

  • Fee collection

    Counter collection with a numbered receipt, in cash, cheque or online, against the invoice.

  • Payments ledger

    Every payment taken, searchable, with the invoice and the person who took it.

  • Outstanding

    What is due, by class and by family, as of today rather than as of the last export.

  • Online payments

    In build

    Parents pay from their own sign-in. The flow is built; your gateway account is connected at setup.

  • Concessions

    Sibling, staff and scholarship concessions applied to the record, not to the receipt.

  • Accounting ledgers

    Planned

    Double-entry ledgers, vouchers and a trial balance inside SchoolOS.

Communication

One place to reach a class, a section or a whole school — addressed from the same records that hold the numbers.

  • Notices

    Notices published to chosen roles, classes or the whole school.

  • Messages

    Direct messages between staff and parents, kept where the conversation belongs.

  • Email delivery

    Outgoing mail through the school’s own mailbox, so it arrives from your address.

  • Push notifications

    Planned

    Notifications for attendance, fees, results and announcements.

  • SMS & WhatsApp

    In build

    The delivery pipeline and metering are built; a vendor account is connected per school.

Operations

The parts of a school that are not academic and still run on records: buses first, because that is where a parent’s attention is.

  • Transport routes & stops

    Routes with their stops and timings, and the students assigned to each.

  • Buses & drivers

    The fleet, with the driver and attendant on each vehicle.

  • Live tracking

    Vehicle position on a map while a route is running.

  • Library

    Planned

    Catalogue, issues and returns against the same student records.

  • Inventory

    Planned

    Stock, issues and consumption for uniforms, books and school supplies.

  • Events

    Planned

    School events with the audience they concern and their place in the calendar.

  • Sports

    Planned

    Teams, fixtures and participation recorded per student.

  • School website

    Planned

    A public site for the school, editable by the school, on its own domain.

  • Hostel

    Planned

    Rooms, allotment and hostel attendance for residential schools.

  • Alumni

    Planned

    Alumni records carried forward from the student record after they leave.

Administration

What a principal or a group office needs: roles, branding, an audit trail, and the dashboard that reads across the school.

  • Administrator dashboard

    Strength, attendance today, collection this month and outstanding, on one screen.

  • Roles & permissions

    Built-in roles plus custom ones, permission by permission, per school.

  • Branding

    The school’s name, logo and colours through the application and its documents.

  • Audit trail

    Who did what and when, for fee collection, result publication and permission changes.

  • Custom domain

    The application on a domain the school owns, with certificates handled for you.

  • Report builder & MIS

    Planned

    Saved, exportable reporting beyond the dashboard and the module reports.

  • Multi-campus consolidation

    In build

    Each campus separate, with group-level reporting across all of them.

Why we publish the gaps

A school choosing this software will find out what is missing in the first month of using it. Finding out now costs us some enquiries and saves both of us an implementation that was sold on something that did not exist.

If a module you need is marked planned, tell us on the call. Which schools ask for what is how the order gets decided, and we will give you a real answer about timing rather than a quarter.

Next step

Tell us which modules you actually need.

We would rather scope a demonstration around the four modules that matter to your office than walk you through all of them.

Book a demoTalk to our team

What a demonstration involves

  • Thirty to forty minutes, on a call, with your screen or ours
  • Roughly how many students and staff you have
  • What you use today for fees and attendance
  • Whether you run one campus or several

No obligation, and no pricing pressure on the first call. If SchoolOS is the wrong fit for your school we would rather say so then.