From the Anthropic edition of November 10, 2026
University of Colorado: AI meeting summaries and transcripts can be public records under CORA; inform participants and review every summary
University of Colorado System (Employee Services and UIS) · Public higher education · Colorado, United States
- Publisher
- University of Colorado (cu.edu)
- Original publication
- June 30, 2026 (inspected November 10, 2026)
- Source retrieved
- 2026-11-11
What happened
The University of Colorado system advises employees that AI-generated meeting summaries, transcripts and chats created while conducting university business can be public records under the Colorado Open Records Act and are not automatically exempt. It tells staff to avoid AI notetaking for sensitive or regulated meetings, inform all participants first, treat every AI summary as a draft requiring human review, verify names, decisions and quotations, consider storage and retention, and use only CU-licensed tools that passed procurement and security review.
Why it matters
Why now: Claude Meetings (announced Nov. 10) adds another AI notetaker that public universities must place within open-records and retention rules. CU's guidance shows the controls campus counsel and records offices already expect; any Claude Meetings pilot at a public university would need the same disclosure, review and licensed-tool checks.
Evidence and measured results
Institutional guidance from a public university system; no measured outcomes.
Limitations and uncertainty
Guidance blog post dated June 30, 2026; predates Claude Meetings and does not name Claude; no data on compliance or incidents. Cross-tagged campus-operations: university administrative records guidance. Newly relevant with the Nov. 10 Claude Meetings announcement.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-11; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Public universities must treat AI meeting outputs as potential open-records material, but new AI notetakers arrive outside existing records systems.
- Stakeholders
- Campus CIO
- University records officer
- Office of general counsel
- Faculty governance leaders
- Discovery questions
- Are AI meeting summaries searchable for open-records requests today?
- Which meetings are excluded from AI notetaking?
- Is Claude licensed centrally or used on personal accounts?
- Value hypothesis
- Aligning Claude meeting use with existing records guidance could let campuses pilot it without creating unmanaged records.
- Potential engagement
- A records-alignment review and pilot design for one administrative unit.
- Unsupported claims
- That AI notes are exempt from CORA
- That human review can be skipped
- Any accuracy or time-savings figure
Pre-sales engineering
Role takeaway
- Fit
- Relevant to public universities with open-records laws considering Claude Meetings.
- Architecture and integration
- Outputs stored in claude.ai require export and search paths for records requests.
- Prerequisites
- University-licensed Claude agreement
- Records retention schedule
- Participant notice template
- Constraints
- Guidance predates Claude Meetings
- Sensitive meetings excluded
- Security
- Restrict to licensed tenants; exclude regulated-data meetings.
- Proof of value
- Mock open-records request on pilot notes
- Verify participant notice
- Check misattribution rate in five summaries
Delivery
Role takeaway
- Work
- Map a Claude meeting pilot to campus records and AI guidance.
- Dependencies
- License terms
- Records office approval
- Counsel review
- Ownership
- Campus IT with the university records office.
- Skills and adoption
- Organizers trained to disclose AI use and review summaries before sharing.
- Governance checkpoints
- Records office approval
- Exclusion list published
- Post-pilot records audit
- Acceptance criteria
- Proposed: 100% of pilot summaries reviewed before distribution
- Proposed: mock records request fulfilled from pilot data
- Risks
- Unlicensed accounts
- Misattributed quotes disclosed
- Records outside retention schedule
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?
AI meeting outputs stored outside the university's records systems complicate open-records searches; storage location should be part of tool review.
Governance
Who approves, reviews and stays accountable for outcomes?
Guidance requires licensed, reviewed tools and human review of outputs; Claude features would need the same review before campus use.
Security and privacy
What data, permissions and controls need testing?
Advises against AI summaries for sensitive, confidential or regulated meetings and warns free or unlicensed tools may not meet requirements.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
AI summaries can support staff who need written follow-up, but CU notes transcription errors and misattribution, so review remains necessary.
Procurement
What should contracts, pricing and exit terms secure?
Use only CU-licensed tools reviewed through procurement and security processes.
Operating model
Which teams own the service once it runs?
Meeting organizers own participant notice and summary review; records retention follows university schedules.
Publication history
- 2026-11-10Anthropic · Issue 1210 resources
Stable resource ID: university-of-colorado-ai-meeting-tools-cora-public-records-guidance-20261110