A school district enables a new GenAI plugin district-wide overnight. What should the auditor emphasize?
Select an answer to reveal the explanation.
Short Explanation
Overnight district-wide flips are like opening every classroom door at once with a new brain in the room. Phase the rollout, tell people, and put it through change control. Equal access does not mean zero governance.
Full Explanation
In a school district, enabling a GenAI plugin overnight across every school is a production capability launch, not a casual productivity tweak. The correct emphasis is phased rollout, stakeholder communication, and formal change control so teaching practice, student data flows, and support readiness move together. Phasing limits blast radius if the plugin mishandles PII, invents unsafe content, or breaks instructional workflows; communication sets expectations for teachers, parents, and IT; change control creates an auditable record of what changed, when, and how to roll back. Deploying in phases with brief notices to teachers addresses blast radius and communication but fails by concept: without formal change control, the rollout leaves no auditable record of what changed, when, or how to roll back, which is the enforcement piece auditors specifically require. Applying standard productivity software update procedures for a district-wide AI capability release fails because a routine update path for student-data-touching AI does not provide the phased rollout and stakeholder communication a launch of this scope requires, regardless of how the ticket is labeled. Requiring comprehensive teacher training and signed acceptable use acknowledgments before classroom activation fails because individual teacher readiness steps, even when thorough, still bypass the phased rollout and coordinated stakeholder communication a district-wide capability launch requires, and leave the enterprise change record to informal activation rather than formal change control. Exam caveat: AAIA-style questions often contrast speed-to-access narratives with change management specific to AI; "equal access" and "not production" are distractors that sound citizen-friendly or low-risk but weaken governance. Operational check: verify a district change record for the GenAI plugin with phased cohorts, communication plan, rollback criteria, and post-launch monitoring before full enablement—not a single big-bang toggle.