Getting a bus conduct write-up from a driver's hands to a resolved response the same day
Flow Forms · Student and school operations
The short answer
A bus conduct write-up that takes days to resolve doesn't just move slowly. It arrives too late to actually help the student. One district's bus drivers used to turn in triplicate forms every one to two weeks; by the time a principal saw what happened, there wasn't much left to meaningfully address. At Columbia Falls Public Schools, the old version of this process ran through inter-department mail or a scan-and-email: a driver's write-up, a principal's response, and a parent's notification, each waiting on the step before it. Doing it well means the write-up, the response, and the parent notification happen inside the same few hours the incident did, not spread across the days it takes paper to move between people.
What a delay actually costs
At Columbia Falls Public Schools, bus conduct write-ups used to run on a duplicate form. A driver wrote down what happened, then the form went to the principal by inter-department mail or by being scanned and emailed. The principal wrote a response on the same form and sent it back the same way. "The process was lengthy and time consuming for all involved," the district's Director of Transportation, Jodee Perkins, said. "The information didn't get to the people that it needed to very quickly."
A second Montana district ran an even slower version of the same problem. Drivers turned in triplicate write-ups every one to two weeks, and a principal would receive stacks of them from different drivers at different times. By the time any single write-up surfaced, staying on top of the discipline it described was close to impossible. The failure wasn't that the paperwork was inefficient. It was that whatever response the write-up was supposed to trigger arrived too late to mean anything to the student it was about.
How the write-up actually moves now
With Flow Forms, a driver reports what happened from a QR code they scan on their own phone: no login, no app, and for bus drivers specifically, nothing that feels like technology the way a dashboard or a portal would. The write-up routes straight to the principal. "The driver writes a student up and within moments this can be routed to a principal," Perkins said. "They can deal with the information and reply how it was handled. A copy of how it was handled arrives back to the driver's email." What used to take days now takes a few hours: "All of this can happen within a few hours vs the days it took previously," Perkins said.
The second district's version of this same mechanism produced a specific, visible change: the principal could meet the student that very morning, ready to bring them to the office, instead of discovering days later that something had happened and needed a response.
The same mechanism now runs in Sioux Falls, South Dakota: the principal is notified before the bus arrives and meets the student when they get off.
Why the parent doesn't need a separate follow-up
The write-up doesn't stop at the principal's response. The same submission that routes to the principal also generates a notification to the parent and requests their signature, a byproduct of the incident report itself rather than a separate step someone has to remember to do afterward. Nobody is maintaining a spreadsheet of which parents still need to be told, or chasing a signature that was supposed to go out days ago. It's already moving by the time the principal's response is written.
What doing it well actually requires
Getting a bus conduct report right isn't about a faster form. It's about making sure nothing between the incident and the parent's notification has to wait on paper moving between people.
The write-up routes from driver to principal in moments, not days
The write-up routes from driver to principal in moments, not days, and a copy of how it was resolved returns to the driver automatically.
The parent notification generates from the same submission
The parent's notification and signature request generate as part of the same submission, not a separate follow-up someone has to remember.
Drivers submit from their own phone, no app or login
Drivers submit from their own phone by scanning a QR code, without a login, an app, or any training.
Columbia Falls Public Schools runs this today
Columbia Falls Public Schools runs this today. "All of this can happen within a few hours vs the days it took previously," said Jodee Perkins, the district's Director of Transportation.
Common questions
Questions we hear from the people who handle bus conduct reports.
- Does the bus driver need to download an app or log into anything to submit a write-up?
- No. The driver scans a QR code with their own phone and a simple form opens, no login, no app, and nothing to install ahead of time.
- What happens if the principal who normally handles this is out that day?
- That approval step can be reassigned to someone else so a write-up doesn't sit waiting for a specific person to be back at their desk. This works the same way for any approval step in Flow Forms, not just this one.
- How does the parent actually find out and sign off?
- The notification and the signature request go out as part of the same submission that routes to the principal, not a separate step added afterward. Nobody has to remember to follow up.
- Is there a record of how a write-up was handled, in case it's needed later?
- Yes. Every submission keeps a timestamped record of who took each step and when, down to the minute.
How Flow Forms handles it
A bus conduct report is really three things happening in sequence: a driver's write-up, a principal's response, and a parent's notification. Flow Forms routes all three through one submission instead of three separate steps waiting on paper or email to move between people, so a district's response arrives while it can still mean something to the student it's about.