Handling a Consultant Conversation After a Rating Downgrade

A rating downgrade puts consultant relations professionals on the defensive before the call even starts. The instinct is to explain, soften, or push back on the rationale. None of that helps. The consultant already reached a conclusion using their own process, and your job now is narrower than it feels, confirm facts, respect their independence, and give them a clear path to the next piece of information they need. Handled well, this conversation preserves the relationship even when the rating itself does not move.

Why This Conversation Goes Wrong

Most reps walk into a downgrade call trying to change the analyst's mind. That framing is the first mistake. The analyst already applied their research process and reached a rating. Arguing with the conclusion signals that you did not understand the process or do not respect it, and either read damages the relationship more than the downgrade itself.

The second problem is vague reassurance. Phrases like "we've addressed that" or "the team is stable now" sound confident but carry no evidence behind them. An analyst who hears this without a source attached discounts it immediately, and rightly so. They cover many managers and have heard every version of "trust us" before.

The third problem is speed. Reps under pressure rush past the analyst's actual question. A downgrade rationale might reference one specific concern, a departure, a process gap, a performance pattern, but the rep answers the general category of "why did our rating drop" instead of the specific point raised. That mismatch wastes the call and leaves the real question unanswered.

How to Prepare Before the Call

Before you pick up the phone, separate what you know from what you can prove. If a portfolio manager left, you know the departure happened. You do not know how the analyst weighs it against other factors unless they tell you. Write down the specific concerns the consultant has cited, in their own words if possible, rather than your paraphrase of what you assume they mean.

Next, gather the materials your firm has approved for external use, succession plans, org charts, process documentation, any client communication about the change. Leave out informal notes, internal memos, or anything not cleared for outside use. If you do not know whether something is approved, treat it as unavailable until you confirm it.

It also helps to understand how the analyst's research process actually works before you try to respond to it. A rating is not a single judgment, it comes from a set of criteria the analyst applies consistently across every manager they cover. Reading about how research criteria become a recommendation gives you language that matches how the analyst actually thinks, rather than language built around your own talking points. Ask Consultants How Research Criteria Become a Recommendation walks through that process in more detail.

Finally, decide who else might need to join a follow up conversation. If the analyst wants to test facts about a transition, an investment professional with direct knowledge often does more good on that call than you can do alone. Identify that person and confirm their availability before you commit to a timeline.

What to Say When the Analyst Pushes

An analyst might open with something like this. "Your rating dropped because the team looks unstable to us. Give me a reason to keep you in consideration." Do not answer that broadly. Ask what they are actually weighing. You might say, "Continuity clearly matters to your review. Can you tell me which specific changes and which evidence you're evaluating, so I bring you the approved materials that speak to those points directly."

Suppose the analyst answers, "There was a senior departure six months ago and we have a research committee meeting in three weeks. We need to understand succession before then." Now you have something concrete to work with. You could respond, "I will confirm exactly what documented succession and process information exists and get it to you well ahead of that meeting. Would it help to speak directly with the investment and research leaders who can address the transition, so you can test those facts yourself before the committee convenes."

If the analyst agrees, close the loop with a specific commitment rather than a vague one. "I will have the succession documentation to you by early next week and can set up that call for whichever day works before your committee meets." That sentence names a document, a deadline, and a next step. Nothing in it promises an outcome, and nothing in it overstates what you know.

Notice what did not happen in that exchange. You did not argue that the team is actually stable. You did not promise the rating would improve. You asked a clarifying question, confirmed the scope of the concern, and made a commitment tied to a real source and a real date.

Mistakes That Undermine Trust

Do not characterize the downgrade rationale beyond what the analyst actually told you. If they mention team stability, do not assume they also mean performance or process. Ask instead of filling in the gaps yourself.

Do not promise that a meeting or a document will change the rating. You do not control that outcome, and claiming otherwise sets up a broken promise the next time you talk. Say what the meeting accomplishes, the analyst gets direct access to the people who can answer their questions, and leave the conclusion to their process.

Do not blur public information with internal speculation. If you are not sure whether a detail about a personnel change has cleared for external conversations, do not share it on the assumption that it is harmless. Confirm first.

Do not skip the internal handoff. Write down the analyst's specific concerns, the documents they requested, the date of their next research event, and whether your client service team needs to know about the downgrade before a client asks about it. A downgrade conversation that ends without that record forces the next person on your team to start from zero.

If a consultant tells you they are stepping back from active review rather than pushing for more information, that is a different conversation with its own discipline. Respond Constructively When a Consultant Declines Further Review covers how to handle that version without arguing the decision or disappearing from the relationship.

How to Practice and Score the Conversation

This conversation is hard to get right on the first live attempt, which is exactly why it deserves rehearsal before it happens for real. Have a manager or peer play the analyst and instruct them to interrupt any answer that sounds like reassurance without a source attached. The rep has to stop, ask a clarifying question, or restate the commitment with a document and a date attached to it.

Record the session and listen back for specific phrases. Anything that implies an outcome, "this should resolve it," "that will satisfy them," gets rewritten as a precise statement of what happens next and by when. Count how many times the rep asked a clarifying question before offering a commitment. Zero is a problem. One or two is a reasonable target for a five minute exchange.

Score the practice on three things. Did the rep identify the specific concern the analyst raised instead of responding to a general category. Did every commitment name a source, a document, or a person, rather than a feeling. Did the rep avoid predicting how the rating conversation would end. A rep who scores well on all three sounds calm, not because they are guessing well, but because they are not guessing at all.

DealSpeak's Asset Management practice conversations let you run this exact scenario against an AI counterpart that pushes back the way a real analyst would, so your team builds this discipline before a downgrade call actually happens.

Building the Habit

A downgrade conversation handled with precision does not erase the rating, but it keeps the door open for the next one. Consultants remember which firms answered their actual questions and which ones talked around them. Practice this exchange enough times and it stops feeling like a test you might fail, and starts feeling like a process you already know how to run.