Clarify a Benefit Design Question Without Making Coverage Claims

A benefit design question can arrive dressed up as a simple ask. An employer group, a consultant, or an internal stakeholder wants to know whether a plan will change a step therapy rule, a formulary tier, or a member pathway next year. The market access manager on the call often understands the clinical and financial reasoning better than anyone else in the room, and that knowledge creates a pull toward answering the question directly. The trouble is that answering directly means making a coverage claim the manager has no authority to make, about a decision that belongs to the payer's own committee process. Handled well, this exchange builds trust. Handled poorly, it turns into an informal promise that someone else has to walk back later.

Why this conversation goes wrong

Most managers do not slip into overcommitting because they are careless. They slip because the stakeholder frames the question as if it only needs a yes or no, and a flat refusal to answer sounds evasive or unhelpful. The manager wants to be useful, so they reach for language that sounds like an answer even when it is not one. Phrases like "that direction looks likely" or "I would expect something similar" feel harmless in the moment, but the stakeholder hears a signal about a future decision.

There is also a real ownership problem underneath the conversation. Benefit design touches pharmacy, finance, clinical policy, and member communications, and the group asking the question rarely knows which of those owns the actual decision. Without a clear picture of who owns the discussion, the manager cannot tell whether they are looking at an approved resource question or a live policy debate. That confusion is what turns a routine information request into a claim about coverage.

How to prepare

Walk into the call knowing three things. First, know what materials your team has already approved for external sharing on this topic, so you can offer something concrete instead of a vague promise to look into it. Second, know who actually owns the plan design discussion for the group in front of you, whether that is a consultant, a pharmacy director, or an internal committee, because that ownership determines whose word matters, not yours. Third, know which specific claims would need confirmation before anyone repeats them outside the room. If you cannot answer that third point cleanly, assume the answer is that any specific claim needs confirmation.

It also helps to separate the three situations a stakeholder might actually be in. They could be reviewing an existing design and want to understand the rationale. They could be looking ahead to a future cycle and want to shape it. Or they could be dealing with a member service problem that has nothing to do with policy and everything to do with execution. Each of these calls for a different response, and you cannot pick the right one until you know which situation you are in.

What to say

An employer benefits lead opens with, "Can we set up a different member pathway for this category next year." The manager does not answer the question as asked. Instead, they say, "I can help make sure you have the materials and evidence relevant to your review. Before we go further, who owns the plan design discussion on your side, and what specific question has that team asked you to bring back."

The lead names a consultant and a pharmacy director who are running the review. The manager responds, "That's helpful. I will pull together the clinical and economic materials that speak to this category and send them ahead of a session with your consultant and pharmacy director. Their process is what determines the plan's design, so I want to make sure they have what they need directly, rather than relaying it through a summary that could get out of sync with what they actually decide."

The lead pushes a little further. "Sure, but based on what you're seeing across other plans, is this the kind of change that usually happens." The manager holds the line without sounding stiff. "I can't speak to what a specific plan will decide, and I would rather not guess in a way that gets treated as a signal. What I can do is make sure your team has the evidence they need to have that conversation with full information. Would it help if I also flagged the questions your consultant typically asks, so nothing gets missed."

Notice what the manager did across those three turns. They redirected the question toward materials and ownership every time, without ever refusing to help. They named the actual decision makers out loud, which quietly reminds the stakeholder that the manager is not one of them. And they offered something real, a working session with the right people, instead of leaving the stakeholder empty handed.

Mistakes to avoid

The most common mistake is answering the underlying question anyway, just with softer language. Saying "I can't say for certain, but plans usually move this direction" is still a coverage claim, it just comes with a disclaimer attached. Stakeholders remember the direction, not the disclaimer.

A second mistake is going cold and procedural, refusing to engage until the stakeholder can prove they have the right owner in the room. That reads as unhelpful and can damage a relationship that took real time to build. The goal is to redirect ownership while still being warm and useful, not to hide behind process.

A third mistake is leaving the stakeholder without a next step. If you decline to make a coverage claim but also don't offer materials, a meeting, or a name, you have created a dead end, and the stakeholder will look for the answer somewhere less careful.

A fourth mistake shows up after the call, when a manager sends a follow up email that restates the conversation in language that sounds more definite in writing than it did out loud. Read anything you send back before you send it, and ask whether a reader skimming it would come away thinking a decision has been made.

How to practice and score it

This is a conversation that rewards rehearsal more than most, because the pressure to just answer the question builds in real time and is hard to feel until you are in it. Run the exchange with a manager or a peer playing the stakeholder, and have them push the way the lead did above, asking for a direction or a hint even after you have redirected once. Then review the transcript and mark every sentence that could be read as a claim about a specific plan's decision, versus every sentence that pointed to materials, evidence, or the right owner.

A good practice session ends with the manager summarizing, in one or two sentences, the difference between an approved resource and a plan decision, and being able to explain why that boundary protects both the stakeholder and the plan. DealSpeak's rehearsal tool is built for exactly this kind of pressure test, since it lets you run the pushback turn as many times as you need until the redirect feels natural instead of rehearsed. You can find more scenarios like this one among the Pharmaceuticals practice conversationsincluding how to Coordinate a Delayed Formulary Committee Follow Up when a decision stalls after this kind of conversation, and how to Handle a Request to Attend a Payer Committee Meeting when a stakeholder wants direct access to the process itself.

Close

A benefit design question is rarely really about the benefit design. It is a test of whether you can be helpful without overstepping what you are authorized to say. Get the ownership question answered early, offer real materials instead of a guess, and the conversation stays constructive even when you cannot give the answer the stakeholder wanted.