Handle Sovereign Mandate Screening With Precise Questions

A sovereign allocator asks you to confirm that your strategy will pass an exclusion screen before the allocator's own legal team has finished writing it. Say yes and you have created a mandate condition that does not exist yet. Say nothing useful and you look evasive. The conversation sits in a narrow gap between helpful and reckless, and institutional sales reps walk into it more often than they expect.

Why This Conversation Goes Wrong

Sovereign allocators often start screening a manager long before the exclusion list, the reference index, or the interpretation rules are final. The person you are talking to may not even know the final wording yet. They ask a direct question because they want a direct answer, and the instinct to be helpful pushes a rep toward saying yes, we qualify, or no, that would not be an issue. Either answer, given before the governing document exists, turns your guess into something the allocator's team may record as a representation from the manager. Once that happens, the allocator has built a decision on a stated fit, not a preliminary read. If the actual restriction lands differently, you have a compliance problem, a credibility problem, and an allocator who now has to unwind a step in their own process. Treat a screening exclusion under discussion as a fact that does not exist yet, not a fact you are being asked to confirm.

How to Prepare

Before the call, know three things. First, know which mandate document, if any, currently governs the review, whether that is a draft investment policy, a term sheet, or an internal memo the allocator is not required to share yet. Second, know your own approved list of exclusions, restricted issuers, and the review process your firm actually uses, so you can describe it accurately without guessing how it applies to criteria that have not been finalized. Third, know who at your firm can interpret an ambiguous restriction if the allocator sends language that is unclear, and get that person's name and availability before the call, not during it.

Write down two or three questions you can ask instead of answering directly. Which document will govern the final screen. Are the criteria still under discussion internally at the allocator's shop. Who can confirm the governing language once it exists. These questions do the work that a premature yes or no cannot do. They move the allocator toward giving you something concrete to review, and they signal that you take their process seriously instead of rushing past it.

If you want a broader sense of how these mandate conversations differ across institutional buyers, the Asset Management practice conversations hub covers related situations, including how to Prepare for a Conversation About a Manager on a Watch List, which shares the same discipline of separating a preliminary flag from a finished conclusion.

What to Say

Here is roughly how the exchange should go.

The allocator says, "We expect to apply a screen on certain issuers before we finalize the mandate. Can you confirm your strategy qualifies?"

You answer, "I can send our approved strategy documentation and walk you through how we handle exclusion screens and the data behind them. Your legal team has not finished the screen yet, so I am not going to state fit today, because I would rather give you an answer that holds up than one that has to be corrected later. Could you share the criteria you are considering, even in draft form, so we can review them properly once the governing language is set."

The allocator replies, "That is fair. I can send the draft list through our usual document channel."

You close with, "That works well. Once I have the draft, I will confirm which of our disclosed positions or exposures might intersect with it, and I will flag anything that needs a formal answer from our compliance team rather than from me."

Notice what this exchange does. It gives the allocator something real, the approved documentation and the process explanation. It refuses one specific thing, a statement of fit, and explains why in plain terms rather than hiding behind process language. It also hands the allocator a next step that keeps the conversation moving instead of stalling it.

Mistakes to Avoid

Three mistakes show up again and again in this situation.

1. Confirming fit based on the allocator's description of the screen rather than the actual governing document. An allocator's summary of a restriction is not the restriction. Wording matters, and small differences in how an exclusion is defined change whether a strategy actually qualifies.

2. Treating silence as safe. A rep who avoids the question entirely, without offering the documentation or a path to an answer, reads as unprepared or unwilling to help. The allocator still needs to make progress, and refusing to engage at all pushes the relationship in the wrong direction.

3. Failing to separate what was said from what was asked. If your notes after the call blend disclosed strategy facts, the allocator's preliminary criteria, and questions that remain open, the next person on your team who picks up the file cannot tell what is confirmed and what is still a guess. Write those three categories down separately every time. It makes due diligence easier to audit later and protects you if anyone asks what was actually said on the call.

How to Practice and Score It

Run a roleplay where the counterpart keeps pressing for a direct yes or no, because that pressure is exactly what happens on a real call. A rep who folds under three rounds of just tell me if we qualify has not learned the skill yet.

Score the roleplay on three things. Did the rep offer something useful in the first response, rather than just deflecting. Did the rep ask for the governing source of the restriction instead of accepting the allocator's paraphrase as final. Did the rep schedule a concrete next step, such as a review once language is confirmed, rather than leaving the question open with no path forward.

A manager reviewing the recording should flag any sentence where an unapproved assumption gets stated as a fact about mandate fit. That single habit, catching the moment a guess turns into a representation, is the most useful thing a manager can train for. If your team is also working through related mandate ambiguity, the piece on Writing an RFP Clarification for an Ambiguous Investment Mandate walks through a similar discipline for written responses instead of live calls.

Reps who handle this well are not the ones with the smoothest answer. They are the ones who know exactly what they can confirm, what they cannot, and how to keep the allocator moving forward without overstating either one. Practice the exchange enough times with a tool like DealSpeak or with a manager standing in as the allocator, and the instinct to fill silence with a guess starts to fade.