Activity Bank
Teachers compare printed AI answers with a source packet during professional learning.

All activities Professional learning

Ban, Allow, or Teach?

A leadership team works the ELE five-question check to craft a defensible stance on generative AI, moving past the headline fight over school AI moratoriums to decide what their own evidence, equity, and families actually require.

Print handouts

Overview

Districts are being pushed to pick a side: some have declared broad AI moratoriums, others are racing to put AI in every classroom. Headlines reward the extremes, but a leader's job is a defensible stance, not a slogan. This session walks a leadership team through the ELE five-question check, vision, evidence, instruction, who's left out, and families, to reason toward a position on generative AI that fits their own context. Teams weigh the real tension in the news (concerns about cognitive offloading and weaker critical thinking against the risk of banning a tool students will use anyway and widening gaps for students without support at home). The outcome is not a predetermined "teach it" answer; a time-boxed, grade-banded moratorium can be the right call for a community, as can structured adoption. What the ELEs require is that the choice be driven by evidence of learning and equity, communicated to families, and revisited, not chosen by whoever is loudest.

Objectives

  • Leaders will apply the five-question check to a generative AI stance decision.
  • Leaders will weigh evidence on both sides of the ban-versus-teach debate without caricaturing either.
  • Leaders will draft a defensible, grade-banded AI stance tied to evidence of learning and equity.
  • Leaders will plan how to communicate the stance to families and when to revisit it.

Materials

On paper

  • Handout A: The Five-Question Check, worksheet (1 per team)
  • Handout B: Four Real Stances, a reading of fictional districts' choices (1 per participant)
  • Handout C: Our Draft Stance + Family Message (1 per team)

On screen

  • Optional: a shared document or slide to capture the draft stance for the full leadership team
  • Optional: existing student-work samples or survey data from your own schools as evidence

Before you start

  1. Print Handout A and C per team and Handout B per participant.
  2. Gather any local evidence you have (student surveys, work samples, teacher concerns) to ground the discussion in your context.
  3. Seat mixed teams so a single strong opinion doesn't drive the table.
  4. Frame the session honestly: there is no pre-approved answer; a thoughtful moratorium and a thoughtful rollout are both on the table.

Step by step

  1. 10–8 min

    Hook

    The headline trap

    Open with two real-sounding headlines: a district announcing a sweeping AI moratorium, and another mandating AI in every lesson. Ask tables: "Whose community does each serve, and whose does it fail?" Draw out that both extremes can be defensible or reckless depending on context, and that a leader's accountability is to reasoning and evidence, not to the louder headline.

    Facilitator noteExpect strong opinions in the room. Validate them, then redirect: the task isn't to win the debate, it's to build a stance you could defend to a skeptical board and a worried parent alike.

  2. 28–20 min

    Explore

    Four real stances

    Teams read Handout B: four fictional districts that chose differently, a K–8 time-boxed moratorium, a high-school "teach it with disclosure" policy, an "allow for busywork, not for graded thinking" rule, and a chaotic no-policy district. For each, teams note what evidence drove it, who it helped, and who it left out. Debrief: none is perfect; each reflects a context and a set of trade-offs.

    Facilitator noteThe no-policy district matters most: doing nothing is itself a choice, usually the least equitable one, because it leaves teachers and families to improvise alone.

  3. 320–50 min

    Apply

    Work the five-question check

    Teams work Handout A on their own context. Vision: what is the learning we want, and where could AI help or harm it? Evidence: what will we watch to know, student work, offloading patterns, growth, not tool-usage counts? Instruction: what changes for teachers, and what support do they get? Who's left out: which students gain or lose under each option (no home access, emergent bilinguals, students with disabilities)? Families: how will we explain this so a worried parent understands? Teams must consider at least a moratorium option and a structured-use option before deciding.

    Facilitator notePush teams off tool-usage metrics. "80% of teachers used the AI tool" is not evidence of learning. Keep asking: what would show student thinking improved, or didn't?

  4. 450–65 min

    Create

    Draft the stance and the family message

    On Handout C, each team writes a one-paragraph stance (what is allowed, for whom, by grade band, and why), the top two pieces of evidence they'll monitor, and a plain-language message to families, three sentences a parent would actually understand. They set a revisit date. Teams swap drafts and stress-test: could you defend this to the board? To a parent who fears AI is doing their child's thinking? To a teacher who loves it?

    Facilitator noteThe family message is the integrity check. If a stance can't be explained to families in plain language, it usually isn't clear enough internally either.

  5. 565–75 min

    Reflect

    Defensible, not loud

    Each team shares its stance in one minute and names the hardest trade-off they accepted. Close on the ELE commitment: a leader's AI stance is judged not by how bold it sounds but by whether it is driven by evidence of learning, protects the students most likely to be left out, is understood by families, and can be revisited as the evidence changes.

    Facilitator noteName that revisiting is strength, not weakness. A stance locked forever will be wrong within a year; one with a built-in review date stays honest.

Paper or screen

Unplugged

The whole session runs on paper: the five-question worksheet, the printed stance scenarios, and the handwritten draft stance and family message. Leadership reasoning and discussion need no devices.

Digital

Capture the draft stance in a shared document so the full leadership team and board can see and refine it, and attach any local evidence (survey results, work samples). If several campuses meet remotely, each team can work a shared slide and compare stances live.

Does it need a screen? This is deliberately unplugged: the work is human judgment and consensus, and paper keeps the five questions, not a tool, at the center. Devices only help afterward, to share and refine the decision.

Evidence of learning

What you should be able to see or collect if it worked.

  • Teams answer all five questions for their own context, considering at least a moratorium and a structured-use option.
  • Evidence named is about student learning (work, growth, offloading), not tool-usage counts.
  • The draft stance is grade-banded, names who could be left out and how it protects them, and sets a revisit date.
  • The family message is three plain sentences a worried parent would understand.

Adaptations

Single campus
One team works all five questions for the whole campus; add department heads so the stance reflects different subjects' needs.
Higher Ed
Frame the stance around academic-integrity policy and syllabus-level AI statements, and weigh program accreditation expectations.
Small district
Combine roles so one team covers vision through families; lean on the four-stance reading to borrow options you don't have staff to invent.
Coaches facilitating
Coaches run the five-question check as neutral facilitators, capturing the team's evidence choices to translate into teacher support later.

Standards connections

Leaders apply the five-question check to craft a defensible, equity-minded generative-AI stance grounded in evidence of learning rather than headlines about AI moratoriums.

TEKS
ethics and laws (c)(9)practical technology conceptsTEKS sections: Technology Applications §126.5–§126.7, §126.8–§126.10, §126.17–§126.19, high school Technology Applications courses (19 TAC Chapter 126)

See how all activities align

Reflect

  • What learning do we want, and where does AI help or harm it? (Leader ELE 1.1: create and communicate a vision for technology.)
  • Under our stance, which students gain and which could be left out? (Leader ELE 4.2: policies for equitable access.)
  • What evidence, not tool usage, will tell us whether this is working, and when will we revisit it? (AI ELE 2.1: ethical, accountable AI use.)

Take it to your students

Within two weeks, bring the draft stance to the full leadership team and one family representative for feedback, then publish the plain-language version to families in the languages they use. Calendar the revisit date now, and decide the two pieces of evidence you'll collect before then.

Pairs well with