Features
What Edunison does
Thirteen modules carrying a school's daily work, all reading the same record: the student is entered once and everything else follows. Each module is described section by section below; when you want the detail, it has a page of its own.
Students and guardians
A student is recorded once; attendance, finance, the portal and communication read the same record. The guardian side is built the way families actually are: siblings, separated parents and “who gets told” live in the system, not in somebody’s memory.
View the detail →- Enrolment, profiles and status tracking; lists narrow by branch and permission
- Guardian, sibling and household relations: one parent with several children, one child with several parents
- A who-gets-told record: communication reaches only the guardian the school marked
Front office
Everything that passes the school’s door and phone goes on record. Pre-registrations and exam applications from your own website land in the same list — no incoming request depends on who happened to see it.
View the detail →- Admission enquiries: candidate records, follow-up notes, reminders
- The web pre-registration form: families apply from your site, straight into the list
- Phone call log: who called, what they wanted, what was done
Staff
A teacher’s subject, availability and workload live on one record; the timetable reads the same one. Roles and permissions are managed here too — who sees what is written on the staff file itself.
View the detail →- Teacher and administrative staff records, active status
- Subject and class assignments: who teaches what, the timetable knows
- The availability calendar: which days and hours a teacher is free
Finance
A fee is defined once, attached to a student, split into instalments, and every collection goes on record. The administrator’s dashboard shows this month’s collections, expenses and the outstanding balance at a glance — without waiting for month end.
View the detail →- Fee schedules and the amount actually agreed per student
- Instalment plans: due dates, amounts, overdue standing — the family portal shows the same figure
- Partial payments and refunds: the record follows how collection really happens
Online payment
A parent sees the balance on the portal and pays in one tap. The money moves through your institution’s own merchant account straight to the school — never through Edunison — and Edunison never sees or stores a card number.
View the detail →- One-tap payment from the portal: the parent sees the balance, pays, the record lands
- Your own merchant account: the money goes straight to the school
- Server verification: a payment counts only after the provider’s callback is verified
Enrolment contracts
The contract wording is the institution’s; Edunison freezes it with the figures as they stood at enrolment, sends it to the guardian over a secure link, and stores the acceptance with a timestamp. The wet-signed copy is scanned and archived on the same file.
View the detail →- Your own template: you write the wording, the system fills the fields
- Frozen figures: the contract carries the amounts as sent — they never drift
- Digital acceptance: the guardian reads and accepts; name, date and address go on record
Timetable
Everything a timetable needs lives in one place: subjects, rooms, the bell schedule, curriculum load, holidays and teacher availability. The timetable is built on top, and the system refuses a clash — a rule works where a coordinator’s memory used to.
View the detail →- Class, subject and room definitions; the bell schedule and the school week
- Curriculum load: how many hours of maths 9-A takes a week, the system knows
- Teacher availability and leave feed the timetable as inputs
Attendance
The register is taken per lesson or once a day — however the school actually works. A register nobody took never counts as an absence: no child reads “absent” on a day the book was never opened. Families follow attendance from the portal.
View the detail →- Per-lesson or daily registers — never mixed, never double-counted
- Present, absent, late, excused: real states under their real names
- The attendance rate is computed only over registers actually taken
Exam management
The whole flow of scholarship and practice exams: you open a sitting, applications arrive through three channels — the office, the student portal and your own website — you record the results and take the list as Excel. On the web form the KVKK contact consent is required and the marketing consent is optional, stored with its timestamp.
View the detail →- Sitting management: date, capacity, application state (draft, open, closed)
- Three application channels: office, student portal, a public web form
- Portal and web applications wait for approval: the office always has the last word
Library
A library is not run from a notebook. The catalogue is searched by title, author, ISBN or barcode; copy counts and what is available right now sit beside every book. A loan is written to the student's record, and a book past its return date shows itself on the list.
View the detail →- A catalogue searched by title, author, ISBN or barcode — copies and availability together
- Loans belong to the student record: who has it, when it went out, when it is due
- Out, overdue and returned — one list, filtered
Inventory
From stationery to cleaning supplies, whatever the institution holds sits on one list. Every intake, issue and stocktake is recorded with who and when; a product below its minimum marks itself "low" — so the order goes out before it runs out, not after.
View the detail →- Products listed with their category; current quantity and minimum side by side
- In, out and stocktake movements — who, when and a note on every line
- Anything below its minimum is flagged; "low only" is one click
Family and student portal
The family sees everything between them and the school at one address. Who sees what is an institutional rule: guardians see the balance and the payments, students see their own timetable and register — a family’s finances are never shown to the student.
View the detail →- Guardians: balance, instalment plan, payment history and online payment
- Students: timetable, attendance record, applying to open exams
- Separated families: each parent sees only the child their own link reaches
Support tickets
Questions and requests live on record, not in the corridor. Every ticket keeps its conversation and its attachments; who asked, who answered, when it closed — all of it reads back later.
View the detail →- Open, discuss, close: one flow end to end
- The conversation lives on the ticket: context is never lost
- File attachments: screenshots and documents sit with the request
See this in your own institution
Try this module right now with the live demo accounts; a short call is all it takes for your institution’s own setup and price.