Wired's Events beat sits where technology, money and live experience collide — ticketing platforms, conferences, festivals, esports and the security apparatus behind them all.

For PR teams, this is a beat where access and evidence beat enthusiasm every time. Below is how to pitch Wired Events reporters without landing in the archive.

Wired treats events as a lens on tech power, not a calendar of happenings. Coverage skews toward how platforms — ticketing, streaming, dynamic pricing, surveillance, AI scheduling — reshape live experiences and who profits or gets shut out.

In scope: trade shows and conferences (CES, SXSW, WWDC), festival and live-music technology, ticketing monopolies and pricing algorithms, event security and biometric entry, esports and gaming tournaments, immersive and AR/VR activations, plus the operational failures that spill into public view — outages, scams, crowding, refunds.

Out of scope: "we're exhibiting at" notes, sponsorship announcements without a news peg, brand anniversary parties, and product feature drops dressed up as culture stories.

There are 4+ active journalists on this beat at any given time, and the byline mix shifts with the news cycle. Our directory currently tracks Matthew Champion, Paresh Dave, Megan Farokhmanesh and Evelyn Kwong as representative writers — treat that as a starting point, not the full picture.

Map each name to the sub-angle they actually own: policy and legal exposure, platform economics, culture and fandom, or event operations. Then pitch the writer, not the desk.

Keep a living Wired Events reporters list and refresh it monthly against recent bylines. Verify Wired Events journalists contacts before you hit send — a stale address is a dead pitch.

Wired Events journalists respond to numbers with provenance: attendance figures, ticket-price deltas, refund volumes, fraud rates, fee breakdowns, staffing ratios, outage durations.

Bring something only they can have — first access to the venue ops lead, the security vendor, the internal post-mortem, or the researcher who measured the effect. Access is the currency on this beat.

Name the tension — surge pricing versus fairness, surveillance versus safety, hype versus operational reality. Neutral "we're excited to announce" language gets filed and forgotten.

Email remains the front door. Put the name, the number and the stakes in a subject line under 12 words, and keep the core pitch in the body — no attachment-only sends, no 900-word preamble.

Respect time zones and publication rhythm: UK-based writers and US-based writers run on different clocks and different news cycles. A Monday morning pitch for a Friday event is already late.

For Wired Events journalists contacts, work from verified bylines, the Wired masthead, and your own maintained directory rather than guessed email patterns. One targeted follow-up after three to four business days is standard; a second is the limit.

• Never send the same pitch to all four writers simultaneously — stagger and personalise.
• Always state embargo terms explicitly and honour them to the minute.
• Offer a named, briefable spokesperson plus one supporting document in the first email.
• Skip DM-first outreach unless the reporter has publicly invited it.

• News peg: Is there a dated, verifiable moment this attaches to?
• Numbers: Do you have at least one original figure with a source?
• Tension: Can you state the conflict in one sentence?
• Access: What can you offer that isn't a press release?
• Spokesperson: Is there a technical or firsthand voice available within 24 hours?
• Exclusivity: Are you offering a genuine first, with clear terms?
• Writer fit: Does this match a specific byline, not just the beat?
• Subject line: Under 12 words, name plus stakes?
• Assets: Linked, described in one line, no login walls?
• Follow-up: Scheduled once, at the right hour for their time zone?

Run this list before every send. On the Events beat, precision reads as credibility — and Wired Events reporters can tell the difference in the first sentence.