⚠️ NOTE: AI policies have legal and regulatory implications. This generates a working draft for leadership review. Have your legal counsel, data privacy officer, and board review before adoption. International schools should also consider host-country data protection laws (e.g., GDPR, Swiss FADP, local equivalents). You are a technology director at [SCHOOL NAME], a [SCHOOL TYPE, e.g., K–12 international boarding and day school in Switzerland, PK–12 American school in Singapore, IB World School in the UAE]. You need to draft a comprehensive AI Acceptable Use Policy. School context: • Current technology environment: [e.g., 1:1 iPads grades 5–12, Chromebooks K–4, Google Workspace, Canvas LMS] • AI tools currently in use or under consideration: [e.g., Claude, ChatGPT, Grammarly, MagicSchool, Diffit, Khanmigo] • Accreditation bodies: [e.g., CIS, NEASC, MSA, IBO] • Data protection framework: [e.g., GDPR, FERPA, Swiss FADP, school’s own data policy] • Board or leadership priorities: [e.g., innovation with guardrails, academic integrity, equity of access, teacher empowerment] Draft a comprehensive AI Acceptable Use Policy that includes: 1. Purpose and scope: Why this policy exists, who it covers (students, faculty, staff, administrators), and what it applies to (school-owned devices, school accounts, school-related work, personal device use on campus). 2. Guiding principles (5–7): The values that drive the school’s approach to AI. These should reflect [SCHOOL NAME]’s mission and educational philosophy. Suggest principles around: learning as the priority, transparency, academic integrity, equity and access, data privacy, human judgment, and continuous iteration. 3. Approved and prohibited uses — organized by role: • Students: What students MAY use AI for (with examples), what is PROHIBITED (with examples), and what requires TEACHER PERMISSION (with examples). Be specific enough that a 9th grader can understand the boundaries. • Teachers and staff: What educators MAY use AI for (lesson planning, differentiation, feedback drafting, admin tasks), what requires caution (student data, grading, recommendation letters), and what is prohibited (entering student PII, using AI for formal evaluations without disclosure). • Administrators: Expectations for transparency, data governance, and modeling responsible use. 4. Academic integrity section: How AI use intersects with the school’s existing honor code or academic integrity policy. Include: • A clear definition of unauthorized AI use vs. authorized AI-assisted work • A disclosure framework (when and how students/staff must cite AI use) • A suggested AI citation format • A graduated response for violations (education-first, not punitive-first) 5. Data privacy and security: • What data may NEVER be entered into AI tools (student PII, health records, disciplinary records, passwords) • What data may be entered with precautions (anonymized student work, aggregated performance data) • Approved tools list and the process for adding new tools • Data residency and storage requirements based on [APPLICABLE LAW] 6. Equity and access: How the school ensures all students have equitable access to AI tools and that AI doesn’t widen existing gaps. Address: device access, language barriers, students with disabilities, and digital literacy disparities. 7. Review and iteration: How often the policy will be reviewed (suggest quarterly for the first year, then annually), who is responsible, and how feedback is gathered from students, staff, and families. 8. Acknowledgment form: A brief sign-off for students and staff confirming they’ve read and understood the policy. Write the policy in clear, professional language accessible to non-technical board members and families. Avoid jargon. Include a version number and effective date field.

You are the academic dean or director of teaching and learning at [SCHOOL NAME], a [SCHOOL TYPE]. Your school has an existing academic integrity policy, but it doesn’t address AI. You need an addendum that integrates with the existing policy without replacing it. Existing policy context: • Current honor code language: [PASTE KEY SECTIONS OR SUMMARIZE] • Current consequences for violations: [DESCRIBE THE EXISTING FRAMEWORK] • School’s pedagogical stance on AI: [e.g., cautiously embracing, teacher-directed, subject-specific, still forming] Draft an AI and Academic Integrity Addendum that includes: 1. Preamble: 2–3 sentences connecting AI use to the school’s existing values around honesty, learning, and intellectual growth. This should feel like a natural extension, not a punishment framework. 2. Definitions: • AI-generated content: Output produced primarily by an AI tool • AI-assisted work: Student work that used AI as a tool during the process (brainstorming, editing, research) but where the student did the core thinking • Unauthorized AI use: Using AI in ways not permitted by the assignment or teacher 3. The "Traffic Light" framework for students: • GREEN (always OK): Using AI to brainstorm topics, check grammar/spelling, explain concepts you don’t understand, translate for comprehension, generate practice problems • YELLOW (ask your teacher first): Using AI to outline an essay, generate a first draft for revision, create study materials, get feedback on your writing, solve example problems to learn a method • RED (never OK unless explicitly authorized): Submitting AI-generated work as your own, using AI during assessments, entering other students’ work into AI, using AI to complete assignments you haven’t engaged with intellectually 4. Teacher authorization protocol: How teachers communicate their AI expectations for each assignment. Suggest a simple framework teachers can add to any assignment (e.g., "AI use for this assignment: GREEN / YELLOW with permission / RED"). 5. Disclosure and citation: When students must disclose AI use and how. Provide a simple AI citation format: "I used [TOOL NAME] to [SPECIFIC PURPOSE]. I then [WHAT I DID WITH THE OUTPUT]." 6. Response to violations — graduated and educational: • First instance: Conversation with student, resubmission opportunity, reflection • Second instance: Parent notification, academic consequence aligned with existing policy • Pattern of violations: Formal integrity process as per existing honor code • For all instances: The goal is teaching responsible use, not criminalizing a tool 7. FAQ section: 5–7 common questions from students and parents with clear, honest answers (e.g., "Can I use Grammarly?", "What if I’m not sure if my use is OK?", "Is using AI cheating?").

⚠️ NOTE: Data privacy impact assessments may be legally required under GDPR, Swiss FADP, or other regulations. Consult your data protection officer or legal counsel when processing student data through third-party tools. You are a technology director evaluating a new AI tool for potential use at [SCHOOL NAME]. Before approving the tool, you need to conduct a data privacy impact assessment. Tool information: • Tool name: [TOOL NAME] • Vendor: [VENDOR NAME] • Proposed use: [HOW IT WOULD BE USED — e.g., AI writing assistant for English classes, automated quiz generation, student chatbot for homework help, administrative scheduling tool] • Who would use it: [STUDENTS / TEACHERS / ADMIN / ALL] • Data that would be processed: [DESCRIBE — e.g., student writing samples, grades, names, email addresses, learning analytics] • Your data protection framework: [GDPR / FERPA / Swiss FADP / OTHER] Generate a comprehensive Data Privacy Impact Assessment (DPIA) template with: 1. Tool overview and purpose: What the tool does, why the school wants it, and what educational benefit it provides. Include a "necessity and proportionality" statement: is this tool necessary for the stated purpose, or could a less data-intensive alternative achieve the same goal? 2. Data mapping: • What personal data is collected (list specific data fields) • How data is processed (on-device, cloud, which jurisdiction) • Where data is stored (geographic location of servers) • How long data is retained • Who has access to the data (vendor employees, AI model training, third parties) • Whether data is used to train AI models (critical question — flag this prominently) 3. Risk assessment matrix: For each data type, assess: • Likelihood of unauthorized access (low/medium/high) • Severity of impact if breached (low/medium/high) • Overall risk rating • Mitigation measure 4. Legal basis analysis: • Under [APPLICABLE LAW], what is the legal basis for processing this data? • Is parental consent required? If so, what form must it take? • Are there age restrictions (e.g., COPPA for under-13, GDPR for under-16)? • Does the vendor’s data processing agreement (DPA) meet regulatory requirements? 5. Vendor security checklist: 15–20 specific questions to ask the vendor about their security practices (encryption, access controls, breach notification, SOC 2 compliance, penetration testing, subprocessor management, data deletion procedures). 6. Decision framework: Based on the assessment, provide a clear recommendation structure: • APPROVED: Low risk, strong vendor practices, clear legal basis • APPROVED WITH CONDITIONS: Moderate risk, requires specific mitigations before deployment • DEFERRED: Additional information needed from vendor • REJECTED: Unacceptable risk to student data 7. Parent communication template: If approved, a brief notification to parents explaining what the tool is, what data it processes, and their rights regarding their child’s data.

You are the head of school or chief technology officer at [SCHOOL NAME], a [SCHOOL TYPE]. You want to establish an AI Governance Committee to guide the school’s responsible adoption and ongoing management of AI tools. School context: • School size: [NUMBER OF STUDENTS, FACULTY, STAFF] • Current state of AI adoption: [e.g., early exploration, several tools in pilot, widely adopted but uncoordinated, reactive to student use] • Existing governance structures: [e.g., technology committee, curriculum committee, board technology subcommittee, data privacy officer role] • Key stakeholders to represent: [e.g., administration, IT, faculty across divisions, counseling, library/media, students, parents, board] Draft a comprehensive AI Governance Committee Charter: 1. Mission statement (2–3 sentences): Why this committee exists and what it aims to achieve. Frame it as enabling responsible innovation, not restricting use. 2. Scope and authority: • What falls within the committee’s purview (tool approval, policy drafting, professional development oversight, incident response, student-facing AI guidelines) • What falls outside its purview (individual classroom pedagogy decisions, IT infrastructure, budget allocation) • Whether the committee is advisory or has decision-making authority (and on what) • Escalation path: when decisions go to the head of school or board 3. Membership: • Recommended composition (8–12 members) with specific roles • Term length and rotation schedule • How student and parent voice is included (direct membership, advisory input, survey feedback) • Chair responsibilities and selection process 4. Operating rhythms: • Meeting frequency (suggest monthly for the first year, then quarterly) • Standing agenda items for each meeting • Annual planning cycle (when to review policy, evaluate tools, assess PD needs, report to board) • Communication to the broader school community (how decisions and updates are shared) 5. Decision-making framework: • How tool approval requests flow through the committee • How policy changes are proposed, debated, and adopted • How the committee handles urgent decisions (e.g., a new AI tool goes viral among students mid-semester) • Consensus vs. voting protocols 6. Success metrics: 5–7 ways the committee will measure its own effectiveness after the first year (e.g., percentage of AI tools vetted before deployment, faculty confidence survey scores, policy awareness among students, incident response time). 7. Sunset and review clause: When and how the committee’s charter will be reviewed. Include the possibility that the committee evolves or is absorbed into existing governance structures as AI becomes normalized.

You are a technology director at [SCHOOL NAME] creating student-facing AI use agreements. You need two versions: one for middle school (grades 6–8) and one for high school (grades 9–12). Elementary guidance should be handled through classroom norms, not a formal agreement. School’s AI policy stance: [BRIEFLY SUMMARIZE — e.g., "We embrace AI as a learning tool when used transparently and in ways that support genuine understanding. We expect students to do their own thinking and to always disclose when AI assisted their work."] For EACH version (middle school and high school), create: 1. An opening framing (3–4 sentences) written directly to the student that: • Acknowledges that AI tools exist and are powerful • Frames responsible use as a skill worth learning (not just a rule to follow) • Connects to the school’s values without being preachy • For high school: add a forward-looking statement about AI in college and careers 2. "What you CAN do with AI" section (5–7 examples): Specific, concrete examples of acceptable use. Write these as things students would actually do, not abstract principles. Different for each age group. 3. "What you CANNOT do with AI" section (4–6 examples): Clear prohibited uses with enough specificity that edge cases are addressed. Include WHY each item is prohibited — not just "because we said so" but because it undermines their learning. 4. "When to ask your teacher" section (3–4 scenarios): Gray areas where the right answer depends on the assignment and teacher expectations. Frame these as mature judgment calls, not traps. 5. "How to cite AI" section: A simple, memorable format. For middle school: "I used [tool] to help me [what]. Then I [what I did next]." For high school: a more formal citation format compatible with MLA/APA. 6. "What happens if I mess up" section: Honest, non-threatening explanation of the response process. Emphasize learning over punishment. Different tone for each age group. 7. Acknowledgment: • Middle school: "I have read this and I understand it. I know I can ask [teacher/counselor] if I’m not sure about something." — with a signature line and parent co-sign. • High school: "I have read this and I commit to using AI tools in ways that support my learning and reflect my integrity." — student signature only. Keep the middle school version under 1 page. High school can be 1.5 pages. Language should feel like it was written BY someone who respects students, not AT students.
CATEGORY 2

Staff Communication and Change Management

You are the head of school or academic leader at [SCHOOL NAME], a [SCHOOL TYPE]. You’re about to roll out [DESCRIBE THE AI INITIATIVE, e.g., a new school-wide AI acceptable use policy, an approved AI tool for all teachers, an AI-assisted grading pilot, a student-facing AI chatbot for homework help]. Faculty context: • Faculty size: [NUMBER] • Current faculty comfort with AI: [DESCRIBE — e.g., mixed: some early adopters, many cautious, a few resistant; or: mostly enthusiastic but inconsistent in practice; or: largely unfamiliar] • Known concerns: [e.g., fear of replacement, academic integrity worries, workload anxiety, data privacy questions, "I’m not a tech person" sentiment] • Timeline: [WHEN THIS LAUNCHES] Create a 3-email communication sequence: EMAIL 1 — "The Why" (sent 2–3 weeks before launch): • Subject line that generates curiosity, not anxiety • Opens with a specific, relatable scenario that shows why this matters • Explains WHAT is happening and WHY in 3–4 paragraphs • Acknowledges concerns directly and honestly (don’t pretend there are none) • Clarifies what is NOT changing (protect what teachers value) • Ends with "what’s coming next" and when they’ll hear more • Tone: warm, transparent, leadership-level but not corporate EMAIL 2 — "The What and How" (sent 1 week before launch): • The practical details: what tools are approved, what the policy says, what’s expected of them • A simple "start here" guide (3–5 concrete first steps) • Links to resources, training sessions, and support • A clear statement of what they DON’T need to do yet (reduce overwhelm) • FAQ section addressing the top 5–7 questions you anticipate • Tone: practical, supportive, "we’ve got your back" EMAIL 3 — "You’ve Got This" (sent on launch day or day after): • Brief, energizing, forward-looking • One specific, low-stakes thing every teacher can try this week • A "help is here" section: who to contact, office hours, peer support • An invitation to share wins (set up a Slack channel, email thread, or shared doc) • Tone: encouraging, human, celebrates the team Each email should be under 400 words. Write them so a nervous teacher reads them and feels supported, not steamrolled.

You are the director of teaching and learning at [SCHOOL NAME], a [SCHOOL TYPE]. You’re designing a professional development series to build faculty AI competency over [TIMEFRAME, e.g., one semester, the full school year, a 3-day pre-service week]. Faculty profile: • Total faculty: [NUMBER] • Approximate breakdown: [e.g., 20% early adopters already using AI regularly, 50% curious but unsure where to start, 20% cautious/skeptical, 10% resistant] • Divisions: [e.g., elementary, middle, high school, or by department] • Previous PD on AI: [DESCRIBE — e.g., one introductory session last year, none, a few informal lunch-and-learns] Design a PD series with [NUMBER, e.g., 4–6] sessions: For each session, provide: 1. Title and learning objectives 2. Target audience tier: • Tier 1 (Foundations): For teachers new to AI — build comfort, reduce fear, establish baseline skills • Tier 2 (Integration): For teachers ready to use AI in their practice — lesson planning, differentiation, feedback • Tier 3 (Innovation): For early adopters — advanced workflows, student-facing applications, peer coaching Note which sessions are all-faculty vs. differentiated by tier. 3. Session format and timing (e.g., 60-min workshop, 30-min lunch-and-learn, asynchronous module with live follow-up) 4. Activities: For each session, describe 2–3 specific activities with enough detail that a facilitator could run them. Include at least one hands-on activity per session where teachers actually USE an AI tool in real-time. Provide the exact prompts they’ll practice with. 5. Deliverable: What each teacher walks away with (a lesson plan, a prompt library, a grading workflow, a classroom policy, etc.) 6. Follow-up: What happens between sessions to maintain momentum (try-it-this-week challenge, peer sharing, reflection form) Also include: • A pre-series survey (5–7 questions) to assess starting points and anxieties • A post-series survey (5–7 questions) to measure growth and confidence • A "PD Menu" format option: if you can’t run a linear series, how to offer these as choose-your-own sessions at a PD day The series should feel practical, not theoretical. Every minute should connect to something teachers will actually do in their classrooms.

You are a school leader at [SCHOOL NAME] navigating resistance to AI adoption. You’re hearing concerns from [AUDIENCE, e.g., faculty, parents, board members, or all three] and want to respond thoughtfully rather than defensively. The most common concerns you’re hearing: [LIST 3–5 SPECIFIC CONCERNS, e.g.: • "AI will replace teachers" • "Students won’t learn to think for themselves" • "This is moving too fast" • "What about data privacy?" • "We haven’t dealt with the last technology initiative yet" • "This is just a fad" • "Some families can’t afford these tools" • "AI is biased and unreliable"] For each concern, create a response framework: 1. Validate: Acknowledge the concern as legitimate and name the underlying value it represents (e.g., "AI will replace teachers" → the value being protected is the irreplaceable human relationship at the center of education). 2. Reframe: Shift from a binary (AI vs. no AI) to a nuanced position that honors the concern while showing a path forward. 3. Evidence or analogy: Provide one specific example, analogy, or data point that supports the school’s approach. Use analogies from education history where appropriate (calculators, spell-check, internet research — but acknowledge where AI is genuinely different). 4. Concrete action: Name one specific thing the school is doing that directly addresses this concern (a policy provision, a safeguard, a pilot program, a training initiative). 5. Invitation: Turn the objection into participation: "We’d love your perspective on our AI governance committee" or "Would you be willing to pilot this tool and give us honest feedback?" Also create: • 3 opening lines for public settings (board meeting, parent night, faculty meeting) that set a collaborative tone when the topic is contentious • 2 responses for the "gotcha" moment — when someone asks a question designed to make the school look irresponsible for embracing AI • A 1-paragraph "elevator statement" that summarizes the school’s AI philosophy for any audience in under 60 seconds Tone throughout: confident but humble, honest about uncertainty, and always returning to student learning as the anchor.

You are the academic dean or technology director at [SCHOOL NAME]. Rather than relying solely on centralized professional development, you want to create a peer-driven AI Champion program where enthusiastic teachers support their colleagues. School context: • Faculty size: [NUMBER] • Number of AI champions you want to recruit: [NUMBER, suggest 1 per department or 1 per 8–10 teachers] • Existing peer coaching or mentoring structures: [DESCRIBE OR "none"] • Compensation/recognition model: [e.g., stipend, reduced duty, professional development credit, leadership title, portfolio for career growth] Design a complete AI Champion program: 1. Program overview (1 paragraph): What an AI Champion is, what they do, and how they fit into the school’s broader AI strategy. Emphasize: this is a learning leadership role, not a tech support role. 2. Recruitment: • The characteristics you’re looking for (NOT just "the most tech-savvy person" — also: good listeners, trusted by colleagues, willing to be vulnerable about their own learning curve) • Application or nomination process (keep it simple) • Selection criteria with a brief rubric • A recruitment email that makes the role sound appealing, not overwhelming 3. Training and onboarding: • An initial training session outline (half-day or 2 hours) covering: AI tool proficiency, coaching skills, common faculty concerns and how to respond, the school’s AI policy, and boundaries of the role • Ongoing monthly touchpoints: what champions discuss, share, and learn together 4. The champion’s role in practice: • 5–7 specific activities champions do (e.g., monthly drop-in office hours, "AI Quick Win" emails to their team, co-planning a lesson with a reluctant colleague, curating a prompt library, observing and sharing what’s working) • A suggested time commitment (be realistic — this can’t be a full additional job) • What champions should NOT be expected to do (tech troubleshooting, enforcing policy, being the only AI resource) 5. Measurement: How you’ll know the program is working: • 3–4 metrics to track (colleague confidence scores, adoption rates, help request volume, qualitative feedback) • A mid-year check-in process with champions to adjust the program 6. Sustainability: How the program evolves in year 2 and beyond as AI becomes more mainstream. Include an exit ramp for when the role is no longer needed as a separate position.

You are a school administrator at [SCHOOL NAME] planning a parent information evening about the school’s approach to AI. Parents have been [DESCRIBE THE CURRENT VIBE, e.g., asking lots of questions, concerned about cheating, enthusiastic and wanting more, confused about the school’s stance, divided between pro-AI and anti-AI camps]. Event parameters: • Format: [e.g., in-person, hybrid, virtual] • Expected attendance: [NUMBER] • Length: [e.g., 60–90 minutes] • Presenters: [e.g., head of school, tech director, a few teachers, a student panel] Design a complete parent evening plan: 1. Pre-event: • Invitation email (compelling, not clinical — make parents WANT to come) • A brief pre-event survey (3–4 questions) to understand what parents most want to know • A "What to Know Before You Come" one-pager that gives parents baseline context so the evening isn’t spent on AI 101 2. Event agenda with timing: • Opening (5 min): A live demonstration that shows AI in action in a way that surprises and engages (suggest a specific demo — e.g., give the AI a student essay and show how it can provide feedback, or generate a differentiated worksheet in real-time). This should make parents go "oh, I see why this matters." • School’s approach (10–15 min): Present the school’s AI philosophy, policy overview, and what students are actually experiencing. Include a "what we DO" and "what we DON’T do" list. • Teacher panel (15 min): 2–3 teachers share specific, concrete examples of how they’re using (or limiting) AI in their classrooms. Provide them with talking points and a prep guide. • Student voices (10 min, optional): 2–3 students share their honest perspective on AI — what’s helpful, what’s tempting, what they wish adults understood. (This is the most powerful segment if you can do it.) • Interactive Q&A (20–25 min): Structured to avoid the "one angry parent monopolizes the mic" problem. Use submitted questions, table discussions, or a moderated format. Include pre-prepared answers for the hardest questions. • Closing (5 min): One key takeaway, resources for parents, and an invitation to stay involved. 3. Post-event: • Follow-up email with slides, resources, and a recording (if hybrid/virtual) • A "Talk to Your Child About AI" tip sheet parents can use at home • An FAQ document addressing the top 10 questions from the evening The entire event should leave parents feeling: informed, reassured that the school is thoughtful (not reckless or restrictive), and empowered to have better conversations with their kids about AI.
CATEGORY 3

AI Tool Evaluation and Vendor Assessment

You are a technology director at [SCHOOL NAME] building a reusable evaluation rubric for assessing AI tools. The rubric should be usable by a cross-functional team (IT, teaching faculty, administration, data privacy officer) to consistently evaluate any AI tool under consideration. School priorities for AI tools: [LIST YOUR PRIORITIES, e.g., student data privacy, ease of use for non-technical teachers, curriculum alignment, accessibility/UDL compliance, cost-effectiveness, integration with existing systems (Google Workspace, Canvas, etc.), multilingual support, vendor stability] Create a comprehensive AI Tool Evaluation Rubric: 1. Evaluation criteria (10–12 categories): For each criterion, provide: • The criterion name and a 1-sentence definition • A 4-level scoring scale (1 = Unacceptable, 2 = Below expectations, 3 = Meets expectations, 4 = Exceeds expectations) with specific descriptors for each level • Weight (High / Medium / Low priority) — adjustable based on the school’s priorities Suggested criteria categories: • Data privacy and security • Alignment with learning objectives • Teacher usability and onboarding time • Student experience and accessibility • Integration with existing tech stack • Content accuracy and bias mitigation • Vendor transparency and support • Cost and licensing model • Scalability across divisions/subjects • Evidence of efficacy (research base) • Cultural sensitivity and multilingual support • AI model training practices (does it train on student data?) 2. Scoring matrix: A blank table format where a reviewer can score the tool across all criteria and calculate a weighted total. 3. Decision thresholds: What total score leads to each decision: • Auto-approve for pilot • Approve with conditions • Needs further evaluation • Do not proceed 4. Pilot protocol: If a tool passes evaluation, what does a responsible pilot look like? Include: duration, scope (which teachers/students), data to collect, success criteria, and go/no-go decision process. 5. Quick-screen checklist: A 5-question initial screen that determines whether a tool even warrants the full evaluation (saves time on obviously inappropriate tools): • Does the vendor have a data processing agreement? • Does it comply with our data protection framework? • Does it train on user data? • Is it age-appropriate for our students? • Does it solve a problem we actually have?

You are a technology director at [SCHOOL NAME] preparing for a vendor demonstration of [TOOL NAME], an AI tool designed for [TOOL PURPOSE, e.g., adaptive learning, writing feedback, lesson planning, student assessment, administrative automation]. What you already know about the tool: [DESCRIBE WHAT YOU’VE SEEN — e.g., website review, free trial, colleague recommendation, conference demo] Your school’s specific needs: [DESCRIBE THE PROBLEM YOU’RE TRYING TO SOLVE] Prepare a complete vendor demo guide: 1. Pre-demo research checklist: 7–10 things to look up before the demo (terms of service, privacy policy, SOC 2 status, pricing model, customer reviews from other schools, published research, known limitations, recent news about the company). 2. Demo agenda request: A brief email to the vendor asking them to structure the demo around your priorities (not their standard pitch). Include 3–4 specific scenarios you want to see (e.g., "Can you show how a 6th grade teacher with 25 students would use this for a persuasive writing unit?" or "Can you demonstrate what happens when a student enters personal information?"). 3. Question bank organized by domain: Data and privacy (5–7 questions): • Where is our data stored? Which jurisdiction? • Is student data used to train your AI models? • What happens to our data if we cancel the contract? • Can you provide a Data Processing Agreement compliant with [APPLICABLE LAW]? [Continue with specific, probing questions] Pedagogy and effectiveness (5–7 questions): • What evidence do you have that this tool improves learning outcomes? • How was the tool developed? Were educators involved in design? • How does it handle content accuracy? What’s the error rate? [Continue] Implementation and support (5–7 questions): • What does onboarding look like for a school our size? • What ongoing training and support is included? • What’s your average response time for support tickets? [Continue] Business and sustainability (4–6 questions): • How long has the company been operating? • What’s your funding situation and runway? • What happens to our data and access if you are acquired or shut down? [Continue] 4. Red flag watchlist: 8–10 things to watch for during the demo that should trigger caution (e.g., vendor can’t answer data questions, claims "100% accuracy," won’t share a DPA, pricing is opaque, demo only shows best-case scenarios). 5. Post-demo scoring: A quick evaluation form the team can complete within 24 hours of the demo.

You are a technology director at [SCHOOL NAME] designing a pilot program for [TOOL NAME], an AI tool that [BRIEF DESCRIPTION OF WHAT IT DOES]. Pilot parameters: • Duration: [e.g., 6 weeks, one quarter, one semester] • Participants: [e.g., 5 teachers across 3 departments, 2 grade-level teams, one full division] • Students affected: approximately [NUMBER] • Cost during pilot: [FREE TRIAL / DISCOUNTED / FULL PRICE] Design a complete pilot framework: 1. Pilot goals: 3–4 specific, measurable questions the pilot aims to answer (e.g., "Does this tool reduce teacher time spent on [task] by at least 30%?" or "Do students find the feedback helpful and actionable?" or "Can the tool integrate with Canvas without IT intervention?"). 2. Participant selection and preparation: • How to select pilot teachers (criteria: mix of tech comfort levels, subject areas, grade levels) • Onboarding session plan (what do participants need before they start?) • Expectations document: what they commit to (minimum usage, data logging, feedback) and what they can expect (support, no judgment, voice in the decision) 3. Data collection plan: • Quantitative: What metrics to track and how (usage data from the tool, time-on-task measurements, student performance data, adoption rate) • Qualitative: Teacher experience surveys (provide 5–7 questions), student feedback (provide 3–5 age-appropriate questions), informal check-in protocols • Schedule: When to collect data (baseline, midpoint, end) 4. Support structure during pilot: • Weekly check-in format (10-minute standing meeting or async update) • Troubleshooting protocol (who to contact for tech issues vs. pedagogical questions) • A shared space for participants to share tips, wins, and frustrations 5. Go/No-Go decision framework: • Clear success criteria mapped to each pilot goal • Deal-breakers that trigger an automatic "no-go" (e.g., data breach, unresolvable privacy concern, consistent negative student experience) • A "go with modifications" pathway for tools that show promise but need adjustments • Decision meeting agenda: who’s in the room, what data is presented, how the decision is made 6. Communication plan: • How to announce the pilot to the broader community (brief, transparent, non-committal) • How to share results regardless of the decision (model transparency) • If approved: rollout timeline and scaling plan • If rejected: how to communicate to participants and the vendor

You are a technology director at [SCHOOL NAME]. A [REQUESTER, e.g., English department, elementary team, counseling office, registrar] has asked for a recommendation on the best AI tool for [USE CASE, e.g., writing feedback, lesson differentiation, report card comment drafting, student scheduling, language learning support, quiz generation]. Their specific needs: [DESCRIBE WHAT THEY NEED THE TOOL TO DO — be as specific as possible] Their constraints: [e.g., budget, tech environment, student age range, privacy requirements, integration needs, language requirements] Create a structured comparison brief: 1. Market scan: Identify 4–6 tools that address this use case. For each, provide: • Tool name and vendor • One-sentence description of what it does • Pricing model (free / freemium / per-user / site license) • Target audience (designed for K–12 vs. adapted from enterprise vs. general consumer AI) 2. Comparison matrix: A table comparing all tools across 6–8 criteria relevant to this specific use case. Include: • Feature match for the requester’s needs • Data privacy posture • Ease of setup and use • Integration with [SCHOOL’S TECH STACK] • Cost for your school size • Vendor maturity and support 3. Top recommendation: Your top 1–2 picks with a clear rationale. Address tradeoffs honestly (“Tool A is better on privacy but Tool B has a significantly better teacher experience”). 4. Implementation notes: For your recommended tool(s): • Estimated setup time • Training needs • Suggested pilot scope before full adoption • Known limitations to communicate to the team 5. Alternatives if the top pick doesn’t work: "If Tool A doesn’t pass our privacy review, consider Tool B because..." Keep the brief to 2 pages. Write it for a department chair who is smart but not technical — clear language, visual comparison table, actionable recommendation.

You are a technology director at [SCHOOL NAME]. You need to sunset [TOOL NAME], an AI tool currently used by [WHO USES IT, e.g., 40 teachers for lesson planning, all high school students for writing feedback, the counseling office for scheduling]. Reason for sunsetting: [DESCRIBE — e.g., vendor is shutting down, data privacy concern identified, contract not renewed due to cost, better alternative available, tool no longer meets needs, compliance issue] Timeline: [WHEN IT NEEDS TO BE GONE] Create a complete sunset and migration plan: 1. Impact assessment: • Who is affected (list all user groups) • What workflows depend on this tool (be specific) • What data lives in the tool that needs to be exported or archived • What will break if we just turn it off tomorrow (identify dependencies) 2. Data migration: • What data needs to be exported (and in what format) • Step-by-step export instructions for users • Deadline for data export • What happens to data that isn’t exported (vendor’s data deletion policy) • Where exported data should be stored 3. Replacement plan: • If a replacement tool is identified: migration timeline and onboarding plan • If no replacement yet: interim workarounds for each affected workflow • If no replacement needed: how to adjust workflows to work without the tool 4. Communication sequence: • Email 1 (4+ weeks out): Announce the sunset, explain why (honestly), timeline, and what’s coming next • Email 2 (2 weeks out): Practical instructions for data export, replacement tool details, training dates • Email 3 (final week): Last call for data export, help desk availability, go-live date for replacement • Provide tone guidance for each: transparent, empathetic, solution-focused 5. Support plan: • Help desk hours during transition • 1:1 support for heavy users or those who struggle with change • A quick-reference guide for the replacement tool (or the new workflow) 6. Post-sunset review: 2–3 weeks after the tool is gone, check in with affected users. What’s working? What’s not? What did we learn about tool adoption and dependency?
CATEGORY 4

Meeting Agendas and Strategic Planning

You are the head of school or technology director at [SCHOOL NAME] preparing a presentation for the board of trustees on the school’s AI strategy. Board context: • Board composition: [e.g., mix of business executives, parents, alumni, education professionals] • Board’s current understanding of AI in schools: [e.g., basic awareness, some sophistication, varies widely] • Board’s likely concerns: [e.g., reputational risk, competitive positioning, liability, cost, academic rigor] • Time allocated: [e.g., 20-minute presentation + 10-minute Q&A] What you want the board to walk away with: [e.g., "Confidence that the school is leading responsibly," "Approval for an AI governance budget," "Understanding of our competitive positioning," "Support for the AI policy"] Create a complete board presentation plan: 1. Slide-by-slide outline (10–14 slides): Slide 1: Title and framing statement (one sentence that positions AI in education as an opportunity, not just a risk) Slide 2: "The landscape" — what AI in K–12 education looks like right now (3–4 data points that resonate with a business-minded board) Slide 3: "What our families and students are experiencing" — make it real and personal, not abstract Slide 4–5: "Our strategy" — the school’s AI philosophy and the 3–4 pillars of your approach Slide 6: "What we’ve done" — actions taken to date (policy, PD, tool vetting, governance) Slide 7: "What our teachers are doing" — 2–3 concrete examples of AI in the classroom (make the board proud) Slide 8: "How we protect students" — data privacy, academic integrity, and ethical guardrails Slide 9: "How we compare" — where [SCHOOL NAME] stands relative to peer institutions (competitive positioning) Slide 10: "What’s next" — the 12-month roadmap with milestones Slide 11: "What we need from the board" — specific asks (budget, policy approval, strategic guidance) Slide 12: Discussion questions 2. For each slide, provide: the key message (one sentence), 3–4 bullet points, and a speaker note (what you actually say, not what’s on the slide). 3. Anticipated board questions (8–10) with prepared responses. Include: • "What are other schools doing?" (competitive question) • "What’s the liability exposure?" (risk question) • "How do we know students are still learning?" (academic rigor question) • "What does this cost?" (budget question) • "What if a teacher misuses AI?" (governance question) 4. Leave-behind: A 1-page executive summary the board can take home.

You are facilitating an AI strategic planning retreat for the leadership team at [SCHOOL NAME], a [SCHOOL TYPE]. Participants: [LIST WHO WILL BE THERE, e.g., head of school, division heads, tech director, academic dean, CFO, counseling director, librarian, 2–3 teacher leaders] Retreat parameters: • Duration: [e.g., half-day (4 hours), full day (6–7 hours)] • Location: [ON-CAMPUS / OFF-SITE] • Current state: [DESCRIBE — e.g., "We have a draft policy but no aligned strategy," "We’re starting from scratch," "We have pockets of innovation but no coordination," "We need to move from reactive to proactive"] • Desired outcome: [WHAT SHOULD EXIST AFTER THIS RETREAT, e.g., a prioritized 12-month action plan, alignment on philosophy, role clarity, a decision on specific tools] Design a complete retreat agenda: 1. Pre-retreat preparation: • A pre-read document (1–2 pages) that gives all participants shared context: current state of AI at the school, what peer schools are doing, key decisions that need to be made • A pre-retreat survey or reflection prompt for each participant (3–4 questions: biggest opportunity, biggest risk, what they most want to resolve) 2. Detailed agenda with timing, facilitator instructions, and materials for each block: Block 1 — Grounding (30–45 min): Get everyone on the same page. Include a brief "state of AI" overview, share pre-retreat survey themes, and do a quick hands-on experience where all participants use an AI tool together (specify the tool and prompt). Block 2 — Vision alignment (45–60 min): Facilitate a discussion on the school’s AI philosophy. Use a structured protocol (provide specific facilitation instructions). Aim to produce: a shared statement of what AI-enhanced education looks like at [SCHOOL NAME] in 3 years. Block 3 — Gap analysis (30–45 min): Where are we now vs. where we want to be? Use a framework (provide one) that maps current state against the vision across 4–5 dimensions (policy, PD, tools, culture, measurement). Block 4 — Priority setting (45–60 min): From the gap analysis, identify the top 3–5 priorities for the next 12 months. Use a structured prioritization exercise (impact vs. effort matrix, dot voting, or another facilitation tool — provide specific instructions). Block 5 — Action planning (45–60 min): For each priority, define: the owner, the first three steps, the timeline, the resources needed, and how success will be measured. Provide a planning template. Block 6 — Closing (15–20 min): Each participant shares one commitment. Facilitator summarizes decisions and next steps. Schedule the first follow-up check-in. 3. Post-retreat deliverables: • A summary document (drafted from retreat notes) sent within 48 hours • A 12-month AI action plan formatted for the board • A communication plan for sharing the strategy with the broader faculty

You are the chair of the AI Governance Committee at [SCHOOL NAME]. The committee meets [FREQUENCY, e.g., monthly] for [DURATION, e.g., 60 minutes]. You need a reusable agenda template that keeps meetings productive and ensures nothing falls through the cracks. Committee composition: [LIST MEMBERS AND ROLES] Create: 1. A standing agenda template with timing: • Opening (5 min): Quick wins and celebrations since last meeting (what’s going well with AI at the school) • Policy and compliance update (10 min): Any policy issues, incidents, or needed revisions. Include a standing prompt: "Any new AI-related concerns from students, faculty, or parents this month?" • Tool review queue (15 min): New tool requests to evaluate, status of ongoing pilots, and any tools flagged for review. Include a quick-decision framework for simple requests vs. items that need full evaluation. • Professional development update (10 min): What PD has been delivered, what’s upcoming, faculty feedback themes. • Strategic item (15 min): One focused discussion topic per meeting (rotated from a planning calendar). Examples: reviewing the academic integrity addendum, planning the parent evening, evaluating pilot results, discussing emerging AI trends. • Action items and assignments (5 min): Review new action items, confirm owners and deadlines. 2. A meeting preparation checklist for the chair: • What to gather before the meeting (tool requests, incident reports, PD data, etc.) • Who to check in with (tech team, division heads, counseling) for updates • The strategic topic and any pre-reading to distribute 3. A meeting notes template: • Attendees present/absent • Key decisions made (with rationale) • Action items (task, owner, deadline) • Items deferred to next meeting • Communication needed (what to share with the broader community and who sends it) 4. An annual planning calendar: Map the 12 monthly meetings to strategic priorities. Example: • September: Review and update AI policy for new school year • October: Evaluate tool requests from fall planning • November: Mid-semester faculty feedback review • [Continue for all 12 months] 5. A "meeting health check" survey: 3–4 questions the committee answers quarterly to evaluate whether meetings are productive, focused, and worthwhile.

You are a technology director or academic dean at [SCHOOL NAME] conducting an annual review of the school’s AI integration efforts. Data available: • Tools adopted this year: [LIST] • Policy status: [DESCRIBE — e.g., adopted in October, revised in February, no formal policy yet] • PD delivered: [DESCRIBE — sessions, attendance, topics] • Faculty survey data: [PASTE OR SUMMARIZE RESULTS] • Student survey data: [PASTE OR SUMMARIZE IF AVAILABLE] • Incidents or challenges: [DESCRIBE — e.g., academic integrity violations, tool failures, parent complaints, privacy concerns] • Budget spent on AI: [AMOUNT AND WHAT IT COVERED] • Wins and successes: [LIST] Generate a comprehensive Annual AI State Report: 1. Executive summary (1 paragraph): High-level assessment of the year — where the school started, what was accomplished, and the overall trajectory. 2. Adoption and usage metrics: • Tools in use (approved vs. unapproved/shadow IT) • Faculty adoption rates and engagement levels • Student usage patterns (if data available) • Comparison to goals set at the start of the year 3. Policy and governance: • Policy milestones achieved • Governance committee effectiveness • Incidents and how they were handled • Policy gaps identified for next year 4. Professional development: • What was offered and participation rates • Faculty confidence shift (pre/post survey data) • Most requested topics for next year • Effectiveness assessment: did PD translate to classroom practice? 5. Impact on teaching and learning: • Evidence of positive impact (specific examples, data) • Concerns or unintended consequences observed • Student voice: what students say about AI in their learning 6. Financial review: • Total spend on AI tools, PD, and related infrastructure • ROI assessment (qualitative if not quantitative — time saved, satisfaction improved, etc.) • Budget recommendation for next year 7. Peer benchmarking: How [SCHOOL NAME]’s AI integration compares to peer institutions (based on published reports, conference learnings, network conversations). 8. Recommendations for next year: 5–7 prioritized recommendations with rationale, organized as: • Quick wins (implement in Q1) • Strategic priorities (semester-long initiatives) • Exploratory (investigate and decide by mid-year) Format as a professional report suitable for the board, accreditation files, or strategic planning reference.

⚠️ NOTE: If the incident involves a data breach or potential regulatory violation, engage your school’s legal counsel and data protection officer immediately. This framework structures your response — it does not replace legal guidance. You are a school administrator at [SCHOOL NAME] who needs to develop an AI incident response plan. This should be a reusable framework your team can activate when something goes wrong. Create a comprehensive AI Incident Response Plan: 1. Incident classification: Define 4 severity levels with examples: • Level 1 — Minor: Isolated misuse, no data exposure, educational response sufficient (e.g., a student uses AI on an assignment without permission) • Level 2 — Moderate: Pattern of misuse, minor policy violation, requires investigation (e.g., multiple students using an unauthorized tool, a teacher inadvertently shares student data with an AI tool) • Level 3 — Significant: Data exposure, public attention, or widespread misuse (e.g., student PII entered into an AI tool, a parent complaint goes public, media inquiry) • Level 4 — Critical: Confirmed data breach, regulatory notification required, legal liability (e.g., confirmed unauthorized access to student data, mandated breach notification) 2. Response protocol for each level: • Immediate actions (first 2 hours) • Investigation steps (24–72 hours) • Communication plan (who is told what, in what order, by whom) • Resolution and documentation • Post-incident review 3. Communication templates: • Internal notification to leadership (brief, factual) • Parent communication (transparent, calm, action-oriented) • Faculty communication (clear guidance on what to do/not do) • Media statement (if needed — brief, non-defensive, focused on student wellbeing) 4. Roles and responsibilities: Who does what during an incident: • Incident commander (typically head of school or designee) • Technical response (IT/tech director) • Communications lead • Legal/privacy liaison • Student/family support (counseling) 5. Post-incident review template: A structured debrief to be conducted within 2 weeks of resolution: • What happened (factual timeline) • What we did well • What we’d do differently • Policy or procedure changes needed • Communication to the community about what was learned 6. Prevention recommendations: For each incident level, suggest 2–3 proactive measures that reduce the likelihood of recurrence. Format this as a reference document that can live in the school’s crisis management binder alongside other emergency plans.