By General on Thursday, 09 April 2026
Category: MHCLG

From emergency to sustainability: creating Share Homes for Ukraine data

In response to Russia’s full scale illegal invasion of Ukraine in 2022, the government launched the Homes for Ukraine Sponsorship Scheme to enable Ukrainians fleeing the conflict to find safe accommodation with UK hosts.

Delivering this scheme at national scale required a digital service to be designed, built and operated at extreme pace, while handling highly sensitive personal and safeguarding data. You can read more about how our team applied digital principles and innovation to effectively respond to this crisis in this case study.

The initial emergency response relied on an existing supplier-owned platform. However, longer term, we wanted to replace the platform with a more flexible technology solution, enabling the Ministry of Housing, Communities and Local Government (MHCLG) to save significant support costs, control the system data and code, and ensure the service met high standards of security, resilience and usability.

In the summer of 2024, we started building our own system for managing Homes for Ukraine data. We needed a system that would provide service continuity and secure data sharing between central government, local authorities and devolved administrations, with more sustainable running costs.

We chose to build ‘Share Homes for Ukraine data’ (or ‘Share’ for short) in-house, giving MHCLG full ownership to adapt the system based on user needs and expand to further use cases.

Challenges

Time constraint and scope

We had less than a year to build the system and migrate 3 years of operational data, which was a very ambitious timeline. We worked with our operational teams and a test group of local authority users to define our minimum viable product, continually tweaking our scope as we progressed and refined our delivery estimates, to ensure we could deliver Share on time with only the essential features needed for day 1.

Security

Given the sensitivity of the data, safeguarding and data security were paramount in our architectural and design choices. We used a phased approach to data migration to allow for multiple rounds of quality assurance.

User-centred design at pace

We wanted to make a system that met users’ needs first time, was intuitive and easy to use, but we had limited time and access to our primary users. We weren’t starting from scratch, as we had a bank of 3 years of research from running Homes for Ukraine. We also leant on the GOV.UK Design system as a template, knowing that this is extensively researched and accessible by default, and focussed our limited user research time on our most complex journeys.

Change management and training

We knew this would be a big change for our local authority users, and we did not want to lose the trust and good relationships we’d built over the previous 3 years working together. We held drop-in sessions over the summer to share progress, demonstrate features and answer any questions. We also created written and video guidance, and both phone and online support mechanisms to ensure our users felt supported through the transition.

Successes

We delivered Share on time in September 2025 and exited our contract with our supplier. Moving to this in-house model is already saving MHCLG millions of pounds a year in running costs. We are also preparing to onboard local authorities in Scotland and Wales, who used their own systems rather than our previous system, making further savings and reducing duplication across the public sector.

Our users report that Share is simpler to use and more accessible than its predecessor. They say:

“It’s easier to navigate than the previous system, safeguarding checks are easier to complete and visualise where cases have outstanding issues.”

“it’s a very user-friendly system, much easier to navigate.”

Launch was only the start of our journey, and we have been making continual releases since September. We have improved stability and performance, made adjustments to make the system more accessible, iterated existing features based on feedback, and built some new features.

Our team (myself included) have learnt a great deal about building, migrating and supporting a system of this scale and complexity. It is a rare and privileged opportunity to work on a project that has such significance: generating real-world impact by continuing to support Ukrainians fleeing war; creating an asset that has potential for further reuse across government; and setting a precedent that it is possible to move a complex live system into a sustainable in-house set up and reduce our reliance on external suppliers.

A screenshot of Share Homes for Ukraine data's homepage

What’s next?

We have built a brilliant multidisciplinary team of dedicated professionals with product, delivery, user-centred design, business analysis and development skills, and we’re sticking together to keep improving Share.

We will continue to support our primary use case in Homes for Ukraine, simplifying and iterating our processes and technology based on user needs.

We are striving to become a ‘best in class’ live service, providing timely and expert support to our users.

We are preparing to take Share to a live service assessment later this year to measure our progress and get feedback from expert peers.

Most excitingly, we are starting to explore opportunities to reuse Share in new service areas. We will be speaking to colleagues in MHCLG and across government to see where there are overlaps in needs and capabilities, to hopefully accelerate other teams’ progress and prevent the need for other services to start from scratch.

Watch this space for more updates, and if you’re interested in using Share in your service, please get in touch at: This email address is being protected from spambots. You need JavaScript enabled to view it..

Find guidance on Data sharing: Homes for Ukraine on GOV.UK.

Read previous blog posts from the Homes for Ukraine Digital team.

Original link
(Originally posted by Coco Chan, Head of Product, Homes for Ukraine Digital)
Leave Comments