Questions to Answer Before Expanding Student AI

Short answer

Questions to answer before expanding student access

Before expanding student AI access, confirm five things: which students and roles get access and with what permissions; that the privacy and compliance review covers student data; how safety concerns and misuse are escalated to an adult; that families have been informed; and who reviews usage and the policy each term.

Use this page as part of a connected review: understand the purpose, consider the people affected, check the relevant safeguards, and follow the related routes for practical next steps.

A teacher pilot can be adjusted quietly. Student access cannot. Once students are using AI, every gap in policy, permissions, or escalation becomes visible to students, families, and staff at the same time. A short pre-launch review gives leaders a clear yes, not yet, or no, and a record of why.

Why student access is a different kind of decision.

A teacher pilot involves adults who can judge a draft, ignore a weak suggestion, and ask a colleague for help. Students are still learning those skills. They may trust an answer too quickly, ask about personal worries, or test the limits of a new tool. That does not mean students should not use AI. It means the school needs safeguards ready before access begins, not added afterward.

There is also a legal and family dimension. FERPA protects the privacy of student education records, and COPPA covers online services that collect personal information from children under 13 and generally requires verifiable parental consent. Your privacy reviewers or district guidance can confirm what applies to your tool and your students. Families, in turn, expect the school to have thought this through before their child logs in.

Running the go or no-go review.

Imagine a hypothetical leadership team meeting for an hour before opening AI support to eighth grade. Each lead answers the questions for their area out loud: the technology lead confirms student roles are set up, the privacy lead confirms the review covers student data, the counselor explains who receives safety alerts and how fast they respond. Anything uncertain is marked "not yet" with a named owner and a date.

The result is a short written record. If the answer is yes, everyone knows why. If it is not yet, everyone knows what is missing. That record is also useful later, when a family or board member asks how the decision was made. Keep it simple: the question, the answer, who confirmed it, and any follow-up.

Testing escalation before students rely on it.

Safety escalation is the part most worth rehearsing. Before launch, walk through a few hypothetical situations with the adults who will respond: a student asks about something not suitable for school, a student repeatedly tries to get the tool to write an essay, a student mentions feeling unsafe at home. For each, confirm who is alerted, what they do next, and how the student is connected to a trusted adult.

Student support staff should know that the tool is not a counselor and should not be treated as one. Its job is to notice, pause, and point the student toward a person. The Ethos Study safety layer, for example, filters topics that are not school-appropriate, sends real-time alerts, applies temporary restrictions while adults review misuse, and redirects personal or sensitive situations to a trusted adult.

Widening access one step at a time.

Phased expansion lowers the cost of mistakes. Opening access to one grade or a few classes first means any gap affects a small group and can be fixed quickly. After a few weeks, review usage, alerts, and feedback from teachers and families. If the review comes back clean, widen to the next group and repeat the questions.

Expect each phase to teach you something. Younger students may need clearer instructions, a new subject may need different course materials, and families of a new grade will need their own message. Treat the questions in this guide as a standing routine rather than a one-time gate, and revisit them at least once a term.

Access and roles. Decide which grades, classes, or programs get access, and which adults have which permissions.

Data and compliance. Confirm the privacy review covers student data, including what is collected, who controls it, and how it is protected.

Safety and escalation. Agree how inappropriate topics are filtered, how misuse is handled, and how personal or sensitive situations reach a trusted adult quickly.

Oversight. Name who reviews usage and safety signals, how often, and when the policy is revisited.

Ready to expand:

Student roles and permissions are configured.

The privacy and compliance review covers student data.

Safety alerts are routed to named adults who know how to respond.

The acceptable-use and academic integrity policies cover students.

People are prepared:

Teachers know how students will use AI in their classes.

Families have been informed and know who to contact.

Student support staff know how escalations work.

A review date for usage and policy is set.

Review. Walk through the questions with each lead and record the answers.

Close gaps. Fix anything marked not yet before access widens.

Expand in phases. Open access to one group first, then widen as reviews come back clean.

Revisit. Repeat the review before each new phase and at least once a term.

Use these questions as a go or no-go review with your leadership, technology, privacy, student support, and family engagement leads before each expansion of student access.

Common questions

Quick answers to what schools and families ask most about this topic.