Route a Request for Real-World Evidence to a Balanced Review

A payer analyst who asks for real world evidence is not asking you to win an argument. The analyst wants to understand the study well enough to defend a coverage decision to a committee. If you answer with a claim of superiority, you put both of you at risk. If you dodge the request, you slow the review and lose credibility. The better path is to route the request toward a balanced review of the evidence, with its population, comparator, and limitations laid out plainly.

Why This Conversation Goes Wrong

Many market access managers treat a request for real world evidence as a chance to reinforce the product story. That instinct is understandable. You have spent months preparing outcomes data, and now an analyst is asking for it directly. But an analyst who asks whether a study proves better outcomes is testing whether you understand the difference between an observational finding and a controlled result. Answer yes, and you have made a claim your data cannot support, so the analyst now has to decide whether to trust anything else you send. Answer with vague reassurance, and the analyst reads that as evasion and escalates to a slower, more skeptical review.

The bigger risk is not silence, it is overclaiming. A single retrospective study, a claims database analysis, or a registry report can show an association. None of them, on their own, prove that one product produces better outcomes than another. The analyst already knows this. Your job in the conversation is to show that you know it too, and that you can help the committee use the evidence for what it actually shows.

How to Prepare

Before you reply to a request like this, get clear on three things about the evidence you plan to route.

First, know the study design cold. Is it a retrospective cohort, a claims analysis, a registry study, or a pragmatic trial. Know the population it drew from, the comparator group, and the size of the effect, along with the confidence interval or the p value if the analyst is likely to ask.

Second, know the gap between what the study shows and what the analyst needs to decide. A committee weighing formulary placement usually needs a defined population, a comparator already on the payer's formulary, and endpoints that map to cost or utilization. Real world evidence built for a different population or a different comparator will not answer the analyst's question, no matter how strong the finding looks on its own.

Third, decide in advance who else should be in the loop. If the analyst wants a data package or wants to talk directly with a medical science liaison, know how to route that request into your organization's medical affairs process quickly. A market access manager who tries to reinterpret clinical methodology alone, without medical input, often ends up out of scope and sometimes out of line with the separation between commercial and clinical communication that most companies require.

If you want more practice on situations where a payer contact tests your precision rather than your enthusiasm, look at the Pharmaceuticals practice conversations hub. It includes drills on how to Discuss a Payer Review Timeline With Useful Precisiona skill that comes up in the same kind of committee review process.

What to Say

Keep your language specific to the study and specific to what the committee still needs to decide. Do not answer a question about proof with a claim about proof.

The analyst opens with a direct question. "Does this real world data prove your product produces better outcomes than the standard treatment?"

You answer without inflating the finding. "One observational study does not prove that conclusion for a broad population. What I can do is arrange a balanced review of the published evidence, including the population it covered, the comparator, and the methods your committee would need to weigh it. Which comparator and which endpoint matter most to your review?"

The analyst narrows the request. "We need methodology detail before we can interpret the results ourselves. Send us the population definition, the comparator arm, and how the outcome was measured, along with anything published on the limitations."

You confirm the scope and the next step. "I will put together the published sources with the study design and limitations included, and I will flag where a medical colleague should join the discussion if your team has questions about the methodology itself. Would a short call with medical affairs help once you have reviewed the package, or do you want to work through the written material first?"

Notice what this exchange does. You never claim the evidence proves superiority. You ask which comparator and endpoint the committee cares about, which gives you a concrete deliverable instead of a vague promise. You name the limitations up front rather than waiting for the analyst to find them. And you offer a path to medical affairs without trying to do their job yourself.

Mistakes to Avoid

The most common mistake is answering the proof question with a soft yes. Phrases like "it certainly suggests" or "the data is very compelling" still function as a claim of proof to a committee that has to justify a coverage decision later. Say plainly what the study can and cannot support.

A second mistake is sending the study alone, without the population, comparator, and limitations attached. An analyst who has to dig for the methodology will assume you are hiding something, even when you are not.

A third mistake is treating this as a one person job. If the analyst's questions move into statistical methodology, trial design choices, or clinical interpretation, get a medical science liaison or a colleague from medical affairs into the conversation. Answering clinical questions yourself, past the point of your training, creates real risk, both to the accuracy of what the committee hears and to your organization's compliance posture.

A fourth mistake is forgetting that the analyst may ask about baseline utilization once the evidence package is in hand. If you have not thought through how to Respond to a Utilization Baseline Requestyou can end up improvising numbers in the same conversation where you just told the analyst to be cautious about proof. Keep that discipline consistent across every data question the committee raises.

Practice and Score the Exchange

Run this as a drill before you face it live. Pick a real request for published sources, one you have handled before or one your team expects soon. Before you draft any reply, write three discovery questions you would ask the analyst. Good questions narrow the population, the comparator, and the format the analyst needs, whether that is a literature summary, a data package, or a call with a medical colleague.

Then score your own draft against three checks. Did you avoid stating or implying that one study proves a broad outcome. Did you name the study's population, comparator, and limitations without being asked twice. Did you offer a clear next step, including when to bring in medical affairs, instead of leaving the analyst to guess what happens next.

A manager reviewing this with a team can apply the same three checks to a written reply or a recorded practice call. DealSpeak lets you rehearse this exact exchange against an AI counterpart and rerun it until the discovery questions come out first, before any data. If a rep or a market access associate cannot answer the proof question without hedging into an overclaim, that is worth catching in practice, not during a live payer review.

The goal of this conversation is not to win the analyst over. It is to give the committee evidence it can actually use, presented with enough honesty about its limits that the analyst trusts the next package you send. Practice the discovery questions until they come before the data, not after, and the rest of the conversation gets much easier.