Custom GPT: Build a Report Writing Assistant for Your Whole Squad
What This Builds
A Custom GPT configured specifically for your department's report format, state legal standards, and most common case types. Unlike ChatGPT's generic Custom Instructions (which only apply to your own account), a Custom GPT can be shared via link with your entire squad — giving everyone access to the same department-standard AI report assistant from day one.
Prerequisites
- ChatGPT Plus subscription ({{tool:ChatGPT.price}}) — required to create Custom GPTs
- Comfortable using ChatGPT for at least 2 weeks of report drafts
- Your department's report format guidelines (or a sample of well-written reports)
- List of your most common charge types and their state statutes
The Concept
A Custom GPT is like a specialized version of ChatGPT pre-configured with your job context. Think of it as the difference between a generic new recruit and an officer who already knows your department's policies, your preferred report format, and your common case types. You set it up once, and every officer who uses it gets that same starting baseline — no re-explaining format preferences every session.
Build It Step by Step
Part 1: Access the Custom GPT Builder
- Log in to ChatGPT Plus at chatgpt.com
- In the left sidebar, click Explore GPTs → then look for Create (or go to chatgpt.com/create directly)
- Click Create a GPT
- You'll see a split screen: conversation on the left (the builder) and preview on the right
Part 2: Write Your System Instructions (the most important step)
In the Configure tab (switch to it at the top), find the Instructions box. This is where the GPT's personality and behavior is defined. Write your instructions carefully — this is what makes your GPT different from generic ChatGPT.
Copy and adapt this template:
You are a police incident report writing assistant for patrol officers at [Department Name / "a municipal police department" if you don't want to specify].
YOUR ROLE:
Help patrol officers draft, improve, and review police incident reports, arrest affidavits, use-of-force narratives, and related documentation.
REPORT FORMAT RULES (always follow these):
- Write in third person, past tense ("The officer observed..." not "I saw...")
- Use professional law enforcement terminology
- Structure narratives chronologically: arrival → observations → actions taken → outcome
- Never add facts, assumptions, or conclusions not provided by the officer
- Flag any gaps in the officer's notes as [MISSING: describe what's needed]
- For arrest affidavits: structure as facts establishing probable cause, cite the charge
STATE-SPECIFIC CONTEXT:
- State: [your state]
- Common charges in this jurisdiction: [list 5-10 common ones — DUI .08+ BAC per [statute], battery on law enforcement per [statute], trespass per [statute], etc.]
ALWAYS DO:
- Ask for clarification if critical facts are missing (time, location, subject description)
- Format reports with clear sections
- Use flag notation [VERIFY: ...] for any facts that should be double-checked
NEVER DO:
- Hallucinate facts not provided
- Add legal conclusions not established by the officer's stated facts
- Change specific names, addresses, dates, or case numbers
Fill in your state, department name (optional), and your most common 5-10 charges with their statutory citations.
Part 3: Add a Conversation Starter
Still in the Configure tab, scroll to Conversation starters. Add these so new users know what to do:
- "Draft incident report from my notes"
- "Draft a probable cause affidavit for [charge]"
- "Review my draft report for gaps"
- "Write a use-of-force narrative from my incident facts"
Part 4: (Optional) Add Knowledge Files
If you want to give the GPT access to your department's policy language or common report templates:
- In the Configure tab, scroll to Knowledge
- Click Upload files
- Upload: department report templates (as .txt or .pdf), common charge definitions, your department's UOF policy
This makes the GPT aware of department-specific formatting and policy language.
Part 5: Test and Refine
Before sharing, test thoroughly:
- Click the Preview panel on the right
- Test each conversation starter
- Test edge cases: what happens if the officer gives incomplete facts? (Should flag [MISSING: ...])
- Test with a real past report: does the output match your department's format?
If anything is off, return to Configure → Instructions and refine.
Part 6: Share with Your Squad
- In the Configure tab, set Who can access to Anyone with a link (or "Only me" for personal use)
- Click Save
- Click Share → copy the link
- Send the link to your squad via group text, department email, or Slack
Officers open the link, click Start chat, and the Custom GPT is ready to use — no setup required on their end.
Real Example: A Sergeant Shares with Their Squad
Setup: Sergeant Kim at a 45-officer department spends 20 minutes building a Custom GPT with department formatting rules and the 8 most common charges in their district.
Input from a junior officer: "Draft report from notes: Vehicle stop on MLK Blvd 2145hrs. Driver failed to signal, DMV showed suspended license. Driver [name] provided ID, confirmed suspended. Cited and released, vehicle towed per policy."
Output: A formatted incident report narrative with: officer's reason for stop, DMV confirmation method noted, charge cited with statute number flagged as [VERIFY: confirm [state] suspended license statute], tow authorization noted. Total time for officer: 4 minutes vs. 20 minutes.
Time saved: Every officer in the squad saves 15-20 minutes per report, every shift.
What to Do When It Breaks
- GPT gives generic responses instead of police format → Your Instructions weren't saved; go back to Configure and re-save
- GPT adds facts you didn't provide → Add to instructions: "NEVER add details not explicitly provided by the officer" — and add specific examples of what not to do
- Officers say it's not matching department format → Have one officer paste their ideal report as a knowledge file example — the GPT will learn the format from real examples
Variations
- Simpler version: Just use Custom Instructions in your own ChatGPT account (Level 3 guide) — no Plus required, just affects your own account
- Extended version: Create separate Custom GPTs for different case types (DUI-specific GPT, domestic violence-specific GPT with mandatory reporting elements, etc.)
What to Do Next
- This week: Share with 2-3 trusted squad members first; get feedback before department-wide rollout
- This month: Refine instructions based on what officers find missing or wrong
- Advanced: Add your department's charge definitions as a knowledge file to make statutory citations automatic
Advanced guide for patrol officer professionals. Custom GPTs require a {{tool:ChatGPT.plan}} subscription. Share links responsibly — do not include real case data in the knowledge files.