West Chester Borough’s latest technology report marks its Microsoft Copilot integration project complete, while separately recording that an AI policy was submitted for approval on October 25.
The distinction appears in Chief Information Security Officer William Mann’s October report, dated November 2, in the packet for the November 11 Administration, Communication & Technology Committee meeting. The borough’s portal lists the agenda as posted November 6.
For residents following AI use in borough government, the report documents a project milestone and a policy submission. It does not establish approval of the policy or identify the individual tasks employees are performing with Copilot.
A continuing project reaches a reported milestone
The borough’s 2026 final budget, page 30, already included continued AI exploration through Microsoft Copilot integration among the IT department’s operational goals. The work therefore predates this month’s committee agenda.
On packet page 7, the October report places a completion label above the Copilot integration project. Its accompanying description still refers to a small AI exploration team examining productivity, potential problems, policy and guidelines.
That entry gives no completion date, license count, list of participating departments or measured time savings. The completion label is the borough’s reported status, rather than an independent assessment of how well the software works.
The policy has its own status
The policy list on packet page 6 covers email confidentiality, application installation, screen locking, personal devices and remote work. It says policies were issued to staff through Paylocity, but separately marks the AI policy as submitted for approval on October 25, 2026.
The entry supplies neither the AI policy’s text nor an approval date. Readers cannot determine its rules for entering resident information, checking generated answers or retaining work from that short status line.
Why the software details matter
Microsoft’s current Copilot overview describes functions such as drafting and summarizing documents and email. It also explains that available features and access to organizational information depend on licensing and configuration, with access governed by user permissions.
Those are the supplier’s product descriptions. They do not establish West Chester’s licenses, settings or actual uses. The borough report’s reference to Copilot for Microsoft 365 alone does not resolve those details.
Useful follow up records would identify which employees and applications the project covers, the recurring cost, what information staff may provide to the system, and who checks an answer before it becomes an official communication. Those questions concern implementation and oversight, rather than whether a project status box says complete.
For a different municipal application, our Kennett Township AI front desk report examines proposed resident communications, fees and transfers to staff.
Where to follow the West Chester discussion
The November 11 agenda includes public meeting management and AI under reports. The portal schedules the committee for 6:30 p.m. at the Municipal Building, 401 East Gay Street, West Chester. Recheck the meeting listing for changes before attending.
The agenda does not list an AI policy approval vote. Any later adoption or detailed operating rules would need their own supporting record. Our West Chester meeting records guide explains how to follow agendas through to minutes and recordings. More local technology reporting appears in the Chester County coverage hub.
Photo: Aleksandar Cvetanovic on Pexels, used under the Pexels License. Illustrative stock photograph of a smartphone beside a laptop. It does not show West Chester equipment or a Copilot session.




