The Code of Conduct module enables schools to manage learner behaviour through Recognitions and Violations linked to positive and negative discipline marks. This guide covers the school setup requirements and the six functions in the order they should be set up and used, with a link to the detailed article for each.
My School > Code of Conduct
Before the Code of Conduct is used, two settings must be indicated under the school setup:
Code of Conduct Disciplinary Head: indicate the staff member who acts as the disciplinary head for the Code of Conduct.
Discipline entry expiry: indicate when discipline entries expire.
Important: when discipline entries expire, the historic data is not removed — it remains on d6 and stays visible on the parents' app.
Categories group violation and recognition reasons into levels. A standard set is supplied when you start using the system.
Open the Categories function and review the default categories.
Create, edit or delete categories to match your school's discipline policy.
Confirm the Disciplinary Head and accumulated mark settings before proceeding.
Read more: Categories
The Conduct function creates the violations and recognitions and links them to the levels created in Categories. Ensure Categories is set up first.
Navigate to My School > Code of Conduct > Conduct.
Create violations with negative mark values and recognitions with positive mark values.
Link each entry to the applicable category level and save.
Read more: How to set up and manage conduct
Action Setup configures the disciplinary actions that are automatically triggered when a learner reaches a set number of violations, such as letters for detention or interviews with parents. Only violations count towards actions.
Open the Action Setup function.
Define each action and the violation threshold that triggers it.
Save the setup before any actions can be processed.
Read more: How to set up Discipline Actions
Action Processing is task-driven: tasks only appear once a learner has reached a violation threshold configured in Action Setup. It generates and prints Code of Conduct letters, with four letter types available: Notice Letter 1 to Parents, Notice of Detention, Interview with Parents, and Interview with SGB.
Open Action Processing and review the outstanding tasks.
Select the applicable learners and letter type.
Click Continue to generate the letter batch.
Read more: How to process Code of Conduct actions
Action Control is also task-driven. Tasks only appear once a learner has reached the configured number of violations and Action Processing has been completed.
Open Action Control and review the outstanding tasks.
Record the outcome of each action (for example, detention attended or interview held).
Complete the task to close it off.
Read more: How to use Discipline Action Control
My School > Code of Conduct > Discipline Letters
The Discipline Letters screen manages all letter batches created during Action Processing. You can preview, edit, delete or restore letters and batches, and redo Action Processing and Action Control if needed.
Read more: How to manage Discipline Letters
Complete the school setup first (Disciplinary Head and discipline entry expiry), then set up Categories, Conduct (violations and recognitions), and Action Setup. Action Processing, Action Control and Discipline Letters are used in that order once incidents are being recorded.
No. Only violations count towards the thresholds configured in Action Setup.
No. When discipline entries reach their expiry, the historic data remains on d6 and stays visible on the parents' app.
The system never stores a single running score. Each screen recalculates a learner's totals from the raw recorded incidents every time it is opened. See How are Code of Conduct discipline points and totals calculated?
Last updated: July 2026 | Version 1.0