Cloud-Based Case Management Platform
Custom software development and modernization for a government consumer protection department
ABOUT the project
- Client:
- Government consumer protection and rent control department
- Location:
-
Bermuda
- Company Size:
- 20+ Employees
- Industry:
-
Government/Public Sector
- Solution:
- Custom Software Development
Services:
Technologies:
Leobit designed and built a cloud-hosted case management system on a reusable core for a government consumer affairs department in Bermuda. The platform allows the client to replace a legacy CMS and paper records with one system covering complaints, rent control, licensing, appeals, and debt collection.
The team first built a Core CMS covering security, a shared data model, case lifecycle management, documents, audit trails, and communications. The regulatory modules were then developed on top of this foundation and released independently. The first release went live seven months after discovery began, with the remaining modules and digitization work delivered incrementally.
The department wanted to move fast, and the right way to do that was to slow down at the start. We spent six weeks in discovery with a senior BA before writing code, and that is why every module afterward could be built on the same foundation instead of as a separate system.
About Project
Leobit designed and built a cloud-hosted case management system on a reusable core for a government consumer affairs department in Bermuda. The platform allows the client to replace a legacy CMS and paper records with one system covering complaints, rent control, licensing, appeals, and debt collection.
Customer
The client is the consumer protection department of Bermuda’s national government. It oversees five regulatory functions that affect residents and businesses daily: consumer complaint resolution, rent control and landlord-tenant disputes, vacation rental licensing and inspections, appeals against rent increases, and licensing of debt collection agencies.
The platform’s primary users are caseworkers, inspectors, investigators, licensing officers, and department management. External users include members of the public submitting complaints, landlords and tenants, and license holders who need to track their applications. The engagement was contracted through a US technology partner, with an independent consultant advising the department on procurement.
Business Challenge
The department relied on a legacy CMS alongside paper records, with each of its five functions handled separately. The government issued an RFP outlining clear objectives: move to a secure, cloud-hosted system with no on-premises servers; digitize and preserve historical paper records to public-sector standards; bring cases, licenses, inspections, investigations, and documents together on one platform; and improve reporting and management oversight.
Beneath these objectives were several operational gaps. Staff couldn’t quantify office activity because phone calls and emails weren’t logged against cases. Assessment numbers lacked a complete history across modules. Legacy rent control data remained in a separate system. Documents had to be stored and reopened in their original formats. The government also reserved the right to audit digitization processes and outputs at any stage, so record handling had to be defensible, not just convenient.
The department had no in-house engineering team capable of designing, building, and hosting a system of this scope. It began looking for a partner that could take end-to-end ownership of the architecture, delivery, and Azure environment.
Why Leobit
Leobit’s proposal stood out for its approach to project scope, not simply how quickly it could provide a quote. When the technology partner first contacted Leobit, timeline pressure was high. Leobit recommended starting with a structured discovery phase, and the partner agreed. The team scoped discovery at a fixed cost and provided a rough order-of-magnitude estimate for the full project within a short timeframe.
The partner specifically requested a senior business analyst to lead discovery, helping the team move quickly and efficiently once the requirements were clear. Leobit’s track record with .NET and Azure, along with its experience building role-based case management and licensing workflows, further strengthened the proposal.
Project
in detail
The engagement followed the plan outlined in the proposal, beginning with discovery and moving into active development.
The discovery phase involved a full-time senior business analyst, a development lead/application architect allocated half-time, and a senior UI/UX designer allocated half-time. The BA mapped existing workflows across all five functions and turned the RFP requirements into a prioritized list of capabilities. The designer created wireframes for the priority modules and established a visual direction aligned with accessibility standards. The architect assessed the legacy environment and defined the target cloud architecture, environment strategy, security model, and Azure deployment approach under the partner’s cloud solution provider (CSP) arrangement.
This phase ran for several months. The active development team consisted of four full-stack developers (lead, senior, intermediate, and junior), a manual QA engineer, the senior BA working full-time, and a project manager allocated 25% of their time. The development lead owned the architecture and code reviews. The senior developer led the Core CMS implementation, while the intermediate and junior developers built the portal, reporting features, and complaints module using established patterns.
The team first implemented Core CMS functionality, including authentication and authorization, role-based access control with segregation of duties and rules for internal and external users, and a shared data model for cases, licenses, and inspections. The team then added module-level operational reporting, an external portal with a reusable public intake framework, and the Consumer Complaints module, including a scoped migration of historical complaint data.
Phase 2 is ongoing and covers the delivery of Rent Control, Licensing (multiple license types with inspections and supporting evidence), Appeals linked to rent increases, and Debt Collection as separate production releases. The phase also includes electronic imports of legacy rent control data, an optional integration with land valuation data, cross-module dashboards and KPIs, the digitization program, role-based training and documentation, and the transition to ongoing support.
A Reusable Core Before Any Module
The key architectural decision was to build the Core CMS as a product in its own right before developing any regulatory modules. The five functions differ in law and procedure but share the same basic workflow: a matter is opened, assigned, tracked against deadlines, accumulates documents and communications, and closes with a recorded outcome.
The team applied the same principle to the external portal. It built the first complex public intake form as a reusable framework. Additional forms for rent control disputes, license applications, and appeals reuse that pattern.
The back end started as a single ASP.NET Core monolith exposing an HTTP API to a separate Angular application, with command-query separation inside the monolith. The plan is to move toward a modular monolith as the module boundaries become clearer, rather than split the system into separate services before the domain is fully understood.
Assessment Numbers as the Audit Backbone
Assessment numbers are the identifiers the department uses to reference matters in correspondence, decisions, and records. In the legacy system, each function issued its own numbers, with no shared history across modules. This made it difficult to trace a landlord’s case from a rent control dispute to an appeal or licensing inspection.
Leobit made assessment number generation and history a Core CMS capability. Numbers are generated automatically when a case is created and remain unique across all modules. Every change in status, ownership, or linkage is recorded against the relevant number. The case lifecycle engine, audit trail, and search functionality all use this identifier. As a result, records retrieved from any module show their complete history.
Bridging the Legacy System Without a Big-Bang Cutover
Because the modules are going live one at a time, the legacy CMS and the new platform must coexist throughout much of Phase 2. Instead of relying on manual exports, Leobit set up change data capture on the legacy SQL Server database using Debezium. Changes are published to Azure Event Hub and replicated into the new platform’s data store.
Records created in the legacy system for functions that haven’t yet migrated remain visible in the new platform. This means each module can be cut over by switching its write path rather than treating the transition as a separate data migration event.
The Journey
Behind Our Success
Technology Solutions
- Core CMS built as a shared foundation, with security, RBAC, data modeling, case lifecycle management, auditing, and communications implemented from day one
- Assessment number generation and cross-module history implemented as platform-level capabilities integrated with the audit trail and search
- Monolith-first ASP.NET Core back end with command-query separation and a planned transition to a modular monolith as module boundaries mature
- Legacy system coexistence managed through change data capture with Debezium and Azure Event Hub, replicating SQL Server changes into the new platform to support module-by-module cutover
- Reusable public intake framework in the external portal, with record-level authorization restricting external users to their own cases
- Documents retained in their original file formats in Azure Blob Storage, with OCR text indexed for full-text search and every record linked to a case, license, or assessment
- GitHub Actions pipelines used to promote builds across environments, with Azure Application Insights supporting monitoring
- Digitization managed as a separately budgeted, phased workstream with QA, validation, and controlled return of physical records
Value Delivered
- Five previously separate regulatory functions consolidated on one platform with role-based access and configurable workflows
- Legacy CMS and on-premises dependencies retired
- Workload metrics, including call and email activity counts, SLA tracking, and module-level reporting, made available to management
- Complete audit trails and cross-module assessment histories designed to support government audit requirements and accommodate future legislative changes
- Historical paper and electronic records preserved, searchable, and linked to active cases