01
Officer workflow
How officers enter notes, answer prompts, revise the draft, and complete their review.
The LeoPen platform
The report is only
the beginning.
LeoPen connects report drafting with fact review, Florida jury instructions, agency policy sources, warrant preparation, and the people responsible for approving the work.
Current tools can be demonstrated today. Each agency confirms its pilot scope and deployment before testing begins.
Available to evaluate now
The working platform.
Exact features and deployment configuration are scoped for each pilot.
01
Report drafting
Turn officer-provided notes into a working narrative ready for correction and review.
Officer facts · Draft provenance · Review handoff
02Fact & instruction review
Compare the draft with the officer’s facts and exact language from Florida jury instructions.
Fact check · Confirmation prompts · Exact clauses
03Policy sources
Ask questions across agency-provided policy and inspect the retained source.
Agency library · Cited answers · Source page
04Warrant preparation
Organize warrant facts, nexus, timing, reliability, and particularity for review.
Guided facts · In-tab drafting · Legal review
05Source-grounded review
See how task-specific workflows, approved sources, and review states shape the AI service inside LeoPen.
Source retrieval · Application rules · Review state
How a pilot works
Start small. Test the work. Keep the evidence.
A pilot begins with a defined use case and ends with a written decision based on what officers and reviewers actually saw.
- 01
Choose a narrow use case
Agree on the report types, users, reviewers, test scenarios, and success measures.
- 02
Confirm the setup
Document access, sources, retention, deployment, and responsibilities before agency data is used.
- 03
Run representative reports
Officers use realistic scenarios and compare each draft with the notes that produced it.
- 04
Review the evidence
The agency scores the results, records problems, and decides whether the pilot should continue.
What a pilot should test
Evaluate the work around the report.
A useful pilot defines representative scenarios, expected reviewer behavior, source ownership, access, deployment, and measurable acceptance criteria.
02
Supervisor review
Fact-comparison signals, source links, draft context, and the handoff into the agency’s approval process.
03
Source governance
Which Florida jury-instruction sets are included and how policy documents are approved, updated, and opened by users.
04
Administration & deployment
Protected access, agency scope, role-aware functions, providers, data flow, and the operating responsibility split.
Connected by design
The draft starts the review.
The same documented facts continue through the narrative, fact check, prompts, instruction comparison, and source inspection.
- 01Supply the facts the officer documented
- 02Create and revise a working narrative
- 03Check the draft against the supplied fact set
- 04Confirm relevant missing information
- 05Compare with a Florida jury instruction
- 06Open the source and complete agency review
Product scope
What stays outside the software.
- Unconfirmed information is not inserted automatically
- Charging and probable-cause decisions remain outside the product
- The product does not issue admissibility, compliance, or guilt conclusions
- Officer, supervisor, prosecutor, policy, and legal review remain part of agency procedure
Preview & roadmap
Separated from current availability.
Crash-scene tools
Preview workflow; pilot scope must be confirmed.
Video analysis
Roadmap capability; not represented as generally available.
Direct RMS integration
Planned integration work; current output can be reviewed and exported.
RMS today
Review, then copy or download.
LeoPen does not connect directly to an RMS today. Officers review the working draft, then copy or download it for the agency's existing report process. Direct RMS integration remains planned.