Current status: Tenet Gateway is a founding-district program. The parent-facing assistant is included with every new Tenet Gateway customer this semester. District implementation scope, infrastructure, approved sources, and operating requirements are defined during rollout.
Every new Tenet Gateway customer gets a parent-facing AI chatbot included this semester.
A parent should be able to ask, “What time does the elementary school day begin?” and get a useful answer without digging through five menus, a PDF handbook, and last year’s calendar.
The assistant uses approved public district information. It can answer the question, show the source behind the answer, and link the parent back to the district’s own page.
That is the offer. The more important part is what sits underneath it.
Give families answers from sources the district already approves
A district can load a deliberate collection of public information, including:
- district and school calendars;
- family and student handbooks;
- graduation requirements;
- enrollment instructions;
- transportation and meal information;
- family technology guides;
- board policies and other public procedures.
When the assistant answers, it cites the approved page or document that grounded the response. A parent can verify the answer instead of being asked to trust a fluent paragraph with no source.
Citations help. They do not make an AI answer infallible. The district still needs someone to own the source collection, remove stale material, test common questions, review failure behavior, and give families a clear route to a person.
The live District Public Information Guide demonstrates that narrow scope. It uses approved public demo-district information. It cannot access student records, private district systems, or information about an individual student.
Why the assistant is included with Gateway this semester
AI infrastructure can sound abstract. A parent assistant is not abstract.
It answers a real question that district communications and front-office teams receive every week. It also forces the right implementation decisions into the open: which sources are authoritative, who owns them, what the assistant must refuse, which model route is approved, and what evidence the district needs when something goes wrong.
That makes the assistant a practical first application for the Tenet Gateway founding-district program. It gives the district something useful now while establishing a governed path for what it wants to build next.
The chatbot is included with every new Tenet Gateway customer this semester. It is not a permanently free standalone chatbot for districts that are not Gateway customers.
AI chatbots are becoming much easier to build
A capable team can now stand up a basic chatbot in days or roughly a week. The exact timing depends on the data, integrations, security requirements, accessibility work, evaluation, and review process.
That is not a promise that every district can launch safely in one week. It is evidence that the technical barrier to producing a convincing first version is falling fast.
That is good and scary.
It is good because a district no longer needs a giant software project to test a focused AI application.
It is scary because the demo is no longer the hard part. The hard and durable problem begins after people start depending on it.
Build or buy, you still have to govern it
A district can build an assistant, buy one from an established vendor, or start from a reference application. Those are legitimate operating choices, and our school district AI chatbot build-versus-buy guide explains the tradeoffs.
None of those choices removes the governance work.
Before launch, and again as the application changes, district leaders should be able to answer five questions:
- Who is allowed to use the application?
- What parent, student, or staff data may reach a model?
- Which models are approved, and for which purposes?
- Where is the operational and audit record?
- How does the district hold the next AI application to the same standard?
A polished interface does not answer those questions. A vendor contract does not answer all of them either. They require a district operating model and controls that survive the first application.
The AI application is not the control layer
The parent chatbot is an application. It owns the family experience, retrieves from the approved knowledge collection, produces citations, and refuses questions outside its public-information scope.
Tenet Gateway is the shared control layer for AI applications a district builds and vendor applications it connects to that governed path through a scoped implementation. Gateway is designed to identify the calling application and apply district rules for purpose, permitted data, eligible model deployments, budgets, and content-minimized decision evidence before the approved model is called.
The distinction matters. The chatbot should be useful and replaceable. The governed path should be reusable.
The next district application might be an authenticated IT help desk, a board-policy assistant, or an internal drafting workflow. It should not require another disconnected process for approved models, access, data handling, and recordkeeping. When it runs through the same control layer, it can inherit the relevant standards and receive its own application-specific limits.
That does not eliminate application review. A public family assistant and an internal employee tool have different audiences, source collections, risks, and failure modes. Shared governance makes those differences explicit instead of hiding them inside separate products.
Gateway and Tenet Edge govern two different AI paths
Tenet Gateway governs AI operations inside district applications. The caller is an application, and the traffic runs toward an approved backend model deployment.
Tenet Edge is the complementary browser layer for people using supported AI products on district-managed Chrome. It can extend configured district rules into supported services such as ChatGPT, Gemini, and MagicSchool. Available controls vary by product surface, content type, configuration, and rollout scope, as documented in the supported-products capability matrix.
The two paths should not be collapsed into one stream of data. They solve different enforcement problems. They can still use a shared policy language for identity, purpose, approved data, eligible models, constraints, and evidence.
That is the broader Tenet thesis: govern the AI applications people already use, and govern the AI applications the district builds or connects next.
Try the assistant, then talk to us about the control layer
Start with an ordinary parent question. Ask when school begins, how many credits are required to graduate, or where a family can get Chromebook help. Then open the citation and inspect the public source behind the answer.
Try the live District Public Information Guide.
If the application is useful, the next conversation is not only about the chatbot. It is about how your district will govern the next five AI applications without inventing five different control systems.
Explore Tenet Gateway, or discuss a district rollout.
Sources
- AI Risk Management Framework Core, National Institute of Standards and Technology
- Privacy and Education Technology, U.S. Department of Education Student Privacy Policy Office
- RAG infrastructure for generative AI using Google Cloud, Google Cloud Architecture Center
Tenet Gateway remains a founding-district program. Production scope, integrations, data handling, controls, and validation are documented with each district. This article is practical product guidance, not legal advice.