Wired treats policy as a technology story with a power struggle inside it. If your pitch leads with process — hearings, filings, bill numbers — you will lose to a reporter who leads with what the rule actually does to systems and people.

This guide covers how to approach Wired Government Relations reporters with the framing, evidence, and timing their beat demands.

Wired's government relations coverage sits at the seam between regulation and technical reality. The beat is less "what Congress said" and more "what the rule breaks, enables, or hides."

Expect appetite for: AI rulemaking and agency guidance, state AI and privacy statutes, antitrust actions against platforms, encryption and surveillance mandates, broadband and spectrum policy, chip export controls, procurement of emerging tech, and records-driven accountability work.

The audience is technically literate. They will reject a pitch that explains what an API is but accepts one that explains why a procurement clause quietly locks a city into a single vendor.

The beat is thinly staffed, which is an advantage. A small roster means less competition for attention and a higher premium on pitches that arrive pre-reported.

Start with the Wired Government Relations reporters list in your directory and verify each name against their current author page. In this buildout, Mike Dent is the representative entry — treat that as a starting point, not a complete map.

Wired Government Relations journalists frequently file across adjacent desks, so tag anyone covering policy, security, or business of tech who has published a policy-adjacent piece in the last 90 days. Recent bylines are the most reliable signal of live interest.

Build a working tracker: name, recent pieces, sub-beat signals, sourcing style, and preferred contact channel. Refresh it monthly — beat assignments at Wired shift with news cycles.

The winning pitch answers three questions fast: what changed technically, who controlled the decision, and what happens next. Anything else is context.

Strongest assets, in rough order of value: original records (FOIA responses, contracts, comment dockets), proprietary datasets, named on-record sources with direct knowledge, and access to the engineers or officials closest to implementation.

Weak assets: vendor surveys, coalition letters, position papers, and "exclusive" commentary from a think tank that has already briefed six other outlets.

Specific angles that fit Wired's register:

• Implementation gap stories. The law passed; the agency has no staff, no budget, or no technical definition. Wired likes the gap between statute and reality.
• Procurement as policy. Contracts are underreported and highly citable. They show intent where press releases show ambition.
• Enforcement capacity. Who actually inspects, audits, or tests? Often the answer is a small team with a spreadsheet.
• Technical consequence. A rule that changes default encryption or model disclosure requirements is a Wired story. A rule that changes a reporting form is not.
• Conflict of interest with receipts. Revolving doors, lobbying disclosures, and calendar records travel well when documented.

Send one email. Make it readable on a phone screen in under thirty seconds.

Your first contact should include the hook, the evidence you hold, what you can provide, and a clear ask — usually fifteen minutes or a document handoff. No attachments; link to materials instead.

When sourcing Wired Government Relations journalists contacts, verify against the author's own page and public profile rather than relying on a scraped address. Wired reporters are active on Bluesky and X, and a brief, non-pitchy DM about a document can open a channel email cannot.

Respect the structure of a small desk. Never pitch two Wired reporters on the same beat simultaneously, and never CC a press inbox on a personal pitch. If the story is sensitive, offer Signal and say so plainly.

Keep embargo terms realistic and explicit. Wired honors embargoes when the material is genuinely original and the terms are stated cleanly in the first email.

Run this before hitting send.

• Hook in one sentence. Can a reader who covers policy daily repeat it after one pass?
• Artifact ready. Document, dataset, or named source locked and holdable for 48 hours.
• Stakes named. Who gains power, who loses it, what breaks if the rule stands.
• Timeliness anchor. Docket close, vote, audit release, contract award — date it.
• Exclusivity stated. First-look, or clearly shared with other outlets.
• Contact block clean. Name, role, Signal number, one-line bio. No signature graphics.
• Subject line tested. Under 60 characters, artifact-first, no all-caps, no "Re:".
• Follow-up scheduled. One touch at day 3–4, then stop.

Pitch the artifact, not the announcement. That single habit is what separates pitches that land with Wired Government Relations reporters from the rest of the inbox.