Conduct cases that close on time, land the same way twice, and survive an appeal.
Student conduct and disciplinary case management built around the three things an institution is judged on: a fair process, a timely decision, and a record that holds up. Reports arrive at the right desk, sanctions come from your own policy, and every action is time-stamped as it happens.
The problem
A conduct case is an institutional risk living in someone's inbox.
Most institutions run discipline on goodwill: a form that lands in a shared mailbox, a folder of statements on someone's drive, a spreadsheet of sanctions nobody outside the office can see. It works until a decision is challenged. Then the question is not what you decided, it is what you can show.
Three failures repeat. Reports are routed by memory, so a serious case can sit for a week while a minor one is handled the same day. Outcomes are inconsistent, because the sanction depends on who heard the case. And the file is scattered, so an appeal is defended from email threads rather than a record.
What changes
Four outcomes, and the mechanism behind each one.
A conduct system earns its place by changing four things: how fast a case reaches the right person, how consistently it is decided, what you can prove afterwards, and what you learn from the pattern. Features are underneath, named, so you can check the claim.
The right desk, the same day.
Severity and category are set as the report is filed, so triage assigns the case to the reviewer or committee that owns it. Reassignment is a tracked act, not a forwarded email.
The same offence, the same outcome.
Sanctions are selected from a repository your policy defines and tied to incident type and severity, so two committees hearing similar cases reach comparable decisions. Compliance and appeal eligibility are tracked on the sanction, not remembered.
An appeal you can answer.
Findings, interviews, evidence, notifications and the decision sit in one file, each entry time-stamped and access-controlled. When a case is challenged, the panel reads the same record the decision was made on.
Patterns caught before they repeat.
Closed cases become data: frequency by category, resolution time, sanction distribution, repeat involvement. Student affairs can act on a hotspot in one hall or one module instead of discovering it in an annual review.
The operating model
Fairness is a design choice, not a good intention.
Four choices turn discipline from an office practice into an operating layer: policy configured once, intake that classifies, an investigation that records itself, and a closure that produces evidence.
Policy is configured, not remembered
Misconduct categories, classifications within them and the sanction repository are set up to your regulations. Every case is then classified and decided from the same scheme, across departments and campuses.
Intake decides urgency, not the queue
Reports carry severity, category and the people involved from the moment they are filed, so triage routes on risk. Confidential and anonymous submissions are supported without opening the record to everyone.
The record is written as work happens
Findings, interviews, uploads, messages and reassignments are logged in the workflow at the time they occur. Nothing is reconstructed after the fact, which is what makes the file defensible.
Closure produces evidence
A closed case yields a system-audited lifecycle record, an exportable report for audit or accreditation, and analytics on frequency, type and resolution time.
What it does
Five outcomes. The features that deliver them.
Every capability here maps to something a dean of students can be held to. Pick an outcome to see exactly what sits inside it.
Reports arrive complete, classified and assigned to the person who owns them.
- Guided incident reporting form with structured fields and attachments
- Confidential reporting mode for anonymous or restricted submissions
- Multi-party involvement mapping: complainant, respondent, witness
- Incident intake with severity, urgency and category triage
- Automatic assignment to the responsible reviewer or committee
- Dynamic case reassignment with configurable rules and audit trail
One policy scheme, applied by every committee that hears a case.
- Misconduct category configuration for academic and behavioural violations
- Incident classification configuration for nature and severity
- Conduct sanction repository defined by the institution
- Sanctions tied to incident type and severity
- Sanction enforcement with compliance and timeline tracking
- Appeal eligibility recorded on the outcome
The case file is built as the investigation runs, not afterwards.
- Investigation workflow management with progress and findings
- Interview notes and internal communications logged in the case
- Evidence vault for files, transcripts and review notes
- Time-stamped uploads with role-based access controls
- Permission and access governance by institutional role
- System activity audit log of every action taken on the case
Contextual, recorded communication instead of phone calls and rumour.
- Case communication engine for updates and decision notifications
- Email and portal alerts, with delivery recorded on the case
- Secure stakeholder collaboration hub for questions and clarifications
- Role-aware visibility so parties see only what concerns them
- Post-resolution feedback collection from complainant or respondent
What happened, how long it took, and what it tells you.
- Resolution and closure lifecycle with structured status updates
- System-audited lifecycle record on every closed case
- Conduct analytics dashboards: frequency, type, resolution time, outcomes
- Repeat-involvement and hotspot views for student affairs
- Exportable reports for audits, accreditation bodies and policy reviews
Inside the product
A case from report to closed, in one place.
This is the application, not a diagram. Move through the surfaces a conduct office works in: intake, triage, investigation, decision and sanction, communication, and the analytics that follow.
| Case | Category | Severity | Assigned to |
|---|---|---|---|
| CC-2026-0142 | Academic misconductPlagiarism, repeat | Level 2 | Conduct Committee |
| CC-2026-0147 | BehaviouralResidence hall | Level 3 | Dean of Students |
| CC-2026-0149 | Academic misconductFirst instance | Level 1 | Department reviewer |
| CC-2026-0151 | BehaviouralConfidential report | Level 3 | Reassigned, logged |
| Sanction | Tied to | Compliance | Status |
|---|---|---|---|
| Written warning | Academic misconduct, Level 1Sanction repository | Acknowledgement due 7 days | Applied |
| Grade penalty on assessment | Academic misconduct, Level 2Policy clause 4.2 | Recorded on the assessment | Applied |
| Conduct probation, one term | Behavioural, Level 3Sanction repository | Review at term end | Tracked |
| Appeal window | Level 2 and aboveAppeal eligibility | Closes 28 Mar | Open |
Lifecycle or product
The lifecycle is the operating model. This is the product that runs it.
Two pages, two jobs. Read the lifecycle to understand how conduct sits inside the wider student journey; read this page to see the application a conduct office opens on Monday.
One of the institutional lifecycles: the governed model for the student record, advising, standing and support.
The application that runs a case: intake, triage, investigation, sanction, communication and analytics.
How do conduct, advising, records and academic standing stay consistent for one student?
What do conduct officers, investigators and committees actually see and do in each screen?
The full student success model, including records, support, retention and standing.
Report to closure: policy configuration, triage, evidence, sanctions, appeals and reporting.
You are designing the operating model or comparing architectures. See the lifecycle →
You are replacing forms, email and a sanctions spreadsheet. See inside the product →
Displacement
A case tracker manages the case. The consequence lives somewhere else.
Standalone conduct tools handle intake and casework well. But a conduct decision rarely ends at the decision: it changes standing, it can carry a registration hold, it belongs in the student record, and it is asked for at audit. A separate tracker leaves each of those to be re-entered by hand, which is exactly where consistency is lost.
A letter and a row in a tracker.
A governed record on the student, read by advising and registration.
Emailed to the registrar to apply.
Applied where it belongs, with the case as its provenance.
A report assembled by hand.
Exported from the same evidence the office already produced.
Good at casework. Disconnected from the record the decision actually changes.
Also part of the operating system
Student Conduct is also part of Student Success & Records.
Connect it and a conduct outcome reaches the places it matters: the student record, advising, academic standing and the evidence you present at audit. One record, no re-entry.
Built for every role
One case. Five people who need different things from it.
Sees case load, ageing and severity in one view, and can answer how long cases take and why without a data request.
Works the case instead of assembling it: intake is complete, the file builds itself as the investigation runs.
Receives the academic consequence as a record, not an email, with the case as its provenance.
Reports an incident in minutes, then sees it progress rather than wondering whether anything happened.
Knows the process, the timeline and the appeal window, and is told the outcome by the system, on the record.
What academic teams say about running student records and cases on Creatrix.
Creatrix Campus has helped us centralise all student information in one reliable and intuitive system, improving efficiency and reducing errors. We use it to manage student data, schedule sessions, and automatically generate transcripts, which has simplified many of our academic processes.
What I like best is its user-friendly and intuitive design. It makes managing tasks, attendance and academics seamless and efficient.
Go deeper
From the Creatrix library.
Blogs, whitepapers and case studies for the people who own the process: deans of students, conduct officers, registrars and quality teams.
Frequently asked
Plain answers about conduct cases.
Can students report an incident anonymously?
Yes. A confidential reporting mode accepts anonymous or restricted submissions, and case visibility is limited by role permissions, so a sensitive report is not readable by everyone with a login.
How do you keep a sensitive case private?
Permission and access governance controls who can open a record, by institutional role.
Every view, edit, upload and assignment is written to the system activity audit log, so privacy is enforced and provable rather than promised.
Does it enforce our conduct policy, or its own?
Yours. Misconduct categories, incident classifications and the sanction repository are configured to your regulations, and sanctions are tied to incident type and severity.
A committee selects from institution-defined options instead of improvising an outcome per case.
What happens when a decision is appealed?
The file is the defence. Investigation findings, time-stamped evidence, notifications sent, the sanction applied and the appeal window all sit in one record with a complete activity log, so the panel reviews exactly what the decision was made on.
Can we run Student Conduct on its own?
Yes. It runs standalone, and it connects into the Academic Operating System when you are ready: your call on when to expand.
Does a case connect to the student record?
On Creatrix, yes. Cases, sanctions and compliance dates are governed objects on the student record, so advising, registration holds and academic standing read the same outcome instead of being told about it by email.
What reporting comes out of it?
Dashboards cover case frequency, category, resolution time and sanction outcomes, and exportable reports serve audits, accreditation bodies and institutional policy reviews.
BRING A CASE YOU HAD TO DEFEND
Bring a real case type. We will run it end to end.
A tailored proof session uses your categories, your sanction policy and your escalation rules, not a canned demo. Leave with a named, dated next step.