Build a PBM Meeting Agenda for Scientific Questions

A PBM contact asks for one meeting, but underneath that single request are two different conversations. One is administrative, about turnaround times, prior authorization queues, and how offices move through the process. The other is scientific, about efficacy data, comparative evidence, and how a product performs against alternatives. A market access manager who treats this as one meeting with one agenda usually gets a call that runs long, leaves technical questions half answered, and puts a commercial colleague in the position of answering something outside their role. Sorting the questions before the meeting, not during it, is what keeps the conversation useful and keeps every answer accurate.

Why this conversation goes wrong

The failure starts with the invitation. A PBM director sends a short note asking for data and process information in the same breath, and the manager who receives it books a generic call with whoever is available. Nobody separates the scientific questions from the operational ones, so the wrong people end up in the room for half the discussion. A commercial or access team member gets asked a question about trial design or adverse event rates and either guesses, defers awkwardly, or worse, answers with confidence they do not actually have. None of those outcomes serve the PBM or the manufacturer. The scientific side of pharmaceutical communication runs through medical affairs and approved channels for a reason, and blurring that line during a live call creates real compliance exposure, not just an awkward moment.

There is a second failure hiding in the same meeting. Once the group is mixed, it becomes easy to slip into language that ties a data answer to a coverage outcome, even unintentionally. A rep trying to be helpful might say something like the data should support broader access, and that single sentence can read as a commitment the company never intended to make. The fix is not a smarter answer in the moment. The fix is a meeting structure that never puts an unqualified person in front of a scientific question in the first place.

How to prepare

Before you accept the meeting, go back to the PBM contact and ask them to sort their own questions into categories. Ask directly whether each item concerns evidence and data, day to day operations, or process and timing. Most contacts will do this without pushback because it also helps them get better answers faster.

Once you have the list, identify who owns each item. Confirm which people on the PBM side actually make coverage or formulary decisions, since that changes who needs to be in the room and how much detail the conversation should carry. Ask whether any questions need to be submitted in writing beforehand, particularly the scientific ones, so the medical team can prepare approved materials rather than answering cold. Coordinate with medical affairs early, not the day before the call, since securing a clinical reviewer often takes lead time.

Build the agenda around ownership, not chronology. For each question, write down who answers it, what material they need to bring, and what decision or follow up is still open. A short agenda built this way, even just four or five lines, does more to protect the meeting than a long one that mixes everything together. If you want a model for how to frame a related but different situation, the post on how to Communicate Carefully About a Pending Coverage Change shows the same discipline applied to a topic where the stakes of an imprecise sentence are even higher.

What to say

Here is how that separation actually sounds in practice. The PBM director opens with a mixed request. He says, "We need more detail on the clinical data, and we also want to understand how quickly your field offices can move through the review process." That single sentence contains both conversations, and the manager's job is to split it without sounding like she is pushing back on the request itself.

She responds, "Both of those matter, and they deserve separate attention rather than being rushed through the same call. I will put together an agenda that routes the data questions to our medical affairs contact and the process questions to the right person on our access team. Could you send the specific data questions in writing ahead of time so the medical team can prepare accurate, approved material instead of answering on the spot?"

The director agrees and says he will have his clinical reviewer send over three questions about the trial population and comparative safety data by the end of the week. The manager confirms the operational questions can be handled live during the same call, since those do not require the same preparation, and closes with, "I will send a short agenda by tomorrow so everyone knows which section they own before we get on the call." That last line matters. It tells the PBM contact exactly what to expect and gives the manager a paper trail confirming that scientific and operational content were never mixed.

Mistakes to avoid

Do not send a generic invite and hope the right people self select once the call starts. That approach almost guarantees someone answers a question they should not.

Do not let a commercial or access team member answer a scientific question, even a simple sounding one, just to keep the meeting moving. A polite deferral to the medical resource costs you nothing and protects the answer's accuracy.

Do not phrase a data answer in a way that implies it will change a coverage decision. Stick to describing the evidence and let the PBM's own review process draw its own conclusions.

Do not skip the written question request for the scientific portion. A live, unprepared answer to a technical question is far more likely to introduce error than one drafted against approved materials.

Do not assume the categories are obvious from the contact's first message. PBM directors often write a single paragraph covering everything on their mind, and it is your job, not theirs, to sort it before the meeting happens.

How to practice and score it

This is a skill you can rehearse before it happens with a real PBM contact. Take a mixed list of questions, three or four items covering data, timing, and process, and practice turning it into a short agenda within a few minutes. Score yourself on three things. Did every question get a named owner. Did every line specify what material that owner needs to bring. Did the agenda avoid any language that promises an outcome rather than describing a process.

A manager reviewing this skill on your team can run the same exercise cold, handing you a messy paragraph of questions and timing how long it takes you to produce a clean, ownership based agenda. The real test comes in the live exchange that follows, where the pressure to just answer a question yourself, rather than redirect it, is much higher than it is on paper. DealSpeak's Pharmaceuticals practice conversations let you run this exact scenario against an AI counterpart playing the PBM director, with scoring on whether you kept scientific and operational content separated and whether your language stayed inside your role. If you want to practice a related judgment call, the post on how to Clarify an Uncertain Policy Effective Date covers a similar moment where precision in wording carries real weight.

A well built agenda does not just save time on the call. It protects the accuracy of every answer given and keeps each team member inside the role they are actually qualified to fill. Get the sorting right before the meeting, and the meeting itself takes care of most of the rest.