Route 14 and 1,800 Parents
On a Thursday afternoon, a kindergarten student on Route 14 is dropped at the wrong stop and is found by a neighbor 40 minutes later. That morning, four drivers called out; dispatch was run by one person using a paper spreadsheet; the route had been double-covered since September. By Friday, a parent Facebook group has 1,800 members and two board members have joined it. A reporter has filed a public records request for driver callout logs and the transportation contract. A city council member has publicly called for your resignation. A facilities bond is on the ballot in seven months, and your last two bond measures failed by 4 and 6 points.
1. What are your first 48 hours?
Read the worked answer
Child first, facts second, message third, records throughout.
Within hours:
- Confirm the child is safe and call the family yourself. Not a designee. Do not bring the district attorney or a communications staffer onto that call.
- Verify whether any other student was affected. This is the question that will define next week, and you want the answer before a parent finds it.
- One spokesperson, one inquiry log. Every call, email, and records request gets logged with a date and an owner, or you will contradict yourselves publicly by Tuesday.
Within 24 hours:
- A short, factual public statement that owns the failure without assigning cause before the review is complete: what happened, that the child is safe, what you are doing now, when you will report back with a date. No speculation, no passive voice, no 'the driver failed to follow procedure.'
- Brief the board in closed session on the facts and the legal exposure, and let the board president handle the council member. Elected officials answer elected officials; a superintendent who argues with a council member in the paper loses.
- The records request goes to counsel immediately and is answered on time and completely. Withhold only what is legally withholdable, and document why. A slow or partial release in a story like this is worse than the content, and it will be the second story.
Within 48 hours:
- Do not join the Facebook group and do not respond in it. Assign one person to monitor it and report themes daily. Parents in that group are your best source of what is actually broken.
2. How do you run the 30-day correction, and how do you tell the truth about the cause?
Read the worked answer
Fix the system that made the error likely, and describe it that way.
The proximate cause is a driver error or a route error. The system causes are the ones you own: no substitute coverage plan for four callouts, one dispatcher on a paper spreadsheet, double-covered routes running since September with no escalation, and no verification that a kindergartner got off at the right stop.
Thirty-day actions, each with a named owner and a date:
- Verified hand-off for K-2 riders -- a named adult at the stop or the child returns to school. Non-negotiable.
- Digital dispatch with live route visibility, replacing the spreadsheet.
- A callout escalation protocol with a second dispatcher on peak mornings and a defined threshold that triggers route consolidation rather than double coverage.
- A family notification channel so parents hear from you before they hear from a neighbor.
On the message:
- Say 'our scheduling and dispatch system made this outcome possible and we have changed it' rather than 'the driver made a mistake.' Both may be true; only one tells the public what will be different.
- Do not sacrifice the dispatcher or the driver publicly. You have 27 driver vacancies. If the workforce believes a bad morning ends a career, your vacancy problem doubles.
- Publish the fixes and dates, then report publicly against them at 30 and 60 days. Credibility in a crisis comes from verifiable follow-through, not from the quality of the apology.
3. How do you manage the political dimension -- the council member, the board members in the Facebook group, and a bond seven months out?
Read the worked answer
Separate three tracks that will bleed into each other if you let them.
- Operational: the 30-day fixes above, run by the transportation director with your weekly review. Keep this track boring and on schedule.
- Political: the board president responds to the council member, not you. Privately, ask the president for a direct closed-session conversation about whether the board still supports you -- better to have that question asked to your face than to read it in the paper. Two board members in the Facebook group are a governance problem; raise it with the president as a board norms issue, not as disloyalty, and propose that members route constituent concerns to you rather than to the group.
- Public trust and the bond: do not let the bond campaign absorb the crisis, and do not hide from it either. A bond seven months out does not need a message; it needs a record. Propose an independent transportation review with published findings and milestones, funded from operating money. Outside verification is the only thing that converts 'they say they fixed it' into 'it is fixed.'
Two things to avoid. Do not let the bond consultants tell you to go quiet until spring -- silence reads as concealment in a story with a child in it. And do not use the crisis as a reason to delay the bond decision; if the facilities need is real, deferring it because of a bus failure trades one problem for a worse one.
Finally, expect the emotional load to be aimed at you personally. Take the anger in public, keep the analysis in private, and keep your own counsel about resignation until you have had the closed-session conversation with the board.