{"resourceId":"verona-wi-generative-ai-policy-copilot-only-full-disclosure-20261026","versions":[{"version":"external-e295dc651ac230c66d3320049d2f65f89011beda235a1d9b44cf61623349252c","resource":{"id":"verona-wi-generative-ai-policy-copilot-only-full-disclosure-20261026","title":"Verona, Wisconsin adopts a staff generative AI policy: Copilot only, disclosure of any AI use, termination for entering protected data","organization":"City of Verona, Wisconsin","sector":"Municipal workforce AI policy","geography":"Verona, Wisconsin, United States","publishedAt":"27 October 2026, 12:09 p.m. CDT (Verona Press)","publicationDate":"2026-10-27","eventDate":"2026-10-26","sourceName":"Verona Press","sourceLabel":"Local news report on a council vote","sourceUrl":"https://www.veronapress.com/news/government/council-talks-ai-2027-budget/article_790892c2-332e-4332-b016-6dcf697f3675.html","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["governance-procurement","data-security","accessibility-workforce"],"finding":"Verona's council approved a generative AI policy for employees on 26 October that makes Microsoft Copilot the only approved platform unless otherwise permitted, requires disclosure whenever AI is used to create something (the council removed a 'substantial' use threshold), makes employees responsible for accuracy, and bars entry of personnel records, personal information and records exempt from public disclosure, with unauthorized entry grounds for termination. An alder asked for matching AI expectations for contractors.","sledRelevance":"Why now: although reported on 27 October, it is newly relevant beside the 28 October Falls Church report, because both cities rely on Copilot-centred rules and staff responsibility; Verona's article describes no monitoring mechanism, which is the gap Falls Church acknowledged.","evidence":"Reporter's account of the council meeting with quoted alders; policy text not opened.","architectureImplications":"A single approved platform simplifies controls but depends on blocking or detecting other tools.","governanceImplications":"Full-disclosure rule and termination penalty set a strict standard; alderpersons are outside the policy.","securityPrivacyImplications":"Prohibits personnel, personal and disclosure-exempt data in AI tools; enforcement method not described.","caveats":"Policy text not opened; no implementation detail; elected officials excluded.","streamIds":["local-government"],"roles":{"sales":"Framing: Verona has adopted a strict, Copilot-only staff AI policy with full disclosure and termination for misuse of protected data. Interpretation: cities adopting similar rules may need help turning them into training, disclosure practice and contractor terms. The article does not show how compliance will be checked, so a bounded offer is an implementation plan, not a tool. The evidence cannot support claims that the policy prevents data exposure or improves productivity.","engineering":"Framing: a single approved platform is only as strong as the controls around it. Interpretation: engineers should confirm what tenant settings, sensitivity labels and logging exist for Copilot, and whether other AI tools are blocked or merely prohibited. Because unauthorized entry of protected data is a termination offense, the city will need evidence of what was entered, which depends on audit logging that the article does not mention.","delivery":"Framing: full disclosure and termination penalties make clarity essential. Interpretation: delivery teams should define what counts as AI use requiring disclosure, how disclosures are recorded, which data categories are prohibited in practice, and how contractors are bound to similar rules. Training should come before enforcement. Acceptance criteria are proposals, such as all staff trained and contractor clauses drafted, because the source reports only adoption."},"roleDetails":{"sales":{"customerProblem":"A city has adopted strict staff AI rules and must make them workable and enforceable.","stakeholders":["City administrator","IT staff","HR","City attorney","Common Council","Department heads"],"discoveryQuestions":["How will disclosures be recorded?","How will entry of protected data be detected?","Will contractors be bound to the same rules?","What training is planned before enforcement?"],"valueHypothesis":"Bounded: an implementation plan could reduce inconsistent disclosure and enforcement disputes.","potentialEngagement":"Policy implementation support covering disclosure practice, training and contractor clauses.","unsupportedClaims":["The policy prevents data leaks","Copilot use improves productivity","Employees understand the disclosure rule"]},"engineering":{"fit":"Municipalities standardizing on one approved generative AI platform.","architectureIntegration":"Configure the approved platform's data protection and audit settings and block or monitor unapproved tools.","prerequisites":["Tenant configuration review","Data classification for personnel and exempt records","Decision on blocking other AI sites"],"constraints":["Elected officials outside policy","Public records law obligations","Small IT capacity"],"security":"Apply sensitivity labels and logging so prohibited data entry can be evidenced before any disciplinary action.","proofOfValue":["Confirm that audit logs capture prompts for the approved platform","Test whether unapproved AI sites are reachable from city devices"]},"delivery":{"work":"Translate the policy into training, a disclosure method and contractor terms.","dependencies":["City attorney guidance on disclosure","HR process for violations","Vendor support for tenant settings"],"ownership":"City administrator with IT and HR.","skillsAdoption":"Staff learn what to disclose, which data is prohibited and how to check AI output for accuracy.","governanceCheckpoints":["Training completion before enforcement","Review of disclosure practice after first months","Contractor clause adoption"],"acceptanceCriteria":["Proposed: all employees trained on the policy","Proposed: documented disclosure method in use","Proposed: AI clause added to new consultant contracts"],"risks":["Over- or under-disclosure","Disputed disciplinary cases without logs","Shadow use of other tools"]}},"retrievedAt":"2026-10-29T22:16:32-05:00","enrichedAt":"2026-10-29T22:25:58-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Places accuracy review and data-handling duties on each employee, with termination as a possible consequence, which raises the stakes of training.","procurementImplications":"Council discussion points to adding AI-use expectations to consultant and contractor agreements.","operatingModelImplications":"Disclosure of all AI use will create a volume of disclosures that someone needs to define and track.","sourceVerification":{"openedUrl":"https://www.veronapress.com/news/government/council-talks-ai-2027-budget/article_790892c2-332e-4332-b016-6dcf697f3675.html","referenceExcerpt":"Unauthorized entry of such information into AI systems is grounds for termination.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}