{"resourceId":"university-of-colorado-ai-meeting-tools-cora-public-records-guidance-20261110","versions":[{"version":"external-cae271e231a4798197f30637bee0329e6e0fe56438c3fb268b7490b9aaaa8660","resource":{"id":"university-of-colorado-ai-meeting-tools-cora-public-records-guidance-20261110","title":"University of Colorado: AI meeting summaries and transcripts can be public records under CORA; inform participants and review every summary","organization":"University of Colorado System (Employee Services and UIS)","sector":"Public higher education","geography":"Colorado, United States","publishedAt":"June 30, 2026 (inspected November 10, 2026)","publicationDate":"2026-06-30","eventDate":null,"sourceName":"University of Colorado (cu.edu)","sourceLabel":"University IT and records guidance","sourceUrl":"https://www.cu.edu/blog/tech-tips/using-ai-meeting-tools-understand-your-cora-obligations","evidenceClass":"standards-guidance","outcomeClass":"cautionary","topics":["governance-procurement","data-security","knowledge-work"],"finding":"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.","sledRelevance":"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":"Institutional guidance from a public university system; no measured outcomes.","architectureImplications":"Interpretation: AI meeting outputs stored outside the university's records systems complicate open-records searches; storage location should be part of tool review.","governanceImplications":"Guidance requires licensed, reviewed tools and human review of outputs; Claude features would need the same review before campus use.","securityPrivacyImplications":"Advises against AI summaries for sensitive, confidential or regulated meetings and warns free or unlicensed tools may not meet requirements.","caveats":"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.","streamIds":["anthropic","campus-operations"],"roles":{"sales":"Open with the open-records obligation. CU tells employees AI meeting summaries and transcripts can be public records under CORA and must come from licensed, reviewed tools with human review. For public-university CIOs and records officers considering Claude Meetings, ask how AI notes will be disclosed, stored and searched. Offer a records-alignment review for the pilot. Do not claim AI notes reduce records exposure or are exempt from disclosure.","engineering":"Engineering fit hinges on records retrieval: Claude Meetings outputs would sit in claude.ai, so the campus must be able to search and export them for open-records requests and apply retention. Confirm the tool is licensed through the university's Claude agreement, test participant notice behavior, and confirm sensitive-meeting exclusions can be enforced by policy or calendar tagging. Proof of value should include a mock records request against pilot meeting notes.","delivery":"Delivery would align any Claude meeting pilot with existing campus AI and records guidance: participant notice, sensitive-meeting exclusion list, mandatory human review, and retention mapping. Dependencies include the university's Claude license terms and records office approval. Owner is campus IT with the records office. Risks include unlicensed personal Claude accounts used for university meetings and misattributed quotes in summaries that later become disclosed records."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"Aligning Claude meeting use with existing records guidance could let campuses pilot it without creating unmanaged records.","potentialEngagement":"A records-alignment review and pilot design for one administrative unit.","unsupportedClaims":["That AI notes are exempt from CORA","That human review can be skipped","Any accuracy or time-savings figure"]},"engineering":{"fit":"Relevant to public universities with open-records laws considering Claude Meetings.","architectureIntegration":"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.","proofOfValue":["Mock open-records request on pilot notes","Verify participant notice","Check misattribution rate in five summaries"]},"delivery":{"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.","skillsAdoption":"Organizers trained to disclose AI use and review summaries before sharing.","governanceCheckpoints":["Records office approval","Exclusion list published","Post-pilot records audit"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-11-11T04:21:09Z","enrichedAt":"2026-11-11T04:32:28Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: AI summaries can support staff who need written follow-up, but CU notes transcription errors and misattribution, so review remains necessary.","procurementImplications":"Use only CU-licensed tools reviewed through procurement and security processes.","operatingModelImplications":"Meeting organizers own participant notice and summary review; records retention follows university schedules.","sourceVerification":{"openedUrl":"https://www.cu.edu/blog/tech-tips/using-ai-meeting-tools-understand-your-cora-obligations","referenceExcerpt":"AI-generated content is not automatically exempt from disclosure requirements.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}