Capabilities
What the portal supports and what requires court configuration.
The capability matrix shows where the portal fits with existing court systems, payment processors, and filing rules.
| Capability | Status | Operational value | Production dependency | Tyler / eFileTexas-style current state | Portal approach |
|---|---|---|---|---|---|
| Traffic shopping cart | Available | Reduces public friction and support calls. | Citation and court CMS adapters. | Often one citation/payment at a time. | Multi-violation cart with proof and traffic school actions. |
| Transparent fee split | Available | Makes court funds, pass-through, and platform margin explainable. | Payment processor and finance policy. | Fees often appear as one opaque convenience charge. | Separate court, service, pass-through, and markup lines. |
| County value calculator | Available | Turns transaction volume into a planning model. | Actual court volume and fee policy. | Rarely shown as a modernization funding model. | Low/base/high scenarios for program planning. |
| File-and-serve wizard | Available | Shows eFile & Serve parity without overbuilding the CMS. | EFM/EFSP certification and service rules. | Mature but often complex for filers. | Guided subsequent filing, document validation, eService preview. |
| Clerk review workspace | Available | Improves deficiency handling and staff visibility. | Clerk policy and CMS docketing APIs. | Review queues exist but vary by vendor and court. | Validation score, reason taxonomy, and action playbooks. |
| ECF/NIEM integration | Architectural | Builds credibility with court technologists. | Court-specific adapters and certification. | Vendor-specific implementations. | Adapter-first model with ECF-shaped payload preview. |
| Real payments or filings | Requires setup | Requires court authorization before public launch. | Contracts, compliance, processor, court authorization. | Production systems already process real transactions. | Enabled after processor, CMS, filing, and court approval gates. |