Wired's transportation desk is small, senior, and allergic to press-release theater. With roughly one full-time writer owning the beat, a single well-aimed pitch can define a story cycle — and a generic one disappears in minutes.

This guide covers editorial scope, roster mapping, angle construction, and outreach protocols for Wired Transportation reporters, built around the realities of a thin, high-influence beat.

Wired treats transportation as a technology-and-power story, not a trade vertical. The through-line is how new systems — software, batteries, sensors, capital — reshape how people and goods move, and who wins or loses.

Recurring territory: EVs and battery supply chains, robotaxis and driver-assistance systems, transit policy and funding, road safety data, aviation, rail, freight logistics, and micromobility.

Wired skips: dealership promotions, quarterly earnings recaps without a tech or policy hook, and straight product reviews (those route to the Gear desk, not the beat).

Build your Wired Transportation reporters list from bylines, not from a static media database. Pull the last 90 days of transportation coverage and note who actually filed.

Aarian Marshall is the anchor byline on the beat, covering EVs, autonomy, transit, and transport policy. Adjacent coverage frequently comes from AI, security, and business writers — track those too, since they can carry a transport-adjacent story faster than the beat lead.

Verify each entry quarterly. Beat assignments rotate, and stale Wired Transportation journalists contacts are worse than none — they signal you haven't read the outlet.

Lead with a finding, not a company. The strongest pitches open with a number that contradicts conventional wisdom, then explain why the system produced it.

Angles that consistently land:

• Proprietary datasets — charging reliability, crash rates by ADAS mode, delivery fleet utilization, transit ridership recovery.
• Regulatory friction — permit fights, liability gaps, NHTSA and FTC posture, state-level rule divergence.
• Access and field reporting — a ride in a robotaxi, a shift in a warehouse, a depot tour with an engineer who'll speak plainly.
• Failure analysis — what broke, why, and what the industry is quietly changing.

Skip: funding rounds without a mechanism story, "partnership announced" news, and anything that reads like it was written by the comms team.

Wired Transportation journalists reward specificity and punish hype. If you can't state the counterintuitive claim in one sentence, the pitch isn't ready.

Use email. Keep it under 150 words, put the claim in the subject line, and paste the key data point in the body — never behind an attachment.

For Wired Transportation journalists contacts, use the outlet's staff page, verified social profiles, and reputable media databases. Never scrape personal numbers or pitch via DMs unless invited.

Offer exclusivity when you have it, and say plainly how long it holds. Wired's writers work on multi-week arcs; a 48-hour exclusive rarely moves them, but a two-week window with real data often does.

If you get silence, one follow-up after five business days is the ceiling. Then move to the adjacent writer with a different angle — not the same pitch.

Run this before sending:

• Does the subject line state a finding, not a company name?
• Is the counterintuitive claim in the first two sentences?
• Is there proprietary data, a document, or field access attached?
• Have you read the writer's last three pieces this month?
• Is the spokesperson an operator or researcher, not just a CMO?
• Is the exclusive window realistic for a multi-week reporting cycle?
• Would this survive a Wired editor asking "so what changes?"

Ship it tight. On a one-writer beat, precision is the entire strategy.