Courthouse exterior

YOUR COURT. YOUR PEOPLE. ONE CONNECTED WORKSPACE.

CJMS.
A home for the
work of justice.

Bring the clerk's office, the bench and your justice partners together—with a clear next step for every case.

Meet your court workspace
Independent court software by RB Technologies · Demonstration records shown
One permission-aware searchHearing readiness before decisionsSourced CJMS-native recordsYour court's identity first

LESS FRAGMENTATION. MORE CONTINUITY.

A court workspace that
feels like it belongs to you.

The whole court. Your work.

Court-wide activity and personal assignments in one place, with your institution's name and identity at the centre.

  • One primary, permission-aware record search
  • Hearings, recent cases and department queues
  • Persistent case context across workspaces
CJMS Court Home showing court calendar, personal work and department queues
Actual CJMS workspace · fictional demonstration records

CJMS-NATIVE RECORDS

Connected records.
Clear provenance.

Build your agency's own record feeds inside CJMS. Every record carries a source reference, review state and revision history, and can be returned to a court through the internal review exchange.

01

Person & driver records

Local identifiers, person alerts and driver records with defined source references.

02

Vehicle & firearm records

Exact identifiers connect a request to reviewed internal records—not an assumed identity match.

03

Orders, registries & reviews

Protection-order records, local registry entries and eligibility-review notes stay attributable to their sources.

Create a sourced draftReview & activateMatch a court requestReturn analyst findings

CJMS-native feeds are internal product services, not government LEADS, NCIC, NICS, SOS or statewide registries. No government connection or endorsement is claimed. A local match—or no match—is not an enforcement authorization or firearm clearance.

GOVERNANCE, NOT GUESSWORK

Preserve the record.
Keep people accountable.

Role-aware access

Server-side permissions and confidentiality controls govern court records and partner workspaces.

Court-scoped data

Tenant-prefixed collections separate each court's records. Approved internal exchanges are tracked rather than silently shared.

Reviewed changes

Hearing decisions, preparation changes and native-record reviews carry actor, time and source history.

Explicit boundaries

Government feeds and Microsoft/Adobe connections are not live. Zoom, email and payment integrations retain their existing demonstration or configured status.

PLAN FOR YOUR COURT

A clear starting point.

Annual subscription per named user. Implementation and support are quoted separately; confirm scope and terms in your formal proposal.

Small court

Up to 50 named users

$1,140per named user / year

Mid-sized court

51–200 named users

$960per named user / year

Large court

201–500 named users

$780per named user / year

FROM FIRST LOOK TO COURT FIT

Start with your workflow.

01

Tell us about your court

Share your departments, current process and priorities.

02

Review the fit together

Confirm case flow, policy requirements and the scope of a court-specific trial.

03

Evaluate in your workspace

Use a 30-day isolated trial to assess your day-to-day work, with demonstration data—not a substitute for production acceptance.

BEFORE WE BEGIN

Your questions, answered.

How does the 30-day court trial work?

Submit the request form. RB Technologies reviews your court or agency request and arranges an isolated trial workspace after approval. Evaluate court configuration and case workflows with demonstration data for 30 days. Submitting the form does not automatically activate a trial or send working credentials.

What happens on day 30?

Unless the workspace has been purchased, or a contract is pending or approved with RB Technologies, the trial workspace is terminated on the 30th day. Data is retained so a purchase or contract can reactivate it without re-entry.

Is our data separated from other courts?

Court records are separated through tenant-scoped collection prefixes and permission checks in the shared database architecture. Explicitly authorized partner exchanges are tracked. This is not a claim that every court has a separate physical database.

Are CJMS-native feeds government databases?

No. Native feeds are CJMS-owned, source-referenced records managed by authorized staff. They support internal matching and court-to-agency review; they do not connect to or replace government LEADS, NCIC, NICS, SOS or statewide registries. A local search is not a government clearance.

What does hearing readiness verify?

The checklist shows configured participant appearances, linked case-document requirements and action-specific findings before recording a decision. Missing mandatory items are validated on the server. It assists court staff; it is not legal advice or certification that all statutory requirements have been met.

Who can see sealed or confidential records?

Confidentiality is enforced on the server. Sealed and confidential matters are filtered at the query layer for every list, search and report, so a role without the right permission never receives them.

Can we bring our existing case data?

Yes. RB Technologies works with your team on structured import of case histories, parties, dockets and warrants during implementation planning. Ask about it in your trial request or a sales conversation.

How is the system priced?

Annual subscription per named user in three court-size tiers, with implementation and support tiers quoted separately. Cooperative purchasing, multi-year and consortium discounts are available — request a formal quote.

LET'S TALK ABOUT YOUR COURT

Your next chapter
starts here.

Walk through a case with us—from intake and hearing readiness to a recorded decision and partner review.

Existing customer support

Government pricing, RFP responses, pilots and implementation planning.