To brief a journalist on a technical topic without burning the relationship, match the briefing to the reporter's level of knowledge, bring the person who does the work, open with why it matters, spend most of the time on the reporter's questions, name the limits yourself and follow up with exactly what was asked for. Each step protects the reporter's trust, which is worth more than any single story.
Updated November 15, 2026. Part of EPR's media relations coverage.
Key points for a technical briefing
Calibrate: read five recent pieces by the reporter and start one level below the knowledge they assume.
Bring the specialist, such as the principal engineer or clinical lead, and keep senior leaders for framing questions.
Open with what the news changes, within the first 90 seconds.
Aim to spend more of the session answering questions than presenting.
Name the weakness before the reporter finds it, and send only the follow-up materials requested.
Before a technical briefing you should learn the reporter's technical level, choose the right expert and prepare that expert for questions. Most briefings go wrong in this stage, not in the room.
Learn the reporter's technical ceiling first. A reporter on a healthcare beat at a general business outlet usually knows less about FDA approvals than a reporter at a specialist outlet such as STAT, and the briefing has to fit the person actually in the room. Read five recent pieces by the reporter in your category and note which concepts they explain and which they assume readers know. Start one level below that baseline.
Choose the right internal expert next. The instinct is to bring the CEO, but a reporter with technical questions usually wants the principal engineer, the clinical lead or the product manager who does the work. Senior leaders can join for framing questions, and technical leaders should run the technical portion.
Then prepare the expert, not only the deck. A two-hour prep session covering expected questions, framing language, what not to say and how to handle a hostile follow-up is worth more than two more days of slide work. Give the expert a one-page guide with three likely hard questions and suggested framings, two or three real examples cleared for disclosure, and one limitation to raise first.
Sponsored · 5W5WLaunching something?5W plans the launch, the press and the follow-through so it gets noticed.Talk to 5W212.999.5585info@5wpr.com
How should you run the briefing?
Run the briefing as a conversation led by the reporter's questions, and open with what the news changes. A reporter should learn within 90 seconds why the topic matters to a patient, user, customer or market.
Four habits keep the session useful:
Open with significance. Briefings that begin with company milestones lose attention in the first minute, while briefings that begin with what changes for the category hold it.
Let the reporter steer. A reporter who asks questions in their own order leaves with the story they want to write, so plan for more question time than presentation time.
Use real examples. Reporters want a specific patient, customer or deployment, not a clean hypothetical, and specific examples produce specific coverage.
Name the limitations. If the briefer names a weakness, it becomes a paragraph in the piece. If the reporter finds it alone, it can become the piece.
Which mistakes burn the relationship?
The mistakes that burn a reporter relationship are the ones that waste the reporter's time or signal disrespect for their intelligence. The table pairs each mistake with what the reporter experiences and the fix.
Mistake
What the reporter experiences
Fix
Over-using analogies
An explanation that drifts away from the concept they already understand
Use technical language when the reporter knows the concept, and analogies only for real gaps
Talking down
Being treated as a beginner
Respect the expertise the reporter has, even outside your category
Reading the deck
A presentation instead of a conversation
Treat the deck as a reference document and keep it to 8 to 12 slides
Repeating talking points
The same sentence the last three companies used
Give specific answers that show command of the subject
Hiding the limits
A weakness found alone, which then drives the story
State the trade-off before the reporter asks
Sending extra collateral
Marketing material nobody requested
Send only what the reporter asked for
What should you do after the briefing?
After the briefing you should send exactly the materials the reporter requested, answer fact-check questions clearly and avoid chasing the story. Reporters remember which sources are reliable fact-check partners, and they return to those sources.
Send follow-up materials within a day, and limit them to what was asked for. When the reporter sends numbers or claims to check, respond with clarity and correct anything that is wrong. One email to ask whether a piece has run is reasonable. Three is not, since the reporter will publish when the story is ready.
How do you know a technical briefing worked?
A technical briefing worked when the reporter asks specific follow-up questions within 48 hours or comes back months later for another story. Both signals show the reporter is building something from the briefing, not just filing a note.
The best briefings do not produce a single piece of coverage. They produce a reporter who returns to the expert as a trusted source over months and years. When a reporter calls six months later for an expert quote on breaking news in your category, that callback is the return on the briefing. Track callbacks and expert quotes, not only the first story.
How long should a technical briefing for a journalist be?
Plan around 30 to 45 minutes and leave more of that time for the reporter's questions than for presentation. Keep any deck to 8 to 12 slides and treat it as reference material.
Who should brief a journalist on a technical topic?
The specialist closest to the work, such as the principal engineer, clinical lead or product manager, should run the technical portion. Senior leaders can join for framing questions.
Should you use analogies in a technical briefing?
Use analogies only when the reporter has a genuine conceptual gap. If the reporter already understands the concept, use the technical term.
What should you send after a technical briefing?
Send only the materials the reporter asked for, within a day, and respond promptly and accurately to fact-check requests.
How do you handle a question the expert cannot answer?
The expert should say so and offer to follow up with the answer. Admitting uncertainty builds more trust than a talking point.
Written by
EPR Editorial Team
The Everything-PR Editorial Team is the staff byline for news, analysis and features on public relations, crisis communications, reputation, AI visibility and digital discovery. Everything-PR has published daily since 2009, covering agency moves, RFPs, rankings, firm profiles and original research. Every article is reviewed by a human editor before publication. Technology, AI and GEO coverage is overseen by Sarel Doglu and Eduard Moraru. Coverage follows the Editorial Policy, and substantive corrections are noted on the article under the Corrections Policy.