ts potential to support cross-sector goals. Though we’ve split this between LA-centric and DfE-centric use cases, in most cases, anything improving data work in the sector will ultimately benefit both DfE and LAs. • Extended ChAT – potential to make shared tools like the ChAT more useful • Patch – potential to extend the D2I “patch” tool with wide-ranging online analysis tools • FOI response work – potential to share scripts for answering FOIs based on standard dataset • Demand modelling – potential to make shared demand tools more insightful with wider standard dataset available for modelling • Responding to DfE data requests – potential to share scripts for answering DfE requests • Quarterly benchmarking – potential to dramatically reduce admin burden of quarterly returns • Quarterly benchmarking – potentially to dramatically expand reach of quarterly benchmarking without increasing admin burden for individual LAs • Further collaboration – with our away from D2I, standard data formats enable collaborative projects between LAs nationally to improve processes, better understand markets, etc. 18 7.7. Other central government use cases This is a non-comprehensive, indicative list of example use cases for the SSD once implemented, to help stakeholders understand the value of the approach and its potential to support cross-sector goals. Though we’ve split this between LA-centric and DfE-centric use cases, in most cases, anything improving data work in the sector will ultimately benefit both DfE and LAs. • Aligning with uses of DfE’s proposed Common Child Identifier (CCI) and other systems- connecting initiatives - we have future-proofed the SSD specification by including fields for this in the draft specification, and for other relevant identifiers • Ad hoc data requests to