Skip to content

BytesRaw EduSuite — User Guide

This guide explains how a school runs its day inside BytesRaw EduSuite: who does what, where each screen lives, what each button does, and what the system will refuse to let anybody do by accident.

It is written for the people who use the software — the admissions office, the registrar, the accountant, the class teacher, the transport manager, the principal. There is no code in it and no technical reference. Every page describes a process: what you start with, the steps in order, and how you know the step worked.

How to read this guide

If you are… Start here
New to the system Who uses the system, then Setting the school up
Opening a new school year Academic calendar
Handling enquiries and applications Admissions
Registering children and keeping their files Student records · Document checklists
Billing and collecting money Fees and collection
Taking the register every morning Attendance and leave
Running the buses Transport
Looking after staff records Staff and teachers
Stuck on a message the system showed you Why the system stopped you

The idea the whole system is built on

One sentence, because it explains nearly every screen you will meet:

Almost nothing belongs to a child. It belongs to a child's year at school.

A child has one permanent file — name, date of birth, nationality, admission number, guardians. Everything that happens during a year — the class they sit in, their attendance, their fees, their bus seat — belongs to that year's enrollment, which is a separate record.

That is why the system never asks you to "change a student's class for next year". You enroll the child again for the new year. Last year keeps its own class list, its own register and its own fee account, unchanged, for as long as the school keeps records. A report you print for 2026–27 in five years' time still says what it said the first time.

See Enrollment for what this means in practice.

The apps

The suite is not one giant menu. Each area of school life is its own app with its own menu:

App What it holds
School The academic calendar, the school structure, and the rule tables
Admissions Applications, interview slots, admission sources
Students Student files, enrollments, guardians, documents
Staff Teaching assignments, performance records
Fees Student fee accounts, quotations, scholarships, fee structures
Attendance Taking the register, attendance records, leave requests
Transport Bus and driver register, routes, stops, seat allocation

About these docs

This guide covers the areas of the system that are in use today. The school is being built in stages, and the guide grows with it; see What is available today for exactly what is finished and what is still coming.

Reading this guide as a website The guide is written as plain text files and published with MkDocs.
pip install -r docs/requirements.txt
mkdocs serve
Then open the address it prints. `mkdocs build` produces a folder of HTML that can be hosted anywhere or handed to the school on a USB stick.