From the Campus Operations edition of October 17, 2026
Eastern Michigan regents approve a faculty contract that adopts an AI policy on faculty work and intellectual property and creates an AI Task Force
Eastern Michigan University Board of Regents; EMU chapter of the American Association of University Professors (EMU-AAUP) · Public regional university: faculty labor relations and HR · Ypsilanti, Michigan, United States
- Publisher
- 89.1 WEMU (public radio)
- Original publication
- 16 October 2026, 7:01 AM ET (WEMU); regents meeting 15 October 2026
- Source retrieved
- 2026-10-18
- Event date
- 2026-10-15
What happened
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.
Why it matters
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 and measured results
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.
Limitations and uncertainty
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.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-17; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- 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?
- Value hypothesis
- Interpretation: mapping contract IP terms to vendor data settings can reduce grievance risk for AI tools that use faculty content.
- Potential engagement
- A vendor-terms and tenant-settings review against a faculty contract's AI and IP provisions, plus a task-force charter draft.
- Unsupported claims
- That the AI policy improves outcomes
- Details of the AI policy text
- Any link between AI and the severance program
Pre-sales engineering
Role takeaway
- Fit
- Relevant to AI tools that store, process or train on faculty materials or research.
- Architecture and integration
- 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.
- Proof of value
- Demonstrate training opt-out in each tenant
- Show retention settings match policy
Delivery
Role takeaway
- 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.
- Skills and adoption
- Task-force members need concise technical briefings on data flows.
- Governance checkpoints
- Task-force review before launch
- Annual review of vendor terms
- Acceptance criteria
- 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
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
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.
Governance
Who approves, reviews and stays accountable for outcomes?
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.
Security and privacy
What data, permissions and controls need testing?
IP concerns translate into data-handling requirements: retention, training use and sharing terms for faculty content in AI services.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
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.
Procurement
What should contracts, pricing and exit terms secure?
AI tools that ingest faculty content may need contract terms on training use and retention consistent with the IP provisions.
Operating model
Which teams own the service once it runs?
A standing AI Task Force gives a joint forum for future AI changes rather than case-by-case grievances.
Publication history
- 2026-10-17Campus Operations · Issue 405 resources
Stable resource ID: emu-regents-approve-aaup-contract-ai-policy-task-force-20261016