Conductor for Regulatory Case Management | Administrative Hearings

Every referral. Every deadline. Every decision on the record.

Case management for hearing offices and adjudicating agencies. Matters arrive from filings or referring agencies, each agency's procedure runs as its own case type, and every order, deadline, and decision lives on one governed record that holds up to appeal and open-records review.

5,000+

Utilities under the commission's oversight

100 days

To baseline delivery, on schedule

5 divisions

On one case record, each with its own walled caseload

The same case engine, in production at a state public utility commission.

See it on a real procedure How a matter moves Back to Regulatory Case Management

The Problem

A hearing office runs many agencies' procedures at once.

Referrals arrive from different agencies in different formats. Each referring agency brings its own rules, timelines, and decision format. The hearing docket lives in one place, the case file in another, and the deadlines in someone's calendar.

Referrals are re-keyed from email, paper, and portal exports before work can start.

Procedural deadlines are counted by hand, and a missed date can void a filing or create an appeal issue.

Assignment to hearing officers depends on who knows which caseload is lightest.

Decisions are drafted in Word and tracked through email until they are issued.

Caseload and timeliness reporting is assembled by hand every time leadership or the legislature asks.

How a Matter Moves

From referral to decision on one record.

Six stages, one matter. Each referring agency's procedure runs as its own case type.

01 · Referral or filing

A matter arrives from a referring agency, an e-filing system, or an intake form, and opens its case automatically.

02 · Case opening

Numbered to your docket convention and given the procedural template for the referring agency and case type.

03 · Assignment

Hearing officer and staff seats filled from a daily queue, with caseload in view and approval where your office requires it.

04 · Prehearing

Procedural deadlines entered from orders and calculated in business or calendar days. Requests for information tracked against the case.

05 · Decision

Proposed and final decisions written from templates, reviewed in the platform, and signed electronically.

06 · After the decision

Post-decision deadlines start automatically. Exceptions, rehearing, and appeals are tracked against the same case.

Underneath every stage: role-based access, walls where impartiality requires them, a before-and-after audit trail, and single sign-on.

Capabilities

Configured for the way hearing offices actually work.

Six capabilities a hearing office gets on day one. Hearing scheduling, party self-service, and exhibit management are configurable on the same platform.

A case type per referring agency

Each agency's procedure, steps, documents, and decision format configured as its own template. Adding an agency is configuration, not a software release.

Deadlines from the record

Procedural deadlines linked to the order that set them, statutory deadlines generated from the decision, and internal deadlines for your own work, on one calendar.

Hearing officer workload

Seats assigned, deferred, or declined from one queue, with current caseload beside every name.

Walls where impartiality requires them

Staff who investigate or advocate can be walled off from those who decide. Access is enforced on every record.

Decisions written in the platform

Templates with comment and suggested edits, legal review steps, e-signature, and a downloadable Word copy when you need one.

Timeliness you can report

Case durations from referral to decision, milestone durations by stage, and workload by officer, with a feed to Power BI or Excel.

Every capability above is configuration on the Conductor platform, delivered and extended in two-week sprints.

Proof

The same engine already runs contested cases in production.

5,000+

Utilities under the commission's oversight

100 days

To baseline delivery, on schedule

5 divisions

On one case record, each with its own walled caseload

21,000+

External stakeholders engaged through the platform

The challenge.

A state utility commission that oversees more than 5,000 utilities needed contested case work to run from the first filing to the final order and beyond, across five divisions, without re-keying and without deadlines living in a calendar that knew nothing about the case.

What changed with Conductor.

Conductor runs contested case work from the first filing to the final order and beyond. Cases open automatically from filings. Deadlines run from orders. Assignments are recommended and approved. Cases referred out to the state's administrative hearings office are flagged and tracked on the same record.

The outcomes.

A hearing office runs the same pattern from the other side of that referral: the matter arrives, opens its case, takes the referring agency's procedure, and carries every deadline and decision on one governed record.

Talk to Our Team About This Deployment

Compliance & Security

Built to the standard your program has to meet.

SOC 2 Type II · ISO 27001, 27017, 27018 · NIST SP 800-53 · HIPAA-ready · WCAG 2.1 AA and Section 508. Built on a FedRAMP Moderate authorized platform. Applications can be deployed into FedRAMP Moderate or High environments where a contract requires it; commercial cloud as standard. Your agency retains exclusive ownership of all data, documents, configuration, and audit logs, with real-time access through an OData connector for Power BI or Tableau, and structured exports plus a Certificate of Data Destruction on exit.

SOC 2 Type II

ISO 27001

ISO 27017 / 27018

NIST SP 800-53

FedRAMP Moderate authorized platform

HIPAA BAA Supported

WCAG 2.1 AA / Section 508

Certifications and attestations

SOC 2 Type II, ISO 27001, ISO 27017, and ISO 27018. Reports are available on request to support agency vendor risk assessments.

FedRAMP where the program requires it

Built on a FedRAMP Moderate authorized platform. Applications can be deployed into FedRAMP Moderate or High environments where a contract requires it; commercial cloud as standard for programs without a federal authorization requirement.

NIST SP 800-53 and StateRAMP

Applications inherit platform-level control implementation and add engagement-specific controls. Delivery aligns with StateRAMP Moderate where required by state contract.

HIPAA

Business Associate Agreements are supported. Encryption, access controls, audit logging, and breach notification align with the HIPAA Security and Privacy Rules where an application processes protected health information.

Accessibility, WCAG 2.1 AA and Section 508

Accessibility is designed in from the first sprint, not audited at the end. Automated scanning runs every sprint, and screen reader testing with NVDA, JAWS, and VoiceOver covers critical workflows before release. An Accessibility Conformance Report in VPAT format is produced as a delivery artifact.

Encryption and access

TLS 1.2 or 1.3 in transit and AES-256 at rest. Every environment uses an isolated database instance. Permissions are enforced at the data model, so a restricted user cannot reach protected data even through an API.

Cloud agnostic. Deploy on the cloud you choose. Azure, Google Cloud, and agency-controlled environments are supported alongside AWS.

See the Kinetech PSN platform

Get Started

Bring one referral type. We'll run it.

Pick a case type your office handles every week. We'll show it in Conductor from referral to decision.

Book a Demo Send Us Your Questions Back to Regulatory Case Management

Already know it fits? Conductor is available through GSA (GS-35F-160CA), Texas DIR (DIR-CPO-5958), TXShare (#2025-018), and TIPS (#220105), so we can start without a full solicitation cycle.

Craig Smith, Partner, Kinetech PSN craig.smith@kinetechcloud.com 773-230-5157