The modern OS for ambitious schools

Every term, every shilling, every mark, in one system. YoShule runs admissions, fees, payroll, timetabling and NLSC assessment for Ugandan schools, on one record per student and one login per member of staff.

  • Student records
  • Admissions
  • Fees & invoicing
  • Payments
  • Arrears
  • Payroll
  • Timetabling
  • Roll call
  • Marks entry
  • Report cards
  • Class progression
  • Requirements
  • Discipline
  • Sick bay
  • Library
  • Inventory
  • Notices
  • Parent portal

Every module shares one record

The reason a school ends up with five spreadsheets is that its systems do not talk. Here, a student admitted in the morning is invoiceable by the afternoon and on a marksheet by the following week, without being entered twice.

Fees that reconcile themselves

Per-term fee structures generate invoices for every enrolled student. Payments post against them as they land, and arrears are a live figure rather than a month-end reconstruction.

Marks to report cards

Subjects, papers and grading scales defined once. Marks entered on a keyboard-navigable grid, report cards generated for a whole class in one pass.

Conflict-free timetables

No teacher, class or venue is ever double-booked.

Roll call in seconds

Scheduled or impromptu, with the full attendance history behind it.

Admissions through to enrollment

Applicants apply on your own portal, you review and admit, and an admitted applicant becomes an enrolled student without anyone retyping a name.

Payroll and HR on the same record

Contracts, allowances, deductions and advances resolve into payslips for the same staff member who appears on the timetable.

One term, start to finish

Nothing here asks a school to change how it works. It follows the term you already run, and removes the retyping between each stage of it.

  1. 01Before the term

    Set the term up once

    Classes, streams, subjects and the fee structure are defined for the term. Everything downstream reads from that one definition: invoices, timetables, marksheets.

  2. 02Intake

    Admit without retyping

    Applications arrive on your school's own portal. Admitting an applicant carries the record straight into enrollment, so the student exists once, not three times.

  3. 03Week one

    Invoice the whole class at once

    Enrolled students are invoiced against the term's fee structure. Payments record against the invoice, and the arrears figure moves the moment they do.

  4. 04Through the term

    Teach against a timetable that holds

    Teachers see their own periods, take roll call from them, and enter marks on a grid built for a keyboard rather than a mouse.

  5. 05End of term

    Close the term, then move it forward

    Report cards generate in bulk against the grading scale. Once the term is marked complete, results reach guardians on the portal and the class progresses.

Everyone sees their own school

Access follows the role, not a shared password. A teacher opens their periods and their classes; the bursar opens the ledger; nobody browses what is not theirs.

Also covered:HRMatronGuardians

Put the whole school on one record

Set your school up, invite your staff by role, and run the term. No migration project and no spreadsheets to keep in step.