A pharma product launch checklist for content teams comes down to one test: every asset a rep, a website or a patient will see on day one is finished, approved against the final label, and ready to file with FDA on Form 2253 when it is first used. For most brands that set includes a core visual aid, an HCP website, approved email, a speaker deck, patient materials, DTC pieces if the brand runs them, and the safety information in every format those assets need. The list itself is not the hard part. The hard part is that most of it is built before the label is final.
This checklist works back from the PDUFA date. It covers the core content set, the timeline, OPDP advisory comments on launch materials, MLR capacity, the risk of a label that changes late, day-one 2253 submissions and the content work in the first months after launch. Rep readiness is a separate problem, covered in a green certification dashboard does not mean a ready field force. This is a practical guide, not legal or regulatory advice: confirm each step with your own regulatory team.
What content must be ready on approval day?
The core visual aid: the comprehensive piece reps use with HCPs. It holds the claims, the data presentations and the safety story that every other asset borrows from, so it is the first asset to start and the first to lock.
The HCP website and approved email: the website usually follows the visual aid's claims and structure, and the first email templates should match the first conversations reps will have after launch.
The speaker deck and patient materials: a deck for the HCP speakers who will present the data, and patient pieces such as an onboarding brochure and any support program content. DTC assets come on top, if the brand runs consumer promotion at launch: a consumer website, print or digital ads, and broadcast if planned.
Safety information in every format: the full prescribing information, any Medication Guide or patient labeling, and the Important Safety Information sized for print, web, email, video and short-form digital. Treat this as its own workstream. The ISI appears in every asset, in several lengths and layouts, and it is the text most likely to change when the final label lands. If each asset carries its own hand-typed copy, a late change has to be found and fixed many times.
Plan everything else as a derivative. A banner, a booth panel or a leave-behind should reuse claims already approved in the visual aid, not introduce new ones. Every new claim added late in the plan is a new review, and launch is the worst time to add review load.
How far before the PDUFA date should launch content start?
The PDUFA date is FDA's goal date for acting on an application. Under PDUFA VII, FDA's goal for a new molecular entity NDA or an original BLA is to act within 10 months of the 60-day filing date under standard review, or 6 months under priority review. A major amendment submitted late in the review can extend the goal date by three months, and FDA can also act before the goal date or issue a complete response letter. The date a launch plan works back from is a target, not a certainty.
Twelve months or more out: agree the claims strategy against the expected label, build the claims library with references, and brief the agency on which claims each asset will carry.
Six to nine months out: draft the core visual aid and the ISI master, run early medical review of the data presentations, take the core set through MLR on the draft label, and build the derived assets from the approved claims.
Three to four months out: if the brand wants OPDP advisory comments, consolidate the core launch materials and submit them, one submission per audience.
The final weeks to first use: absorb the final label, rework what it changes, run final MLR review on the finished pieces, lock the versions and prepare the Form 2253 submissions for the day each piece goes live.
The exact months depend on the brand, the review designation and how much content is new. What does not change is the order. Claims come first, the core visual aid second, derivatives third, and the label-change week gets its own reserved time.
Should you submit launch materials to OPDP for advisory comments?
For most products, asking FDA's Office of Prescription Drug Promotion (OPDP) for advisory comments on launch materials is voluntary, and FDA's submission guidance says such requests are encouraged. FDA defines the launch phase as the first 120 days that the product, or a new indication, formulation or similar change, is marketed to the public. OPDP's stated goal is to comment on draft core launch materials within 45 days of submission, though its own metrics page notes that complex submissions have taken longer.
The guidance spells out what counts as core: one comprehensive professional piece such as a visual aid or detail aid of 12 pages or fewer, one professional ad of 4 pages or fewer, one comprehensive DTC piece such as a patient brochure, one DTC ad, and a professional or DTC website when it derives from a comprehensive piece also submitted. Slide kits and longer pieces are non-core and a lower priority, and FDA recommends applying its comments on the core set to them. A submission includes a clean copy, an annotated copy that ties each claim to its support, and the annotated prescribing information.
Two practical rules follow. First, FDA will generally not review materials under the advisory process once those or substantially similar claims are already in use, so the submission has to come before anything goes public. Second, accelerated approval products are different: under 21 CFR 314.550 and 601.45, unless FDA says otherwise, the sponsor must submit materials intended for the first 120 days during the preapproval review, and submit later materials at least 30 days before first use.
How do you plan MLR capacity for a launch?
Launch puts the full core set, its derivatives and the agency's first drafts in front of the same small group of reviewers at the same time, and then asks them to review much of it again when the final label arrives. Capacity problems at launch are rarely about reviewer speed. They come from volume arriving all at once and from avoidable rounds.
Sequence the queue by derivation. Review the core visual aid first and lock its claims, then build every derived asset from those approved claims. A reviewer checking how a known claim is used in a banner moves much faster than one judging a new claim. This is the case for a maintained claims library, covered in how to build a claims library your MLR team trusts.
Then book the time in advance. Agree a named launch review team, reserve review slots for the weeks around the expected action date, and agree in writing which changes can take a lighter review: a reused approved claim in a new size, for example, against a new claim or a new data presentation. Give agencies the same checklist the reviewers use, so first drafts arrive with references attached and safety information in place.
What happens when the final label differs from the expected label?
Final labeling is often agreed only in the last weeks of review, so content built months earlier rests on what the team expects the label to say. When the final text differs, the changes ripple. A narrower indication, a population limit, a new warning or contraindication, a dosing change or different wording for an endpoint can each touch the claims, the data charts and the safety information in every asset.
Content that stays on label at launch is content that was built to change. Keep a record of which label section each claim depends on, so a change in one section tells you exactly which assets it touches. Hold the ISI as one master text with its derived lengths, not as separate copies. Plan the likely label scenarios in advance and decide, before the label lands, what each would mean for the headline claims.
Hold anything expensive or slow to change until the label is final: printed pieces, broadcast production and large website builds. The goal is that the label-change week is spent making known edits to a known list of assets, not discovering which assets are affected.
What has to happen on launch day and in the first 120 days?
On the day of first use, the FDA filing obligation starts. Under 21 CFR 314.81(b)(3)(i), and 21 CFR 601.12(f)(4) for biologics, the company submits specimens of its promotional labeling at the time of initial dissemination and its advertisements at the time of initial publication, each with Form FDA 2253 and the current prescribing information. FDA's guidance requires these 2253 submissions in electronic format. Have the final versions, the form and the label ready to file as each piece goes live, and make sure the version filed is the version in use.
Launch content does not stop there. The first months bring field questions the visual aid did not answer, specialty-specific email the first wave did not cover, speaker program updates, conference materials and, as coverage decisions land, access messaging. Each new piece is another MLR review and another 2253 submission.
This is where the claims library pays for itself. Pull-through content built from claims already approved at launch moves through review as a reuse, not as a fresh evaluation, and the brand keeps one consistent story while the content volume grows.
Where SwishX fits
Magic Studio produces the launch set from one Brand Dossier and claims library: Video, Docs for visual aids and brochures, Approved Email, Ads and Web. Every claim is cited to its source and checked against the label for its market, and fair balance and safety information are placed in the asset as it is made. Anyone can ask an asset where a line came from, which matters most in the week the final label lands.
Finished work goes into your MLR queue and on into Veeva PromoMats with every claim and its reference attached, so reviewers see what is new rather than re-checking what is already approved. Field readiness for the same launch is the job of Magic Academy; the launch content itself starts in Magic Studio.
Frequently asked questions
What is a PDUFA date?
It is FDA's goal date for acting on a drug or biologic application under the Prescription Drug User Fee Act. For a new molecular entity under standard review, the goal is 10 months from the 60-day filing date, or 6 months under priority review, and a major amendment can extend it by three months.
Is OPDP review of launch materials mandatory?
For most products, no. Requesting OPDP advisory comments on launch materials is voluntary, though FDA encourages it. Products under accelerated approval are the exception: their launch materials must be submitted during the preapproval review unless FDA says otherwise.
What does FDA mean by the launch period?
FDA's promotional submissions guidance defines the launch phase as the first 120 days that a product, or a new indication, formulation, dosage form or similar change, is marketed to the public. Materials intended for use after that are non-launch materials.
When must Form FDA 2253 be submitted?
At the time of initial dissemination of promotional labeling and at the time of initial publication of an advertisement, with the product's current prescribing information attached. For launch, that means the day each piece is first used, not afterward.
Can a company create promotional materials before FDA approval?
Teams can develop and review materials internally before approval, and many must in order to launch on time. What they cannot do is promote the product as safe or effective before approval, so nothing is disseminated until the product is approved and the materials match the final label.