Monday morning, the front office takes forty calls about the same bus route. A principal spends drop-off correcting a rumor. By ten, a board member forwards a screenshot asking why the policy changed again.
None of it started Monday. It started at 9:40 the night before, when a parent wanted to know what time the buses run.
She looked. Three menus deep, a PDF from last year, no answer. So she asked the town parents' group, where someone replied in four minutes with what they remembered from an email in August. That reply is what she repeats at the bus stop, and it's the one your principal has to walk back.
Here's the part worth sitting with. Your district already answers that question. It's in a board policy, a handbook, a transportation page updated in July. The information was never missing. Reaching it at 9:40 on a Sunday was.
Most of us hesitate to put AI on a district website for a good reason: we don't want a machine inventing answers for families. Hold that worry next to what's happening now. The invented answer is already out there. It came from a neighbor, it's four minutes old, and nobody in your district has seen it.
An assistant built on your own approved content doesn't introduce that risk. It moves it somewhere you can watch. You pick the sources. You approve the wording. A family gets your answer, with a link to where it came from, at the hour they're actually asking.
Your community is getting answers at 9:40 on a Sunday night. The only open question is whose.