You have an announcement. Your finger is over send, and you are about to make the most common PR mistake there is: blasting a full press release for something that needed a one-page invitation, or sending a thin advisory for news that deserved the whole story. The two documents look similar and do opposite jobs, and editors can tell within seconds which one you confused. Get the choice wrong and your news dies in an inbox, not because it was bad, but because you packaged it for the wrong purpose.
The press release vs media advisory question is really a question about what you want the journalist to do. One asks them to publish your story. The other asks them to show up to yours. Once you see it that way, the choice stops being confusing and the template writes itself.
Most of the agonizing over PR documents is misdirected effort, spent polishing prose when the real failure was choosing the wrong format for the news. Get the format right and an average writer succeeds. Get it wrong and a brilliant one still flops, because the document is built for a job the situation never asked it to do. So slow down for one moment before you write, and decide which job you actually have.
What a press release actually is
A press release is the complete story, written and ready to run. It has a headline, a dateline, a strong lead that answers the news in the first sentence, supporting paragraphs in descending order of importance, real quotes from named people, and a boilerplate about your organization. The defining trait is self-sufficiency. A journalist should be able to take a good press release and publish a version of it with light editing, because you did the reporting for them.
That completeness is the strength and the trap. A release works when the news is the news itself: a product launch, a funding round, a partnership, a hire, a result, a study. The story can be told fully in text and the reader gets value from reading it. But that same completeness backfires for an event, because if you hand a reporter the whole story in advance, you have removed their reason to attend. Why drive across town to cover something you already have written up in your inbox.
The structure of a release is not arbitrary, either. The inverted pyramid, most important information first, descending to least important, exists so an editor can cut from the bottom without losing the core. A reporter on deadline trims your release to fit the space they have, and if you buried the news in paragraph four, the news is what gets cut. Lead with the actual development in the first sentence, support it with the next most important facts, and save the background for the end. Write it so that a reader who quits after two sentences still walks away knowing what happened.
What a media advisory actually is
A media advisory, sometimes called a media alert, is an invitation, not a story. It is short, scannable, and built around logistics: who is involved, what is happening, when, where, and a tight why-it-matters. It deliberately withholds the full story because the story has not happened yet. The advisory’s only job is to get a journalist or a camera to show up at the right place and time.
Think of the format as a flyer for the press. A reporter scans it in ten seconds and decides whether the event is worth their morning. That means the value proposition has to be obvious and the details have to be flawless: exact address, exact time, parking and access notes, a contact reachable on the day, and any visuals or speakers that make the event worth filming. An advisory that reads like a press release buries the logistics and confuses the reader about what you actually want them to do.
For broadcast and photo desks, the visual is the whole pitch. A TV producer is not deciding whether your news is interesting in the abstract. They are deciding whether there is something worth pointing a camera at. So an advisory aimed at broadcast has to promise a shot: the ribbon being cut, the demonstration, the crowd, the notable person speaking. Spell out the visual moment and the time it happens, because that is the single fact a producer needs to assign a crew. An advisory that promises talking heads in a conference room gets no camera, no matter how worthy the cause.
The five W’s do the heavy lifting, and they should be scannable at a glance, not woven into prose. Who is involved, what is happening, when, where, and why it matters, laid out so a reporter can extract every logistical detail in seconds. This is the one document where a clean, almost bulleted clarity beats good writing, because its job is to be acted on, not admired. Save your craft for the release that follows.
The single question that decides which to send
Here is the decision rule, and it is binary. Ask: is the news an event I want journalists to attend, or a story I want them to publish? If you want attendance at a specific time and place, send an advisory. If you want coverage of information that is complete right now, send a release. Everything else flows from that one answer.
Run a few examples through it. A grand opening with a ribbon cutting at 10 a.m. Thursday: advisory, because you want cameras there. A new executive joining the company: release, because the news is the appointment itself and there is nothing to attend. A research report you are publishing: release. A press conference where your CEO will make a statement: advisory before, release after. The question collapses the confusion into a clean fork, and the fork is almost always obvious once you ask it honestly.
The edge cases are where people talk themselves into the wrong document, so hold the rule firmly. A webinar feels like an event, but if there is nothing for a reporter to physically attend and the value is the information, it is closer to a release with an invitation attached. An award you won is not an event you host, so it is a release. When you feel tempted to send an advisory for something with no time and place a journalist would travel to, that is the signal you actually have a story to publish, not an event to attend, and the release is the right call.
When to send both
For significant events, the professional move is to use both in sequence. Send the media advisory two to four days ahead to drive attendance, with all the logistics a reporter needs to plan. Then, immediately after the event, send a full press release with the quotes that were actually said, the outcomes, the photos, and the complete narrative. The advisory fills the room. The release serves every reporter who could not attend and gives the attendees a clean source to quote.
This one-two pattern is how organized PR teams cover launches, conferences, and announcements with a live component. The advisory and the release are not competitors. They are two stages of the same campaign, each doing the job the other cannot.
The timing of the pair is what makes it work. The advisory goes out a few days ahead, far enough for a reporter to plan but close enough that the event stays on their radar, then a reminder the morning of. The release goes out within hours of the event ending, while it is still fresh and while the attending reporters are writing their pieces. Wait until the next day and you have missed the news cycle the event itself created. Run the two documents on that rhythm and you serve both the journalists who showed up and the far larger number who could not, turning one event into coverage across both groups.
How AI search changed the press release’s second job
A modern press release has a job it did not have a few years ago. Beyond reaching journalists, a well-structured release distributed through credible wires and picked up by news sites becomes data that AI engines read. When someone asks ChatGPT or Perplexity about your company or your category, the engine assembles its answer partly from this kind of indexed, structured coverage. A release that gets syndicated widely can shape how AI describes you, which a media advisory, being ephemeral and event-bound, never will.
This does not change the core decision. It raises the stakes on writing the release well, with clear structure, real quotes, and accurate facts, because that document now talks to machines as well as people. The advisory remains a logistics tool for humans. The release has quietly become part of your AI visibility layer too.
It also raises the value of getting the release picked up beyond your own site. A release that only lives on your newsroom page does little for AI visibility, because engines weigh your own domain as an interested party. The same release syndicated through a credible wire and republished by news sites enters the tier of sources engines trust, which is what lets it shape how you are described in an answer. So the modern release has two distribution jobs: reach the specific journalists who might write about you, and seed the broader indexed web that machines read later. The advisory, being a one-time logistics note for a single event, never does either of those things, which is one more reason to keep the two documents in their proper lanes.
Get the format right before you write a word
The reason both documents fail is almost never the writing. It is the choice. People agonize over headlines and quotes while sending the wrong format entirely, and a beautifully written press release for an event-driven story still flops because it answered the wrong question. Decide the format first using the one binary question, then write to that format’s job: a complete, publishable story for a release, a fast, flawless invitation for an advisory.
Keep a one-line rule taped to your monitor if it helps: event to attend, send an advisory; story to publish, send a release; both, send the advisory first and the release after. That sentence resolves ninety percent of the cases you will ever face, and the remaining ten percent yield to the binary question about what you want the journalist to do. The discipline is not in the writing. It is in pausing long enough to identify which of the two situations you are actually in before you open the document.
Master that and the press release vs media advisory question stops slowing you down. You will know, before your finger hits send, exactly what you are asking the journalist to do, and you will hand them the document built to make them do it.