The Editorial Team
Who writes and reviews BlueLineHub content, how the review cycle works, and why we publish collectively.
How BlueLineHub is written
BlueLineHub is produced by a small independent editorial team. Content is researched, drafted and reviewed collectively, and published under the shared byline “BlueLineHub Editorial” rather than individual names. We do this deliberately: several contributors have current or former connections to UK policing, and individual attribution could compromise them professionally. The trade-off we make in exchange is radical transparency about how the content is produced — everything on this page, plus the policies linked below.
What “reviewed” means here
Every YMYL page (pay, pensions, legal, medical, welfare, recruitment) carries a “Last reviewed” date. A review is a documented pass that checks the page against its primary sources: the current Police Regulations determination, the live College of Policing APP text, the current PFEW circular, the latest Home Office statistical release — whichever sources the page cites. If a source has changed, the page is corrected before the review date updates. Pay and regulation-dependent pages are re-checked monthly and within five working days of a pay award; evergreen guides quarterly.
Where the information comes from
We only make factual claims that trace to an authoritative source — the whitelist is published in our source policy. Where we use AI tooling to help draft or summarise, a human editor verifies every claim against the primary source before publication; the boundaries of AI use are documented in the AI-use disclosure.
What we are not
No member of the editorial team writes in any official capacity. BlueLineHub is not affiliated with any UK police force, the Home Office, the College of Policing, PFEW, IOPC, HMICFRS or any statutory body, and nothing we publish is legal, medical, financial or operational advice. Where a page touches a regulated area, it says so and points at the regulated professional you should actually consult.
Corrections
If we got something wrong, tell us via the contact page. We acknowledge accuracy reports within two working days and fix within five — the process and the public log are described in the corrections policy and update log.