Part seven of seven in the Artificial Intelligence in Education series, beginning with AI Did Not Break Education. It Exposed It. Source cutoff: Oct 30, 2026.
Running a technology business taught me that restoring service and fixing the system are different jobs. The immediate repair matters. The durable work is to understand what happened, document it, assign responsibility, change the process, and check whether the problem returns.
Universities face the same temptation with artificial intelligence. A policy is issued, an approved-tool list is published, faculty attend a workshop, and the institution can say that it responded. The environment changes again before the response has been evaluated.
The university needs a learning system, not a policy snapshot.
That system should move quickly, protect disciplinary judgment, coordinate shared risks, support faculty, listen to students who are not enthusiasts, and scale only what produces meaningful results at acceptable cost.
The short answer
Artificial-intelligence governance should be recurring and federated. The institution should set a narrow floor for shared risks and services, while departments and instructors own learning goals, task design, and evidence.
Usage, attendance, completion, satisfaction, mastery, transfer, judgment, belonging, employment relevance, cost, and risk are different outcomes. A serious pilot chooses the measures that answer its decision.
Responsible speed means clear experiments, visible ownership, student and faculty participation, stop conditions, and the ability to remove a tool when results disappoint.
The university needs a learning loop
The technology will not wait for a committee cycle, but widespread use does not make it educational or safe. A university needs a recurring loop that connects observation, experiment, evidence, decision, and revision.
Begin with a problem rather than a tool. Where are students failing to learn? Where is faculty work consumed by a repetitive process? Where does access break down? Which new professional capability belongs in the curriculum?
Then test a defined design, measure the outcomes that matter, review cost and harm, and decide whether to stop, revise, or expand.
UNESCO, the U.S. Department of Education, and the National Institute of Standards and Technology all emphasize human purposes, lifecycle governance, measurement, and review.[1][2][3] Their frameworks provide a vocabulary. The university still has to build the operating system.
Federated does not mean fragmented
A literature seminar, nursing clinical, engineering laboratory, admissions office, research group, and financial-aid operation do not share one learning objective or risk profile. Central rules detailed enough to control every use will be slow and educationally tone-deaf.
Pure local autonomy creates a different failure. Students receive conflicting instructions. Departments duplicate procurement and security work. Privacy, accessibility, integrity, and appeal depend on who teaches the course. The people closest to the learning problem may lack the legal, technical, or purchasing expertise to assess a vendor.
A federated model divides responsibility:
The institution sets minimum requirements for privacy, security, accessibility, disclosure, record handling, review, appeal, procurement, and incident response.
Shared teams evaluate vendors, negotiate contracts, maintain services, support measurement, and help with implementation.
Programs define disciplinary capabilities, decide where independent performance matters, and design assessment for the capabilities they promise.
Instructors state course- and task-specific rules tied to the learning purpose.
Students receive clear guidance, workable alternatives, access to their records, and a way to question a decision.
Centralize shared protections and capabilities. Keep educational judgment close to the discipline and learner.
The difficult work is local
A central policy, license, or workshop is comparatively cheap to distribute. Redesigning a course requires time, disciplinary knowledge, examination of student work, and repeated correction. Once again, the scalable response is easier than the high-quality response.
A review of 191 articles on changing undergraduate STEM instruction found that sustained, systemic, and locally responsive approaches were more promising than simple dissemination.[4] A tool demonstration or policy email does not redesign a course.
Faculty need protected time to identify the learning objective, test the tool, redesign assignments, examine student work, develop alternatives, and revise. They need instructional and technical help during implementation and peers with whom to compare failures as well as successes.
Budget for and recognize this labor. Treating adaptation as free work added to existing responsibilities produces uneven adoption, hidden shortcuts, and burnout.
Staff in procurement, security, privacy, accessibility, libraries, student support, teaching centers, and institutional research are part of the educational system, not peripheral compliance functions.
Use can spread faster than understanding
Surveys from Ithaka S+R and EDUCAUSE document substantial experimentation alongside uneven confidence, policy awareness, institutional support, strategy, and measurement.[5][6] Faculty and staff can use tools actively without knowing whether that use improves learning or work.
Support should move from awareness to application, verification, judgment, and leadership, with expectations that differ by role and discipline.
Approved is not effective
An approved-tool review should examine data use, retention, model training, subprocessors, security, accessibility, intellectual-property terms, interoperability, pricing risk, and exit options. Federal education-record guidance shows why control, authorized use, and redisclosure matter when student information enters an online service.[7]
Approval means the institution considers the tool acceptable for certain uses under stated conditions. It does not show that the tool improves learning or belongs in every course.
Pedagogical approval requires evidence tied to a learning objective. Operational approval requires evidence tied to service quality, workload, cost, and risk.
The plan for leaving a vendor belongs in the initial decision. Institutions should know how data will be deleted, work exported, integrations removed, and courses supported if prices rise, terms change, or performance disappoints.
Access and inclusion must be tested
Artificial intelligence can expand access through explanation, translation, alternative formats, and flexible support. It can also create barriers through price, devices, inaccessible interfaces, language performance, account requirements, and assignments built around a tool some students cannot or will not use.
Jisc’s 2025 student work found recurring concerns about clarity, access, ethics, and preserving human connection.[8] These are design questions, not a box to check after launch.
Every pilot should test accessibility, accommodation pathways, device and connectivity constraints, and outcomes for relevant student groups. Students using an accommodation should not have to disclose more personal information to use the system.
A premium tool limited to one program, a redesign available only in small seminars, or a mentoring system used mainly by students who already know how to ask can improve the average while widening the gap.
Integrity requires evidence and due process
Universities want a reliable way to identify work produced improperly with artificial intelligence. Detection tools offer a tempting shortcut.
Technical evaluations have found serious performance limits, including false positives for some non-native English writing in the detectors tested.[9][10] Treat a detector or proctoring flag as a lead, not proof of misconduct.
A defensible process requires supporting evidence, human review, notice, an opportunity for the student to respond, and an appeal.
The deeper response is assessment design. Clear task rules, explanation, new cases, process evidence, and appropriate independent checks provide better educational information than a probability score carrying a disciplinary decision alone.
Define success before the pilot
Usage, attendance, completion, and satisfaction are easy to count. None alone shows that a course improved, students learned, or the institution saved money without weakening mentoring or shifting verification work elsewhere.
First name the function being changed, such as instruction, assessment, advising, transition to work, research support, or administration. Then choose only the outcomes that can change the decision: learning, retention, transfer, judgment, access, completion, time, cost, incidents, or vendor dependence.
No pilot needs every measure. It needs the measures that matter to the decision. Data collected without a decision become paperwork and surveillance.
A minimum pilot protocol
Before launch:
Name the problem, the population affected, and the protected human-learning experiences.
Establish a baseline and a credible comparison where practical.
Document the tool, version, data flow, retention, contract terms, accessibility review, human owner, participant guidance, support, alternatives, review, and appeal.
Choose a small set of decision-relevant outcomes, including subgroup effects where they matter, and define the result that will cause the institution to stop, revise, or scale.
One useful experiment would require artificial-intelligence use in a course and evaluate the student’s workflow, judgment, and verification rather than only the answer.[13] The university should compare what those students can later do with a credible alternative.
After the pilot, review the evidence with students, faculty, staff, risk owners, skeptics, and non-users. Scale the component supported by the evidence, not the enthusiasm surrounding it.
The University of Sydney’s separation of secure and open assessments and the University of Michigan’s committee structure provide useful examples of institutions dividing the problem into manageable parts.[11][12] Their value is the architecture, which each institution still must evaluate.
Stop conditions show seriousness
Institutions often define the conditions for launching an initiative and leave continuation to momentum. Responsible experimentation asks the opposite question: what result will make us pause, redesign, or stop?
A stop condition may involve weaker learning, an accessibility failure, a privacy or security incident, disproportionate harm, unmanageable verification time, cost beyond the expected value, unreliable performance, or inability to leave the vendor without disrupting students.
Thresholds should match consequence. A brainstorming aid and a system influencing admission, discipline, clinical education, or financial support do not deserve the same evidence burden.
Reversibility is part of learning. A university that cannot remove a tool, change a policy, or admit that a pilot failed is implementing first and rationalizing later.
Trust is an operating architecture
Trust does not come from saying that artificial intelligence will be human-centered. It comes from observable responsibilities and controls.
Students and faculty should know what a system does, what information it uses, what decision it influences, who reviews it, how an error is corrected, and where an appeal goes. They should know whether participation is required, what alternative exists, and how long information is retained.
The institution should publish decision criteria, owners, review cadence, and what it learned. Transparency will not eliminate disagreement. It gives disagreement something real to address.
Central governance becomes theater when it produces forms without evidence, responsibility, or service. Local innovation becomes unmanaged risk when it relies on private workarounds. A learning institution needs permission to experiment and an obligation to explain.
What rapid adaptation should mean
The best studies still point in different directions. The conclusion colleges can act on is that the world outside has changed.
Information and competent-looking assistance are cheaper. Finished work is weaker evidence of independent capability. Colleges must reconsider knowledge selection, assessment, apprenticeship, workflow design, and institutional responsibility.
Adapting quickly does not mean acting carelessly. It means replacing the slow search for a permanent policy with a faster cycle of clear purpose, disciplined trials, credible evidence, shared learning, and revision.
The university still has valuable work to do. It can organize sustained attention, serious peers, mentorship, direct experience, knowledge, judgment, and responsibility. To preserve those purposes, it must apply the same standard to itself that it applies to students: show the work, learn from feedback, revise the model, and demonstrate what changed.
Questions, corrections, or disagreements are welcome. You can reach me directly at dave@aworkingmodel.com.
Sources
1. UNESCO, “Guidance for Generative AI in Education and Research.” Published 2023; updated 2026. International guidance on privacy, inclusion, capacity, human oversight, and educational design.
2. U.S. Department of Education, “Artificial Intelligence and the Future of Teaching and Learning.” 2023. Policy guidance emphasizing educational goals, human involvement, trust, and responsible use.
3. National Institute of Standards and Technology, “AI Risk Management Framework and Generative AI Profile.” Released 2023 and 2024. Voluntary cross-sector lifecycle guidance.
4. Henderson, Beach, and Finkelstein, “Facilitating Change in Undergraduate STEM Instructional Practices.” 2011. Review of 191 articles; older and STEM-focused, with uneven implementation evidence.
5. Ithaka S+R, “Generative AI and Postsecondary Instructional Practices.” 2024. U.S. instructor survey with 2,654 respondents in the generative-artificial-intelligence block; low response rate, sample skew, and self-report limit prevalence claims.
6. EDUCAUSE, “The Impact of AI on Work in Higher Education.” 2026. Survey of 1,960 qualifying higher-education respondents; a professional, self-selected sample rather than a representative institutional census.
7. U.S. Department of Education Student Privacy Policy Office, FERPA FAQ on using online tools in a course. Current guidance on institutional control, authorized use, and redisclosure; application depends on the facts.
8. Jisc, “Student Perceptions of AI 2025.” 2025. Discussion groups with 173 further- and higher-education students in the United Kingdom; useful for themes rather than prevalence.
9. Weber-Wulff et al., “Testing of Detection Tools for AI-Generated Text.” 2023. Technical evaluation of then-current detection tools; models and detectors continue to change.
10. Liang et al., “GPT Detectors Are Biased against Non-Native English Writers.” 2023. Study of a limited detector set and writing sample; later tools may differ.
11. University of Sydney, “New AI Assessment Policy.” 2024, implemented from 2025. Institution-authored description of secure and open assessment categories.
12. University of Michigan, “Generative AI Committee Reports.” 2026. Institution-authored planning across education, research, operations, and governance
13. Tyler Cowen, “Tyler Cowen’s Radical AI University.” Chronicle of Higher Education interview, Oct 29, 2026. Expert proposal for an AI-only course and process-based assessment.
.