How it works
Scattered pages in.
Trusted answers out.
The information families need already exists—spread across websites, PDFs, and portals. Here’s exactly how reply.school gathers it, keeps it honest, and turns it official when your district joins.
How reply.school works: information from the district website, school calendars, athletics schedules, school documents, and community updates flows into reply.school, which organizes it into parent-friendly results such as a calendar date, a sourced answer, an enrollment step, and a team update. A parent can report a change to improve an answer. When a district joins, the community-maintained information gains an official district partner verification.
The pipeline, step by step.
Step 1
Agents watch the sources
Role-based agents monitor the places schools already publish—the district site, school calendars, athletics pages, documents, and community updates—on a schedule, not once at setup. Each agent owns a slice of school life, so a menu change and a game-time change are handled by specialists, not one giant crawler.
Step 2
Every change is caught and dated
When a page changes, the agent compares it against the last known version, records what moved, and stamps when it was checked. That's why answers can honestly say “checked today”—and why information never silently drifts out of date.
Step 3
Information gets reshaped around families
A staff-facing PDF becomes a calendar entry. A policy paragraph becomes a plain answer with the next step attached. Everything is organized around your week and your kids—not around departments and websites.
Step 4
Parents keep it honest
See something missing, outdated, or wrong? Report it in a tap. Reports route into the same review pipeline agents use, and the fix reaches every family in the district—not just yours.
Step 5
Districts make it official
When a district becomes an official partner, its staff validate answers, publish announcements directly, and take ownership of what carries the district badge. People approve everything official, with an audit trail behind it.
What keeps it honest.
Trust isn’t a feature you bolt on. These rules apply to every piece of information in the system.
Citations, always
Every answer links to where it came from. If we can't source it, we say so instead of guessing.
Freshness you can see
Each fact carries a last-checked date. Stale information is flagged, not passed off as current.
Clear labels
Community-supported information is labeled exactly that. Only district-validated content carries the official badge.
Humans decide what's official
Agents prepare changes and evidence; anything published as official waits for a named person to approve it.
Behind the scenes
When a district joins, the machinery is theirs.
A portal for district staff
Districts get a role-based portal to manage the knowledge base, supervise the agents maintaining their data, and approve anything official from a review queue.
Workflows beside the SIS
Managed workflows from k-12.cloud connect the student information system a district already runs to the family experience—attendance alerts, enrollment welcomes, staff digests—each reviewed before touching production data.
Questions that reach people
When a question needs a human, it routes to the right role—attendance, enrollment, transportation, athletics—with secure follow-up instead of a shared inbox.