How to Verify a Journalist’s Interview Request Before You Reply

Check the request before sharing access
Verify the person and the assignment through an independent contact route before sharing a private diary, files or meeting access. A familiar outlet name does not prove who sent a message. A real journalist’s identity also does not settle what your team may disclose.
For a press team, the aim is a clear decision: proceed, hold for a check, or refer the message for review. This article suggests a practical PR workflow, rather than an official newsroom protocol. Use it alongside your own rules for media requests, data and incident response.
Consider a request for a chief executive’s interview next week. The sender gives a name, outlet and deadline, then asks for the executive’s full diary and a board paper. You can check the interview without sharing either item. The right next step is to confirm the request, then agree a suitable time and scope.
Keep the check proportionate to what is being asked. A request for a public press release needs less handling than access to an unreleased financial file. Neither requires you to treat the sender as an adversary. The team should be able to explain its process in one calm sentence.
Establish who is asking and what they need
Confirm the sender’s identity, the outlet or proposed outlet, and the specific assignment before arranging private access. These are separate facts. Finding a real person’s published work proves that the person exists; it does not prove that this email came from them.
Start with the request itself, without opening an unexpected file or sign-in page. Identify the topic, interview format, intended speaker and deadline, including the time zone. Ask only for gaps that affect your decision. Avoid turning a simple interview enquiry into a long form.
- Who is making the request, and what name do they publish under?
- Which outlet has commissioned the piece, or where will it be pitched?
- What subject, format and broad questions does the interview cover?
- What response is needed now, and by what local time?
- Does the request need public comment, an interview or access to private material?
A freelance reporter may use a personal email address and pitch a story before a commission exists. That is a reason to clarify the arrangement, not a finding of fraud. You might confirm the person through a known professional contact and keep any initial discussion within public facts.
Working across markets adds context to this step. Newsroom habits, job titles and lead times vary, as our guide to international PR from Türkiye explains. Check unfamiliar details rather than judging them by your home market alone.
Use a contact route outside the message
Confirm the request through a contact route you already trust or find independently of the incoming message. Open the outlet’s known website yourself, or use a verified contact already held by your team. Do not use a number or link in the message as your only proof.
The UK government’s guidance on spotting phishing emails advises contacting an organisation through details you know are correct. Phishing means a deceptive message designed to draw out information, money or an unsafe action. Familiar branding and pressure to act can appear in these messages. Neither is a reliable basis for trusting a request.
A short call to a known desk can settle whether a named reporter is pursuing the stated story. Ask about this specific request, not merely whether the person works there. Share only the details needed to match it. A genuine staff listing alone cannot rule out someone using that journalist’s name.
For a freelancer, the route may be their established professional contact or a commissioning editor reached through the outlet. If there is no commission yet, record that fact plainly. Decide whether a public background discussion still makes sense. Do not present a proposed placement as a confirmed interview for publication.
An email domain is a useful clue, but it is not the whole check. Look closely at spelling and the reply address. Do not ask for a passport, identity card or private home address to solve a routine press enquiry. That would create another sensitive record without proving the assignment.
Separate a verified identity from permission to share
A verified journalist should receive only material approved for that request and audience. Identity checks answer who is asking. Disclosure checks answer what your team can share. Completing the first does not remove the second.
Offer a small set of interview slots instead of the executive’s full calendar. Use an approved public biography instead of an internal staff profile. If a reporter asks for data behind a claim, have its owner review the exact file. A useful answer may be an approved extract or a public source.
- Public material: send a relevant, current source once the request is suitable.
- Approved interview access: agree the speaker, time, format and discussion scope.
- Private material: obtain approval from its owner before sending the specific content.
- Unclear status: hold the material and ask the responsible colleague to decide.
The FTC’s business guide to protecting personal information recommends keeping only information a business needs and limiting access. Apply that principle to your own checking process too. Retain enough to explain the decision, without building a dossier on the reporter.
A clear public press page can reduce needless file exchange. Our guide to connecting international PR with searchable content explores the relationship between public information and media work. For this workflow, the practical benefit is simple: a checked public link gives both sides the same reference.
Keep the reply warm when time is short
For an ordinary request with no sign of fraud, acknowledge the deadline while completing the check before promising private access. Say what you can do now and when you expect to respond. Avoid promising an interview before the speaker or their team has agreed.
A suitable holding reply is: “Thanks for getting in touch. We’re checking the brief and our speaker’s availability. I’ll come back to you by 3 pm London time.” Give a time you can meet, and send an update if the check remains open.
You can also explain a callback without sounding accusatory: “We confirm new interview requests through the newsroom before sharing meeting details.” Keep the wording about your routine, rather than the person’s character. If a known colleague can make the introduction, that may be the fastest route.
Do not use that holding reply when you suspect the message is malicious. Stop contact through the suspect channel and refer it through your workplace process. A deadline is neither proof of fraud nor a reason to skip a check. You can miss a deadline without sending a private file to an unconfirmed recipient.
Consistent handling helps protect the quality of media relationships. The same discipline supports the coherent brand presence discussed in our guide to global brand communications. Give the next person handling the request a clear status, so the journalist does not receive conflicting replies.
Record the decision and act on a mistaken click
Keep a short decision record, and tell your IT or security contact promptly if you opened a suspicious link or file. These are different tasks. The record supports a clear handover; the incident report lets the right team assess any exposure.
For a routine request, record the sender, claimed outlet, brief, checking route, date and responsible colleague. Add the result and the scope approved for sharing. Use “unconfirmed” when evidence is incomplete. That label describes the request’s status without accusing the person.
Reuse a trusted contact where appropriate, but check new details that change the risk. A sudden request for credentials, a different file destination or a new recipient deserves another look. A previous successful interview does not approve every later request. Close old records under your team’s retention rules.
The FTC’s advice on recognising and avoiding phishing warns that links and attachments can install harmful software. For a work device, follow your organisation’s response process and describe what happened accurately. State whether you clicked, downloaded, opened a file, entered details or approved a sign-in.
Stop interacting with the suspicious page while getting help. Use a known internal route, not a “support” contact supplied by the sender. Preserve the original message as your team requests, and avoid forwarding a risky attachment to more colleagues. Let the responsible team decide the next technical steps.
Frequently Asked Questions
These answers cover common decisions when checking a new interview request.
Is a personal email address a reason to reject a journalist?
No. Freelancers may use personal addresses. Confirm the person and the proposed assignment through a separate, trusted route, then decide what access is appropriate.
Does an article under the sender’s name prove the email is real?
No. Published work can help establish someone’s professional background. It does not connect that real person to the message in your inbox.
Can we agree an interview before a publication has commissioned it?
You can consider it once the person is checked and the arrangement is clear. Record that publication is proposed, and have the speaker’s team approve the discussion.
What if the request cannot be confirmed before the deadline?
Hold private access and material. For a routine enquiry, explain the delay and offer a checked public source where useful. Refer suspected fraud through your internal process.
