Every school manages behavior. Very few can see it.
ConductKeeper started inside a real school’s discipline workflow. Referrals lived on paper forms that took a planning period to file. Follow-ups lived in inboxes, where they depended on someone remembering. And positive behavior — the thing everyone agreed mattered most — went largely unrecognized, because celebrating it was one more manual job at the end of an already-full day.
The strange part wasn’t that the tools were bad. It’s that they were separate. Discipline lived in the student information system. Rewards lived in an app. Reporting lived in a spreadsheet that someone rebuilt by hand every quarter. Three systems, three logins, and no single place where a student’s whole story — the referral in October and the turnaround in February — actually existed.
One record, one loop
So we built one system that treats discipline and PBIS as the same program. Staff log an incident from a phone, tablet, or laptop in under two minutes, in the school’s own language. Workflows route it to the right administrator, and discipline matrices keep responses consistent. Points, houses, and badges make positive behavior visible — on live leaderboards and hallway TV dashboards students actually walk past. And dashboards, plain-English reporting, and AI insights surface patterns while there’s still time to act on them.
Log. Respond. Celebrate. Learn. One loop, four moments, one record.
Built to be defended, not just demoed
Because it was born in a school, ConductKeeper is built for the questions schools actually ask. Tenant isolation is enforced at the data layer, so every query is scoped to your school automatically. A FERPA audit trail logs access to student records. AI runs with usage caps, cost logging, and an optional strict-privacy mode that keeps student identities out of the models entirely. Even the hallway leaderboards are IP-restricted to your campus network.
We also made one decision early: no invented proof. When we publish numbers, they’ll come from real schools measuring real things — time to log, follow-through, recognition volume. Until then, the pitch is simple: bring your handbook, give us thirty minutes, and see whether the loop fits the way your school actually runs.
Book a walkthrough — 30 minutes, your handbook’s language, no slide deck.