Every referral is a case.
Every case gets closed.
A referral in a Google Form is a message. A referral in Conduct is a case: routed to the right administrator, resolved on the record, shared with the staff who need the outcome — and the teacher who submitted it finally hears back.
Follow one referral through the building.
This is the loop your office already runs by hand — with the follow-through built in instead of remembered.
- 01SubmittedTeacher · 8:03 AM
A structured referral, under a minute from a classroom. No hunting for the right form or the right inbox — routing is automatic.
- 02ReviewedAdministrator
The referral lands in the reviewer's queue with the student's history alongside it — not as a surprise in March.
- 03ResolvedAdministrator
A decision, a consequence if one applies, and a written resolution on the case.
- 04SharedCounselor · secretary · teacher
The resolution goes to the staff who need it — including the teacher who submitted, who finally learns how it ended.
- 05Family — when appropriateOptional, never automatic
Family communication is a deliberate choice on each case, logged when it happens. The system never emails a family on its own.
- 06On the recordStudent timeline
The case closes onto the student's timeline, next to cut slips and device history — searchable, reportable, still there in June.
Sharing is a decision, not a default — family contact stays in the office's hands.
The queue an administrator actually works.
Case numbers, grade routing, statuses that mean something, and the student's history one click away. Built dense on purpose — this screen gets used at 8 a.m., not admired.
Inside Conduct.
Structured conduct referrals, submitted from any classroom and routed to the right reviewer automatically.
Class cuts run through the same review loop as referrals — one queue, one case-number sequence, no side pile of paper.
Pending, verified, not verified, excused — a real status lifecycle with an auditable trail, not a spreadsheet column.
Resolutions go to the counselor, secretary, and submitting teacher on a per-case decision. Family communication stays optional and logged.
Patterns by grade, type, status, and time — answered in the product, not by exporting to a spreadsheet first.
Teachers see submission. Administrators see the queue. Counselors see history. Scoped on the server, every request.
The next StudentOps workflow, on the same student record. It isn't part of Main Office Works yet — we'd rather ship it right than claim it early.
See Conduct on a realistic school day.
Submission, review, resolution, sharing — walked through end to end on anonymized demo data.