The BBC's High Tech desk sits at the intersection of public-service journalism and global technology scrutiny. Pitches win when they are evidence-led, consumer-relevant, and defensible in front of a general audience.

This guide is built for PR teams working a small, high-value beat: two or more active BBC High Tech reporters covering a vast territory. Precision beats volume every time.

BBC High Tech coverage prioritises audience impact over product novelty. Expect strong interest in consumer harm, platform accountability, security, AI governance, and UK tech policy.

The desk also carries a global remit through BBC World Service and digital verticals, so stories with cross-border implications travel further.

Commercial announcements are rarely the story. The story is what the technology changes for people, markets, or regulators.

The beat is lean — a handful of names cover what most outlets split across five desks. Maintain a living BBC High Tech reporters list and review it monthly.

Our directory currently flags Nick Barnes and Jo Hornby as representative writers on this beat. Treat that as a starting point, not a closed roster.

Map each name to actual output before pitching. Read their last ten pieces and note recurring themes, sourcing patterns, and preferred formats.

BBC High Tech journalists respond to stories that can survive a hostile read. Assume your central claim will be independently verified before publication.

Strongest angles cluster around accountability: who is harmed, who knew, and what the regulator is doing about it.

• Consumer harm at scale: breaches, scams, faulty devices, opaque pricing.
• Regulatory friction: Ofcom, CMA, ICO, EU AI Act, Online Safety Act enforcement.
• Platform accountability: moderation failures, algorithmic amplification, child safety.
• AI in public services: NHS, education, policing, benefits — with named pilots.
• Infrastructure risk: outages, supply chain, undersea cables, data centre pressure.
• Cyber incidents: disclosed, attributable, and with demonstrable user impact.

Data points that land: percentage of affected users, financial loss figures, complaint volumes, FOI responses, and independent audit findings. Give the number and its source in the same sentence.

Route pitches through official desk channels and named-bylined emails where published. Avoid mass BCC sends — they are read as noise.

Keep the first email under 150 words: hook, evidence, access, availability. Attach nothing on first contact.

When sourcing BBC High Tech journalists contacts, verify current roles directly. BBC staff move between desks and between national and World Service teams frequently.

State clearly what you can provide: interviewees, datasets, demos, or documents. Vague "happy to chat" offers expire quickly.

Respect embargoes absolutely. A single early breach on this beat costs you the relationship, not just the story.

Run this before every send.

• Story is about impact, not product.
• Hook is timestamps or news-pegged.
• Two independent data points included.
• Named, briefable spokesperson confirmed.
• Visual assets identified and rights-cleared.
• Pitch is under 150 words, plain text.
• Target writer verified against recent bylines.
• Embargo terms stated explicitly.
• Follow-up scheduled for 48 hours, once only.

Two well-aimed pitches a month to the right BBC High Tech reporters outperform fifty generic sends. Precision is the whole strategy.