hey’re like, what difference is this going to make to my child now? But that’s not the issue. The issue is all this data is collated and it’s sent to central government next month. So central government are going to be looking at our data of our looked after children, immunisation, and health data, because of data input, and then they will judge how we’re doing as a local authority to close the gap on health issues for looked-after children by that data input.” (Practitioner) Within this is the understanding of why the data is collected in the first place. Practitioners understood that although they may not consider a data item as relevant to the children and families in their care, it is relevant to other organisations: “There are lots of different data platforms and it feels different agendas for every aspect of things. Every agency will have their own agenda, their own purpose, their own outcome of where they’re going to be going and what is important for them to collect with their data.” (Practitioner) “I guess it’s about whether that data impacts that specific child, but arguably the data impacts actually on the ability of the organisation to know that it’s meeting expectations for all children who are identified.” (Practitioner) As the CMS do not transfer information and data across and between each other (including those used by different agencies working as part of the team around the child, such as education, health and police) it is important that information is recorded on all the relevant forms. This is generally not understood or known by practitioners, causing pain points in data entry: “I can see how many [CLA] reviews are held in timescales...will tell me late/overdue but systems don’t talk to each other.” (Data consumer) Voice of the child/young person 