Tightly coupled legacy applications
Years of interdependent code and data made even targeted changes difficult to isolate and test.
ā€” CASE STUDY
Stabilizing critical corrections systems while CDOC modernized its enterprise platform
Supporting CDOC systems while legacy applications move to a modern suite
theta. kept essential corrections workflows moving while CDOC transitioned from aging custom applications to a modern enterprise suite. By resolving data issues, restructuring backend logic, and improving applications that would remain in place, theta. reduced friction in the legacy environment and created a safer path through a complex, multi-system transition.
ā€” CASE STUDY
Stabilizing critical corrections systems while CDOC modernized its enterprise platform
theta. kept essential corrections workflows moving while CDOC transitioned from aging custom applications to a modern enterprise suite. By resolving data issues, restructuring backend logic, and improving applications that would remain in place, theta. reduced friction in the legacy environment and created a safer path through a complex, multi-system transition.
customer
Colorado Department of Corrections (CDOC)
Contract Role
Subcontractor
Mission
Corrections systems modernization
Delivery Focus
Legacy stabilization, backend modernization, and user-centered transition
Capabilities
Discover & Define | Build & Integrate | Enable & Transfer
Mission Context
CDOC was moving from aging, tightly connected custom applications to a modern enterprise information system. The transition affected inmate information, parole-board actions, back-office operations, and legal communications, while several applications still needed to operate outside the new suite. theta. worked across software delivery and user research to stabilize the current environment, understand the work that could not simply migrate, and improve the systems that would bridge CDOC into its next operating model.
Why it mattered
Corrections work cannot pause for a platform migration.
Corrections work cannot pause for a platform migration. Staff needed dependable access to critical information throughout the transition, and legacy defects or inefficient queries could create operational risk at exactly the moment the technology landscape was becoming more complex.
The Challenge
Modernize connected systems without interrupting essential work
Uninterrupted operations
Essential corrections workflows had to remain available while new systems were introduced.
Applications outside the migration
Some tools required a sustainable path forward even though they were not moving into the new suite.
How theta. Delivered
A more stable bridge from the legacy environment to the modern platform
Stabilized legacy code
theta. analyzed the existing codebase and delivered focused fixes that resolved data problems without creating unnecessary disruption.
Restructured backend logic
theta. simplified backend behavior and reduced avoidable database queries, improving maintainability and system responsiveness.
Designed around real workflows
theta. conducted user research to understand how staff relied on non-migrating applications and translated those needs into practical improvements.
Strengthened delivery practices
theta. supported Agile planning, infrastructure as code, source control, and CI/CD practices that made changes easier to manage and repeat.
Outcomes
Critical workflows remained dependable while modernization moved forward
theta. delivered a more stable and manageable bridge between CDOC’s legacy environment and its modern enterprise platform.
Critical data issues resolved
Focused remediation addressed data problems affecting the operating environment and reduced disruption to essential workflows.
A leaner backend
Fewer unnecessary database calls and clearer backend logic made the legacy applications easier to operate and change.
A safer transition path
Repeatable delivery practices and user-informed improvements gave CDOC stronger continuity while modernization moved forward.
Built for What Comes Next
A maintainable transition layer
CDOC gained a more maintainable transition layer: stable enough to support current operations, flexible enough to change, and grounded in how corrections staff actually use the systems.
Technical environment
Technology and delivery practices
PHP, Shell, JavaScript, Drupal, Informix, infrastructure as code, custom CI/CD, Git, and Azure
Have a complex mission to turn into a usable digital product?
Let us start with the policy, people, systems, and operating realities that shape the work.
Related work
Related case studies
VA
theta. expanded VA’s Rapid Ready for Decision approach to PACT Act claims, connecting claims workflows with existing health data so eligible cases could move forward with less manual retrieval and fewer avoidable exams. The work paired product strategy, prototyping, secure integration, and iterative delivery around the needs of Veterans and claims processors.
CMS
theta. advanced product direction and delivered API, authentication, and credentialing capabilities for CMS’s BCDA and DPC products. The work gave authorized organizations a more dependable way to receive Medicare claims data for care coordination, performance analysis, and value-based care.
CDC
theta. delivered FHIR-based services and last-mile integrations that enabled ReportStream to receive, process, and route public health data across organizations with different technical capacities. The work strengthened an adaptable, observable exchange used for COVID-19 reporting and other public health needs.