
GITNUXSOFTWARE REVIEW
SecurityTop 10 Best Police Rms Software of 2026
Compare police rms software options for law enforcement, with records workflows and fit notes for teams evaluating systems like Omnigo.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy
Tyler Technologies New World Public Safety Records is the best fit for mid-size to large agencies because it ties evidence tracking and chain-of-custody events directly to configurable incident workflows with governance in place, while Southern Software RMS is a strong alternative for teams that prioritize fast case discovery via linked person identities.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Tyler Technologies New World Public Safety Records
Case-linked evidence tracking with chain-of-custody events recorded in line with the incident workflow.
Best for: Fits when mid-size to large agencies need configurable incident and evidence workflows with strong governance controls.
Southern Software RMS
Editor pickMaster name indexing links person identities across reports for faster case discovery and review workflows.
Best for: Fits when incident workflows, evidence tracking, and audit visibility matter more than minimal setup.
Omnigo Software
Editor pickIncident record routing built for configurable report workflows tied to CAD event context.
Best for: Fits when mid-size agencies need workflow-driven RMS with CAD correlation and NIBRS-style reporting exports.
Comparison Table
Tyler Technologies New World Public Safety Records
enterpriseIntegrated law enforcement records management software within the New World public safety suite.
Case-linked evidence tracking with chain-of-custody events recorded in line with the incident workflow.
Tyler Technologies New World Public Safety Records manages police incident report workflows, case records, and evidence tracking from intake through disposition. The system supports records tasks aligned to CJIS expectations with configurable audit trail logging, role-based access control, and retention-driven disposition workflows.
Integration coverage focuses on CAD-to-RMS interfaces and data exchanges used for agency reporting, including NIBRS-related extracts. Admin control centers on user and role governance plus multi-jurisdiction deployment configuration for shared operational environments.
- +Incident report workflow configuration supports consistent field-to-back-office handling
- +Evidence and chain-of-custody tracking stays tied to each case record
- +Audit log and RBAC reduce access gaps across records, evidence, and reports
- +CAD-to-RMS interface supports event-number continuity into incident records
- –Configuration depth can slow initial rollout for agencies with atypical workflows
- –NIBRS and extract outputs depend on correct mapping and reporting setup
Records administrators
Manage case retention and dispositions
Fewer disposition inconsistencies
Evidence coordinators
Track evidence from intake to transfer
Improved evidence traceability
Show 2 more scenarios
Multi-agency operations teams
Run shared RMS across jurisdictions
Consistent cross-agency operations
Support multi-jurisdiction configuration for shared environments with role and access governance.
Reporting specialists
Generate NIBRS-related extracts from RMS
Faster report production
Produce reporting-ready extracts using CAD-to-RMS interfaces for agency submission needs.
Best for: Fits when mid-size to large agencies need configurable incident and evidence workflows with strong governance controls.
Southern Software RMS
SMBPolice records management software for incident reporting, citations, warrants, and investigations.
Master name indexing links person identities across reports for faster case discovery and review workflows.
Southern Software RMS is built for incident-by-incident reporting with configurable work steps for investigators and supervisors who need consistent completion. Evidence and property tracking is included inside the case context, and chain-of-custody status can be maintained through the lifecycle of items. Master name indexing supports cross-incident searches, which reduces reliance on manual report scanning when multiple spellings and aliases appear.
A key tradeoff is that deeper CAD-to-RMS integration and reporting automation depend on specific interface setup rather than being delivered as a universal out-of-the-box mapping. Southern Software RMS fits agencies that run structured incident workflows and need strong internal traceability for edits and approvals. A common usage situation is a mid-size department standardizing investigator steps, then tightening evidence handling and supervisory review before downstream submission processes.
- +Incident workflow configuration supports repeatable investigator steps
- +Evidence and property tracking stays within each report lifecycle
- +Master name indexing improves cross-report search for people and aliases
- +Audit-oriented activity visibility supports supervisor and review controls
- –CAD-to-RMS and external report automation require interface mapping work
- –Some governance features demand careful role configuration to stay consistent
- –Multi-location deployments can increase administrative overhead
- –Advanced customization of forms and fields can lengthen rollout timelines
Investigations unit supervisors
Standardize incident approvals and edits
Fewer incomplete reports
Evidence and property clerks
Maintain custody status by case item
Tighter chain-of-custody tracking
Show 2 more scenarios
Records management staff
Search across reports by identity
Faster report retrieval
Staff can use master name indexing to find related incidents when names vary across submissions.
Agency IT governance teams
Control access and system activity
Clear accountability for changes
Administrators can apply role-based access controls and monitor audit activity for operational accountability.
Best for: Fits when incident workflows, evidence tracking, and audit visibility matter more than minimal setup.
Omnigo Software
enterprisePublic safety records management, CAD, and field reporting software for law enforcement and campus security.
Incident record routing built for configurable report workflows tied to CAD event context.
Omnigo Software is organized around incident and report lifecycles with configurable data capture and permission controls.
CAD-to-RMS correlation connects event context to created records, which reduces duplicate entry during intake.
Reporting outputs support NIBRS and UCR oriented submission preparation so records teams can generate required extracts.
- +Incident-to-report workflows map cleanly to day-to-day case processing
- +CAD-to-RMS correlation supports event-driven record creation
- +NIBRS and UCR oriented exports reduce manual reconciliation work
- +Audit trail logging supports accountability across record edits
- –Advanced automation and integrations require disciplined configuration governance
- –Multi-agency deployments can need extra alignment on shared code sets
- –Field capture workflows depend on setup choices for forms and mappings
- –API extensibility feels narrower than systems built for broad custom integrations
Police investigative units
Connect related records during investigations
Shared record assignments
Police training coordinators
Track course progress and completion
Central training visibility
Show 2 more scenarios
Jail operations staff
Manage bookings and housing checks
More controlled movement records
Run booking, housing checks, scheduled activities, and inmate movement records for daily operations.
Contract security providers
Submit standardized site incident reports
Fewer manual edits
Collect site-specific reports with attachments for supervisor review with less manual correction work.
Best for: Fits when mid-size agencies need workflow-driven RMS with CAD correlation and NIBRS-style reporting exports.
CentralSquare Records
enterprisePublic safety records management software for law enforcement case, incident, and reporting workflows.
Configurable incident report workflow engine that ties reporting states to downstream case processing.
CentralSquare Records is a police records management system built for agency workflows around case management, reporting, and records administration. It supports incident report workflows with configurable forms and status tracking, along with evidence and property handling that ties to investigations.
- +Incident report workflows support configurable statuses and lifecycle tracking.
- +Property and evidence handling keeps links to related incidents and cases.
- +Integration patterns connect records workflows to CAD event numbers.
- +Role-based access control and audit trail logging support governance needs.
- –Configuration-heavy setups can slow changes to reporting and workflow rules.
- –Some jurisdictional reporting mappings require careful administration to stay consistent.
Records supervisors
Route incident reports through statuses
More consistent case records
Investigations analysts
Link evidence and property to cases
Tighter case context
Show 2 more scenarios
Integration coordinators
Connect CAD event numbers to reporting
Reduced manual reconciliation
Use established interfaces to bring CAD event numbers into external reporting requirements.
Agency compliance leads
Audit records access and changes
Clear accountability for actions
Rely on role-based access control and audit trail logging for operational oversight of edits and access.
Best for: Fits when a mid-size or multi-agency deployment needs CAD-linked workflows and controlled evidence administration.
Axon Records
enterpriseCloud-based records management system integrated with Axon's body camera and digital evidence ecosystem.
Evidence status workflows that follow records through the investigation lifecycle with auditable user actions.
Axon Records supports police records management workflows that connect case creation, incident reporting, and evidence tracking into one operational flow.
- +Audit trail logging ties record changes to user actions for accountability
- +Field and case workflows stay linked through end-to-end incident handling
- +Role-based access control supports governed collaboration across investigation roles
- +Evidence tracking workflows reduce handoff gaps between users and statuses
- –CAD-to-RMS integration depth depends on external event mapping quality
- –Some administrative configuration requires disciplined governance to avoid permission sprawl
Field reporting teams
Create and route incident records
Fewer manual handoffs
Records staff and investigators
Add supplements while preserving history
Clear change history
Show 2 more scenarios
Evidence technicians
Document evidence handoffs and status
Traceable evidence movement
Record item status changes and transfers with activity history across evidence technicians and investigation stages.
Investigators
Assemble referrals with supporting records
More complete referrals
Compile reports, exhibits, evidence records, and activity history for review or referral workflows.
Best for: Fits when agencies need incident-to-evidence workflow control with governed access across investigators and records staff.
Hexagon HxGN OnCall Records
enterprisePublic safety records management software for incident documentation, investigations, and compliance.
Hexagon OnCall Records workflow design ties incident updates to evidence and disposition steps with audit trail logging.
HxGN OnCall Records centers on incident workflows that connect case intake, follow-up, and disposition handling in one operational flow. Hexagon also emphasizes integration with Hexagon ecosystem components, which helps reduce manual re-entry when agencies already run Hexagon tools for dispatch, documentation, or digital evidence. The system’s governance is oriented around operational controls such as role-based access and logged change history across record edits.
- +Incident lifecycle workflow keeps case updates aligned across users
- +Audit trail logging supports review of edits and status changes
- +Property and evidence tracking reduces gaps during investigations
- +Integration focus reduces manual re-entry when Hexagon tools are used
- –Cross-jurisdiction reporting mappings demand careful upfront configuration
- –Complex workflows can increase training time for new clerks
- –Some automation depends on configured business rules and templates
- –Customization choices may require ongoing governance to stay consistent
Major city records unit
Process high-volume incident follow-ups
Fewer late corrections
Regional multi-agency task force
Share consistent case data
More consistent case records
Show 2 more scenarios
Agencies with CAD integration
Reduce manual incident entry
Lower data entry workload
CAD event-driven intake supports faster record creation and fewer transcription errors for incoming incidents.
Supervisors and compliance staff
Review changes and accountability
Improved accountability trail
Logged edits and status transitions provide traceability for supervisory review and operational audits.
Best for: Fits when agencies standardize incident workflows and rely on CAD-to-RMS handoffs.
CivicEye Records Management System
vertical specialistCloud-based public safety records management software for police reporting and case workflows.
Multi-jurisdiction configuration that allows local workflow variation while keeping centralized indexing and audit trails consistent.
CivicEye Records Management System is a police records management solution built for multi-jurisdictional deployment, with incident-focused workflows and records lifecycle controls. It supports administrative governance with role-based access control and audit trail logging for operational accountability.
- +Incident workflow routing keeps report steps aligned across shifts
- +Role-based access control supports separation between clerks and supervisors
- +Audit trail logging provides traceability for changes to records
- +Multi-jurisdiction configuration supports shared operations and local variations
- –Configuration complexity increases when jurisdictions require different workflows
- –Automation relies on integration setup for CAD-to-RMS interface timing
- –Field reporting coverage depends on enabled modules and import rules
- –NIBRS extract design requires careful mapping to avoid reporting gaps
Records administrators
Operate incident lifecycle across agencies
Consistent multi-agency workflows
Compliance and audit teams
Review who edited records
Stronger audit traceability
Show 2 more scenarios
Evidence and property coordinators
Run retention-driven disposition with evidence
Fewer disposition errors
Coordinate retention-driven disposition handling tied to evidence and property processes.
Systems integration managers
Connect upstream incident activity
Cleaner incident-to-record alignment
Align records workflows with upstream incident activity using agency system connectivity.
Best for: Fits when mid-size agencies need governed incident workflows and multi-jurisdiction records operations with measurable audit trails.
CrimeCenter by Column
SMBCloud records management and report approval software built for modern police departments.
Incident report workflow ties narrative updates to record lifecycle states with audit trail logging across edits.
CrimeCenter by Column is a police records management system built around incident and case workflows used by law enforcement agencies.
- +Incident-centered workflow keeps report, case, and updates in one place
- +Master person index supports consistent identity lookup across investigations
- +Property and evidence tracking includes controlled status movement
- +Audit trail logging supports review of record and workflow changes
- –CAD-to-RMS and upstream event mapping require careful setup
- –Multi-jurisdictional governance needs disciplined RBAC configuration
Investigators
Manage incidents and linked persons
Better investigation context
Property and evidence custodians
Track property custody status changes
Clear custody status
Show 2 more scenarios
Records administrators
Audit and retain records per policy
Policy-aligned retention
Use audit trail logging, retention configuration, and role-based access to support CJIS-aligned operations.
Records integrators
Import documents and event data
Less manual document handling
Bring external documents and event data into records workflows through configurable imports and interfaces.
Best for: Fits when a mid-size agency needs incident workflow control, evidence tracking, and audit logging with integrations.
Sun Ridge Systems RIMS
vertical specialistLaw enforcement records management software for reports, investigations, property, and warrants.
Evidence and property tracking with chain-of-custody oriented updates tied directly to incident records.
RIMS is built around incident and case work with incident report workflow states that help standardize how narratives, charges, and follow-up steps move through staff queues. Property and evidence tracking connects physical items to case records, which reduces the need for parallel spreadsheets when handling chain of custody steps and updates. Audit trail logging records who changed records and when, which is relevant for security review of modification history across investigators, analysts, and supervisors.
- +Audit trail logging tracks record changes for investigators and supervisors
- +Evidence and property tracking ties items to case records and workflows
- +RBAC limits who can view or edit sensitive incident content
- +Configurable incident workflow supports consistent staff routing
- –Workflow and role configuration requires policy mapping to avoid staff workarounds
- –Integration depth depends on interface implementation for external systems
- –Reporting tuning can take time for agencies with custom oversight needs
- –UI navigation can feel dense for staff used to simpler records tools
Patrol supervisors
Review incident workflow progress
Faster oversight and fewer status disputes
Investigations teams
Manage evidence tied to incidents
Reduced duplicate recordkeeping
Show 2 more scenarios
Records and compliance staff
Control who edits sensitive records
More defensible documentation controls
RBAC and audit trail logging support governance reviews of changes to incident and associated documents.
IT integration teams
Automate data movement between systems
Lower manual re-entry workload
API-oriented extensibility and configuration reduce manual exports when linking RIMS to surrounding systems.
Best for: Fits when agencies need governed incident workflows and evidence tracking with audit-ready change history.
Enforsys eFORCE RMS
vertical specialistPolice records management software with integrated CAD, mobile, and jail management options.
Audit trail logging tied to incident and report lifecycle actions, so approvals and edits remain traceable by role.
Enforsys eFORCE RMS is positioned for police records management with incident-centric workflows and law-enforcement reporting support. The system is built around field-to-record continuity, including capture, review, and officer-ready report assembly with governance features for controlled access.
- +Incident workflow keeps field entries aligned through review and release steps.
- +Audit trail logging supports defensible edit and approval history for records content.
- +Role-based access control helps limit who can change sensitive record fields.
- +Integration with CAD-to-RMS style event identifiers reduces manual reconciliation work.
- –Wider integration coverage may require additional configuration across agency systems.
- –Complex workflows can slow adoption without disciplined role design and training.
Police records staff
Assemble officer-ready reports
Faster report assembly
Investigations coordinators
Maintain continuity from field capture
Less duplicate data entry
Show 2 more scenarios
Reporting and compliance teams
Produce NIBRS extracts from CAD events
More efficient extracts
Use CAD-to-RMS interfaces and downstream outputs to generate NIBRS extracts for submissions.
RMS administrators
Control approvals and releases
Controlled record release
Apply role-based access control and audit trail logging for edit, approval, and release steps.
Best for: Fits when agencies need incident-driven records workflows with auditability and CAD-linked event handling.
Conclusion
After evaluating 10 police rms software, Tyler Technologies New World Public Safety Records stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Frequently Asked Questions About Police Rms Software
How do police RMS systems handle evidence and property tracking tied to incident records?
Which tools support CAD-to-RMS handoffs with incident identifiers?
How does master name indexing affect search across records and case files?
When agencies need multi-jurisdictional deployment, what governance pattern reduces admin drift?
What breaks when incident report workflow states are not tightly connected to downstream case processing?
Which products provide audit trail logging that covers edits, approvals, and release actions?
How do police RMS platforms support CJIS-aligned security controls like RBAC and controlled release?
What integration and API capabilities matter most for automation across records, CAD events, and reporting exports?
How do agencies migrate existing incident and evidence data into an RMS without losing audit context?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
How to Choose the Right Police Rms Software
In police rms software, the differences show up in how data moves and how records stay consistent: integration depth matters when your team needs to import and update events without re-keying, and the automation and API surface determines how much work the system does after deployment. We focus on data model and provisioning-style controls so agencies can operate on the same records reliably across units.
Workflow automation across systems
Why it matters
Workflow automation across systems cuts down on manual re-entry when information changes in one place and must reflect in records everywhere. In police rms software, that reduces mismatches between reports, parties, and follow-ups.
How to check
Ask for a demo scenario where an external system produces a new event and the RMS updates the related record automatically. Then ask whether users can see a before/after timeline that shows what the system updated and when.
API and webhook availability for updates
Why it matters
API and webhook availability for updates matters because agencies often need custom triggers for corrections, notifications, or data synchronization. In police rms software, this affects throughput when teams handle high volumes of changes.
How to check
Request an API overview page and sample request/response for core objects (cases and contacts). Ask whether updates can be tested in a sandbox and whether webhooks include enough fields to reconcile records.
Data model fits real incident records
Why it matters
A data model that fits real incident records prevents forced workarounds and inconsistent fields. In police rms software, you’ll feel it when different units document the same event with different levels of detail.
How to check
During the demo, compare two sample records that represent different incident types and ask how the schema handles optional attributes. Request to see how the system stores parties, narrative sections, and related items without breaking templates.
Admin controls for roles and field rules
Why it matters
Admin controls for roles and field rules keeps data quality steady when multiple units use the same workflows. In police rms software, these controls also reduce the need for after-the-fact cleanup.
How to check
Ask to configure a permission set and a field-level rule in the demo, then log in as two roles to confirm what changes. Test whether the system preserves an audit log of who changed key fields and why the change was allowed.
Change history for key record fields
Why it matters
Change history for key record fields is what lets investigators trust older reports while corrections roll in. In police rms software, you need traceability for updates that affect decisions and downstream review.
How to check
Pick a record from the demo and perform a small edit to a key field (status or party detail). Ask the admin to show the full change history view, including timestamp, user, and the prior value.
Red flags
- Updates require users to re-key the same data across screens
- The system can’t show what changed on a record and when
- APIs lack clear examples for core objects and record updates
Fit by situation
- If we need multiple systems to keep case data current with minimal re-entry, prioritize workflow automation across systems.
- If we plan internal tools to push corrections and status updates, prioritize API and webhook availability for updates.
- If our units document incidents differently, prioritize data model fits real incident records.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Security alternatives
See side-by-side comparisons of security tools and pick the right one for your stack.
Compare security tools→