Open almost any launch plan and you'll find regulatory milestones mapped to the day, supply scenarios in three versions, a media plan by channel and week. Then, somewhere near the bottom, field readiness gets a single line: "kickoff meeting".
That line carries more weight than it looks. The field force is where the strategy either becomes behaviour in front of physicians or quietly doesn't. Our view, from the programs we have run with field forces, is that readiness should be run like any other launch workstream: diagnosed early, measured person by person, fixed, and monitored through the first months, not treated as an event that happens on one day in a hotel ballroom. What follows is a practical timeline, from eight weeks before launch to month six, that fits around the plan you already have.
If you have seen our Launch Excellence program, this is its busiest stretch. That program covers a thirty-month window: awareness and story-building well before the date, readiness certified at launch, and recharges through year two for new data, new markets and new hires. The playbook below zooms into the period from eight weeks before launch to six months after launch, where most of the readiness work is concentrated.
Why the early weeks deserve a workstream
We will keep the case short. McKinsey's analysis of 210 launches between 2003 and 2009, published in 2014, found that about two thirds missed pre-launch consensus expectations in year one, and that most of those were still behind in year two. PharmExec's work on launch drift (July 2026) lists field execution variability and HCP belief barriers among the root causes, and offers a timing rule we find practical: monitor from week one, expect early trends at weeks four to six, and look for confirmation around month three. Field readiness is one factor among many in all of that, but it is one a launch team can measure and act on inside those weeks. That rhythm is the backbone of the playbook below.
Eight to six weeks before launch: diagnose the baseline
Start before the product content is even final. Run a short diagnostic battle on the disease area, current guidelines and the treatment pathway. Five-question, one-minute challenges against colleagues, played in a synchronised window over a few days.
This does two jobs. First, it tells you where the baseline is. A team moving from primary care into a specialist area will have very different gaps from a team that has sold in the indication for a decade. Second, it tells the kickoff team which topics need stage time and which the field already masters. There's nothing more wasteful than an hour of kickoff agenda on content most of the room already knows, while the misunderstood topic gets a single slide.
It also sets up a sequence we've seen work well. In a respiratory launch in Japan in our case library, 257 players went through two waves, disease first and then product, over 32 days. They produced 80,000 answers and 4,503 gaps, and 80% of those gaps were closed. Readiness rose from 75 to 95%. We think securing the disease foundation first gave the product story somewhere to land, though one program cannot prove the sequence caused the result.
Four to two weeks before: build and certify the content
Once the launch materials clear MLR, generate the questions and micro-content from those approved documents, and only those. The core visual aid, the trial summary, the objection handlers, the safety information, the access story.
AI can draft this quickly. The discipline is in what happens next. Medical and regulatory reviewers sign off every item, and any conflict between documents (an older slide against a newer summary, a local adaptation with a different number) is flagged for a human to resolve rather than decided by the tool.
This is also the moment to flag the critical questions: the ones that carry claims, safety messages and key differentiators. They deserve a stricter standard later on. In our programs, a critical gap only counts as closed at 5 of 5 later check questions on the same concept.
A small tip from experience: involve two or three experienced reps in reviewing the distractors. They know which wrong answers colleagues actually give in calls, and those are the ones worth testing.
Launch week: the kickoff battle
At kickoff, play the product content in a synchronised window across every country. Everyone on the same questions in the same days, so the snapshot is fair and comparable.
The goal is not entertainment, although people do enjoy it. The goal is a complete reading of who knows what, taken in the same week the message is delivered. Participation can be very high when the format is short and competitive: in a global immunology kickoff in our library, 1,330 players across four franchise games produced about 301,000 answers in six days. That kickoff was an expected part of the week, so treat the figure as what a well-run window can reach, not as proof of voluntary appetite.
Timing here is not a detail. Across the programs we run, those tied to a business moment such as a launch, kickoff, certification, congress or cycle meeting tend to close more of their knowledge gaps than always-on ones. That is an observed association rather than proof, but it matches our experience that learning attached to a real moment gets more effort than learning scheduled for convenience.
The kickoff is not the finish line for readiness. It's the first full measurement.
Weeks one to six: fix each person's gaps and verify
This is the phase most launch plans skip, and it's where most of the value sits.
Murre and Dros's 2015 replication of Ebbinghaus, a relearning experiment with nonsense syllables, shows that unrehearsed material fades fast and that spacing helps. It does not tell you how much of a product story survives to the first cycle meeting, but it is a good reason not to leave the kickoff unrehearsed.
So, in the six weeks after launch:
- Each person receives the fix for their own gaps, not a generic recap. That's what Gap Fixing is for.
- Short reinforcement waves check whether the fixes held. A gap only closes when the same person answers the same question correctly later.
- Readiness indexes by team, country and topic go to sales and medical leads, so they see where knowledge is holding.
- Managers get the short list of misconceptions that repetition isn't fixing, and the names of the reps who hold them.
That last point matters more than it sounds. On a share of the example questions we track, very few of the people who were wrong ever corrected it; some of those were never retested, so not all are proven misconceptions. In a global immunology kickoff, a mechanism misconception held by 125 reps barely moved with more rounds. Errors like that behave like beliefs, not missing facts. They need a conversation, often on a ride-along, and a manager who knows exactly which three people to have it with.
Weeks four to twelve: put readiness next to the commercial numbers
This is where PharmExec's timing rule earns its place. Early trends in uptake emerge around weeks four to six. The question every launch team asks at that point is "why is country X behind?"
Too often the answer offered is market-level: access delays, a competitor's pricing, a formulary decision. Often that's right. Sometimes knowledge is part of the story too. Putting readiness by country, team and topic in the same review as the commercial indicators is how you find out whether it is worth investigating.
A scenario we see often: two neighbouring countries with similar access conditions diverge in early uptake. The readiness data shows one of them still has a wide gap on the key differentiator versus the current standard of care. That does not prove knowledge explains the difference in uptake; it tells you where to look next, with ride-alongs, CRM call notes and the local team. If it is part of the cause, it is fixable inside the window where it still matters.
A fair objection is that commercial teams already have plenty of dashboards, and one more won't change anything. We'd agree, if it's another dashboard. The point is not a new report but a single row added to the existing launch review: readiness on critical topics, by country, next to the uptake line. If the two move together, you have a lead worth checking, not a proof. If they don't, you've probably ruled something out.
Month three to six: switch to always on
By month three, PharmExec suggests, early trends are usually confirmed. From here the job changes from launch readiness to staying ready.
New questions arrive from the field every week: a payer raises a comparison, a KOL asks about a subgroup, a nurse asks about administration. An assistant that answers from approved content only (Atrivity Assistant does this) gives reps a fast, compliant answer, and every question asked is a signal. When the same question keeps coming up, it goes into the next wave.
New evidence needs the same treatment. When a congress brings new data, turn it into a short challenge within days rather than waiting for the next POA. In an APAC MedTech vascular program in our library, seven congress challenges ran over 26 months in three-day windows; pooled across them, every content area closed between 46 and 52% of its gaps. The same program found that 110 of 345 players could not state the three factors behind device choice in complex anatomy, exactly the kind of finding that should shape the next field coaching plan.
And keep checking the critical topics. A claim that was secure in week six can erode by month five if nobody asks about it.
Take one question to your next launch meeting
You don't need to redesign the launch plan to do any of this. Most of it slots around milestones that already exist: MLR approval, the kickoff, the first cycle meeting, the monthly launch review.
The question to bring to the next launch meeting is simple: at week six, what will we know, person by person and country by country, about whether the field can deliver the critical messages? If the honest answer is "we'll know who attended the kickoff", the playbook above is a place to start.
It's the timeline we run with customers at Atrivity, from diagnostic battle to always-on assistant. The first year matters, and the field is one part of it you can measure, fix and support in exactly that window.