EduOS — features

Everything it handles

Written in the vocabulary a school already uses — not translated into generic software language.

Records & classroom

Admin holds the register. Teachers and students are issued logins, with a password change forced on first sign-in.

Present, late or absent, marked by the teacher who owns the class. Late counts as attended in every rate the system reports, consistently.

Set an assessment against a subject and class, enter marks, and know the dashboard averages come from those same numbers.

A teacher's dashboard, student list, grade entry and attendance cover their own classes only — enforced in the API, not just the buttons.

Upload curriculum PDFs with subject and grade, search and filter them, and read them in the browser without downloading anything.

Give it a page range, or paste a lesson, and it drafts questions from that material for the teacher to edit before anyone sits it.

Socratic by instruction — it asks rather than answers. Sessions are stored, so a student picks up where they stopped.

Attendance and grade movements, and the class that stands out, all computed by arithmetic. The model is used only when you ask it a question.

One ledger covers both directions. Status is derived from the due and paid dates, so there is no separate field to drift out of sync.

Generate one fee per student in a class in a single action, with anyone who would be billed twice skipped and reported instead.

Set a monthly fee or salary once and generate each period when you are ready. Re-running it never bills the same person twice.

Teachers see their own salary history; students and their families see the fees due. Neither can see the other's.