Microsoft 365 Copilot

Microsoft 365 Copilot is not police technology. It is generative AI built into Word, Outlook, Teams and the rest of the Microsoft office suite: drafting documents, summarising meetings, searching across an organisation's own files and email.

It appears in this catalogue because at least 21 English police forces have deployed it, and because a general-purpose tool inside a police force operates on police material.

WHY A GENERAL TOOL RAISES SPECIFIC QUESTIONS

The documents in a police force's Microsoft environment are not ordinary corporate documents. They include intelligence reports, victim and witness statements, case files, custody records and safeguarding referrals.

A tool that summarises meetings is summarising strategy discussions about live investigations. A tool that searches across an organisation's files is searching material subject to disclosure obligations, data protection restrictions and, in some cases, legal privilege. A tool that drafts documents is drafting text that may end up in a case file.

None of that makes deployment wrong. It does mean the assurance questions differ from those a private company would ask, and that the absence of policing-specific scrutiny is itself notable — this site's tracker records at least one force having paused its deployment.

THE CASE FOR IT

Police forces run enormous administrative overheads, and officers consistently report paperwork as the largest drain on time available for policing. Generic productivity gains in drafting and summarisation are real and apply as much to a force as to any other large organisation.

It is also enterprise software from an established supplier with contractual data-handling commitments, deployed inside an existing environment. That is a different risk profile from bespoke police AI bought from a startup with no track record, which is much of what this catalogue contains.

And unlike almost everything else here, it is not directed at the public. Its subject is the force's own paperwork.

THE CASE AGAINST

The absence of specificity cuts both ways. Because it is not a policing tool, it may not have been assessed as one — no equality impact assessment, no evaluation against policing use cases, no consideration of what happens when generated text enters an evidential document.

Generative AI produces fluent text regardless of accuracy, and this site's page on AI report writing documents what that means when the output is a police document. Copilot is not marketed for report writing, but nothing prevents an officer from using it that way, and the disclosure requirements now legislated in some US states for AI-drafted reports would not obviously be triggered by a general-purpose tool.

Auditability is the practical problem. A dedicated report-writing tool logs that AI was used. A general assistant embedded in Word does not necessarily leave that trace, which makes it impossible to establish afterwards which documents were machine-drafted.

Summarisation carries its own risk: a summary that omits a material detail from a long document is a failure mode that looks like success.

WHAT IS NOT ESTABLISHED

Which forces have deployed it, and with what restrictions on the material it may access, is not systematically published.

Whether any force has conducted a policing-specific impact assessment is not established.

The reason for the paused deployment recorded on this site's tracker is not documented.

Whether outputs are logged as AI-assisted in any force is not established.