{"resourceId":"cu-boulder-faculty-assembly-openai-nonrenewal-resolution-20261008","versions":[{"version":"external-e3f9cf4cdc70bc636bfe05e4e49dd4e9cb37e3491539f2c5de1b99277f75015f","resource":{"id":"cu-boulder-faculty-assembly-openai-nonrenewal-resolution-20261008","title":"CU Boulder faculty assembly passes resolution calling on the chancellor not to renew or extend the campus OpenAI ChatGPT Edu contract","organization":"University of Colorado Boulder, Boulder Faculty Assembly","sector":"Public research university: faculty shared governance over AI procurement","geography":"Boulder, Colorado, United States","publishedAt":"8 October 2026 (CU Boulder Today), reporting the 1 October assembly meeting","publicationDate":"2026-10-08","eventDate":"2026-10-01","sourceName":"CU Boulder Today","sourceLabel":"Institutional news report on faculty governance action","sourceUrl":"https://www.colorado.edu/today/2026/10/08/faculty-assembly-introduces-ai-resolution-hears-housing-assistance-update-more","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["governance-procurement","accessibility-workforce"],"finding":"At its 1 October meeting the Boulder Faculty Assembly took up a resolution asking the chancellor to consult a faculty-led working group on any renewal or extension of the campus OpenAI contract, and asking the administration to develop an AI strategy with faculty governance before initiating, extending or modifying any AI contracts. An amendment calling on the chancellor not to renew or extend the OpenAI contract at all was approved, and the resolution passed. Why now: on 19 October CU Anschutz, in the same university system, expanded its OpenAI agreement, so the two records show opposite directions on the same vendor within one system.","sledRelevance":"Faculty governance is seeking a role in AI vendor contracts and, at Boulder, has formally opposed renewal. Campus IT and procurement planning renewals should expect governance review of AI licenses, not just security review.","evidence":"University news summary of the meeting. The separate BFA resolution page, also opened, gives the text and a 39-8-1 vote. The resolution is advisory; the administration's response is not reported.","architectureImplications":"Limited direct relevance; non-renewal would force migration or replacement planning for users and data in the current tenant.","governanceImplications":"Faculty assert a principal role over AI decisions touching pedagogy and research and ask for a faculty-led working group in contract negotiations.","securityPrivacyImplications":"The resolution text cites end-user privacy among its concerns about the vendor; the news summary does not detail them.","caveats":"Published 8 October, before the last completed run; included for the same-system contrast with CU Anschutz on 19 October. Advisory resolution; no administrative decision reported. The source is institutional news, classed here as reporting because it summarizes a governance body's action rather than speaking for the administration.","streamIds":["campus-operations"],"roles":{"sales":"Sales framing: at Boulder, faculty governance has voted against renewing a campus AI contract, so any AI license renewal faces a governance process, not just procurement. Bounded help is a neutral renewal evaluation: usage data, alternatives and exit costs presented to the faculty working group. Do not position as pro- or anti-vendor, and do not claim the administration will follow the resolution.","engineering":"Engineering framing: a contested renewal makes exit readiness a technical requirement. Confirm what user data, custom GPTs and integrations live in the tenant, how they export, and what a replacement platform would need. Usage data should be available to inform the governance discussion without exposing individual users. Note that the Anschutz campus has expanded its agreement with the same vendor, so any Boulder exit must respect system-level contract terms that this report does not describe.","delivery":"Delivery framing: plan for both outcomes. Build an exit and transition plan with export, communications and replacement options, and a renewal path with conditions the faculty working group might set. The CIO owns the service decision; shared governance owns the consultation. Proposed acceptance: a documented exit plan exists before the renewal decision date. Keep users informed without pre-empting the chancellor's decision."},"roleDetails":{"sales":{"customerProblem":"A campus faces a faculty vote against renewing its AI contract and must decide on renewal with governance involvement.","stakeholders":["Chancellor","CIO","Procurement","Faculty assembly leadership","AI steering committee"],"discoveryQuestions":["When does the current AI contract expire?","What usage data can be shared with faculty governance?","What alternatives would faculty accept?"],"valueHypothesis":"Interpretation: evidence on usage and alternatives may help reach a renewal decision faculty can accept; not shown here.","potentialEngagement":"A neutral renewal evaluation and exit-cost estimate for one AI platform, delivered to both administration and faculty governance.","unsupportedClaims":["That the contract will not be renewed","Faculty consensus beyond the vote","Any vendor wrongdoing"]},"engineering":{"fit":"Exit-readiness and renewal-evidence work.","architectureIntegration":"Inventory tenant contents, integrations and export options.","prerequisites":["Usage reporting from the tenant","Export tooling","List of integrations"],"constraints":["Advisory resolution; decision rests with the chancellor","Campuses in the same system on different paths"],"security":"Data export and deletion on exit must be verified.","proofOfValue":["Export a sample of user data and custom configurations","Produce anonymized usage reports for governance"]},"delivery":{"work":"Prepare exit and renewal-with-conditions plans in parallel.","dependencies":["Chancellor decision","Faculty working group","Contract dates"],"ownership":"CIO owns the service; faculty assembly owns consultation.","skillsAdoption":"Communications plan for users if the tool is withdrawn.","governanceCheckpoints":["Faculty working-group consultation before renewal","Security review of any replacement"],"acceptanceCriteria":["Proposed: exit plan documented before renewal decision","Proposed: usage report shared with governance"],"risks":["Abrupt loss of a used tool","Conflict between governance and administration","Data left in vendor tenant"]}},"retrievedAt":"2026-10-19T21:56:40-05:00","enrichedAt":"2026-10-19T22:05:34-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Non-renewal would remove a campus-provided tool for faculty, staff and students who rely on it, unless it is replaced.","procurementImplications":"AI renewals at Boulder may now need faculty working-group consultation, adding time and conditions to renewal cycles.","operatingModelImplications":"AI contract decisions shift toward shared governance alongside IT, procurement and the AI steering committee.","sourceVerification":{"openedUrl":"https://www.colorado.edu/today/2026/10/08/faculty-assembly-introduces-ai-resolution-hears-housing-assistance-update-more","referenceExcerpt":"an amendment to the resolution was also introduced that calls on Schwartz to not renew or extend the OpenAI contract at all.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}