In our latest blog, Job, one of our regulators,  demystifies the job of a statistics regulator.

Statistics regulator. It’s quite a strange-sounding job. If you asked a random person on the street what they think a statistics regulator does, they would probably say that it’s someone who regulates statistics. But if you asked them what this means, they would probably draw a blank. Fair enough – most people aren’t familiar with the idea of regulating statistics. 

So, what does a statistics regulator do? A wide range of things! There is no such thing as a typical week – what we do can vary from week to week – but there are some common activities. The journal below gives you a flavour of the kinds of things I do as the lead of a domain in OSR. 


In the morning, I checked our information dashboard, an internal tool developed by our Data and Methods team. It scrapes data from government statistics release calendars, news websites, Twitter, and Hansard, which helps us monitor the release and use of official statistics. I came across several interesting media articles and Twitter threads about hate crime data. I reviewed what they say and decided that there’s nothing I need to investigate further. 

In the afternoon, I spoke to a couple of users – an academic and a think tank – of Home Office’s police officer uplift statistics, which report on progress with the recruitment of an additional 20,000 police officers in England and Wales. We recently assessed these statistics against our Code of Practice for Statistics (the Code). Assessment is one the main tools we use to review whether statistics are meeting the standards of trustworthiness, quality and value set out in the Code. Speaking to users is a really important part of assessments. It helps us understand what the statistics are used for and what users think of their trustworthiness, quality and value, to identify where improvements can be made. 


In the morning our Head of Private Office and Casework Manager emailed me about a piece of casework I’ve been working on. Casework is what we call our work investigating issues raised with OSR. We have an interventions policy that sets out when and how we intervene in the use of statistics. We can raise casework ourselves internally or members of the of the public can raise casework with us, which could be anything from something which was identified as misleading in a government report, to something a Member of Parliament (MP) said on Twitter. For the case I worked on today, I investigated the concerns raised, prepared a briefing with a summary of the issues, analysis of the statements and statistics, and recommendations for what we should do next.  


My morning started with two back-to-back team meetings: a site catch-up and an organisation-wide “Cascade” with colleagues in the Edinburgh, London and Newport sites (and those based elsewhere). It’s a chance to hear about what’s happening across OSR and to share any important updates. In today’s meeting I gave an update about the domain I work in, alongside the seven other domains in OSR. We also heard about next year’s business planning from our Senior Leadership Team.  

Every other Wednesday afternoon we have team learning sessions. These are mostly used to share knowledge across the team, but we also use them to discuss ways of improving how we work. Today is a ‘Code Case Learning’ session, where two colleagues presented some regulatory work that they’ve been involved in covering a specific principle of the Code of Practice for Statistics. The idea is to help regulators develop their understanding of aspects of the Code and hone their judgement in applying the Code.      


In the morning I met with the Deputy Head of Profession for Statistics and Head of Publications at the Ministry of Defence (MOD). We discussed new developments to their statistics and an idea I have for a short review of a set of MOD statistics. As regulators, we meet regularly with statisticians in different departments to find out what is happening with their statistics and how we can best support them to meet the standards of the Code. 

I spent the afternoon drafting a letter to the Department of Justice in Northern Ireland setting out the results of our compliance check of their prosecution and conviction statistics. Compliance checks are another tool we use to review statistics against the Code. They’re shorter and less detailed than assessments, which allows us to review a wide range of statistics every year.       


Friday is my non-working day. OSR and the Civil Service offer flexible working arrangements, which is great for maintaining a work-life balance. 

On Fridays, our Director General, Ed Humpherson, sends a weekly update to the whole team reflecting on the activities and events of the week. It’s great to hear about Ed’s external meetings and the impact of our work is having. It’s a good reminder of the difference that regulators can make!