Non-crime hate incidents should be scrapped, police leaders to recommend

The College of Policing, led by chair Lord Herbert, is set to recommend scrapping the recording of non-crime hate incidents (NCHIs) in favor of recording only the most serious incidents, arguing social media has pulled police into policing tweets and low-level online disputes. The review, coordinated with the National Police Chiefs' Council and to be decided finally by the home secretary next month, follows pressure from the policing watchdog, the Metropolitan Police’s decision to stop investigating NCHIs and reports that 43 forces logged over 133,000 NCHIs since 2014; proponents say the change would refocus resources on real-world threats and protect free speech.

Analysis

Market-structure: Removing non-crime hate incident (NCHI) recording shifts monitoring and risk assessment from public police records to private-sector verification, moderation and security providers. Winners: identity/AML/background-check vendors (e.g., GBG.L, EXPN.L) and cloud/AI moderation providers (MSFT, GOOGL, AMZN) that can sell automated tooling; losers: suppliers of police monitoring tech (e.g., PLTR) and boutique legal firms that advised on NCHI disclosures. Expect modest re-pricing (1–3% revenue tailwind for verification vendors over 12–24 months if private checks scale) rather than market-wide shock.

Risk assessment: Tail risks include a political reversal (Home Secretary rejects review) or a high-profile online incident that forces re-adoption — each could rapidly reassign monitoring costs back to police and spike litigation. Timing: immediate (days) volatility around the review release next month, short-term (weeks–months) policy debate, long-term (quarters–years) structural shift if ministers adopt recommendations. Hidden dependencies: police budget reallocation could free funds to other enforcement (violent crime), creating offsetting demand for different tech/services. Catalysts: review publication, Home Secretary decision (likely within 1–3 months), and any high-profile online incident.

Trade implications: Direct plays: go long UK identity/verification (GBG.L) and cloud/AI moderation exposure (MSFT, GOOGL) with 6–18 month horizons; hedge or trim exposure to government surveillance vendors (PLTR) over 3–12 months. Options: buy 3–6 month put spreads on PLTR (10–20% OTM) as asymmetric hedge and buy 3–9 month call spreads on GBG.L to capture policy-driven uptake. Sector rotation: modestly overweight Tech/Software (+1–2% portfolio tilt) and select Legal/Compliance services, underweight Government IT contractors.

Key Decisions for Investors

• Establish a 1.5% long position in GBG PLC (GBG.L) within 30 trading days, target 6–12 month horizon; use a 3–9 month call spread (buy ATM, sell 20% OTM) if implied vol >25% to cap cost — thesis: private verification demand replaces police-record reliance, aim for >15% upside if Home Office adopts recommendations.
• Add 1–2% net long exposure to large-cap cloud/AI moderators (split MSFT and GOOGL) over 6–18 months to capture increased moderation tooling spend; trim 0.5–1% if the review is rejected or if a major platform reports unexpected moderation costs next quarter.
• Reduce exposure to Palantir (PLTR) by 25% or hedge with a 3–6 month put spread (10–20% OTM) sized to cover 1% portfolio risk; trigger: material adoption of recommendations by Home Secretary (expected within 1–3 months) indicating lower UK law-enforcement monitoring spend.
• If the review is published as recommended, reallocate an incremental 0.5–1% from government IT contractors into private security/services names (or GBG) within 2 weeks; if high-profile online incident occurs within 60 days, pause deployment and reassess for short-term defensive buys.