CT Agency Suite for case work

Case management for human services agencies.

Modern case management built around the consumer receiving services — the MT/MH/SCS rhythm, the plan lifecycle, and the SC's day. HIPAA-aligned, shaped around how human services agencies actually run cases — not how generic software thinks they should.

Apply for early access What's included

HIPAA-aligned: Encryption, access controls
Consumer-centric: Built around the people receiving services
Modular: Adopt the modules you need

Case management essentials

Built around the case work, not the buzzwords

Human services case management has its own rhythm. The suite reflects it — consumer records, monitoring tools, checklists, and plans in one place.

Consumer-centric record across every module
MT visits monthly (by SC); MH and SCS checklists annually
ISP and service plan lifecycle
Documents organized by category
Permissions tuned to human services roles

HIPAA-aligned

Built into the platform

Consumer-centric

About the people you serve

Multi-state

KY, IN, GA, FL, NM, and expanding!

Built for the work

Not generic case management

Why this matters

Generic case management was built for hospitals and insurance. Human services case work is different.

When a disability services agency or a Medicaid waiver provider tries to use generic case management, the gaps show up immediately. Plan structures don't match. The MT/MH/SCS rhythm doesn't fit. The fields that matter to support coordination aren't represented at all. Teams end up keeping a parallel spreadsheet to track what the system can't.

CT Agency Suite is shaped around human services case management specifically. The consumer record is the center of gravity. MT visits happen monthly at every check-in (some by phone, some in person). The MH Checklist is an annual document the SC completes. The SCS Checklist is an annual document the supervisor completes. Plans have lifecycle states that the SC can act on, with expirations surfacing in time to renew.

Permissions are tuned to roles that exist in human services agencies: support coordinator, supervisor, QA, billing, clinical lead, administrator. Each role sees what they need without seeing what they shouldn't. The suite ships with sensible defaults for NJ DDD agencies and adapts to other states' terminology.

What human services case management requires

Consumer-centric records — group home, plan dates, MT history, MH/SCS Checklist completion in one view
Monthly MT visits — by the SC, in person or by phone, with upload-vs-visit color coding
Annual checklists — MH (by SC), SCS (by Supervisor)
Plan lifecycle — expiring plans surfaced 60 days out, not 30 days late
Documents organized by category — where the SC needs them, scoped to the right roles

Case management capabilities

What the suite actually does for human services case work.

Consumer record as the center of gravity

DDD ID, programs, ISP, group home, plan dates, Medicaid end date, MT history, MH Checklist completion (annual, by SC), SCS Checklist completion (annual, by Supervisor), documents, contacts — one searchable view, no swivel-chair between screens.

MT visit tracking (monthly, by SC)

MT visits are conducted monthly at every check-in — some by phone, some in person. The platform tracks each MT visit with upload-vs-visit-date color coding so it's obvious when a visit happened but the documentation hasn't been uploaded yet. Late visits show up where supervisors will see them.

MH Checklist (annual, by SC) and SCS Checklist (annual, by Supervisor)

MH and SCS checklists are first-class records. The MH Checklist is the SC's annual document; the SCS Checklist is the Supervisor's. The suite tracks completion per consumer per year, surfacing what's outstanding without a parallel spreadsheet.

ISP and service plan lifecycle

Plans have lifecycle states — draft, current, expiring, expired. Renewal workflows surface plans 60 days before expiration so renewals don't lapse. (We don't track per-edit revision history; the current plan is the source of truth.)

SCPA — biller-only, kept simple

Support Coordination Prior Authorization is scoped to the billing team. SCs don't see SCPA, QA doesn't see SCPA, supervisors don't see SCPA — it stays where it belongs, with the biller. There is no reviewer-assignment workflow because SCPA in NJ DDD doesn't actually need one. The DDD Participant Search import flags SCPAs as billable based on monthly MT upload status.

Documents organized by category

Documents are categorized at upload and retained per category rules, attached to the right consumer record. The SC and supervisor see what they need to do their work; the biller sees what they need to bill. Where audit evidence is needed downstream, the data is there — but the page-one job is supporting the consumer.

Role-based permissions tuned to human services

SC, Supervisor, QA, Billing, Clinical Lead, Administrator — each role's view of records, ability to edit, and access to reports is configured specifically. Junior staff see what they need; sensitive records stay scoped.

What it looks like in practice

A few ways teams use this.

Support Coordinator opening a case

You're assigned a new consumer. You open the record and see the full picture — DDD ID, group home, plan dates, MT history, MH and SCS Checklist completion, documents, contacts. You schedule the next MT visit and capture a personal follow-up reminder. What used to be a day of orientation is twenty minutes of context.

QA doing an internal record review

QA pulls a sample of consumers and drills into each one — MT history (with upload-vs-visit color coding), MH and SCS Checklist completion, ISP currency, document categorization. Anything missing is obvious. They follow up with the SC. This is internal QA work, not external-audit prep.

Clinical lead investigating an incident

An incident report comes in. You open the consumer's record, scroll through MT history, see who visited recently and when, review the latest plan, and look at staff assignments. Your investigation has its facts in five minutes, not five days.

Frequently asked

Common questions from human services agencies.

Is CT Agency Suite suitable for our specific Medicaid waiver program?

The suite is built around the general structure of disability services and Medicaid waiver case work, with NJ DDD as the most deeply-modeled program. Other state programs are supported with configuration of program tags, document categories, plan types, and visit cadences. We'll walk you through what's available for your specific waiver during a demo — if there are gaps, we close them as part of onboarding.

How does the suite handle HIPAA compliance?

HIPAA-aligned controls are built into the platform: encryption in transit and at rest, role-based access control with multi-factor authentication, audit trail on every sensitive action, multi-tenant data isolation, and document retention rules. The platform is the HIPAA-aligned layer; agencies are responsible for their own administrative and physical safeguards on top of that.

Can we configure the suite for our agency's specific document categories and program tags?

Yes. Document categories, program tags, plan types, visit types, and most other taxonomic data are configurable per agency. Sensible defaults ship with the platform; configuration adapts to your state's terminology and your agency's internal conventions during onboarding.

How do plan lifecycle states work?

ISPs and service plans have lifecycle states — draft, current, expiring (within 60 days), expired — with workflows that surface expiring plans 60 days out so renewals don't lapse. The current plan is the source of truth; we don't track per-edit revision history. Renewing a plan creates the new version of the plan; the prior plan moves to archived state.

What's the timeline for general availability?

CT Agency Suite is targeting general availability in 2026, with an active early-access program now. Early-access partners get direct input into priorities, dedicated migration support, and founding-customer pricing. When the suite is ready, existing PNB customers will be migrated to it — this is a forced cutover, fully supported (same data, same team, hands-on training), but the move itself is happening.

How does the suite differ from broader healthcare or hospital case management tools?

Hospital and broader healthcare case management tools are built for episodic, encounter-driven care — admit, treat, discharge, bill. Human services case work is longitudinal: same consumer, same coordinator, same plan structure across years, with monthly MT visits, annual MH and SCS checklists, and plan renewals as the spine. The suite is built for that longitudinal, consumer-centered shape — with the data also there if and when an audit needs it.

Case management built for human services.

Apply for the CT Agency Suite early-access program. Walkthrough tailored to your specific waiver program and caseload size.

Apply for early access Back to CT Agency Suite