Finding an expert for a technical story is not a directory problem, it is a targeting problem. You start from one specific claim your story needs someone to confirm or explain, work out what kind of expertise speaks to that claim, and only then search for names. This guide walks through how to find experts for a technical story end to end: defining the claim, searching the channels where that expertise is actually visible, checking independence before you quote anyone, and writing an outreach note a busy researcher will answer.
Most cold outreach fails on the first sentence, not the sourcing. A reporter asks a professor to “comment on the story,” and the professor forwards it to a colleague as free work with no value in it. Bring the specific question instead and the response rate changes completely.
Updated October 2026.
Table of Contents
- What You Need
- Step-by-Step: How to Find Experts for a Technical Story
- Common Mistakes
- Frequently Asked Questions
- Do I need an academic title to be treated as an expert on a technical story?
- How do I find an expert who does not work for the company in the news?
- How do I write an outreach email an expert will actually answer?
- What do I do when no expert will comment on my story?
- Can a journalist pay an expert source for an interview?
- How long should I wait before following up with a source who has not replied?
- Stop Starting Every Story From Zero
What You Need
Before you open a single directory, five things should exist in writing. Skipping them is what turns an hour of sourcing into two days of cold emails.
- A claim list. Every factual assertion in your draft that needs an outside voice, written as a sentence. “The model degrades on long documents” is a claim. “This is a well-known AI story” is not.
- A technical requirements sheet. The domain, the systems or platforms involved, the level of jargon you can safely use, and whether you need someone who builds systems, studies them, or regulates them.
- A triage rule. Before you look at any candidate, decide which of the three expert types you need: the practitioner who operates the technology, the independent researcher who studies it, or the vendor representative who sells it. They are not interchangeable.
- A contact record. One table, always growing, with fields you will want at publication time rather than reconstructing later.
- A fact-check file. A running document of what is verified, what is attributed, and what remains unconfirmed. Keep the sourcing evidence attached to it.
Add a real deadline to that list. Technical experts run on grant, teaching and release cycles. The mismatch between your newsroom deadline and their working week is the single biggest cause of non-response, and it is structural rather than personal.
Step-by-Step: How to Find Experts for a Technical Story
Here is how to find experts for a technical story in six moves. Each one has a finish line you can check before moving on.
Define the expertise the story actually needs
Convert the story from a topic into an evidence requirement. “AI data centers” is a topic; “someone who has actually run power and cooling for a large training cluster” is an evidence requirement.
Write a one-sentence source brief before you search. Mine the people you need to talk to: the technical domain, the kind of role, any location or language constraint, known conflicts with the parties, and the exact question they must answer.
A useful brief reads: “Needs an electrical engineer or facilities researcher who has published on data center power draw, not employed by any hyperscaler or its landlord, to explain why a 100MW campus takes four years to energize in Northern Virginia.” That sentence eliminates most of the internet for you.
Finish line: you can say, out loud, what a successful answer sounds like, and what would make the answer useless.
Map the technical field and adjacent disciplines
Technical stories rarely get explained by people in the obvious category. Map who sits in the territory: the labs and research groups publishing on the question, the standards bodies and regulators writing the rules, the universities running the relevant programs, the companies operating the systems, the practitioner communities where people post war stories, and the adjacent fields whose experts understand the mechanics even when they lack the title.
A story about grid interconnection delays might be best explained by a transmission planner, a state utility commissioner, or an energy-systems economist rather than by the company whose permit is stuck. A story about a data breach often needs a detection engineer, not a security vendor’s communications lead.
Sketching this map on paper takes twenty minutes and saves hours of pitching the wrong people well.
Search where subject experts are discoverable
Search source-first. Read what the person published or presented, then find them, rather than scrolling a contact list hoping someone fits.
- Publication records. Google Scholar, ORCID and ResearchGate tell you who is active, on what, and with whom. A named author on a relevant paper is an easy, respectful cold approach.
- Faculty and staff directories. University sites list research staff, lab members and former doctoral students. Department pages of less famous universities often surface people who suddenly look relevant because you never thought to look there.
- Conference programs. Accepted abstracts and speaker lists tell you who works on the exact problem and who is comfortable talking publicly. Large conferences gather a striking number of approachable experts in one place.
- Professional communities and specialist press. Mailing lists, forums, niche trade publications and engineering Slack or Discord spaces surface practitioners with no public profile but deep operating knowledge.
- Press and communications offices. Useful as a filter and as a route to a named spokesperson, but never as your only channel.
- LinkedIn. Good for practitioners and for mapping who works where in a company, weaker for researchers than a publication record.
- Expert-finding services. Directories such as Muck Rack, HARO and Science Media Centre style networks, plus press-release wires, give you breadth fast. Vet every name independently, and know that a listing tells you nothing about independence.
- Search engines with intent. Query the claim, not the job title, then mine the linked authors of the useful results.
A note on social platforms: they work for leads and for finding people who post publicly and thoughtfully about the subject, but a hot take in a thread is a lead, not an expert.
Check credentials, relevance, and independence
Verification happens before the interview, not after you have a quote you like. Work through three tiers.
Tier one, subject fit. Does their recent work touch the actual claim? Read the last two or three items in their publication or project record rather than a bio, because bios go stale and rarely mention the current role.
Tier two, real credentials. A degree, a licence or a professional certification is verifiable in institutional directories. For practitioners, verifiable means shipped systems, published postmortems, conference talks or open-source work with a commit history.
Tier three, independence. This is where most guides stop early and where stories get burned. A conflict of interest is not a disqualification; undisclosed influence is. Check advisory boards, equity, grant funding from a party in the story, consulting relationships, prior op-ed advocacy on the same issue, and whether they hold a communications or investor role.
| Expert type | What they are best at | Usual bias to guard against | Use them when |
|---|---|---|---|
| Practitioner | How systems actually behave in production | Advocacy for their own tooling or community | The story is about operations, failure modes or day-to-day reality |
| Independent researcher | Evidence, mechanisms, honest limits of what is known | Academic incentives and career stage | You need an authoritative claim explained and bounded |
| Vendor representative | Company position, roadmap, internal numbers | Employment and messaging | The company is the subject and its voice must appear on the record |
Treat vendor quotes as attributed statements from that company, never as independent analysis, no matter how senior or how technical the person is.
If you bootstrapped your list with an AI tool, verify before you pitch. Check that the person appears in a real publication record, that the affiliation they are listed under actually exists and employs them, and that they have not retired, moved institutions or left the field. Then find one primary artifact: a paper, a talk, a repository, a filed document. If you cannot find one, delete the name.
Finish line: for every name on your list you can point to a specific piece of evidence and a specific affiliation you checked.
Contact the expert with a precise, ethical pitch
The pitch has six parts: who you are, what the piece is, the exact question, the real deadline, the attribution terms, and an offer to correct factual errors before publication. Keep it under 200 words.
For an academic or researcher:
Subject: Question on transmission interconnection timelines for a reported piece
Dear Dr. Okafor, my name is [name] and I write for [outlet]. I am reporting a piece on why transmission projects in [region] now take four to seven years to energize, and I need someone who has worked on interconnection filings to explain where the time actually goes.
Three specific questions: which stage adds the most time in your experience, what changed in the last five years, and what a project would have to demonstrate to move faster.
I am aiming to file by [date], and I would like a 30-minute call on [two windows] or a short written exchange if that is easier. I would attribute you as [affiliation], and I will send you any factual claim about your work for correction before publication. No fee is involved; I would be glad to credit your published research.
Thank you, [name], [outlet], [email]
For a practitioner, shorten it. Engineers reply to a concrete artifact question faster than to a topic question, and they want to know what you already know.
Follow-up. Send one nudge three or four business days later, adding something rather than repeating yourself: a link to the relevant paper, a second deadline, or a narrower question that is easier to answer. Then stop. Two messages is the ceiling for a cold pitch.
If you get a no, reply thanking them and asking whether anyone else comes to mind. That single line is where many of your next sources come from.
Build and document a usable expert pipeline
One spreadsheet with the fields below is enough. The point is that your sourcing survives the story, so the next assignment starts warm.
| Field | What to record | Example |
|---|---|---|
| Name and role | Title as they ask to be described | Dr. Ana Ruiz, principal engineer |
| Affiliation | Institution plus any employer or client ties | Midwest university; consulting clients unlisted |
| Beat and topic | Narrow tags you will search later | grid interconnection; permitting |
| Evidence link | Paper, talk or post that justifies the call | Recent IEEE paper on queue reform |
| Contact | Email, work phone, assistant or PIO | Institutional email, not a personal one |
| Attribution terms | On the record, on background, or named generically | On the record, title only |
| Last contact and outcome | Date plus responded, declined, or ghosted | 12 Sep, responded, call booked |
| Conflicts | Funding, boards, prior advocacy | Grant from a utility in the piece |
Review the sheet monthly. Response rate per channel is the number that tells you where to spend your next hour, and it is the metric most reporters never measure.
When someone does not reply, escalate in this order: check whether the address is institutional or personal and resend to the correct one, look for a public information officer or assistant who can route it, find a reason they should answer specifically by reading their most recent work, and finally find a second expert who may know who to talk to.
If you truly cannot find an expert, say so in the story. Use the public documents, filings, inspection reports, peer-reviewed literature and base rates instead, and describe the uncertainty plainly rather than filling the gap with the only person who picked up the phone.
Common Mistakes
Contacting only executives. Chief technology officers and heads of communications are well-spoken and available, and they represent an employer. Fix: build the independent side of the list first, then add the company side.
Treating credentials as proof. A senior title shows seniority, not truth. Fix: check the actual work product and look for someone whose interest does not depend on the outcome.
Asking vague questions. “Can you comment on this story?” reads as unpaid labour. Fix: ask three specific things and say what you already know.
Ignoring conflicts of interest. Funding, advisory seats, equity and prior advocacy are checkable in an afternoon. Fix: record them in the contact row and disclose material ties in the piece.
Relying on stale bios. Bios written three years ago still describe people who have since changed jobs. Fix: verify the current role on the institution’s own directory or their most recent publication.
Publishing one expert’s claim uncorroborated. One technical voice on a contested point is a single source. Fix: get a second, independent voice, or narrow the claim to what one person can attest to.
Omitting the deadline. An email without a date reads as low priority forever. Fix: give a real date and two concrete windows.
Disappearing after publication. Sources remember whether you sent the draft, fixed an error, or credited their work. Fix: send the link, thank them, and log the outcome.
Frequently Asked Questions
Do I need an academic title to be treated as an expert on a technical story?
No. Reporters regularly use engineers who have run the systems in question, practitioners with public postmortems, regulators, standards committee members and community specialists. What matters is verifiable, relevant work plus the independence to speak without pressure from a party in the story. An academic title is one route to that, not the only one, and the piece is often stronger with a practitioner paired alongside a researcher.
How do I find an expert who does not work for the company in the news?
Search the adjacent ecosystem rather than the subject’s own employer: university labs that study the technology, former employees documented in conference talks, standards bodies, regulators, academics named as critics in peer-reviewed reviews, and the comment sections where practitioners of that stack trade notes. Check publication records for co-authored work with the company, and check funding disclosures before you rely on the answer.
How do I write an outreach email an expert will actually answer?
Keep it under 200 words and put the specific question up front, not the request for comment. Name the piece, give the exact question or three, give a real deadline with two windows, state the attribution terms you plan to use, and offer a factual correction pass before publication. Show that you read their actual work. Vague requests for comment are the most common reason experts ignore a pitch.
What do I do when no expert will comment on my story?
Say so in the piece and shift the evidence base rather than repeating the pitch. Use filings, inspection reports, procurement records, court documents, peer-reviewed literature and published base rates, and present the uncertainty explicitly. A story built on documents and clearly framed limits is stronger than one padded with a spokesperson who agreed to talk about everything except the problem.
Can a journalist pay an expert source for an interview?
Some outlets do, but payment changes the relationship and most newsroom codes treat it as a disclosure requirement rather than a routine practice. If you do pay, disclose it to the reader and never let it be the reason you chose the source. If you offer something, an honorarium for genuine time or a clear credit to their research usually costs less and works better than cash.
How long should I wait before following up with a source who has not replied?
Three to four business days for a practitioner or company contact, up to a week for an academic whose week is built around teaching and grant work. Send one follow-up that adds information, such as a link to relevant work or a narrower question, rather than a please-respond nudge. After two attempts, move to another name and note the outcome in your source tracker.
Stop Starting Every Story From Zero
Knowing how to find experts for a technical story comes down to three habits: write the claim first, send a second contact the same day you find a promising name, and keep the record so the next assignment starts warm. Do those and the cold-start problem happens once per career instead of once per story.
