, and connections. Code and guidance for the specification is located at the Data to Insight code repository, hosted by GitHub: GitHub - data-to-insight/ssd-data-model: Standard Safeguarding Dataset (SSD) 5.4. Pilot deployment As research concluded and the draft specification stabilised (in autumn 2023), we commenced development of production methods to generate the SSD dataset from local systems. In our bid we identified two possible routes for this work: one was to work with CMS suppliers to build the SSD production code into their core systems and maintained business processes; the other was to work with LAs to produce generic SQL-based data extract scripts for each CMS which could be tailored to the local context in each user LA. We identified that a key stipulation in the DSDF funding framework would inhibit the supplier engagement option; the funding agreement was explicit that all intellectual property generated by the project would be the property of the DfE on project close. After discussion within the steering group and with partners, we mapped the likely pathways for supplier engagement in light of these stipulations and decided that the risk of a compromised product, and the risk of initial negotiations delaying the overall project, was too great, and we selected an LA-engagement option as our first choice of approach. We quickly found multiple suitable LA partners for co-developing SQL extracts from the two market- leading CMS products, and started work mapping our specification to their local systems. As this neared completion, we began to write and test SQL extract code locally, and then to test it against other partner LA systems to understand compatibility and possible tailoring needs. 11 Midway through this work we identified a database technology spli