Publish menus per day or per month — structured items or the monthly PDF you already make — to the app, your public website, and the no-login public app in one motion. Then the move nobody else can make: a guardian's menu view flags items containing their own child's on-file allergens, computed server-side with a hard privacy guarantee. Nutrislice publishes menus; it has no idea who's reading. Bloomz knows it's Maya's mom.
A substitute gets class access for exactly the coverage window — roster, hall passes, the lesson plan attached — and the access expires by itself, because it was never a membership at all. Tutoring sessions log in seconds and attach to a student's open Thrive case as intervention-delivery evidence, with quiet-case flags when sessions stop. Volunteer hours total automatically from visitor sign-outs and coordinator entries, exportable for recognition night.
Assign a registered staff member to cover a class for an exact window — they get the class tools for exactly that window, with the lesson plan attached. Access expires by itself; there is nothing to remember to revoke.
Route 12 leaves school; staff tap Departed; every family on the route gets the push, in their language, resolved from the same dismissal plans the car line uses — no GPS hardware, no student location ever collected. The library logs visits on the day's check-in spine and checkouts in a simple list with overdue flags on Pulse. Both show up on the student's day timeline, because everything does.
Staff tap Departed and Arrived per route; every family on that route gets the push instantly — resolved from the same dismissal plans the rest of the day already uses. No new app, no separate roster.
Bring your hardest scenario, a multilingual community, a PBIS rollout, a vendor consolidation, and we'll walk through the actual product.