t unknowns mean making an accurate overall estimate is challenging. This is because set-up and ongoing costs depend on resources available and the position of the organisation together with how much data would need to be processed, based on the size of historic datasets and ongoing usage. All consideration of cost should be balanced against the significant potential for savings due to reduced time spent on data retrieval. See Section 4.3 (Evaluation of Expected Benefits) and Section 4.4.2 (Evidence – Time Spent on Data Retrieval Tasks). The development of each requirement by experts at delivery partners (Microsoft and Simpson Associates) and cross-council services has also provided accompanying recommendations for improvements. For 26 OFFICIAL - SENSITIVE example, there are opportunities to link information from the dataset to geospatial reporting, including where addresses and locations are held within unstructured data. 4.1.5 Lessons Learnt A lessons learnt workshop took place, this involved informal conversations based around process and impact evaluation questions. This allowed project stakeholders to reflect on the completed project in a structured approach. This format allowed participants from the Project Team to share detailed perspectives on the work and included discussing and identifying areas for improvement and learning from both successes and mistakes. Lessons learnt are included at Section 3.6 (Process Evaluation Questions) and 3.7 (Impact Evaluation Questions). A summary of technical issues and resolutions are included at Section 4.1.2 (Technical Issues and Resolutions). The information available in these sections should be stored and shared to enable the organisation and wider sector to:  Learn from mistakes  Gather best practice  Build trust  Ident