Responding to Public Plan Questions About Manager Diversity Reporting
Help institutional sales teams handle public plan diversity reporting requests with verified disclosures.
A public plan staffer asks for your firm's diversity reporting before agreeing to a research meeting. The request sounds routine, almost administrative. It is not. It is a disclosure and governance question wearing the costume of small talk, and the way you answer it decides whether the plan trusts your data enough to keep talking to you at all.
Why this conversation goes wrong
Institutional sales reps feel pressure to keep momentum. A prospect asks a question, and the instinct is to answer it on the spot so the meeting stays alive. That instinct is the problem here. Manager diversity reporting is not a talking point you can improvise. It is tied to a specific policy, a specific reporting period, and specific field definitions that vary from plan to plan and from year to year.
The rep who answers fast usually blends two different things without meaning to. One is an internal initiative the firm is proud of. The other is a verified public metric the plan's board or staff can cite in a memo. Those are not the same, and treating them as interchangeable is how a firm ends up correcting its own numbers in front of a client six weeks later. A plan that catches one wrong figure will question every figure you send after that, including the ones that were accurate the first time.
The other failure mode is silence, or worse, a vague promise to look into it and never following through with anything concrete. Public plan staff deal with dozens of managers, and they remember who gave them a real answer and who gave them a stall. Precision costs you nothing. Guessing costs you the meeting, and possibly the mandate.
How to prepare before you respond
Before you say anything substantive, find out what the plan actually adopted. Boards do not all use the same policy language, and a term like diverse owned firm or diverse ownership percentage can mean different things depending on the plan's own definitions. Ask which fields the board or investment staff will review, what reporting period the policy covers, and what source format they expect, a form, a questionnaire, a narrative letter, or a data file.
Know, before the call, which team inside your firm owns this data. In most asset managers it sits with compliance, legal, or a dedicated diversity and inclusion function, not with sales. Have that contact ready. Know what your firm has already disclosed publicly and where, so you are not promising something that contradicts an existing filing or a prior submission to a different plan.
Also find out who owns the comparison on the plan side. Sometimes it is procurement. Sometimes it is investment staff running an internal screen. Sometimes a board committee makes the final call on whether a manager meets a stated threshold. That distinction matters because it tells you who actually needs to see the data and in what form, and it keeps you from implying that your firm has cleared a bar that only the plan's own reviewers are authorized to confirm.
What to say
Staff opens with something like this. Our board adopted a new reporting policy last quarter. Can you send your diversity data today.
The instinct is to say yes and scramble later. Do not do that. Instead, say something like this. I want to make sure we send you the same definitions and period your policy actually requires, rather than a generic version that might not match. Can you tell me which fields the board will review and what format they expect, a form, a data file, or something else.
Staff responds with the policy name, the field list, and a deadline three weeks out.
You say this. I will coordinate the version of our disclosure that has already been approved for external use and check whether it maps to those specific fields. If any field is not covered by what we currently disclose, I will tell you exactly which one and go to the source owner on our side rather than filling the gap myself. You will have a clear answer, not a partial one dressed up as complete.
Staff may push once more, asking whether the firm meets a particular threshold the board cares about.
You say this. I can tell you what we report and how it is defined. Whether that meets your board's threshold is a determination your reviewers need to make, since your policy sets the bar, not us. I do not want to tell you we clear something and have your committee read the same numbers differently.
That last line matters more than it sounds. It draws a line between reporting a fact and making a judgment that belongs to the client. Plans respect that distinction. It is also, frankly, the safer position, because if your firm later fails a screen you claimed to pass, that conversation is far worse than the one where you were careful from the start.
Mistakes to avoid
A few patterns show up again and again in these conversations, and all of them are avoidable.
- Citing an internal program or initiative as if it were a verified external metric. Say plainly which is which every time.
- Committing to a same day turnaround before you know what the field list actually requires. A realistic timeline builds more trust than a fast, vague one.
- Guessing at a definition instead of asking the plan to confirm it. Terms like diverse owned or minority led are not standardized across plans, and assuming your firm's internal definition matches theirs is a common, costly error.
- Implying that your firm meets a threshold the plan's own staff or board has to determine. That judgment is theirs, not yours.
- Leaving the request undocumented. Write down every field asked for and the date the information is requested as of, because that record is what prevents a dispute in the actual meeting later.
How to practice and score it
This is not a conversation most reps get to rehearse before it happens for real, which is exactly why it goes wrong so often. A useful drill gives the rep a request containing one metric they already know cold and two undefined terms they have never seen phrased that way. The rep has to ask targeted questions, name the internal source that owns the approved disclosure, and propose a realistic follow up timeline instead of an answer on the spot.
Score the drill on precision, not speed. Did the rep separate what they knew from what needed confirmation. Did they avoid stating a judgment that belongs to the plan's reviewers. Did they get a clear field list and a deadline before the call ended. A rep who slows down and asks three sharp questions is doing this job better than one who fires back a confident answer that turns out to be half wrong.
DealSpeak's Asset Management practice conversations include this exact scenario, along with adjacent ones worth rehearsing alongside it. If you want to see the same disciplined, question first approach applied to a review that has gone quiet, read Reconnect With a Stalled Institutional Review Through a Useful Question. And if your plan work involves screening tied to a government or sovereign mandate, the same care around precise definitions shows up again in Handle Sovereign Mandate Screening With Precise Questions.
Public plan staff are not trying to trap you with this question. They are trying to find out whether your firm treats disclosure the way their board expects it to be treated. Answer with precision, route the details to the right owner, and put the request in writing. That is what keeps the meeting, and the relationship, intact.
Practice these next
Teach institutional sales teams to map stakeholders without assuming influence.
Help institutional sales teams support a search led by a consultant while respecting the allocator's process.
Help institutional sales teams discuss an endowment's liquidity concern without assuming its cash flow needs.
Help institutional sales teams clarify mandate fit before proposing a due diligence path.
Help institutional sales teams turn an OCIO transition question into a documented planning conversation.
Questions that help institutional sales teams identify policy limits before advancing a strategy discussion.