Handle a Client's Custom Risk Limit Question With the Agreed Metric

A client with a custom risk limit is not asking for reassurance. They are asking whether the portfolio sits inside a number they helped define, measured the way they agreed to measure it. When a Client Portfolio Specialist reaches for the standard dashboard instead of the agreed metric, the answer can be technically true and still wrong for the question that was asked. Here is why that conversation goes sideways, how to prepare for it, and what to say when a client presses for a quick yes or no.

Why This Conversation Goes Wrong

Custom risk limits exist because standard reporting does not fit every mandate. One client caps tracking error against a blended benchmark that differs from the firm's default index. Another limits sector concentration using a formula the risk team built specifically for their account. A third defines value at risk with a lookback period nobody else on the desk uses. The limit lives in a side letter, an investment policy statement, or an email exchange from eighteen months ago, not in the dashboard you open every morning.

When a CIO or trustee asks whether the portfolio is inside budget, the easy move is to glance at the standard risk report and answer with confidence. That report might use a different benchmark, a different confidence interval, or a different rebalancing assumption than the one the client approved. You end up answering a question nobody asked. Calling the portfolio safe without naming the measure behind that word feels helpful in the moment, but it sets up a problem later. If the client checks your answer against their own calculation and finds a gap, you look like you either misunderstood the mandate or tried to talk past a real risk question. Once that happens, trust drops fast, and a single good report rarely earns it back.

Prepare Before the Question Comes Up

You cannot improvise your way through a custom metric during a live call. Build the groundwork ahead of time so you can respond with facts instead of guesses.

1. Locate the exact limit language in the investment policy statement or side letter, including the metric name, the formula, and the threshold the client agreed to.
2. Confirm the approved reporting date and the system that produces that metric, and check whether any recent mandate change or methodology update affects how the current number compares to prior periods.
3. Know which person on the risk team can validate an interpretation question, and loop them in early whenever the calculation is contested or unclear.

Keep a short reference sheet for each client that maps their custom limits to the owner, the reporting source, and the last date the methodology was reviewed. Five minutes spent building that sheet saves you from scrambling when a CIO calls and wants an answer before lunch. It also means you walk into the conversation citing a document instead of your memory of a call from last quarter.

What to Say When the Client Presses You

A CIO says, "Just tell me straight, are we still inside budget."

You respond, "I want to give you an answer you can check against your own numbers, not just a yes. Should we use the tracking error limit from the amended investment policy statement in March, or the original mandate language. And would you like someone from the risk team on this review, given how the calculation changed."

The CIO says, "Use the current policy statement. Pull the number as of quarter end, and yes, get the risk team involved."

You say, "I will have the risk team run the quarter end figure against the amended limit and send you the report with the calculation date and methodology attached by tomorrow morning."

Notice what this exchange does. You do not dodge the question, and you do not stall without giving a reason. You name the two possible versions of the limit so the client picks the right one instead of assuming you did. You bring in the risk team when the interpretation carries weight, rather than guessing at a number that sits outside your authority. And you close with a specific deliverable and a specific date, so the client knows exactly what they are getting and when. That last part matters as much as the analysis itself. A CIO who hears "I'll look into it" has no way to judge whether you took the question seriously. A CIO who hears "by tomorrow morning, with the calculation date and methodology attached" can hold you to it.

Mistakes That Undermine the Client's Trust

The most common mistake is treating two different risk measures as if they were interchangeable. If the client's limit is defined against a custom benchmark and your standard report uses the firm's default index, quoting the standard number without flagging the difference is not a shortcut, it is a misstatement. Say plainly when the two numbers cannot be compared directly, and explain what would need to change to make them comparable.

A second mistake is offering verbal comfort instead of a documented answer. Telling a client "you're fine" over the phone feels efficient, but it leaves nothing they can point to later, and it puts your judgment on the line for a number you have not actually pulled. A written recap should state the exact metric used, the date of the calculation, and any limitation in the report, such as a data lag or an assumption that changed since the last review.

A third mistake is skipping the risk team when the interpretation is genuinely contested. Some specialists avoid looping in risk because it feels like admitting they do not have the full picture. That instinct is backwards. Involving risk on a disputed calculation protects the client and protects you, and most CIOs respect a specialist who says the interpretation needs another set of eyes rather than one who guesses and gets it wrong.

Finally, avoid giving a vague timeline or none at all. "I'll follow up soon" tells the client nothing. Commit to a date, even a short one, and hit it.

Practice and Score the Conversation

This conversation is hard to get right the first time because the pressure to answer fast fights against the discipline of confirming the right metric first. Practice it with someone playing a CIO who keeps pushing for a single word answer and resists your attempts to clarify which version of the limit applies. DealSpeak's role play scenarios for asset management are built around exactly this kind of pressure, letting a specialist rehearse the exchange until the clarifying questions come out naturally instead of sounding like a stall tactic.

A manager scoring the practice run should check three things. Did the specialist identify the governing document and the specific metric before answering. Did the specialist avoid a premature yes or no and instead ask which version of the limit and reporting date applied. Did the specialist close with a concrete next step, naming who would run the analysis and when the client would see it. A specialist who checks all three has handled the conversation well, even if the actual risk number turns out to be less favorable than the client hoped.

You can rehearse this exchange and others like it through Asset Management practice conversations, which cover the recurring conversations client portfolio specialists face. For a related scenario, see Leading a Client Conversation After a Portfolio Drawdown, which walks through a different moment where precision and calm both matter. If a client ever questions how an ESG figure was calculated, the same discipline applies, and Reconcile an ESG Report Question With a Client's Own Definitions covers that case directly.

A custom risk limit deserves a custom answer, not a borrowed one from the nearest dashboard. Slow down long enough to confirm the metric, get the right people in the room, and put the answer in writing. That approach costs you a few extra minutes up front and saves you a much harder conversation later.