Wired has no formal "Children" desk. What exists is a cluster of coverage — policy, security, science, and culture stories where minors are the users, subjects, or regulatory targets.

That distinction shapes everything. You are not pitching a parenting column; you are pitching a technology newsroom that treats childhood as an infrastructure and policy problem.

Wired covers children as systems: the platforms, laws, devices, and datasets that govern young people's lives. Expect regulation (COPPA 2.0, KOSA, state age-verification laws), platform accountability, and school technology.

Strong territory: AI companions and chatbots marketed to teens, edtech surveillance, kids' data brokers, app-store age gates, youth mental health and device research, gaming economies, and child-safety-versus-encryption fights.

Weak territory: product roundups, seasonal gift guides, generic "screen time is bad" trend pieces, and anything that reads like parental advice. Wired's readers want mechanism and evidence, not moral reassurance.

Our directory shows a thin beat: one or more active bylines, with Tim Marchman as the representative writer. Treat the Wired Children reporters list as a starting map, not a fixed roster.

Marchman's range spans health, misinformation, science policy, and the politics of expertise — which means children's topics land with him when they involve contested science or regulatory failure. Pitch the evidentiary fight, not the sentiment.

Because the beat is a composite, coverage also surfaces from security, policy, and science reporters. Before any send, pull 60–90 days of bylines on your exact subtopic and pitch the person who actually wrote it.

Lead with a finding that would survive a fact-check by a hostile engineer. The strongest pitches contain a number nobody has published, a document nobody has obtained, or a test nobody has run.

Winning angles we see convert:

• Original testing. You audited 40 teen-facing AI companions against their own safety policies. Report the failure rate.
• Document trails. State AG correspondence, school district contracts, FTC comment filings, platform transparency data.
• Policy mechanics. A law's enforcement date versus its technical feasibility — who actually complies, and how.
• Researcher access. A named academic with unpublished data who will speak on record.

Avoid positioning children as a monolith. Wired's best work distinguishes ages, platforms, and jurisdictions — a 9-year-old on a school Chromebook is a different story from a 16-year-old on Discord.

Email remains the channel. Keep it under 150 words, put the finding in the subject line, and paste the core evidence in the body rather than attaching files.

Verify every address before you use it. Wired Children journalists contacts change with newsroom moves, and a bounced pitch or a misaddressed blast costs you the relationship — reconfirm against recent bylines and public profiles.

Offer the exclusive first, plainly: "This data hasn't been published; you have first look until Friday." Do not simulate urgency, and do not follow up more than once in seven days.

Be ready for a fast, technical conversation. Wired reporters ask how you got the data and who else has it — have your methodology paragraph written before you hit send.

Run this before every send to Wired Children reporters.

• Subtopic match. The recipient published on this exact issue in the last 90 days.
• One-line finding. The subject line states a result, not a topic.
• Evidence attached inline. Data, document, or named on-record source.
• Mechanism named. You can explain how the harm or gap occurs.
• Exclusivity stated. First look, exclusive documents, or clearly non-exclusive.
• No panic language. Claims survive a skeptical read by an engineer or lawyer.
• Contact verified. Address confirmed against a recent byline or public profile.
• Follow-up rule. One nudge, seven days later, then close the file.

If two or more boxes are unchecked, the pitch is not ready. Rebuild it around the document, not the narrative.