Coordinate a Delayed Formulary Committee Follow-Up

A delayed formulary committee follow up gets urgent fast. Someone from the coordinator's office calls or emails and says the agenda closes in a day, sometimes in hours, and every unanswered question on the list suddenly feels like a fire. As the market access manager, you feel the pull to just answer, to unblock the coordinator and keep the product on schedule. That pull is exactly what gets people into trouble. An answer that has not gone through medical or clinical review is not a favor to anyone. It is a liability sitting inside a committee packet for as long as that packet exists.

Why this conversation goes wrong

Most of these calls go wrong for the same three reasons. First, the coordinator is working under their own deadline and does not always distinguish between a question you can answer from memory and one that needs a clinical or regulatory reviewer. To them, a question is a question, and all of them need to move. Second, pressure compresses time, so people start promising things they cannot actually deliver, phrases like we will get that to you today, without checking whether the right reviewer is even available today. Third, nobody writes down who owns what. The call ends, everyone assumes someone else is handling it, and two days later nothing has moved.

None of this is really about the deadline. It is about structure. A tight deadline does not require a bad process, it requires a fast one, and those are different things. The cost of getting this wrong is not a bad phone call, it is a scientific claim or a data point sitting in committee minutes with no reviewer behind it, and that record does not disappear once the crisis passes.

How to prepare

Before you call the coordinator back, do three things. Pull the full list of outstanding questions and read every one, do not skim. Sort each question into one of two piles, administrative questions you or your team can answer directly, and questions that need input from medical affairs, clinical, or legal. Then check who on your side actually owns each pile and whether that person is reachable before the deadline.

This is also the moment to confirm the mechanics nobody thinks about until it is too late. What format does the committee expect, a short written response, a table, a formal memo. Do they need citations or references attached. What time, not just what date, does the agenda lock. A deadline of Friday means something different if the committee finalizes the packet at eight in the morning versus six in the evening.

If you are still getting comfortable with how these committees operate, DealSpeak's Pharmaceuticals practice conversations cover the surrounding scenarios too, including how to confirm your own role before a presentation. That same idea, nailing down who does what before the pressure hits, is covered in Confirm Roles Before a Formulary Committee Presentationand it applies just as much to a follow up call as it does to the main meeting.

What to say

Keep the conversation short and specific. Confirm what you heard, split the questions, and give a real time for a status update, not a vague promise.

The coordinator opens with pressure. "Can you just send me something now? The agenda closes Friday and I have nothing from your side yet."

You do not match that pressure with a rushed answer. "I can get you a real answer, and I would rather send something ready for committee use than something fast and wrong. Let me confirm two things. Which of these questions need medical or clinical input, and what time on Friday does the packet actually lock?"

The coordinator answers. "Questions three and five need clinical input, the rest are administrative. The packet locks at nine in the morning Friday."

You close the loop with a plan, not a promise. "Good. I will route three and five to clinical review this afternoon and get the rest turned around by end of day today. You will have a written status with a named owner and a date on each question by five o'clock, and the full response before Thursday close so there is buffer before Friday morning."

Notice what happened there. No answer went out before it was ready. Every question got a real owner. The coordinator got a specific time to expect something, not just the day of the deadline itself.

Mistakes to avoid

A few patterns keep showing up in these calls and they are worth naming directly.

1. Sending a partial or guessed answer to a clinical question because the deadline felt closer than the review process. This is the most damaging mistake on the list, since it puts unreviewed content into a permanent record.

2. Promising a full response by the deadline itself instead of building in a buffer. If your internal deadline matches the committee's deadline exactly, you have no room for anything to go wrong, and something usually does.

3. Leaving a question unassigned because it looks minor. Every question needs a name attached to it, even the ones that seem easy.

4. Treating the coordinator as an obstacle instead of a partner. They are usually under more pressure than you are, and a calm, organized response from you makes their day easier, not harder.

5. Giving a status update that only names a team instead of a person. A note that says clinical is reviewing it tells the coordinator nothing about when to expect an answer or who to call if it slips.

If the coordinator asks you to attend the committee meeting itself rather than just answer questions in writing, that is a related but separate situation. Read Handle a Request to Attend a Payer Committee Meeting before you agree to anything.

How to practice and score it

This conversation is easy to describe and hard to do well under real pressure, so it is worth rehearsing before the first time a coordinator calls with a real deadline. Run the scenario with a colleague playing the coordinator, and have that person push exactly the way a real coordinator would, repeating the deadline, asking for something now, resisting your attempt to split the questions apart.

Score the result against a short checklist. Every question on the list should end up with one named owner and one specific date next to it, not a group or a department. No answer should go out without the right review, even under direct pressure to skip it. The status update you give should include a time, not just a day. And you should never let a phrase like we will get back to you stand on its own without a concrete next step attached to it.

A manager reviewing this practice session should stop the exercise the moment a vague phrase slips in and ask for the specific version instead. DealSpeak scores this same kind of exchange automatically, checking whether each question got a real owner and whether any answer went out before review was complete, which gives you a concrete score instead of a gut feeling about how the call went.

Close

A delayed follow up does not have to turn into a scramble. Confirm the questions, split them by who needs to answer, and give the coordinator a real time to expect movement. That is the whole job, done calmly instead of frantically.