ther partner LA systems to understand compatibility and possible tailoring needs. 11 Midway through this work we identified a database technology split for one of the market-leading CMS products, requiring us to work with another test partner and adapt our existing T-SQL code to a separate Oracle-SQL option for that product. By March 2024, we produced shareable data extract code for the first version of the SSD specification, for the two market leading CMS products, including testing our pilot developments in unrelated partner councils to demonstrate national scalability. Within the project year we were unable to complete the same work for three CMS products with smaller market share – we have outlined our proposals for completing this work in the separate “Future Support Plan” document. 5.5. Product delivery Throughout the project we embraced open working principles, looking to share our work-in- progress widely, frequently, and in ways which suited our varied audience of stakeholders. We blended formal show-and-tell meetings with open team meetings, including DfE in our regular project planning discussions to ensure client visibility of the ongoing work, and ensuring our colleagues in LAs and the wider sector had opportunities to discuss the project with us directly. We also shared drafts of our core deliverables as we arrived at them, including early publication of the framework for presenting and maintaining the SSD specification. As such, each of our products has more than one “delivery date”, and often several; the below timeline notes the key points at which DfE first received different project outputs: May 2023 “Summarising User Research” document and presentation Jul 2023 First public SSD specification diagrams and production pipeline Oct 2023 Updated SSD speci