See exactly what Copilot Chat does for your people.
Pick a role below. You'll see three realistic prompts an NYPD member could type today — no training required — along with what a good response looks like. Every example works with your existing Copilot Chat license. Nothing here requires extra add-ons.
Runs in GCC
Enterprise Data Protection (EDP) — prompts aren't used to train models
No add-ons required — works with the Copilot Chat license you already have
Choose a role to explore
Police Officer (Sector)
Three prompts a sector officer could realistically type between jobs — from the RMP laptop, a Department-issued phone, or at the desk after tour.
Prompt 1
Turn rough notes into a clean Activity Log narrative
Rewrite the notes below into a clear, objective Activity Log narrative. Use past tense, third person, and neutral professional language. Keep every fact. Remove opinions, slang, and filler. Put events in the order they happened. Flag anything that reads like an assumption rather than an observation so I can review it before I finalize the entry.
Notes:
[paste your notes here]
What it does
Takes raw on-post notes and shapes them into the tone and structure your digital Activity Log already expects, without changing any facts.
What good output looks like
A tight narrative in past tense and third person, events in time order, no slang, with anything that reads like an assumption called out separately for the officer to verify.
Prompt 2
Explain a NYS statute in plain English before a citizen contact
Explain NYS Vehicle and Traffic Law Section 1111(d) — failure to stop at a steady red signal — in plain English, as if briefing a new officer at roll call. Tell me:
1. What the violation actually is, in one sentence.
2. The elements that have to be present to issue a summons.
3. Two or three common real-world examples in a NYC setting.
4. One thing officers frequently get wrong about it.
Keep it under 200 words.
What it does
Gives the officer a quick, plain-language refresher on a NYS statute so they're confident explaining it to a motorist or pedestrian.
What good output looks like
A four-part answer under 200 words: one-sentence definition, bulleted elements, concrete NYC examples, and a common pitfall — readable in under a minute.
Prompt 3
Prepare respectful talking points for a sensitive community interaction
Give me five short talking points I can use to respectfully explain to a resident why I can't share details about an ongoing investigation on their block. The resident is worried about their family's safety. Tone should be calm, empathetic, and non-confrontational. Each talking point should be one or two sentences, plain spoken, no legal jargon.
What it does
Prepares an officer with ready-to-say language for a hard doorstep conversation — acknowledging concern without compromising the case.
What good output looks like
Five short, human talking points an officer could actually say out loud: acknowledges the concern, explains the limit plainly, offers a next step, and never sounds scripted.
Desk Officer / Platoon Commander
Three prompts for the supervisor running the tour — moving fast, keeping it clean, and communicating up, down, and across.
Prompt 1
Draft a roll call from a short list of items
Draft a five-minute roll call based on the items below. Order it safety alerts first, assignments second, administrative notes last. Keep the whole thing under 400 words and written for reading out loud. Use short sentences. Don't add anything that isn't in the list.
Items:
- [paste your bullets here]
What it does
Takes the platoon commander's quick bullet list and turns it into a clean roll call script that reads aloud well at the start of tour.
What good output looks like
A single-page roll call under 400 words, ordered safety → assignments → admin, in short spoken sentences — nothing invented, nothing padded.
Prompt 2
Write a mutual aid request to a neighboring command
Draft a short, professional email to a neighboring precinct or PSA requesting mutual aid for a planned community event. Include: purpose of the event, date and hours, expected crowd size, the specific resources we're asking for, a polite ask for a single point of contact on their side, and a thank-you. Keep the tone collegial, not formal. Under 250 words.
Event details:
[paste details here]
What it does
Produces a ready-to-send mutual aid request that covers the six things the other command actually needs to decide quickly.
What good output looks like
A polished email under 250 words with a clear subject line, the six required pieces of information, and a tone that sounds like one supervisor writing to another.
Prompt 3
Turn raw notes into a clean end-of-tour recap
Turn these notes into a clean chronological end-of-tour recap for the incoming platoon commander. Use 24-hour time. One event per line. Objective, neutral language — no opinions or conclusions. If times are missing or unclear, list the entry as "time not confirmed" rather than guessing. End with a short bulleted list of anything the next tour needs to pick up on.
Notes:
[paste notes here]
What it does
Converts messy tour notes into a defensible handoff the relieving commander can actually use.
What good output looks like
A clean chronological list in 24-hour time with one event per line, honest flags where data is missing, and a short list of carryovers — never a guess presented as fact.
Integrity Control Officer / Operations Lieutenant
Three prompts for the lieutenant running the administrative side of the precinct — Interim Orders, CompStat prep, and public-facing correspondence.
Prompt 1
Summarize an Interim Order into a one-page command brief
Summarize the Interim Order below into a one-page brief for the precinct command. Structure it as:
- Order number and effective date
- What changed from the prior Patrol Guide language (plain English)
- Who this affects day-to-day (patrol, detectives, supervisors)
- Three things supervisors need to do differently starting now
- Anything I should flag back to the Legal Bureau or the Police Academy
Keep it to one page. No jargon. If something in the order is ambiguous, call it out rather than paper over it.
Order:
[paste the Interim Order text here]
What it does
Compresses a dense Interim Order into a one-page command brief that answers the questions the CO and XO always ask first.
What good output looks like
A single page, plain English, five clearly labeled sections, with ambiguities flagged for Legal or the Academy instead of smoothed over.
Prompt 2
Draft CompStat talking points from a set of numbers
Turn the numbers below into a short set of CompStat talking points for my CO. I need:
- Two sentences on what the numbers show (up, down, flat, against what baseline)
- Three sentences on what we are doing about it (deployment, outreach, enforcement)
- One sentence on what we'd ask the Borough for
Use plain, confident language. Do not speculate beyond what the numbers support. Under 200 words total.
Numbers:
[paste the category totals and comparisons here]
What it does
Turns raw crime category numbers into a crisp, honest briefing script the CO can actually deliver under CompStat pressure.
What good output looks like
Under 200 words, six sentences split the way the prompt asks, grounded only in the numbers provided, with one clear ask to the Borough.
Prompt 3
Write a courteous response to a FOIL request
Draft a professional response letter to a Freedom of Information Law (FOIL) request. Use a courteous, formal tone. Include: acknowledgment of the request and date received, what records we are providing, what records we are withholding and the general reason (without disclosing protected content), how to appeal to the NYPD Records Access Appeals Officer, and a point of contact. Do not speculate about motives. Keep it under one page.
Details:
- Requester: [name]
- Date received: [date]
- Records requested: [topic]
- Providing: [list]
- Withholding: [list] under [exemption, e.g., Public Officers Law § 87(2)(e)]
What it does
Produces a respectful, legally careful FOIL response that covers the standard elements without sounding defensive.
What good output looks like
One page, formal but human, acknowledges & lists what's provided, explains withholdings without oversharing, gives appeal rights and a contact — ready for Legal review.
Precinct Detective
Three prompts for the Precinct Detective Squad — including the domestic violence investigators now posted at every command — between knocks, interviews, and paperwork.
Prompt 1
Prepare witness interview questions for a nervous witness
Help me prepare an interview outline for a witness to a commercial robbery. The witness is nervous and speaks English as a second language. Draft ten open-ended questions, starting with non-threatening context questions (who they are, where they were, what their day looked like) and moving toward specifics (what they saw, heard, and did). Keep each question to one idea, plain language, short sentences. At the end, give me three follow-up probes I can use if answers are vague.
What it does
Builds a trauma-aware, ESL-friendly interview outline so a detective walks in with a plan instead of improvising under pressure.
What good output looks like
Ten open-ended questions in a clear arc from rapport to specifics, all plain English and one idea each, plus three concrete probes for vague answers.
Prompt 2
Turn investigative notes into a case chronology for the ADA
Turn the notes below into a clean case chronology I can share with the ADA. Use neutral language. Date and 24-hour time on every entry. After each fact, put a short source tag in parentheses — (witness), (video), (911 call), (physical evidence), (officer observation). At the end, give me a short list of gaps that still need to be closed before the case is trial-ready.
Notes:
[paste your investigative notes here]
What it does
Organizes messy investigative notes into a source-tagged chronology the ADA can read quickly — and makes the remaining gaps obvious.
What good output looks like
A dated, time-stamped timeline in neutral tone, each fact tagged to its source, followed by a short honest list of what still needs to be verified or obtained.
Prompt 3
Rewrite notes as a clean follow-up report
Rewrite the notes below as an investigative follow-up report. Past tense, third person, objective tone. Cover who, what, where, when, and how in that order. Keep every fact. Remove opinions. Flag anything that reads as speculation or hearsay so I can verify before I file. End with a one-line status: "Open — further investigation" or "Closed — pending review."
Notes:
[paste your follow-up notes here]
What it does
Gets a detective's rough notes into the shape and tone a supervisor expects for a follow-up report — so the detective's time goes into the case, not the formatting.
What good output looks like
A disciplined past-tense, third-person narrative covering the five W's, speculation flagged separately, and a clean one-line status at the bottom.
What Copilot Chat will not do with the Basic license
With the Copilot Chat Basic license only — no add-ons — the boundaries below describe where Copilot Chat stops on its own and where supervisory or Legal Bureau review takes over.
Copilot Chat is a general-purpose reasoning and writing assistant protected by Enterprise Data Protection. It is not grounded in your systems, and this prompt set is intentionally scoped to internal-first artifacts that go through normal review before anything external happens.
What Copilot Chat will not do with the license alone
Won't read an officer's Outlook mailbox or calendar
Won't read Teams chats, channels, or meeting transcripts
Won't search or summarize SharePoint or OneDrive files automatically
Won't connect to CAD, RMS, DAS, eSummons, or any case-management system
Won't retrieve real-time crime data, CompStat numbers, or arrest records (public web data still accessible)
Won't draft public-facing communications involving named complainants, victims, or subjects (not a system constraint, governance/policy decision)
Won't produce arrest reports, complaint reports, or use-of-force statements (not a system constraint, model can generate this content)
Won't perform probable cause determinations or disciplinary documentation (not a system constraint, advisory limitation)
Won't replace supervisory or Legal Bureau review of any report before it's filed or sent (not a system constraint, human oversight requirement)
Won't retain your prompts to train foundation models (EDP protection)
Ready to see this in your environment?
We'll run a 45-minute live demo against your GCC tenant with your team's real-world scenarios — no configuration required on your side.