Management
Cases
A case is opened automatically when a student crosses a configured rule. Every case has a named owner, an auditable history, and an explicit next action. The intelligence layer can prepare work but never closes a case on a consequential outcome.
Open cases
Open attendance cases in your scope
In progress
Attendance cases actively tracked in scope
Awaiting guardian
Waiting for guardian follow-up in scope
Need a human decision
Cases requiring a human decision in scope
Case register
Showing 5 authorized attendance cases. Each row opens the underlying Student 360 record.
Case status changes are written to the audit log with the deciding user and timestamp.
Rules that opened these cases
Alerts report a measured breach. They describe what crossed a threshold and when — never why.
Triggering rules
Threshold breaches and operational exceptions detected by the intelligence layer.
Grade 8 attendance below configured threshold
Grade 8-A is at 86%, which is 6 points under the 92% school threshold configured in Rules v4.2.
AI governance in this module
Nothing below the analytics tier executes without an authorised human decision, and consequential decisions are never initiated by the intelligence layer.
Runs automatically
Cases are raised and prioritised automatically from configured rules. Severity is a rule output, never a model judgement about a child.
Requires authorisation
Follow-up messages and reminder drafts are prepared for the case owner and released only after approval.
Human decision only
Suspension, disciplinary action, fee penalties and enrolment decisions are closed by a named human. The intelligence layer cannot open, progress or resolve them.