{"resourceId":"emu-regents-approve-aaup-contract-ai-policy-task-force-20261016","versions":[{"version":"external-1bc2fd21f7c5fa1abc149f2162025b663727d7e5b92a5e62d53b36e2d646ab86","resource":{"id":"emu-regents-approve-aaup-contract-ai-policy-task-force-20261016","title":"Eastern Michigan regents approve a faculty contract that adopts an AI policy on faculty work and intellectual property and creates an AI Task Force","organization":"Eastern Michigan University Board of Regents; EMU chapter of the American Association of University Professors (EMU-AAUP)","sector":"Public regional university: faculty labor relations and HR","geography":"Ypsilanti, Michigan, United States","publishedAt":"16 October 2026, 7:01 AM ET (WEMU); regents meeting 15 October 2026","publicationDate":"2026-10-16","eventDate":"2026-10-15","sourceName":"89.1 WEMU (public radio)","sourceLabel":"Independent public-radio reporting, read with the regents' board recommendation document","sourceUrl":"https://www.wemu.org/wemu-news/2026-10-16/emu-board-of-regents-passes-contract-agreements-with-teacher-and-police-unions","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["accessibility-workforce","governance-procurement","operating-model"],"finding":"WEMU reported that EMU's Board of Regents on 15 October approved three-year agreements with the AAUP faculty chapter and the police officers' union. Chief Human Resources Officer Curt Ellis said the faculty contract also adopted an AI policy addressing faculty work and research, and that faculty wanted to keep the university from pushing their intellectual property into areas where it could be compromised. The regents' recommendation document (opened separately; see inspections) says the agreement covers about 500 faculty, was ratified by the unit on 18 September 2026, notes a recently adopted AI policy 'designed to serve as the foundation for future developments', and states that the agreement creates an AI Task Force. The same document lists a voluntary severance incentive and the replacement of the Faculty Senate with an advisory University Senate from 11 January 2027.","sledRelevance":"A ratified contract, not a demand: AI terms settled through bargaining and approved by a public board, with a joint task force as the mechanism for future AI questions. Useful contrast with the unresolved City Colleges, Yale and York disputes in the archive.","evidence":"Short news report quoting the HR chief, corroborated by the board document. Neither source publishes the AI policy text or the task force's charge.","architectureImplications":"IP protection terms may limit where faculty-created materials can be sent, including vendor AI platforms that train on or retain content; data-flow reviews for teaching and research tools become a contract matter.","governanceImplications":"AI policy is embedded in a collective agreement with a task force for future developments, alongside a shift of shared governance from decision-making to advisory status.","securityPrivacyImplications":"IP concerns translate into data-handling requirements: retention, training use and sharing terms for faculty content in AI services.","caveats":"AI policy text not public; the HR officer's summary is management's characterisation. The broader contract includes workforce-reduction tools (severance incentive) and governance changes that may affect how AI decisions are made, but no link between them and AI is stated.","streamIds":["campus-operations"],"roles":{"sales":"Sales framing: EMU shows that AI terms can be settled at the table and approved by a public board, with a task force to handle what comes next. Institutions heading into bargaining may want help translating faculty IP concerns into concrete vendor data terms and a task-force charter. Keep the offer to policy-to-contract mapping; nothing here shows outcomes, and the AI policy text itself is not public.","engineering":"Engineering framing: faculty IP protections become technical requirements once AI tools ingest course materials or research content. Pre-sales should check each AI service's training-use, retention and sharing terms and whether tenant settings can enforce them. Validation should confirm that faculty content is excluded from model training and that retention matches policy. Because the policy text is not public, treat any mapping as provisional until the institution shares the actual contract language.","delivery":"Delivery framing: the task force is the delivery interface. Teams deploying AI that touches faculty content should bring data-flow diagrams and vendor terms to it before launch. HR and the provost's office own the contract obligations; IT owns tenant configuration. Acceptance should include documented task-force review for each relevant tool, plus a periodic recheck when vendors change their data terms, since a silent terms change could put the institution out of compliance."},"roleDetails":{"sales":{"customerProblem":"Faculty want AI rules that protect their intellectual property, and administrations need a stable way to handle future AI changes.","stakeholders":["Chief HR officer","Provost","General counsel","CIO","Faculty union leadership"],"discoveryQuestions":["Does your faculty contract address AI or IP in AI tools?","Which AI services ingest faculty-created content today?","Is there a joint body for AI changes?"],"valueHypothesis":"Interpretation: mapping contract IP terms to vendor data settings can reduce grievance risk for AI tools that use faculty content.","potentialEngagement":"A vendor-terms and tenant-settings review against a faculty contract's AI and IP provisions, plus a task-force charter draft.","unsupportedClaims":["That the AI policy improves outcomes","Details of the AI policy text","Any link between AI and the severance program"]},"engineering":{"fit":"Relevant to AI tools that store, process or train on faculty materials or research.","architectureIntegration":"Tenant-level controls on training opt-out, retention and sharing in LMS-embedded and standalone AI services.","prerequisites":["Inventory of AI tools using faculty content","Vendor data-processing terms","Clear IP policy"],"constraints":["Contract terms not public","Vendor defaults may conflict with IP provisions"],"security":"Confirm no model training on faculty content and enforce retention limits.","proofOfValue":["Demonstrate training opt-out in each tenant","Show retention settings match policy"]},"delivery":{"work":"Bring AI tools touching faculty content to the task force with data-flow and vendor-term evidence.","dependencies":["Task force charter and schedule","Vendor documentation"],"ownership":"HR and provost own contract compliance; IT owns configuration.","skillsAdoption":"Task-force members need concise technical briefings on data flows.","governanceCheckpoints":["Task-force review before launch","Annual review of vendor terms"],"acceptanceCriteria":["Proposed: every AI tool using faculty content has a reviewed data-flow record","Proposed: zero tools with training use enabled on faculty content"],"risks":["Task force becomes a bottleneck","Vendor term changes break compliance","Governance shift reduces faculty trust"]}},"retrievedAt":"2026-10-17T21:53:01-05:00","enrichedAt":"2026-10-17T21:58:13-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Faculty secure IP-related AI terms in the same agreement that introduces a severance incentive and reduces sabbaticals; AI and restructuring sit side by side.","procurementImplications":"AI tools that ingest faculty content may need contract terms on training use and retention consistent with the IP provisions.","operatingModelImplications":"A standing AI Task Force gives a joint forum for future AI changes rather than case-by-case grievances.","sourceVerification":{"openedUrl":"https://www.wemu.org/wemu-news/2026-10-16/emu-board-of-regents-passes-contract-agreements-with-teacher-and-police-unions","referenceExcerpt":"the teachers’ contract also adopted an AI policy addressing faculty work and research","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}