Why We Built OnTrack

Every teacher we talked to said the same thing: behavior management was eating their day. Not the actual work of redirecting a student or having a hard conversation — that part they were trained for. The paperwork. The after-school data entry. The three different forms they had to fill out to document one incident.

That’s where OnTrack started.

The problem nobody was solving

School behavior software has existed for years. Most of it was built for administrators — compliance-focused, report-heavy, and completely disconnected from the moment a teacher actually needs it. By the time a teacher logged into the system, found the student, and filled out the form, five minutes had passed and their class was off the rails.

We wanted to build something that fit into the existing rhythm of a school day. Fast enough to use mid-lesson. Clear enough that a substitute could figure it out. Useful enough that a teacher would actually open it again tomorrow.

What we learned from our pilot schools

We ran our first pilot at two schools with very different contexts — one urban middle school and one rural K–8. The feedback that shaped OnTrack the most wasn’t about features. It was about speed. Teachers told us they needed to log a behavior event in under ten seconds, or they simply wouldn’t do it.

So we designed around that constraint. One tap to open a student’s record. Two more taps to log what happened. Done. The data is there when you need it at the end of the week, when a parent calls, or when you’re sitting with a counselor trying to figure out if a student’s pattern has changed.

Where we go from here

OnTrack is free for early adopters. We believe the teachers who help shape the product in its first year deserve to use it at no cost — forever, as a thank-you for the feedback that makes it better for every school that comes after.

If you’re a teacher or administrator who wants to try it, get in touch. We’d love to hear what your school day actually looks like.