A management system that knows what PEF asks for
If you hold a PSRP licence, most of your software problem is not admissions — it is the monthly enrolment return, the deadline, the monitoring visit and the paperwork behind each one.
No card. Thirty days, the whole product.
The monthly return and the 10th
Enrolment submission with the deadline on the face of it, and a submission that keeps its own copy of what was claimed.
Nothing is claimed twice
A child who has left is a child who has left. The verified count is left empty for a person to fill rather than copied hopefully from the roll.
Findings that cannot be closed quietly
A monitoring observation needs evidence attached and a second person to verify it. The person who fixed it cannot be the one who signs it off.
Rules with dates and sources
Every rule carries where it came from and when it took effect, so a score from last term survives a rule change.
What else is in it
Attendance in two taps
A teacher marks a whole class from an entry-level phone, on a bad connection, without waiting for anything to load. Marks made offline are kept and sent when the signal comes back.
Fees, receipts and who has not paid
Fee heads, structures per class, discounts that need a second signature, and a defaulter list that is current rather than a month old.
Payroll, approved by two people
Salary components per member of staff, a run you can check before you commit it, and an approval that the person who prepared it cannot give themselves.
Marks, report cards and the timetable
Papers, marks entered class by class, grade boundaries you set, and report cards that are frozen the moment they are issued.
A parent sees their own child, and only their own child
Attendance, fees due, results once they are issued, and whatever the school has announced.
PEF compliance, if you are a partner school
The monthly enrolment return, the 10th-of-the-month deadline, dropped-out children, and a monitoring register where a finding cannot be closed without evidence and a second person.