esources available and this could cause delays (internal and also with partners)  Timeframes set are unachievable and/or missed  There is a risk that there are errors in the set-up of:  the mechanism for secure transfer of data from an on-premises database to the Azure tenant  the Azure environment / configuration is incompatible with the development work that needs to take place  Tools developed do not have universal usability and are restricted to one model of service/technology provider  Project outcomes are not properly evaluated (see new risk identified at closure)  Planned IT work such as migrations could disrupt or delay project activities Ongoing risks – open, can be influenced (these would be relevant if there was further development work):  Data security risk (well-mitigated through secure infrastructure design)  Using new technologies might not produce quality/accurate outcomes and/or lack of understanding of capabilities/appropriate application to practice  Legal risk relating to the funding agreement  Records that are currently restricted for particular staff in liquid logic case management system will be able to be viewed through the search tool (e.g., technical the solution that is in place restricting some records has not been replicated) (NB: project was a proof of concept and not implemented so no users have access to it)  Practitioners might use new search technology to circumvent existing restrictions and access information about people that they are not entitled to access (NB: project was a proof of concept and not implemented so no users have access to it)  Issues with the source data may prevent some goals being achieved  Practitioners may not be able to navigate from the tool back to source documents  Skills and knowledge gap and t