Last fact-check: May 25, 2026
In February 2025, California State University announced that it had purchased ChatGPT Edu for 460,000 students and called itself the nation’s first AI-empowered university system. Fifteen months later, the system’s own data showed that 0.7 percent of those students had completed the training meant to come with the deal. The contract was renewed anyway.
If you are the chancellor, provost, CIO, or board member of a state university system watching this unfold and trying to figure out what to do differently — SUNY, Texas, Florida, Virginia, Georgia, Michigan, anyone — this article is for you. It’s a counterfactual. It walks through the rollout CSU should have run, as a project plan, with the decisions named, the tradeoffs surfaced, the things that got cut, and the costs accepted. It’s not theoretical. It’s the specific work that would have produced a different outcome.
It’s part of Tygart Media’s free AI Literacy curriculum. The pillar article on the CSU literacy gap is here. The full curriculum is at tygartmedia.com/category/ai-literacy and is free to fork, adapt, embed, or distribute.
The starting position
You run a large public university system. Several million students total across multiple campuses. Your faculty are using AI in inconsistent ways. Your students are using AI almost universally without training. You have multiple vendors — OpenAI, Anthropic, Google, Microsoft — knocking on your door with institutional deals. You have a real budget constraint and a real timeline.
Three things you know going in: (1) AI is not going away, and pretending it is leaves your students worse-prepared than your peers’ students. (2) Just buying a product doesn’t change anything about teaching and learning. (3) Your faculty and student governance bodies will have opinions about whatever you do, and ignoring them is what CSU did, and you do not want what CSU got.
The project below is the work that produces a defensible rollout. It takes about fourteen months from initial decision to general access, which is slower than CSU’s six and faster than doing nothing for years. The reason it takes that long is that the procurement decision is the smallest part of the work. The pedagogical, governance, and training decisions are the work.
Month 1-2: The governance question, settled before anything else
Before any vendor conversations happen, decide who actually decides. This is the step CSU skipped and never recovered from.
Set up a Generative AI Governance Committee with binding authority — not advisory authority — over the rollout. Composition matters. CSU’s existing committee had students and faculty but no decision-making power; the Workforce Acceleration Board added later “makes no final policy or guidance decisions” by its own student representative’s admission. Avoid both failure modes by making this committee actually empowered.
Composition that works:
- Two faculty senate representatives, both with classroom teaching loads (not just administrators with faculty titles)
- One representative from your academic integrity office
- One representative from your campus IT or CIO’s office
- Two student government representatives, ideally one undergraduate and one graduate
- One representative from your faculty union, if you have one
- One representative from your staff union, if you have one
- One librarian (more important than people think — librarians have been the campus AI experts in many places already)
- One representative from your disability services office (AI use intersects significantly with accessibility)
- The provost or a vice provost, as chair
Twelve people. Empowered to recommend yes or no on the rollout. Empowered to set systemwide policy. Reports to the chancellor and the board.
The decision that needs to be made in months 1-2 isn’t which vendor. It’s whether this committee will be the body that owns the rollout. If governance is unclear, every later decision gets contested. If governance is clear, contested decisions get resolved.
The thing CSU cut: this kind of governance is slow and uncomfortable. It produces real disagreements that have to be worked through. Doing it well takes two months of meetings before anything visible happens. That’s the cost. The benefit is that everything that comes after is institutionally legitimate.
Month 3-5: The pedagogical question, before the procurement question
Before deciding what AI to buy, decide what you’re trying to accomplish with it. This is the order CSU reversed. They bought the product first and then tried to figure out what it was for.
The Generative AI Governance Committee should produce a written pedagogical framework that answers three questions:
What AI literacy should every graduate of this institution have? Not what they should be able to do with one specific product. What general competencies should they have, regardless of which AI tool they’re using? This becomes the basis for every curriculum decision downstream.
What’s the role of AI in our teaching mission? Tool? Subject of instruction? Both? Pedagogical assistant for faculty? Tutoring system for students? Research aid? The answer to this question shapes which features matter in any product you eventually buy.
What are our red lines? What uses of AI will not be permitted, regardless of student or faculty preference? Examples might include: AI grading of student work, AI evaluation of admissions, AI-only academic advising, AI tutoring without human oversight in mental health contexts. Naming the red lines early prevents pressure to cross them later.
The output of months 3-5 is a 10-20 page pedagogical framework document. Published. Open to comment. Discussed at faculty senate. Discussed at student government. Revised. Approved by the committee. Adopted by the board.
This document is what makes everything that follows defensible. When the vendor pitches a feature, you have a framework to evaluate it against. When a faculty member asks “why are we using this,” you have an answer. When a student asks “what am I supposed to learn about this,” you have an answer. When a legislator at a hearing asks “what’s your AI strategy,” you have a document to hand them.
The thing CSU cut: this is months of work before anything visible happens. It feels slow. It is slow. It also defines everything that comes next, which is why CSU’s “AI strategy” — when it had to be articulated to the Assembly Standing Committee on Higher Education — read as procurement justification rather than educational vision.
Month 6-7: The procurement question, with the framework in hand
Now you talk to vendors. But you have a framework. The framework tells you what to ask.
For every product on offer, the procurement evaluation needs to address:
Pedagogical fit. Does this product serve the framework, or does it require us to bend the framework to fit it? CSU’s deal was a general-purpose chatbot retrofitted as education technology. The faculty petition’s strongest line — “ChatGPT Edu is not educational technology, it is a general-purpose chatbot that is not designed, trained, or optimized for education” — was correct, and it was correct because the procurement happened without a framework to test the product against.
Data handling. What does the vendor do with student conversations? What are the defaults, and what are the opt-ins? Where is the data stored? How long is it retained? Under what circumstances can the institution access it? Under what circumstances can the vendor? Get answers in writing, in the contract, not in the sales deck.
Bias auditing. What testing has the vendor done for bias in their model? Are the results public? Will the institution have access to ongoing audit results? If the model produces biased output in a high-stakes context, what is the vendor’s response obligation?
Reliability and uptime. Public universities run on academic calendars. A vendor outage during finals week is a serious problem. What are the SLAs? What’s the institution’s recourse if they’re not met?
Exit and portability. If you decide to change vendors in two years, what happens to the student data? Can faculty migrate custom GPTs or projects to another platform? Are there contractual lock-in mechanisms that make switching prohibitively expensive?
Total cost. Not just the contract price. The implementation cost. The training cost. The ongoing support cost. The cost of the staff time you’ll need to allocate to managing the relationship. CSU’s $17 million looked like a single number. The real institutional cost was several multiples of that, mostly absorbed by faculty time that didn’t appear on any budget line.
Run an actual competitive evaluation. Multiple vendors. Real comparison against the framework. CSU’s own assistant vice chancellor told CalMatters that OpenAI was selected as the “least-costly option.” Cost matters, but cost-as-only-criterion is what produces “least costly option” decisions that don’t survive contact with the framework.
The procurement decision goes back to the governance committee for a recommendation, and from there to the chancellor and board.
The thing CSU cut: this evaluation takes time. The vendor wants to close. The board wants a headline. The competitive pressure feels real (“USC just signed a deal!”). Resisting that pressure is the job. The deals that get rushed are the deals that produce 0.7 percent training completion fifteen months later.
Month 8-9: Faculty preparation, before student access
Once a product is selected, faculty get it first. Not students. Faculty.
This is the inversion CSU got most wrong. CSU made the tool available to everyone at once. Faculty were expected to figure out how to teach with it in real time, with their students simultaneously using it in ways the faculty didn’t yet understand. The result was the 16 percent faculty training completion rate, which is bad, but it’s bad in the context of faculty being asked to do something genuinely impossible.
The sequence that works: faculty get the tool, get training on the tool, get pedagogical support for redesigning their courses around the tool, get a semester to actually do that redesign, and then students get access in the following term.
The faculty preparation phase needs three components:
Required training. Not voluntary. Required. Two to four hours, depending on the depth of integration expected. Tied to a stipend or course release, because asking faculty to do uncompensated training is asking for the result CSU got. If your faculty union is going to push back on required training, that’s a negotiation worth having explicitly rather than punting via a voluntary program nobody completes.
Course redesign support. Each instructor preparing to teach with AI gets one-on-one support from an instructional designer or AI literacy specialist. The conversation is specific to their course: what are your learning objectives, how does AI fit, what changes to your assessments make sense, what’s your syllabus language going to be. This is labor-intensive. It’s also the work that actually changes outcomes.
A model syllabus statement. Drafted by the governance committee, available for every faculty member to adopt or adapt. Specific enough to be useful. The fact that Cal Poly San Luis Obispo’s 200-policy crowdsourced repository exists is a damning artifact of CSU’s failure to provide this. The model statement doesn’t have to be the only allowed statement, but it needs to exist so that the default isn’t “every professor reinvents the wheel.”
The thing CSU cut: this phase. Entirely. They moved from procurement to general access with no faculty preparation step in between. The “AI Commons” hub was made available, but no required training happened, no course redesign support was systematic, no model syllabus statement was produced. The 16 percent faculty training completion rate is the predictable consequence.
Month 10-12: Pilot, before scale
Even with faculty prepared, full systemwide rollout shouldn’t be the next step. Pilot first.
Select a representative subset of courses across multiple campuses, disciplines, and course levels. Maybe 50-100 courses across the system. The instructors are the ones who completed faculty preparation and chose to participate. The students in those courses get AI access for that term. Everyone else doesn’t yet.
The pilot accomplishes three things. It surfaces problems at a survivable scale before they hit the full population. It generates data about what actually happens — which uses help learning, which uses hurt it, which assessments break, which new assessments work. And it produces internal case studies and worked examples that the next wave of faculty can learn from.
The pilot needs explicit evaluation infrastructure. Pre- and post-term assessments of student learning. Surveys of faculty experience. Tracking of academic integrity incidents. Comparison data, where possible, with similar courses that didn’t have AI access. The CSU systemwide AI survey released in April 2026 is the kind of thing that should have happened before broad rollout, not after.
At the end of the pilot, the governance committee reviews the data and makes a real decision about whether to scale. Real meaning: scaling is not a foregone conclusion. The committee can decide to expand, to expand with modifications, to expand to specific contexts only, or to not expand. The optionality is the value.
The thing CSU cut: the pilot. CSU went from procurement to general availability with no intermediate step. The April 2026 survey is essentially the post-hoc version of what a pilot’s evaluation should have been, except it happened after every student already had access and after every faculty member was already on their own.
Month 13-14: Scale, with infrastructure
Now the rollout goes systemwide. But the infrastructure is in place.
Required student training, completed before access. Not “voluntary AI Commons modules” that 0.7 percent of students complete. A 30-60 minute orientation that every student goes through before they can use the institutional account. This is similar to the way most institutions handle required harassment training, security training, or library orientation. It’s not glamorous. It works because it’s required.
A model syllabus statement, in active use. Faculty either adopt the model or articulate why they’re adopting a different one. Departments review the policies in their courses for internal consistency. Students know what to expect from any given class because the syllabus addresses AI explicitly.
Ongoing professional development for faculty. Not a one-time training. Recurring, with each new term, with new modules as AI changes. The model is the same as institutions have for any technology that affects teaching — Blackboard, Canvas, video conferencing tools all have ongoing training.
A reporting and feedback infrastructure. Faculty and students can flag specific problems — bias incidents, hallucinated content in submissions, classroom policy conflicts, data concerns. Reports go to the governance committee, which reviews them and adjusts policy.
Public reporting of metrics. Quarterly: how many faculty have completed training, how many students have, what’s the academic integrity incident rate, what are the survey results on student and faculty experience. The data is uncomfortable when it’s bad. That’s the point. CSU’s data is uncomfortable now, but it became visible only fifteen months in, and only because it was used to justify a renewal decision that had already been made.
The thing CSU cut: the infrastructure. There’s no required student training. The model syllabus statement was never produced. Professional development is voluntary and one-time. The reporting and feedback infrastructure is the AI Commons hub, which is a website, not a system. The metrics weren’t public until the April 2026 survey, which framed bad numbers as “important data points” rather than as the alarms they actually are.
The honest cost
What this approach costs that CSU’s didn’t:
Fourteen months instead of six. The pressure to move fast is real. Doing it right is slower. Anyone selling you a faster path is selling you the path that produced 0.7 percent training completion.
Real money for required training, faculty preparation, instructional design support, and ongoing professional development. CSU’s contract was $17 million for the tool. The institutional cost of doing the rollout right is probably another $10-15 million on top of that, spread over the first two years. That money buys outcomes. Without it, the tool is shelf software at $17 million.
Slower-feeling political wins. A press release in February that says “we will be the first AI-empowered university system” plays better than a press release in March that says “we have begun a fourteen-month process to thoughtfully integrate AI into our pedagogy.” The fast version generates headlines. The slow version generates outcomes. You don’t get both.
Real organizational conflict. Required faculty training is a union conversation. Empowered governance committees mean the chancellor’s office can’t unilaterally decide. Public reporting of bad metrics means accountability. None of this is pleasant for administration. All of it is necessary.
The honest benefit
What this approach gets you that CSU didn’t:
A rollout your faculty actually own. A student body that’s actually been trained on the tool. Policies that are actually consistent across courses. Metrics that actually mean something because they’re tied to a framework. Defensibility in front of legislators, journalists, and your own community. The ability to renew or not renew the contract based on data, rather than based on the political cost of admitting an experiment didn’t work.
And the thing that’s hardest to measure but matters most: an institution that can credibly claim to be doing AI literacy, rather than one that bought AI access and called the access literacy.
The closing recommendation
If you are at SUNY, Texas, Florida, or anywhere else considering a major institutional AI deal, the single most important decision you will make is whether you treat this as a procurement project or as an academic project. CSU treated it as a procurement project. The results are public, measurable, and bad.
The cost of treating it as an academic project is real. The benefit is that you don’t produce the largest AI literacy gap in American higher education at your institution. That’s a benefit worth fourteen months and a few million dollars.
This article is part of a free curriculum that Tygart Media is publishing to fill the literacy gap CSU’s rollout produced. If your institution is about to make similar decisions and any of this is useful, take it. The work is licensed for any institutional use. If you’d like to talk through how it might apply to your specific situation, we’re available. But the article itself is what you need to start.
About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any institutional planning, classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.
Leave a Reply