{"resourceId":"uc-berkeley-ai-use-case-library-public-20261102","versions":[{"version":"external-b7a1d13cc256c91ea027746ee1e60073b34e45b92bf5b1c86772401d022cb67f","resource":{"id":"uc-berkeley-ai-use-case-library-public-20261102","title":"UC Berkeley opens its campus AI Use Case Library to the public, with reviewed staff submissions, ratings and a leaderboard, and says inclusion is not a risk review","organization":"University of California, Berkeley (Berkeley IT, AI Tiger Team)","sector":"Higher education IT and administrative operations","geography":"California, United States","publishedAt":"2 November 2026 (Berkeley IT news post)","publicationDate":"2026-11-02","eventDate":"2026-11-02","sourceName":"UC Berkeley Information Technology","sourceLabel":"Institutional IT announcement","sourceUrl":"https://technology.berkeley.edu/news/ai-use-case-library-now-open-public","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["knowledge-work","operating-model","governance-procurement"],"finding":"Berkeley IT announced on 2 November 2026 that its AI Use Case Library is open to the public. Entries span Administration, Research, Teaching, Learning and Personal Productivity, and each records the goal, impact, AI tool, limitations and lessons learned, and a campus contact. Staff can rate entries (feeding a leaderboard) and submit their own; every submission is reviewed before publication and must exclude confidential, student or personal data. Berkeley states that inclusion is not an endorsement and not a risk review, and points users to its appropriate-use guidance before deploying a tool.","sledRelevance":"A low-cost pattern for spreading administrative AI practice across decentralized offices, while explicitly separating knowledge sharing from risk approval.","evidence":"Primary institutional announcement; it describes the library's structure, not the number of entries or any measured impact.","architectureImplications":"A curated catalog with authenticated (Berkeley Google account) rating and an editorial review workflow; no integration with tool provisioning is described.","governanceImplications":"Review of submissions is editorial; the post says it is not a risk review, so tool approval remains a separate process.","securityPrivacyImplications":"Submitters are told not to include confidential, student or personal data in entries.","caveats":"No counts of entries, users or measured benefits are given; impacts in entries are self-reported by staff.","streamIds":["campus-operations"],"roles":{"sales":"Sales framing: Berkeley is cataloguing staff AI use cases with stated goals, tools and impacts. Interpretation: CIOs may want help standing up a similar reviewed catalog, or using one to pick which administrative uses to scale. Do not claim measured savings; the post reports none.","engineering":"Engineering framing: a reviewed catalog with sign-in ratings, separate from risk review. Interpretation: pre-sales can propose linking catalog entries to approved-tool status and data classification so popular uses map to sanctioned tools.","delivery":"Delivery framing: the library needs curation, review and feedback handling by a named team. Interpretation: delivery plans should budget editorial review and a path from a highly rated entry to a formal risk review."},"roleDetails":{"sales":{"customerProblem":"Staff AI use cases are scattered across offices and repeated without shared lessons.","stakeholders":["CIO","AI program lead","Administrative unit heads"],"discoveryQuestions":["Where are staff AI use cases recorded today?","Who reviews them, and how does a use case reach risk review?","Which administrative areas are most active?"],"valueHypothesis":"A reviewed catalog may reduce duplicated effort; Berkeley reports no measurement.","potentialEngagement":"A bounded design of a campus AI use-case catalog and its link to tool approval.","unsupportedClaims":["Time or cost savings","Number of use cases or users","Endorsement of any tool"]},"engineering":{"fit":"Campuses with decentralized administrative AI adoption.","architectureIntegration":"Catalog with institutional SSO for ratings and a review queue; tie-in to tool approval not described.","prerequisites":["SSO","Appropriate-use guidance","Reviewer capacity"],"constraints":["Entries must exclude confidential, student or personal data","Not a risk review"],"security":"Content screening for sensitive data at submission review.","proofOfValue":["Tag entries with approved-tool status","Track which entries are adopted by other offices"]},"delivery":{"work":"Launch and curate a reviewed AI use-case library for staff.","dependencies":["IT AI team","Unit contacts","Policy owners"],"ownership":"Berkeley IT AI Tiger Team.","skillsAdoption":"Staff learn from named colleagues' documented uses.","governanceCheckpoints":["Editorial review before publication","Separate risk review before deployment"],"acceptanceCriteria":["Proposed: every entry lists tool, limitations and contact","Proposed: no sensitive data in published entries"],"risks":["Entries read as endorsements","Stale entries","Self-reported impact"]}},"retrievedAt":"2026-11-02T21:52:05-06:00","enrichedAt":"2026-11-02T22:05:00-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Peer-to-peer learning for staff; each entry names a campus contact.","procurementImplications":"Not an endorsement of products; it may still steer demand toward the tools named in popular entries.","operatingModelImplications":"An AI Tiger Team curates the library and handles feedback.","sourceVerification":{"openedUrl":"https://technology.berkeley.edu/news/ai-use-case-library-now-open-public","referenceExcerpt":"Inclusion in the library is not an endorsement of any product, tool, or service, and it is not a risk review","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}