How to Onboard Pharma Sales Reps for a Product Launch: Plan the Certification Window

To onboard pharma sales reps for a product launch, split the work at FDA approval. Before approval, reps learn everything that doesn't depend on the final label, such as the disease state, the market and your company's compliance policies. After MLR or PRC approves the launch materials, every rep certifies on the approved message before the launch meeting.

Certification has to fit between that approval and the launch meeting. Plan those days first, starting with who reviews each certification attempt and how many review hours that takes.

This guide is for commercial training leads at US pharma companies whose launch cohort mixes tenured reps moving from another brand with new hires. For a first commercial launch, where every rep is new, see how to onboard 50+ field reps for a first commercial launch.

What Can Reps Learn Before Approval?

Before approval, reps can learn what doesn't depend on product claims, within your company's compliance policies. Anything built on the product's claims waits for the final label and for MLR or PRC to approve the launch materials.

Practice on claims has to use the approved wording because a rep's presentation is promotion. FDA's Bad Ad Program page (content current as of March 6, 2025) lists "sales representative presentations" among the promotion its Office of Prescription Drug Promotion regulates. Among common promotion issues, it lists "failing to present a 'fair balance' of risk and benefit information."

Ask MLR or PRC before approval how they want to review the training scenarios, and book that review for the days right after approval.

How Do You Split the Cohort Into Tracks?

Split the cohort by what reps already know, and finish both tracks at the same certification. Tenured reps moving from another brand already know your company's policies and systems. New hires need those foundations as well as the new disease area.

Give tenured reps a test-out before approval: a knowledge check on the disease state and market context. Those who pass skip that module and use the time for selling-skills practice with no product claims in it. Those below the pass mark take the module with the new hires.

Two tracks that meet at one certification.

Hold both tracks to the same rubric and pass mark at certification.

How Long Does the Certification Window Need to Be?

Size the window by review hours as well as practice days. When a first-line manager or a trainer reviews each certification attempt, the window depends on their hours, and those reviewers have launch work of their own. Count only the certification attempts a person reviews. Work it out in three steps.

1. Attempts. Multiply the cohort by the attempts you expect per rep. If 60% of reps passed on the first attempt at your last launch and nearly everyone else on the second, plan for about 1.4 attempts per rep.

2. Review hours. Multiply the attempts by the minutes one review takes, and divide by 60.

3. Review days. Divide the review hours by the hours your reviewers can give each day.

Then add the days reps practice before their first attempt and a buffer for retakes.

In the illustrative plan below, a cohort of 200 at 1.4 attempts per rep makes 280 attempts. At 15 minutes a review, those take 70 review hours. Twenty managers reviewing for an hour a day need three and a half days, rounded up to four. With three practice days and two buffer days, the window is nine working days.

An illustrative window plan for a cohort of 200, in demo data.

If certification is live, each attempt also needs the rep and a trainer at the same time, in person or on a video call. Book those sessions when you size the window, because the trainers' open slots cap how many reps certify each day.

The launch certification window planner at the end of this guide works through this math on one page.

What Should Certification Check?

Certification should check the approved message before anything else. Write the rubric before approval and load the approved wording when it arrives. Each required statement is pass or fail.

• Required statements: the approved indication and the safety information, with fair balance. Missing one fails the attempt.

• Off-label questions: the persona asks one, and the rep refers it to Medical Information. An off-label answer fails the attempt.

• Objections: answered with the approved data, including access objections such as step therapy.

• Call flow: the approved visual aid, in order.

An illustrative rubric applied to one attempt, in demo data. The attempt scores 90 and still fails on a missed pass-or-fail check.

Calibrate the reviewers before the first certification attempt. During the practice days, have every reviewer score the same three recorded practice attempts on the approved message, then compare scores and agree on the differences. In the illustrative chart below, one of the three attempts passes or fails depending on who scores it until the reviewers calibrate.

Illustrative scores from 20 reviewers on the same three attempts, before and after calibration, in demo data.

How Do You Track Readiness Before the Launch Meeting?

Track certified reps by region and by track every day of the window, and share the view with brand and sales leaders. A region that falls behind gets more reviewer hours. A step in the call that holds back reps in several regions gets a short module and a targeted roleplay, both built from approved content.

An illustrative daily readiness view on day 8 after approval, in demo data.

What Does This Look Like for a 200-Rep Launch?

In this hypothetical example, 197 of 200 reps certify by the planned close of a nine-day window, four working days before the launch meeting. The numbers are demo data.

Imagine a specialty brand launching with 200 reps in 10 regions and 20 first-line managers, two per region. Of the reps, 140 are moving over from another brand and 60 are new hires. The new hires start foundations six weeks before the expected approval date. The tenured reps take the disease-state test-out, and 112 of them pass.

Approval comes 15 working days before the launch meeting. Counting approval as day 0, MLR signs off on the training scenarios on day 2, and the window opens on day 3 with three days of practice. The 20 managers calibrate on three recorded practice attempts during those days. From day 6, they review certification attempts for an hour a day.

By day 8, reps in two regions stall on the same step therapy objection. Trainers assign a five-minute module and a targeted roleplay built from the objection response MLR already approved, and both regions catch up by day 10. When the window closes on day 11, 197 reps are certified. The other three stay off calls on the new product until they certify in the first week after the meeting.

Illustrative certified reps by working day after approval in the 200-rep example, in demo data.

For what happens once reps reach the field, see the first 90 days after launch.

Where Does SmartWinnr Fit?

SmartWinnr runs both tracks and the certification practice in one platform. The middle column below quotes SmartWinnr's product pages, and the last column lists what to confirm in a demo.

[VISUAL: annotated SmartWinnr screenshot of a certification attempt from the demo environment · shows a missed required statement and the reviewer's view · Product to supply and approve]

On how long the platform itself takes to roll out, the AI Roleplay page says "Most organizations launch with four to five scenarios in a few weeks, then expand by market, product, or role." If you adopt it for a product launch, build the certification scenarios first and add the rest once reps are in the field. For SmartWinnr's pharma setup, see pharma sales training with SmartWinnr.

Plan Your Launch Window

Download the launch certification window planner (PDF). [LINK: the PDF or its HubSpot form, added in the Framer build] It holds the launch dates, the two tracks, the review-hours math, the rubric checks and a daily readiness tracker on one page. To see a launch path and certification set up in SmartWinnr, request a demo.