{"resourceId":"chelan-wa-draft-ai-policy-copilot-preferred-claude-for-complex-ai-prompts-public-records-20261031","versions":[{"version":"external-3c704b545575033e6b1abd2b77df62360e35b057da7c7d616b35212e473cd9a9","resource":{"id":"chelan-wa-draft-ai-policy-copilot-preferred-claude-for-complex-ai-prompts-public-records-20261031","title":"Chelan, Wash., drafts an AI use policy that makes Microsoft Copilot the preferred tool, reserves an enterprise Claude for complex work, and treats AI prompts and outputs as potential public records (council first look Oct. 27; reported Oct. 31)","organization":"City of Chelan","sector":"Local government","geography":"Chelan, Washington, United States","publishedAt":"2026-10-31","publicationDate":"2026-10-31","eventDate":"2026-10-27","sourceName":"Lake Chelan Mirror (Ward Media)","sourceLabel":"Local news report on a city council work item","sourceUrl":"https://lakechelanmirror.com/stories/chelan-considers-rules-for-ai-use-public-records-and-data-privacy,194304","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["governance-procurement","data-security","knowledge-work"],"finding":"The Lake Chelan Mirror reports that Chelan's council got its first look at a draft AI use policy on Oct. 27 and took no action. Microsoft Copilot would be the preferred platform because it works inside Outlook, Word and Excel. Free Copilot could be used only with publicly available information; licensed enterprise Copilot could be used with authorised city information. For complex tasks such as technical analysis, the city would favour an enterprise version of Claude. Personal ChatGPT and Gemini accounts would generally be barred. AI could not be the sole basis for permitting, enforcement or employment decisions. Prompts, conversations and outputs may be public records, and qualifying records must be kept in approved city systems.","sledRelevance":"A small US city is writing a tiered Microsoft policy: free Copilot for public data, enterprise Copilot for city data, and a second vendor for heavier work. It also treats Copilot conversations as records under Washington public-records law. That is the decision many small local governments face when Copilot Chat arrives inside Microsoft 365.","evidence":"A local reporter's account of a staff presentation and council discussion. The draft policy text was not published with the article and was not read.","architectureImplications":"The free/enterprise split depends on users signing in with city accounts and on IT being able to tell tenant-protected Copilot apart from consumer Copilot. Dual-vendor use (Copilot plus Claude) means two sets of identity, logging and data controls.","governanceImplications":"The city administrator would approve tools and IT would run security reviews. Annual policy review, mandatory training and graduated discipline are proposed. Human review is required before AI output is released or relied on.","securityPrivacyImplications":"SSNs, financial and medical data would be limited to approved enterprise systems. Attorney-client, executive-session and some law-enforcement information would need the city attorney's authorisation before entry into any AI system.","caveats":"Draft only; council took no action and the policy may change. Based on news reporting, not the policy text. A small city, so scale and staffing differ from large jurisdictions. The Claude element is outside this stream and is noted only for context.","streamIds":["microsoft","local-government"],"roles":{"sales":"Sales framing: Chelan shows how a small city picks Copilot by default because it already lives in Outlook, Word and Excel, then still plans a second vendor for complex analysis. The opening is not a licence pitch. It is help writing and running a tiered policy: which data can go into free Copilot, which needs enterprise licences, and how AI records are kept. Teams should ask which tasks the city thinks Copilot cannot do, and avoid claiming Copilot covers every use case the draft assigns to another tool.","engineering":"Engineering framing: the policy's free-versus-enterprise split only works if the tenant can enforce it. Engineers should check that city staff sign in to tenant-protected Copilot Chat, that consumer Copilot is blocked or clearly separated, and that Purview retention and eDiscovery cover Copilot interactions for public-records requests. If an enterprise Claude is added, identity, logging and data-loss rules must be set up for both tools. Law-enforcement-sensitive content needs labels that keep it out of AI grounding until the city attorney authorises use.","delivery":"Delivery framing: a small city needs a light but real operating model before adoption. That means an approved-tool list owned by the city administrator, short training that covers public-records duties, a simple way to save non-transitory prompts and outputs into city systems, and an annual review. Delivery teams can help draft the training and records procedure, and define how human review before release will be evidenced. Success should be measured by policy adoption, training completion and records captured, not time saved."},"roleDetails":{"sales":{"customerProblem":"A small city wants staff to use AI that is already in Microsoft 365 but must protect sensitive data and meet public-records law.","stakeholders":["City administrator","HR and communications director","IT staff","City attorney","City council"],"discoveryQuestions":["Which tasks does the city expect Copilot to handle, and which go to another tool?","How will staff tell tenant-protected Copilot from consumer Copilot?","How will AI prompts and outputs be found for a public-records request?","Who approves new AI tools?"],"valueHypothesis":"Helping the city stand up a tiered Copilot policy with records procedures may reduce unapproved consumer AI use, if staff adopt the approved path.","potentialEngagement":"A short policy-to-practice engagement: tenant settings review, training module and records-capture procedure for Copilot.","unsupportedClaims":["That Copilot replaces the separate tool the draft names for complex work","That the policy has been adopted","Any productivity gain for city staff"]},"engineering":{"fit":"Good fit for a Microsoft 365 city that wants governed Copilot Chat with clear data tiers.","architectureIntegration":"Copilot Chat in the city's tenant, with Purview retention and eDiscovery for AI interactions; a second AI vendor would sit alongside with separate controls.","prerequisites":["City accounts for all staff using AI","Sensitivity labels for confidential and law-enforcement content","Retention policy covering Copilot interactions"],"constraints":["Small IT staff","Washington public-records obligations","Policy is still a draft"],"security":"Block or separate consumer Copilot, label attorney-client and law-enforcement content, and log AI use for audit and records requests.","proofOfValue":["Run a mock public-records request for Copilot prompts and outputs","Check that labelled confidential content is excluded from Copilot answers"]},"delivery":{"work":"Turn the draft policy into tenant settings, training and a records-capture procedure for Copilot.","dependencies":["Council adoption of the policy","IT security review","City attorney guidance on sensitive information"],"ownership":"City administrator for policy; IT for tenant controls and accounts.","skillsAdoption":"Short role-based training on approved tools, verification and records duties before access is granted.","governanceCheckpoints":["Council adopts the policy","Tenant settings match the policy's data tiers","Annual policy review"],"acceptanceCriteria":["Proposed: 100% of AI users complete training before access","Proposed: a test records request returns Copilot content within the statutory response process","Proposed: no consumer AI accounts used for city business in a sampled audit"],"risks":["Policy changes before adoption","Staff keep using consumer tools","AI records lost before capture"]}},"retrievedAt":"2026-11-02T14:33:16Z","enrichedAt":"2026-11-02T14:41:07Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Training on approved tools, security and public-records duties would be required before use.","procurementImplications":"Copilot is preferred because it is bundled with existing Microsoft software, while a separate enterprise Claude purchase is contemplated for complex work, so Microsoft is not assumed to be the only AI vendor.","operatingModelImplications":"IT owns security review and accounts; the city administrator owns tool approval; employees own verification and records capture.","sourceVerification":{"openedUrl":"https://lakechelanmirror.com/stories/chelan-considers-rules-for-ai-use-public-records-and-data-privacy,194304","referenceExcerpt":"Prompts, conversations and documents generated through AI tools may qualify as public records when they relate to city business.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}