Built for the badge. From Orange County.
Report960 is a two-person startup - a working Orange County police officer and a developer - building the report-writing tool we wished existed on shift. Grounded in verbatim California law, defensible by design, and made for the reality of end-of-watch paperwork.
Why "960"?
In Orange County, 960 is the radio code for "officer needs backup." When you key up and call 960, help is already on the way.
That's the entire point of this product. Report writing is where good arrests get lost, where cases get kicked, and where careers get second-guessed years later. Report960 is backup for the part of the shift nobody trained you for in the academy.
Mission
Give every officer a defensible, accurate, second set of eyes on their report - grounded in the actual California code - so they walk out of end-of-watch confident the paperwork won't come back to bite them.
Better reports. Cleaner filings. Fewer callbacks from the DA. A record you can stand behind years later.
Why we built this
Report960 started the way most useful things do - a cop complaining about paperwork, and a developer who wouldn't let it go.
Officers were already using ChatGPT, Gemini, and every other public LLM to help polish their reports. It "worked" - until it didn't. The models hallucinated Penal Code sections. They cited case law that had been overturned. They invented Vehicle Code subsections that don't exist. Officers were spending twenty minutes bouncing between three AI tabs and a codebook trying to figure out which answer was actually right - and quietly hoping the DA didn't notice when they were wrong.
That's not a workflow. That's a liability with extra steps.
So we built the opposite. Report960 won't cite law it can't quote. Every citation and every flagged passage is checked against verbatim California statute - Penal, Vehicle, Health & Safety - pulled from the actual codebook, not from whatever the model half-remembered from training data. Anything the library can't back up, or any quote the system can't find word-for-word in your narrative, gets dropped before you ever see it. It is still AI, and you still review every finding - but you are reviewing sourced work, not guesses.
Four things, non-negotiable.
Every flag cites the exact statute or CourtListener case. No paraphrasing the code. No inventing case law. If we can't ground it, we don't say it.
Every analysis is versioned, timestamped, deterministic, and auditable. Years later, you can compare two runs and show exactly what the system saw, what it flagged, and what you did about it.
You didn't sign up to babysit AI. Sub-60-second reviews, fixes re-verified issue by issue as you write, drafts that auto-save, and one-click PDF/DOCX exports.
The more you use it, the more you internalize. Report960 is a coach that leaves a paper trail - not a crutch that replaces judgment.
Two people. One badge. One keyboard.
Report960 is deliberately small. Every feature is pressure-tested against a real patrol shift before it ships. Nothing gets built because it demos well.
A working officer who has written more reports than he can count and read even more that never should have been filed the way they were. Every issue Report960 flags is a issue he's personally watched blow up a case.
A product engineer who spent years building trust-critical software and got tired of watching AI companies sell "magic" that hallucinates in fields where hallucinations ruin lives. Report960 is what you get when a developer treats a courtroom the way they'd treat a production database.
Officers deserve tools built for themnot repurposed chatbots.
You carry the weight of every word you write. Report960 keeps every finding sourced, quotable, and traceable - so the work you sign off on is work you can stand behind today and ten years from now.