Handling a Consultant's Challenge to a Risk Model

A consultant analyst pokes at one number in your risk model, and the room tension spikes. This moment tests something narrower than most people assume. It is not about defending the number. It is about proving you know exactly where that number came from, what assumptions built it, and who owns the answer when the assumptions get questioned.

Why This Question Throws People Off

Consultant relations professionals spend most of their time on relationship work, scheduling, updates, positioning. A risk analyst who challenges a specific metric is doing something different. They are testing whether your firm can explain its own numbers under pressure, not whether the manager underperforms. Many reps respond to the challenge as if it were personal, and they try to defend the number on the spot. That is the wrong instinct. The consultant is not asking you to win an argument. They are asking whether your firm's process holds together when someone pulls on a thread.

The danger sits in the gap between confidence and accuracy. A rep who sounds sure of a number they cannot actually source creates more damage than one who pauses and says they need to check. Consultants remember which firms guess and which firms verify. That reputation follows you into the next search, and into the next committee meeting, long after this particular call ends.

Preparing Before the Call

You cannot prepare for every possible number a consultant might raise, but you can prepare your method. Know, before any call, the four or five metrics your firm's risk model is built on, and know where each one lives in your approved documentation, drawdown, standard deviation, downside capture, tracking error, and their published time windows.

Write down three things before every consultant call. 1. The exact definition your firm uses for each key risk metric. 2. The benchmark and calculation frequency tied to each metric. 3. The name of the risk or investment professional who owns deeper analysis once a comparison gets specific.

When you sit down for a consultant call, you should be able to answer three questions without hesitation. What does this number measure. Over what period. Against what benchmark. If you cannot answer those three questions cold, get that information before you take another call.

What to Say When the Challenge Comes

The analyst says, "Your downside protection number looks too flattering compared with what we're seeing in our own model."

Instead of defending the number, ask for the analyst's inputs first. You say, "Before I respond to that, I want to compare definitions rather than assume we're measuring the same thing. What time window are you using, and what benchmark and frequency feed your calculation."

The analyst answers that they used a different benchmark and monthly return observations rather than daily figures.

Now you can respond with something grounded instead of defensive. You say, "That likely explains the gap. Our published figure may use a different benchmark or a different observation frequency, and I don't want to guess at the reconciliation on this call. I will send you the approved methodology description, and I will ask our risk team to run the specific comparison you're describing, so you get an answer built on your actual inputs rather than my assumption."

Notice what happened in that exchange. You did not defend the number. You did not concede that it was wrong either. You separated the question of definitions from the question of validity, and you named a real person who will close the loop. Calm curiosity followed by a specific commitment is what a good risk conversation sounds like.

Mistakes That Undermine Your Credibility

The most common mistake is answering from memory when the honest answer is that you do not know yet. A rep who improvises an explanation for a discrepancy they have not actually verified is gambling with the firm's credibility on a guess. If the guess is wrong, the analyst now has two problems, an unresolved number and a contact who overstates certainty.

The second mistake is treating the challenge as an attack that needs a defense. Analysts ask these questions because it is their job, not because they want to embarrass you. Getting defensive, or even mildly dismissive of the analyst's own model, closes a conversation that should stay open.

The third mistake is closing the call without a specific next step. Saying you will look into it is not a commitment. Naming a person, a document, and a rough timeframe is. If you tell the analyst you will send the approved methodology description and loop in your risk team, do it quickly, or the next call starts from a worse position than this one did.

The fourth mistake is forwarding only the final number in your follow up. A useful comparison needs the benchmark, the frequency, the lookback period, and the exact definitions behind the calculation, not just the headline figure. Ask whoever owns the analysis on your side to preserve those inputs when they respond, so the analyst can reconcile the two models instead of receiving another number to question.

How to Practice and Score This Conversation

This is a hard conversation to rehearse alone, because the value sits in the back and forth, not in a set of talking points. A manager can run a useful drill by asking a deliberately vague or slightly wrong question about a risk metric and watching what the rep does next. Does the rep slow down and ask for definitions, or start explaining right away. Does the rep name an approved source, or speak in general terms about the firm's process. Does the rep close with a named owner and a next step, or leave the analyst without a clear path forward.

Score the rep on three things. Whether they asked for the analyst's inputs before responding. Whether everything they said matched approved documentation rather than personal interpretation. Whether the call ended with a named owner and a concrete next step rather than a vague promise.

Tools built for this kind of rehearsal, like DealSpeak, let a consultant relations team run this exact scenario against an AI counterpart that pushes back the way a real analyst would, then score the response against those same criteria. That repetition matters more here than in most sales conversations, because the skill being tested is restraint, not persuasion. You can browse more Asset Management practice conversations built around the moments that come up most often in consultant relations work.

This scenario often sits next to two other conversations consultant relations teams need to rehearse. One is what happens after a search does not go your way, covered in Following Up After a Consultant Search Does Not Advance. The other is how to talk through a gap in a track record without sounding evasive, addressed in Explain a Break in a Track Record to a Consultant With Clear Context.

A risk model challenge is not a test you pass by sounding certain. It is a test you pass by being precise about what you know, honest about what you do not, and fast about getting the real answer to the person who needs it. Handle it that way, and the analyst walks away trusting your process, even if the number itself still needs a second look.