Discipline & code of conduct
One system for students and staff — incidents, points, and what each action actually does.
Discipline records incidents about students and staff. Almost everything about the two differs — what may be done, who may read it, and where a penalty lands — so the system knows which it is dealing with rather than pretending they are the same.
A staff disciplinary record is never visible to guardians, and it is readable only by holders of conduct.staff — not by teachers generally, and not by the person who reported it, who is a witness rather than an investigator.
The subject can always read their own record and their own reply. Discipline you are not allowed to read is not a process.
Nothing about your disciplinary policy is baked into the product. In settings you define:
Categories — what kind of thing happened, per person type, each with a default severity, default points, and whether incidents in that category count toward the character score. That last flag is how "uniform" can be recorded without following a child for years while "bullying" always counts.
Severities — your own labels and ranks, not a fixed minor/moderate/major/severe.
Actions — and this is the important one. Each action declares what it *does*: whether it needs dates, needs an amount, notifies the guardian, writes attendance, which permission may decide it, how many points it carries, and whether it debars the person from sitting an exam.
> That last flag matters more than it looks. Debarment used to be guessed from the wording of an action, which meant it never actually took effect. If an action should stop somebody sitting a paper, tick that box — the exam hall reads it directly.
Policy — the response window for a show-cause, points caps and whether balances reset each term, the fine due date, and a cap on staff salary deductions as a share of pay.
Bullying is under-reported when the reporter is visible, so reports are anonymous unless you turn that off.
The reporter is always recorded. Anonymity is about what is shown, never about what is stored — otherwise there would be no recourse against a coordinated false report. Revealing an identity needs its own permission, separate from reading staff records, and every reveal is logged.
An accused person's written response is recorded against the incident. For staff this follows the ordinary show-cause → reply → decision sequence; students get the same right, for the same reason.
A student fine becomes a challan on their fee account, due after the number of days you configured.
A staff penalty is a payroll deduction — a staff member has no fee account. It is capped as a share of salary, because a deduction larger than the month's pay is a data-entry error rather than a decision, and anything over the cap waits for next month rather than being part-taken or quietly forgotten. It appears on the payslip with its reason, because the employee will ask.
Student incidents, the staff register (behind conduct.staff), incidents by category — a category with four hundred entries is usually a process problem rather than four hundred badly behaved children — merit & demerit balances, and who is debarred.