- Problem
- The institution managed a national network of partner organisations, their sites, group memberships and billing arrangements, along with incoming enquiries, across spreadsheets and email. Staff needed one system they could trust, designed so it could connect to other systems later without a redesign.
- Approach
- We wrote the high-level solution design and environment strategy, then designed and built the data model. It covers partner organisations, sites with unique identifiers, group memberships with start and end dates, and billing relationships, all protected by validation rules so duplicates cannot creep in. Each staff role got least-privilege permission set groups, and enquiries are routed through queues. Every change moved through source control and pull requests across development, QA and training environments, and user acceptance testing defects were fixed and retested before promotion.
- Outcome
- The first release was deployed to production with all 164 components passing, backed by a release runsheet, a training environment for staff and documentation the institution owns. Later releases, such as web enquiries and integrations, can build on the same design.