{"resourceId":"stanislaus-county-employee-genai-policy-board-item-20261013","versions":[{"version":"external-f2a7afbdaab439678dbc2a63000957e1cae4ce22ce727405a4110237dbbf574c","resource":{"id":"stanislaus-county-employee-genai-policy-board-item-20261013","title":"Stanislaus County, California puts an employee GenAI policy on its Oct 13 consent agenda, barring public-tool uploads of confidential data and AI-made decisions","organization":"Stanislaus County Board of Supervisors, California","sector":"County government workforce AI policy","geography":"Stanislaus County, California, United States","publishedAt":"October 13, 2026 (agenda date)","publicationDate":"2026-10-13","eventDate":"2026-10-13","sourceName":"Stanislaus County","sourceLabel":"Board of Supervisors agenda item and attached policy","sourceUrl":"https://www.stancounty.com/bos/agenda/2026/20261013/B11.pdf","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["governance-procurement","data-security","knowledge-work"],"finding":"The Chief Executive Office recommended the board adopt Personnel Manual Tab 16, an AI policy developed by a staff workgroup. It bars entering non-public information into public GenAI tools, asking GenAI to find facts or make decisions without expert human review, concealing GenAI use (including listening, transcription or translation tools), and using GenAI for employment decisions. It requires written IT approval before integrating GenAI with county systems, lets IT block risky tools, treats prompts as potentially subject to public records requests, cites HIPAA, CJIS, IRS and CCPA obligations, and exempts CIO-approved \"Trusted GenAI\" from some rules. No immediate fiscal impact; existing staff administer it.","sledRelevance":"Mid-size California county policy that is practical and specific (disclosure of listening tools, records treatment of prompts, employment-decision ban), useful as a comparison template for other counties.","evidence":"Board agenda item 5.B.11 PDF opened in full with pdftotext, including the attached September 2026 policy. Search reporting indicated approval; the opened document is the staff recommendation, so final board action was not verified from minutes.","architectureImplications":"Distinguishes public GenAI from CIO-approved Trusted GenAI; any integration with county systems needs ITC written approval, implying a review path for enterprise tools.","governanceImplications":"CIO and CEO review the policy periodically; departments may add stricter rules; GenAI training is encouraged, not required.","securityPrivacyImplications":"Prohibits credentials, PHI, personnel and confidential material in public tools; names HIPAA, CJIS, IRS and CCPA; treats prompts as public-record-like.","caveats":"Agenda recommendation, not confirmed minutes; Trusted GenAI exemption is undefined in scope; training is voluntary; no inventory or monitoring mechanism described.","streamIds":["local-government"],"roles":{"sales":"Sales framing: Stanislaus is formalizing staff GenAI rules with no new budget, which signals demand for help operationalizing them: a Trusted GenAI approval process, training, and integration reviews. The policy names specific risks (listening tools, records exposure, employment decisions) that make good discovery anchors. Do not position this as a buying signal for a specific platform. Interpretation: policy-first counties often need an approved tool list next.","engineering":"Engineering framing: The key design hook is the Trusted GenAI designation, which exempts CIO-approved tools from some public-tool rules. Pre-sales should map how an enterprise tool would earn that status: data residency, no-training terms, logging and records handling for prompts. Integration with county systems requires written ITC approval, so plan that review. Constraint: CJIS and HIPAA data limit which departments can use any tool. Interpretation: approval criteria are not yet written.","delivery":"Delivery framing: Turn the policy into practice: define Trusted GenAI criteria, publish an approved tool list, build a short training module, and set up the ITC request path for integrations. Departments can tighten rules, so map department variants. Ownership sits with ITC and CEO Human Relations. Interpretation: the policy describes no inventory or monitoring step, so compliance will depend on self-reporting until one is added."},"roleDetails":{"sales":{"customerProblem":"County needs consistent, enforceable staff GenAI rules without new staff or budget.","stakeholders":["Board of Supervisors","Chief Executive Office","CIO/ITC","CEO Human Relations","Department heads"],"discoveryQuestions":["What criteria will make a tool Trusted GenAI?","Which departments handle CJIS or HIPAA data?","How will prompt records be retained for public records requests?","Is training going to become mandatory?"],"valueHypothesis":"Clear approval criteria and training may speed safe adoption under the new policy; no adoption metrics exist.","potentialEngagement":"Short engagement to draft Trusted GenAI criteria, an approved tool list, and staff training aligned to Tab 16.","unsupportedClaims":["That the policy reduced data exposure","Productivity gains from GenAI in the county","That the board adopted it unchanged (not verified from minutes)"]},"engineering":{"fit":"Enterprise GenAI tools that can meet no-training, retention and records requirements.","architectureIntegration":"ITC written approval gate for any integration with county software; trusted tools separated from public tools.","prerequisites":["Defined Trusted GenAI criteria","Data classification by department","Records retention guidance for prompts"],"constraints":["CJIS, HIPAA, IRS and CCPA obligations","No dedicated staffing","Department-specific stricter rules"],"security":"Public tools barred from confidential data; trusted-tool controls undefined.","proofOfValue":["Test that an enterprise tool meets no-training and retention terms","Prompt logging retrievable for records requests","Blocking of unauthorized tools verified"]},"delivery":{"work":"Define approval criteria, publish tool list, create training, run integration request process.","dependencies":["Board adoption","ITC capacity","HR training channels"],"ownership":"ITC with CEO Human Relations.","skillsAdoption":"Employees learn to verify AI output and disclose AI listening or transcription tools.","governanceCheckpoints":["Board adoption confirmation","Trusted GenAI designation reviews","Periodic CIO/CEO policy review"],"acceptanceCriteria":["Proposed: published Trusted GenAI criteria","Proposed: approved tool list available to all staff","Proposed: training completion tracked by department"],"risks":["Shadow use of public tools","Undefined trusted-tool exemption","Voluntary training gaps"]}},"retrievedAt":"2026-10-14T22:17:05-05:00","enrichedAt":"2026-10-14T22:18:10-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Bans GenAI in hiring, discipline and other employment decisions; employees bear full responsibility for AI output accuracy.","procurementImplications":"Covers acquiring GenAI software but sets no procurement review criteria beyond ITC approval.","operatingModelImplications":"Policy administered by existing CEO and IT staff with no added resources.","sourceVerification":{"openedUrl":"https://www.stancounty.com/bos/agenda/2026/20261013/B11.pdf","referenceExcerpt":"Ask GenAI systems to find facts or make decisions without expert human review.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}