Skip to content
Cyntrix ICM

Investigative Case Management

Know where every case stands, and where every hour went.

Cyntrix ICM is case and time management for investigative units, built by a working detective. Detectives log time as they work. Supervisors see the whole caseload and every filing deadline. Command staff get the numbers behind staffing, grant, and budget decisions.

Private betaPilot agencies get the first year free
  • Two-factor on every account
  • Tamper-evident audit log
  • Per-charge limitation deadlines
  • Your data leaves with you
ICM's case list: each case with its offense, statute of limitations date, complainant, hours logged, status, flag, and latest note. Screenshot from a demo agency with fictional data.

Screens and examples are from a demo agency. Every case, person, and vehicle in them is invented.

  • Working toward full CJIS compliance
  • Moving to AWS in the United States
  • Per-charge limitation deadlines
  • Team notes and a private case log
  • Tow yard holds matched to cases
  • Reminders with snooze
  • Agency-wide At Large board
  • Timers that follow you across the app
  • Two-factor on every account
  • Hash-chained, daily-sealed audit log
  • Command analytics with drill-through
  • CSV import and full agency export
  • Quiet hours for notifications
  • Multi-unit supervisors

Why it exists

Most investigative units run on a spreadsheet, a whiteboard, and memory.

That works until someone asks a question it cannot answer: which cases are closest to their limitation date, why a case sat for a month, or how many hours the unit spent on burglaries last year. ICM answers those from the record instead of from recall.

Deadlines kept by hand

Limitation dates live in a spreadsheet column or in someone's head, and a missed one cannot be undone.

Hours nobody can show

The workload is real but undocumented, so a request for another investigator rests on anecdote.

Status that goes stale

A shared spreadsheet is only as current as the last person who remembered to update it.

How a unit actually works

Built around the people on the case, not just the case.

What it looks like when ICM is running. Every example here is invented.

Team and agency

The unit works the case together, and the private parts stay private.

Team notes are for everyone on the unit. The case log is between the investigator and their supervisors. Supervisors can oversee more than one unit, and a supervisor can hand a caseload to someone else with its history intact.

Notifications

The things that need you, when they need you.

A team note on your case, your reminder coming due, a limitation deadline getting close, a tow yard match. Mute any kind, set quiet hours, and turn on desktop notices while ICM is open.

Tow yard holds

Every held vehicle, matched to its case.

Load the tow yard's daily holds report and ICM reads every row, matches each vehicle to its case by service number, and offers the match to the case's investigator. Nothing is added until they say so. Automatic pickup from the tow yard's email each morning is built, ready for agencies whose mail setup allows it.

The case

Each charge carries its own clock.

Deadlines are computed per charge from the offense date, with the warrant number on the charge it belongs to. The nearest one rides on the case, the case list, and the At Large board.

Reminders

Set it on the case, and it finds you.

Pick a time in one tap, see a clock on the case row, then snooze or finish it when it comes up. Reminders are yours alone.

Agency-wide

Everyone wanted, across every unit, on one board.

The Active at Large board lists every open warrant in the agency with its days remaining. Another unit's row names the unit and the investigator without opening their file, and the list can be shared by print, email, or CSV.

Analytics

Numbers that run the unit, not just the clock.

Time is one measure. The analytics answer what supervisors and command staff actually get asked: is the backlog growing, what is clearing and how it cleared, what is about to expire, and whether the unit has the people for its caseload. Every figure comes from the same records and is compared with the period before.

Invented numbers, laid out as the app shows them.

For supervisors

The unit view

  • A needs-attention row: deadlines closing in, cases idle 30 days, waiting to file, open past 180 days
  • Intake, dispositions, and the backlog, against the prior period
  • Clearance, median days to file and to close, and days from offense to case
  • How cases ended, and whether charges were filed as charged or amended
  • Every chart opens the list of cases it counted
  • A data-quality check that flags the records the numbers cannot trust

For command staff and administrators

The department view

  • Every unit rolled up, intake against disposal, and which way the pile moved
  • Each unit's load: open cases per investigator, idle cases, deadlines at risk, capacity used
  • The backlog by status and age, split by unit
  • Trends against the same months last year
  • Counts only: administrators see the numbers, never the case files
  • Printable, and exportable as CSV for a budget or grant packet

The product

The caseload, the clock, and the calendar, in one place.

The real screens, from the demo agency.

Time tracking that answers to command staff, not to the detective.

The point is not to watch anybody work. It is to answer the questions a unit usually cannot answer with evidence: where the hours actually go, what a caseload costs to carry, and what the unit could take on with another investigator.

  • Start, stop, or switch a timer from any screen
  • Every entry tied to a case or another duty, with a category
  • Case work and everything else counted separately
  • Missed a timer? Add or correct the entry afterward
ICM's History screen: a week's totals for all logged time and case time, then each day's entries with their case or duty, category tag, description, and times. Screenshot from a demo agency with fictional data.

Also in it

  • Search by service number, name, offense, or warrant number
  • Seven case statuses, and a required disposition to close
  • Import an existing caseload from a CSV template
  • Flags with reasons, and your unit's own case tags
  • In-app notifications with quiet hours
  • A command palette to jump to any case from the keyboard
  • Guided setup and a short orientation tour for each role

For the whole unit

One system, from the desk to the command staff.

Detectives

Your cases, their deadlines, and your time, in one place instead of three.

  • A running timer that follows you across the app
  • The nearest deadline on every case in your list
  • Personal reminders on each case

Supervisors

The whole unit's caseload, who carries what, and what has gone quiet.

  • Cases idle 30 days, waiting to file, or near a deadline
  • Every chart opens the cases behind it
  • Reassignment and archive, with full history kept

Command staff

Department-wide numbers that hold up in front of a budget committee.

  • Intake, dispositions, and backlog by unit
  • Clearance, days to file, and days to close
  • Hours by category, against unit capacity

Agency administrators

The roster, units, records rules, and audit review in one console.

  • Accounts set up by emailed link
  • Units, roles, and department-wide analytics
  • Retention periods, legal holds, and a full export

Security and accountability

Built for material that has to be handled properly.

ICM holds investigative working material, so security was designed in from the start rather than added on later.

Working toward full CJIS compliance

Full compliance with the FBI CJIS Security Policy is the goal we are working toward now. ICM is moving to AWS in the United States, into a production account built around the policy's technical requirements, and pilot agencies' cases go there. It is not CJIS authorized yet: the CJIS Security Addendum, background checks, and your state CSA's review come next, and a move to AWS GovCloud (US) follows when an agency needs it.

Two-factor on every account
Required, not a setting. Authenticator apps, up to five per account, and ten self-service recovery codes that reset sign-in rather than bypass it.
Tamper-evident audit log
Every change is recorded with the value it replaced, along with case views, searches, exports, and prints. Entries are hash-chained and sealed daily, and readable by your supervisors and administrators, not by us.
Enforced password rules
At least 12 characters, checked against a blocklist, changed every 90 days, and never one of the last 10. Users are emailed whenever a password or sign-in method changes.
Sessions that lock
The screen locks after 30 minutes idle and every session ends after 12 hours. Exports ask for identity again, and anyone can sign out their other devices.
Accounts that open and close cleanly
Set up by emailed link, never a temporary password. Deactivating one removes its password and second factors at once, and its cases stay put for reassignment.
Access scoped to the unit
Case files open only inside the unit that owns them. The agency-wide At Large board names other units' defendants without opening their files.
Records rules set by the agency
Your agency sets its own retention periods and legal holds. Nothing is destroyed automatically, and disposal is a deliberate, confirmed step.
Your data leaves with you
A full agency archive of every case, person, note, and hour, plus CSV exports and PDF case packets. Leaving is a supported operation.

Where it is going

AWS, in the United States.

What production is being built to. Pilot agencies' cases go here.

US East (Ohio) ยท moving now

An account of its own
A production AWS account that holds nothing but ICM, under organization-level rules that stop it turning off audit logging or threat detection, lock out the root user, and allow only two US regions.
Encrypted at rest and in transit
The database, files, backups, and logs encrypted with keys held for ICM alone. TLS 1.2 or higher on every connection, including the app's own connection to its database, and AWS services reached through their FIPS endpoints.
A database with no way in from the internet
Isolated subnets that only the application can reach, two data centers at once, 35 days of point-in-time recovery, a separate backup copy, and protection against being deleted by accident.
A firewall in front
AWS WAF screening every request: known bad addresses, SQL injection, and common exploits blocked, and anything that floods the site slowed down.
Watched around the clock
GuardDuty threat detection across the account with alerts on anything serious, Security Hub checks against NIST SP 800-53, and network, DNS, and application logs kept for at least a year.
A domain that is hard to fake
cyntrixicm.com is signed with DNSSEC, only Amazon may issue its certificates, and its mail is signed so that forged messages are rejected.

Where it is headed

Today, next, and after that.

Built with the units that use it. What is live is live; what is planned is labelled that way, with no dates promised.

  1. In ICM today

    • Texas

      Offense catalog and statute of limitations rules, live.

    • Everything on this page

      Cases, time, deadlines, notes, reminders, tow holds, analytics, and the audit log.

  2. Underway

    • The move to AWS

      The production account, its guardrails, threat detection, and the domain are in place; the app moves before the first pilot case.

    • 15 more states

      Catalogs and limitation rules built, each released once it passes legal review.

    • Passkey sign-in

      Built and switched off until it is ready to turn on.

  3. Planned

    • Full CJIS compliance

      The CJIS Security Addendum, background checks and training, a System Security Plan, and your state CSA's review. Our current focus.

    • AWS GovCloud (US)

      The same system, moved to AWS's US-persons-only region when an agency needs it.

    • RMS integration

      Bring a case's basics across from your records system instead of typing them twice.

    • Other agency systems

      Connections to the other systems a unit works in, such as CAD, chosen with pilot agencies.

    • More tow yard formats

      Holds reports from more impound systems, as agencies bring them.

    • All 50 states

      The rest of the country, state by state, each through the same legal review.

Planned items are not in ICM today. Pilot agencies have a real say in what gets built, and in what order.

Straight answers

What ICM is, and what it is not.

The questions an agency asks before it puts a caseload anywhere.

Does ICM replace our records management system?

No. The official record stays in your RMS. ICM is where an investigative unit manages its caseload, its time, and its filing deadlines. It does not connect to RMS, CAD, or NCIC today, and it does not store evidence, attachments, or photos. RMS integration is on the roadmap, so a case's basics can come across instead of being typed twice.

Is ICM CJIS authorized?

Not yet, and we do not claim it is. Full CJIS compliance is what we are working toward now. ICM is moving to AWS in the United States, into a production account built around the CJIS Security Policy's technical requirements, and pilot agencies' cases go there. What remains is the paperwork and review that make it official: a CJIS Security Addendum with your agency, fingerprint-based background checks and security awareness training for everyone with access, a written System Security Plan, and your state CSA's review. A move to AWS GovCloud (US) follows when an agency needs it. We will walk your IT and security staff through exactly where it stands.

Where is our data kept?

Pilot agencies' cases are kept on AWS, in data centers in the United States (US East, Ohio), in a production account that holds nothing but ICM. ICM is moving there now, ahead of the first pilot. The database has no route to the internet, and everything is encrypted at rest with ICM's own keys and in transit with TLS 1.2 or higher. One thing does go out: a vehicle's VIN is decoded by NHTSA's public vPIC service, and nothing else about the case goes with it.

Which states does it support?

Texas is live today. Offense catalogs and statute of limitations rules are also built for 15 more states: Alaska, Arkansas, California, Florida, Illinois, Iowa, Kansas, Kentucky, Missouri, Montana, Nebraska, Nevada, New York, North Dakota, and Utah. Each goes live once its limitation rules pass legal review, and more states are on the way.

Can we bring our existing cases in?

Yes. ICM imports cases from a CSV in its own template, so an existing spreadsheet usually needs its columns mapped to that template first. Charges import by offense code.

Does it work on a phone?

ICM is a web app that runs in any current browser, including on phones and tablets. There is no native app and no offline mode, and notifications and reminders appear while ICM is open.

What does a pilot cost?

Nothing for the first year. Pilot agencies also have a direct line to the person who builds ICM, and a real say in what gets built next.

Pilot program

Join the pilot waiting list.

Cyntrix ICM is in private beta and is not taking on new agencies right now. When the next pilot group opens, the agencies on this list are the first we contact.

  1. 1

    Tell us about your unit

    Agency, unit size, and what you use today. Nothing about any case.

  2. 2

    Hear first when a group opens

    Agencies on the list are the first we contact for the next pilot group.

  3. 3

    First year free

    Pilot agencies pay nothing for the first year and help shape what comes next.

Tell us about your unit

Enough to size a pilot and to know it is a real agency asking. Nothing here is a commitment on either side.

Optional. It tells us which RMS integration to build first.

No obligation. We reply from a real address, not a sales sequence.