From the Campus Operations edition of October 23, 2026
CSU's AI bargaining proposal frames faculty AI terms as non-binding principles and rejects bans on AI performance evaluation and employee monitoring
California State University (proposal to the California Faculty Association, posted by CFA) · Public university system: faculty labor relations and AI governance · California, United States
- Publisher
- California Faculty Association (posting CSU proposal)
- Original publication
- 9 July 2026 (document header 'CSU #3 (CFA) 07/09/2026')
- Source retrieved
- 2026-10-24
- Event date
- 2026-07-09
What happened
CSU's 9 July proposal places AI terms in a memorandum of understanding of 'general, aspirational principles' that does not create new rights or obligations and expires with the contract. Its text, with comments marking agreement, keeps AI from serving as Instructor of Record, leaves use or non-use of AI in instruction to faculty, requires disclosure of AI for notes and summaries, commits to vendor review and contractual safeguards for faculty data, bars AI from independently determining employment actions, bars discipline for using or refusing AI by itself, and creates a one-time $2.5 million professional development fund. Meet and confer is limited to impacts required by HEERA. CSU rejects CFA's proposed bans on AI in faculty evaluation and on AI employee monitoring, and its bar on reassigning unit work to AI.
Why it matters
Why now: the CFA strike authorization vote announced 22 October names AI guardrails as unresolved, and this document shows exactly where the parties differ: binding protections versus aspirational principles, and evaluation and monitoring uses.
Evidence and measured results
Employer's own bargaining proposal with margin comments; a party document that describes positions, not outcomes.
Limitations and uncertainty
July position; parties have since moved through impasse and mediation, so current offers may differ.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Employers proposing non-binding AI principles face unions seeking enforceable protections, especially on evaluation and monitoring.
- Stakeholders
- System labor relations
- Provosts
- CIO and information security
- Faculty union leadership
- Discovery questions
- Which AI commitments are binding versus aspirational?
- Do any tools evaluate or monitor employees?
- How will the training fund be used?
- How are vendor data safeguards verified?
- Value hypothesis
- Interpretation: clarity on enforceable commitments could narrow bargaining disputes; no outcome evidence.
- Potential engagement
- A bounded review mapping institutional AI commitments to enforceability and current tool use.
- Unsupported claims
- That this is CSU's current offer
- Bargaining outcome
- That non-binding terms will be accepted
- Guaranteed savings
Pre-sales engineering
Role takeaway
- Fit
- Relevant to tools that touch faculty data, evaluation or monitoring.
- Architecture and integration
- Third-party AI services and learning management systems holding faculty data need vendor review and safeguards.
- Prerequisites
- Vendor risk assessment
- Inventory of AI features in HR and LMS tools
- Data classification
- Constraints
- HEERA scope limits
- Disputed evaluation and monitoring uses
- Security
- Agreed text bars entering confidential data into generative AI in ways that compromise privacy and requires reasonable controls for faculty personal information and IP.
- Proof of value
- Identify any AI scoring or monitoring of employees
- Verify vendor contracts include data safeguards
- Confirm AI cannot independently trigger employment actions
Delivery
Role takeaway
- Work
- Prepare operations for AI commitments already agreed in principle while disputed items remain open.
- Dependencies
- Bargaining outcome
- Tool inventory
- Training program design
- Ownership
- Faculty affairs and labor relations, with IT for tool controls.
- Skills and adoption
- Use of a one-time $2.5 million professional development fund if ratified.
- Governance checkpoints
- Human decision on all employment actions
- Disclosure of AI notes and summaries
- Hold on AI in faculty evaluation until resolved
- Acceptance criteria
- Proposed: inventory of AI note-taking and summary tools completed
- Proposed: documented human review for any AI-assisted employment process
- Proposed: training fund plan ready at ratification
- Risks
- Reliance on terms that change after impasse
- Deploying contested uses
- Loss of trust if principles seen as unenforceable
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?
Limited; requires vendor review, risk assessment and data security standards for third-party AI services holding faculty data.
Governance
Who approves, reviews and stays accountable for outcomes?
Choice between enforceable contract articles and a non-binding MOU is the central dispute; management rights to pilot or discontinue AI are reserved.
Security and privacy
What data, permissions and controls need testing?
Confidential data may not be entered into generative AI in ways that compromise privacy; reasonable controls for faculty personal information and IP across cloud and LMS platforms.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Protections against AI replacing faculty-led instruction and against discipline for non-use; disputed limits on AI evaluation and monitoring.
Procurement
What should contracts, pricing and exit terms secure?
Vendor review and contractual safeguards for third-party services are agreed text.
Operating model
Which teams own the service once it runs?
Bargaining over AI impacts limited to legally required scope; MOU reassessed at contract expiry.
Publication history
- 2026-10-23Campus Operations · Issue 464 resources
Stable resource ID: csu-ai-systems-mou-counterproposal-aspirational-no-new-rights-20260709