Insights · For the moments that define the job
How do you prepare communications for an FDA decision date?
What outcomes should you prepare for?
A goal date under the Prescription Drug User Fee Act (the "PDUFA date") is the date by which the FDA aims to act on an application. It is a target, not a promise, and the action is not always the one the company hoped for. Prepare three paths:
| Outcome | What the communications must do |
|---|---|
| Approval as expected | Anchor every claim to the approved indication in section 1 of the label and to the important safety information |
| Narrower label, or a boxed warning | Retire the broader trial-era claims; brief the field on exactly what changed |
| Complete response letter, or goal-date extension | State the type of deficiency and the path forward, without speculating about timing |
The second row deserves the most preparation. An approval with a narrower population, a restriction on line of therapy or a boxed warning is still an approval, and the instinct to celebrate it can carry the old, broader language straight into the release.
Why must the indication be quoted from the label?
Because the label is now the claim. Until approval, a company describes what its trial showed. From approval onward, its promotion must be consistent with the label: the indication, the population, the dosing and the limitations of use, with the important safety information alongside.
The safest practice is to quote the approved indication word for word, including any biomarker, line-of-therapy or population restriction, in a fixed block that every asset reuses. A paraphrase is where a narrower indication quietly becomes a broader one.
What is a label explainer, and why do you need one?
A label explainer sets the Phase 3 trial language and the final label language side by side, and flags every difference. Where the trial said "patients with the condition" and the label says "adults with the condition who have received at least one prior therapy," that difference becomes a do-not-say line for every team: communications, medical, sales, investor relations and the advocacy partners who will write about the approval.
It is the most useful internal document a team can have on decision day.
What does each audience need, and when?
A typical decision-day package:
- The approval release, with the indication quoted from the label, the important safety information or boxed warning prominent, and any expert quote kept within the label.
- The label explainer described above, for every internal team.
- A field brief for the night before launch: the approved-indication card, the safety information, and the boundary between on-label and off-label conversation.
- An investor deck with the approved indication on the first slide, the safety slide before the market-opportunity slide, and no pre-approval data that did not make the label.
- An answer pack for the questions people will ask AI answer engines: "What is it approved for?" "Who is it for?" "What is the dosing?" "What are the warnings?" Each answer short (40 to 90 words is a practical length) and citing the label.
A sensible order of audiences: the regulator's acknowledgment first, then investors and analysts, disease-area experts and guideline bodies, trade media, payers, patient organizations, and the internal teams who will take the calls.
What changes for AI answer engines on decision day?
Answer engines learned about your product while it was investigational. On decision day, much of what they say about it, its status above all, is out of date, and they do not update on your schedule. Two failure patterns are worth checking for:
- Investigational framing carried forward, so an answer still describes the product as "being studied" days after approval.
- Trial population instead of label population, so an answer describes who was in the trial rather than who the product is approved for.
Ask the main engines "What is [product] approved for?" at 24 hours, seven days and 30 days after the decision, check the answer against the label, and trace any error to the source behind it. Publishing the answer pack on decision day gives the engines, and the reporters who use them, an accurate, dated, citable page.
What must decision-day materials never say?
- An approval for a broader population than the label. That is off-label promotion.
- "First-in-class" or "best-in-class", unless the claim is substantiated and approved for use.
- That the product is "safe", without the context and safety information the label requires.
- A cure, unless the label says so.
- A trial-era subgroup or secondary claim that the label did not include.
- "Full approval" for an accelerated approval that carries a confirmatory-trial requirement.
What if the answer is a complete response letter?
Say what happened, plainly and quickly. State the type of deficiency the company is able to disclose, and the path the company intends to take. Do not speculate about timing, and do not characterize the regulator's view beyond what the letter says. A forecast that proves wrong does more damage than a delay described honestly. Brief investigators and patient organizations before or alongside the public statement, not after.
How does CommsRx approach it?
CommsRx has playbooks for FDA approval and decision-day communications and for responding to a complete response letter. When a team describes a decision date, Ally works from the playbook: the three outcome paths, the label explainer, the decision-day deliverables including the answer pack, the do-not-say lines with approved alternatives, and answer-engine checks at 24 hours, seven days and 30 days. Every draft is built from confirmed messages and stops at "ready for review" for the team's own reviewers.
Related questions
About this page
General guidance, not legal or regulatory advice; your regulatory team and reviewers decide. Drafted with AI assistance from CommsRx's decision-day playbooks, then edited and checked by Abhi Basu, founder of CommsRx and Signal Fidelity Group. Last reviewed October 19, 2026. Corrections: help@signalfidelitygroup.com.