From the Student Success edition of October 19, 2026
Daily Emerald: University of Oregon AI Council pushes 18 recommendations, including a required AI policy in every course and a standard AI-use acknowledgment, while UO declines to endorse AI detectors
University of Oregon (UO AI Council; Office of the Provost; UO Senate Academic Council) · Higher education academic integrity, course AI policy and AI literacy governance · Eugene, Oregon, United States
- Publisher
- Daily Emerald
- Original publication
- Daily Emerald, 19 October 2026
- Source retrieved
- 2026-10-20
- Event date
- 2026-10-09
What happened
The UO AI Council released 18 strategic recommendations in September, discussed with faculty on 9 October. A top priority is requiring every course to state how students and instructors may use generative AI, tied to learning outcomes and differentiated by assignment rather than blanket rules, plus a university-wide format for acknowledging AI use. UO has updated its Student Conduct Code so uncited AI content may count as plagiarism and added AI to required academic-integrity training for incoming students. UO does not endorse AI-detection tools because of false positives. Other recommendations cover faculty AI literacy, investment in assessment-integrity infrastructure and possibly adding AI to Core Education. The Senate Academic Council must approve recommendations before they become requirements.
Why it matters
Shows a U.S. public research university moving from instructor-by-instructor AI rules toward required course-level policies and standard disclosure, while explicitly declining detector use. This is the governance baseline that student-facing AI tools sit within.
Evidence and measured results
Reported recommendations, conduct-code and training changes, and faculty quotes. No measurement of policy effects.
Limitations and uncertainty
Recommendations are not yet requirements. Reporting relies on council documents and quotes; the recommendations were not independently reviewed for this record.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Students face inconsistent AI rules across courses, and integrity processes rely on unclear expectations and unreliable detectors.
- Stakeholders
- Provost and executive vice provost
- AI Council co-chairs (associate CIO and university librarian)
- Faculty senate academic council
- Student conduct office
- Teaching and learning center
- Discovery questions
- What share of courses state an explicit AI policy today?
- How do students currently disclose AI use, if at all?
- What support do faculty need to write assignment-level guidance?
- How are AI-related integrity cases resolved without detectors?
- Value hypothesis
- Interpretation: required course policies and a standard disclosure format could reduce student confusion and contested integrity cases, if faculty receive templates and support.
- Potential engagement
- A bounded policy-template and disclosure-workflow design engagement, piloted in a few departments with feedback collection.
- Unsupported claims
- Reduced misconduct rates
- Improved learning outcomes
- Faculty time savings
- That disclosure formats are reliable evidence of AI use
Pre-sales engineering
Role takeaway
- Fit
- Fits institutions that want to standardise AI expectations through the LMS and syllabus systems without detection tools.
- Architecture and integration
- Structured syllabus AI-policy fields and an AI-use acknowledgment step in LMS submissions. No platform is named.
- Prerequisites
- LMS support for custom submission fields
- Syllabus template system
- Approved disclosure wording
- Integrity process guidance
- Constraints
- Recommendations require Senate approval
- No detector use per current guidance
- Accessibility review of any new forms
- State public-records and privacy rules
- Security
- Limit access to disclosure records, set retention rules, and separate disclosure data from automated disciplinary flags.
- Proof of value
- Pilot measuring share of courses with explicit policies
- Student survey on clarity of expectations
- Faculty time to complete the template
- Review of integrity case volumes before and after
Delivery
Role takeaway
- Work
- Pilot course AI-policy templates and disclosure workflows, then scale after Senate approval.
- Dependencies
- Senate Academic Council approval
- Faculty development capacity
- LMS configuration
- Student communications
- Ownership
- Office of the Provost, advised by the UO AI Council.
- Skills and adoption
- Faculty workshops on assignment-level AI guidance; updated incoming-student integrity training.
- Governance checkpoints
- Senate approval of each recommendation
- Student conduct review of disclosure use
- Accessibility review of forms
- Annual policy review
- Acceptance criteria
- Proposed: at least 90% of pilot courses publish an AI policy tied to outcomes
- Proposed: student clarity rating improves against a pre-pilot survey
- Proposed: no detector-based allegations in pilot departments
- Proposed: faculty template completion under an agreed time
- Risks
- Policy fatigue among faculty
- Disclosure used punitively
- Inconsistency persists across departments
- Delay in Senate approval
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?
A standard AI-use acknowledgment format could be built into LMS submission workflows; investment in assessment-integrity infrastructure is unspecified.
Governance
Who approves, reviews and stays accountable for outcomes?
Course-level policy requirement, standard disclosure, conduct-code update and detector non-endorsement, subject to Senate approval.
Security and privacy
What data, permissions and controls need testing?
Not detecting AI avoids sending student work to third-party detectors; other privacy aspects are not discussed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Faculty AI literacy and practice-sharing are recommended; workload of writing per-assignment AI guidance falls on instructors.
Procurement
What should contracts, pricing and exit terms secure?
Non-endorsement of detectors is a signal against procuring detection tools; infrastructure for assessment integrity may imply other purchases.
Operating model
Which teams own the service once it runs?
Responsibility currently sits with students to understand each course's expectations; the council proposes shifting clarity onto required course policies.
Publication history
- 2026-10-19Student Success · Issue 425 resources
Stable resource ID: daily-emerald-uo-ai-council-18-recommendations-course-policies-no-detectors-20261019