The sixth system

October 2026 · By Zach Brown, Chief Revenue Officer, eHawk, Inc.

Walk into any probation office and count the systems an officer touches in a day. The case management system. The drug testing vendor’s portal. The electronic monitoring vendor’s portal. The court or jail system. Email and the desk phone. Five, give or take, and none of them talk to each other.

So when a director asks me “does it integrate,” I know what they’re really asking. They’re asking whether RePath is going to be the sixth system their officers have to type into. That’s a fair question and it deserves a straight answer instead of a checkbox.

Five systems already, none of them talking. The question is whether we are a sixth.

The real question is double entry

Nobody cares about integration for its own sake. They care about an officer finishing a visit and then entering the same thing twice. That’s the problem. Every hour we give back to an officer gets eaten if the note they got from RePath has to be retyped somewhere else.

So let me answer that question in three parts: the floor, the ceiling, and what agencies did in between.

The floor: copy and paste, and it takes seconds

Your case management system stays the system of record. On day one, at most agencies, the Visit Assist summary gets copied from RePath and pasted into the case note. That’s it. No project, no IT ticket, no procurement step.

“We don’t write chronos anymore, which was a duplication of tasks. I generate the transcript and copy and paste it to Athena and the chrono is done.”

I lead with this because it’s the version most agencies will actually run, and it already removes the thing people are worried about. The note that took 30 to 45 minutes to write takes about five to review and a few seconds to move. That’s not a workaround. For a lot of agencies it’s the answer.

The ceiling: case data flowing both ways

Where an agency wants more, there’s more. RePath has an API that can create cases from your system, push visit summaries back into it, hand over chat history and appointments, and fire a webhook when something happens that your system should know about.

Two honest answers to “does it integrate,” and both are true

The floor: day one

• Your case management system stays the system of record
• The Visit Assist summary is copied into the case note
• A few seconds per visit, no project, no IT ticket
• Running today at most agencies on RePath

The ceiling: a built connection

• Cases created in RePath from your system
• Visit summaries pushed back automatically
• Chat history and appointments handed over
• A webhook when something your system should know about happens

One state corrections department built that connection. Case data from the state’s own system lands in RePath within five minutes, so an officer is never working from a stale record and never creating a person twice. That department had already decided the integration was the one requirement it wouldn’t move on, and it was right to.

What I won’t tell you is that we import from every case management system out of the box. Nobody does, and the vendors who say so are describing a sales call, not a deployment. Every state’s system is different. Some have an API. Some have a nightly export and a prayer. We’ll tell you which one you have before you sign anything, because finding out after is how six-system offices get built.

What agencies did in between

Here’s the part that usually settles it. That state department didn’t wait for the deep integration to start. It ran the pilot on the floor, copy and paste, while the connection was being built, and expanded the integration mid-pilot once officers were already seeing the time come back. By the time the state went statewide, the five-minute sync was running and nobody had waited a quarter for it.

That’s the sequence I’d recommend to anyone. Start on the floor the week your officers are trained. Decide on the ceiling once you know what your own system can do. Don’t let the integration conversation delay the part that returns the hours, because the hours are the reason you’re having the conversation.

What to ask any vendor, including us

Three questions, and you’ll know in ten minutes whether you’re buying a sixth system.

1. On day one, what does my officer do with the note? If the answer is longer than “copy it over,” keep asking.
2. What has to be true about my case management system for the deeper connection to work? If the answer is “nothing, it just works,” be suspicious.
3. Show me an agency where the connection runs today, and tell me how long it took.

We’ll answer all three before a contract, in writing. The short version is on our FAQ. The long version is a conversation, and I’d rather have it early.