Skip to Content

School ERP — Discipline

by
Odoo

$ 199.00

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 3424
Technical Name do_school_discipline
LicenseOPL-1
Websitehttp://doincredible.com
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 3424
Technical Name do_school_discipline
LicenseOPL-1
Websitehttp://doincredible.com
School ERP — Discipline
Odoo 19 · School ERP Suite

School ERP — Discipline

Record student discipline incidents and track them through to resolution — classified by type and severity, with a clear audit trail and guardian visibility.

Incidents Resolution Workflow History Guardian Notice
Overview

Consistent, auditable handling of behaviour issues

The Discipline module records and follows up on student behaviour incidents in a consistent, auditable way. Each incident captures its type, severity and action taken, then moves through an open-to-resolved workflow with full chatter history. It links directly to student records, surfaces incidents to guardians, supports multiple companies and is country-neutral.

Schools get a single, dependable place to log what happened, who reported it and what action followed — turning ad-hoc notes into structured, searchable records that staff and parents can trust.

What you get

Key features

Incident Records

Capture each incident against a student with date, description and the reporting user recorded automatically.

Type & Severity

Classify by type — misconduct, unexcused absence, bullying, property damage or other — and by low, medium or high severity.

Status Workflow

Move incidents through Open, Action Taken and Resolved with dedicated action buttons on the form.

Audit Trail

Field change tracking and chatter record who reported what and what action followed, end to end.

Priority Flag

Mark urgent cases as high priority so they surface for quick triage and fast follow-up.

Analytical Views

List, form, kanban, pivot and graph views for day-to-day handling and trend analysis by type and severity.

A look inside

Screenshots

Discipline incidents board
Discipline incidents board
Incident tracked to resolution
Incident tracked to resolution
Step by step

How it works

1
Record a new incident against the student involved, with the date and a clear description of what happened.
2
Set the incident type and severity, and flag it as high priority if the case needs urgent attention.
3
Note the action taken and move the incident to Action Taken; guardians can see the incident on the student record.
4
Resolve the incident once it is closed out — the full history stays in chatter for the audit trail.
5
Review trends by type and severity through the pivot and graph views to spot recurring patterns.
Who can do what

User roles

Role Access
Teacher Read, create and edit discipline incidents (cannot delete).
Principal Full access to create, edit and delete incidents.
School Administrator Full access to create, edit and delete incidents.
Student Read-only visibility of their own incidents.
Parent / Guardian Read-only visibility of their child's incidents.
Fits the suite

Integration

Student records

Links directly to students from the School ERP Student module, with a discipline smart button on the student form for cross-navigation.

Parent portal

Builds on the School ERP Parent module so guardians get read-only visibility of their child's incidents.

Mail & chatter

Uses Odoo mail for field change tracking and chatter, giving every incident a complete activity history.

Under the hood

Technical information

Odoo Version: 19.0 (Community)

Models: do.discipline.incident

Dependencies: do_school_student · do_school_parent

License: LGPL-3

Part of the School Management ERP Suite · Odoo 19 Community · by DO Incredible

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.