girl, ipad, tablet, education, woman, email, internet, computer, fashion, ipad, ipad, ipad, ipad, ipad, tablet, tablet
Photo by dumcarreon on Pixabay

Pitching

PR outreach operations

Set up a shared PR outreach workflow for pitch approval, send records, duplicate checks, replies and requests to stop contact.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Newsroom Desk.

undefined

PR outreach operations are the checks between approving a story and closing the last journalist conversation. Give each pitch a named owner, keep a shared record of what was sent, check for earlier contact before every send, and act on replies and stop requests before another message goes out.

Build one working record

Use a shared outreach record that everyone sending pitches can update. For each proposed contact, record the story and pitch version, intended recipient, reason for approaching them, channel, owner and planned send time.

Record actual sends and replies as separate events, so a scheduled pitch is not treated as sent. Isentia Connect is a media database and PR distribution platform that lets users add their own contacts to its database (Isentia).

The record should answer three questions quickly: who has been approached about this story, what was sent, and what can happen next? Track the conversation separately from any contact restriction, so closing a story does not erase a request for no further pitches.

At approval, confirm the pitch version and contact relevance. Before queueing, check earlier sends and restrictions; at send, record whether the message left the system and which address received it. Route replies by their request or outcome, then close only after open requests are handed over and further sends are stopped where appropriate.

A sent record does not establish delivery, readership or consent.

Put a legal and editorial decision gate before sending

Check the person and angle, not just the address. Colleagues may hold different addresses for the same journalist, and an agency and in-house team may each have the same contact on their lists. A shared queue lets the owner resolve those conflicts before sending.

If a pitch is a commercial electronic message, check the Spam Act 2003: it prohibits unsolicited commercial electronic messages and requires accurate sender information and a functional unsubscribe facility. Schedule 2 addresses consent, including when it may be inferred from publication of an electronic address and when withdrawal takes effect. Section 42 is headed Additional ACMA functions (legislation.gov.au).

Honour a clear request to stop receiving pitches regardless of the message’s classification.

Treat replies as instructions

Route replies to someone who can act on them. A request for information needs an owner. A correction to a journalist’s name or beat should update the contact record. A decline closes the current angle; it does not necessarily rule out an unrelated future approach.

A clear stop request calls for an immediate pause and a restriction visible across the sending tools and teams involved.

Leave silence as unanswered. Do not mark a contact interested or consented because a message was sent, opened or left unanswered. Set a follow-up date only where there is a specific editorial reason; log that reason and recheck duplicates and restrictions before each new send.

Record the source and basis for any consent relied on, and retain the supporting evidence. If relying on publication of an electronic address, record that basis separately; Schedule 2 of the Spam Act addresses when consent may be inferred from publication and when withdrawal takes effect (legislation.gov.au).

If personal information is used for direct marketing, check APP 7. OAIC guidance says both exceptions require a simple means to opt out, and APP 7 does not apply to the extent the Spam Act or other legislation prescribed by regulations applies (oaic.gov.au).

Keep the operation proportionate

Record only information needed to prevent repeat mistakes and fulfil legitimate requests. Limit access, correct stale details and review records that may no longer be needed.

At campaign close, reconcile the queue with sent messages and unresolved replies. Report only what the record establishes: messages sent, responses received, requests fulfilled and restrictions applied. Review coverage separately.

Make privacy controls usable at handover

For an organisation covered by the Australian Privacy Principles, identify the Privacy Act in handover guidance and assign an owner for privacy inquiries. APP 1 requires reasonable steps to put practices, procedures and systems in place to support compliance and handle inquiries or complaints about that compliance (oaic.gov.au).

Keep the outreach record focused on contact information needed for the pitch. Capture its source, the reason the person is relevant, the record owner, any consent evidence and any stop request; keep the evidence with the record so another sender can act on it.

If a pitch uses personal information for direct marketing, check APP 7. OAIC guidance says both exceptions require a simple means to request not to receive direct marketing, and APP 7 does not apply to the extent the Spam Act or other legislation prescribed by regulations applies (oaic.gov.au).

At handover, route privacy inquiries and complaints to an identified team member, record who owns the response, and keep open requests visible after the campaign closes. APP 1 covers systems that enable an entity to deal with inquiries or complaints about compliance (oaic.gov.au).

Key Compliance Requirements for PR Outreach

Australian Privacy Principle (APP) 1
Requires reasonable steps to support compliance and handle inquiries
Spam Act 2003 – Section 42
Outlines additional ACMA functions including enforcement and guidance
APP 7 – Direct Marketing
Requires opt-out mechanisms; does not apply where Spam Act overrides
ACMA – Avoiding Spam
Guidance on sending commercial electronic messages without consent
OAIC Guidance on Consent
Explains when consent may be inferred from public publication of an email

In this guide

  1. Recording who received each pitchKeep a precise PR pitch record of addresses used, pitch versions, send times, replies and failed sends.
  2. Avoiding duplicate outreach to the same journalistPrevent duplicate pitches with checks for known addresses, story angles, reservations and live conversations.
  3. Respecting a request not to receive further pitchesAct on a journalist's request to stop pitches by pausing sends, recording its scope and updating relevant outreach lists.
  4. Tracking replies without treating silence as consentClassify journalist replies, keep unanswered pitches accurate and assess each follow-up as a new decision.

More from Pitching