Oxford Mail explains court reporting paywall strategy
Summarised from 2 outlets · Updated 25 Oct, 16:31 · Archive
The Oxford Mail places some Crown Court reports behind a subscriber paywall to fund comprehensive local journalism.
The Oxford Mail says it places some Crown Court reports behind a subscriber paywall to support its journalism operation. The outlet argues that comprehensive court reporting requires substantial time, expertise and resources. Journalists attend Oxford Crown Court hearings weekly, covering cases ranging from murder trials and serious assaults to large-scale drugs conspiracies, sexual offences and complex fraud cases.
The publication says many of its stories would otherwise go unreported. Whilst court proceedings are held in public, the outlet notes that court coverage involves spending hours listening to evidence, taking detailed notes and ensuring accurate reporting whilst understanding legal restrictions and complex criminal procedures.
The Oxford Mail says this work helps keep communities informed about crime, the operation of the justice system and the impact on victims and families. The outlet argues that subscribing provides access to in-depth local reporting not found elsewhere, whilst funding wider journalism on breaking news, local politics, education, health, transport, business and community stories.
How it is being reported
- Why you should subscribe for Oxford Crown Court reportsAs the Oxford Mail's court and crime reporter, readers may sometimes notice that some of my court stories are available only to subscribers.Oxford Mail · 25 Oct, 16:00
- Why you should subscribe for Oxford Crown Court reportsAs the Oxford Mail's court and crime reporter, readers may sometimes notice that some of my court stories are available only to subscribers.Oxfordshire Guardian · 25 Oct, 16:00
In this story: Oxford Mail · Oxford Crown Court · Oxfordshire
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem
Comments (0)