Keep a Consultant Database Profile Accurate Between Reviews

A consultant database profile is often the first document a researcher opens, and a single wrong number in that first look can shape every conversation that follows. Consultant relations teams that treat the profile as a static form to update once a quarter end up defending stale figures instead of talking about performance and strategy. Building a process that keeps the profile accurate between formal reviews protects the trust that makes the rest of the relationship work.

Why This Conversation Goes Wrong

This exchange goes wrong because it looks easy until you are the one filling in the field. A request lands on a Thursday with a Friday deadline, and the instinct is to open the last approved questionnaire and copy the numbers forward. That instinct is reasonable when nothing has changed, but it fails the moment a portfolio manager has left, a mandate has grown past a threshold, or the firm has revised how it counts committed but uncalled capital. The consultant is not just checking a box either. They feed your numbers into a model that ranks your strategy against peers, and if your assets figure uses a different definition than everyone else's, the ranking is wrong before anyone notices. The pressure to answer fast, combined with the assumption that a database field is low stakes, is exactly what produces the kind of mismatch a consultant remembers for years.

A stale or wrong figure does not just sit quietly in a database. Some consultants pull the same field into a formal review deck months later, and by then nobody remembers why the number was wrong or who to ask. Fixing it after the fact costs far more time than getting it right the first time.

How to Prepare

Start with a field inventory before you touch the request. Sort every field in the profile by who owns the underlying fact. Assets and performance figures come from finance. Personnel descriptions, strategy guidelines, and capacity numbers come from the investment team. Statements about compliance history or regulatory status come from legal. Once you know who owns each fact, you know who has to sign off before it goes live, and you stop guessing at numbers you cannot independently verify.

Assign one person on the consultant relations team to own the update itself, even though multiple departments supply the facts. A single owner keeps the change log complete and gives the consultant one name to contact if a question comes up later.

Next, get specific about definitions. Assets can mean firm assets, strategy assets, or assets in the specific vehicle the consultant is researching. Inception date can mean the date the strategy launched, the date it opened to outside capital, or the date a track record became verified. Team experience can mean years at the firm or years managing the strategy. When a request does not specify which definition applies, ask before you upload anything. A number that is accurate under one definition and misleading under another will surface again later, usually in a meeting where you are not in the room to explain it.

Finally, check the review date on every field you plan to touch. If a figure was last verified two quarters ago and nothing in your inventory shows a reason it changed, confirm it again anyway rather than assuming it still holds.

What to Say

Picture a consultant relations associate named Priya. A consultant emails her Thursday afternoon asking her to confirm assets under management as of the most recent quarter end and to note any changes to the portfolio management team, with a Friday deadline for the profile refresh.

Priya writes back the same day. She says, "I want to give you a number I can stand behind, so I am confirming the quarter end figure with finance today and checking the personnel description with the strategy team. I expect to have both back to you by tomorrow morning."

The consultant replies, "That works. Just so you know, we are comparing this strategy against several peers on a total strategy assets basis, not firm assets, so please make sure that is the figure you send."

Priya answers, "Understood. I will confirm total strategy assets specifically, and I will note the measurement date in the same message so your team can line it up with the peer group." The next morning she sends the update. It reads, "Total strategy assets as of the requested quarter end, confirmed with finance on the date shown. One portfolio manager departed last month, and their responsibilities have moved to two existing team members whose updated roles are described below. Please let us know if your taxonomy for either field has changed since our last submission."

That last message does three things worth noticing. It states the exact definition used, it names the date the number was confirmed, and it invites the consultant to flag any mismatch in taxonomy before the number goes into a model. None of it reads as promotional. It reads as something the consultant can trust without calling to double check.

Mistakes to Avoid

Do not copy a figure forward from a prior submission without confirming it is still accurate and still uses the same definition the consultant is asking for. Do not answer a data request before checking who actually owns the underlying fact, because a guess dressed up as confidence is worse than a short delay for verification. Do not treat the profile as a place for favorable language. Superlatives and vague claims about being a leader in a category do the opposite of their intent, since a researcher who catches one unsupported claim starts reading every other field with suspicion. Do not skip the change log either. If you update a field without recording what changed, why it changed, and who verified it, you will have no good answer when a consultant asks why last quarter's number does not match this quarter's. Do not assume a consultant's definition matches the one your firm used in the last submission, since consultants update their own taxonomies without always announcing it.

How to Practice and Score It

A manager can score this conversation on three things. First, check whether the associate identified the field owner before answering. Second, check whether the associate asked about definitions instead of assuming them. Third, check whether the final message to the consultant was specific enough for the consultant to verify later. Role play the exchange with a deadline attached, since real requests almost always come with one, and watch whether the pressure of the clock causes shortcuts. A good run includes at least one moment where the associate pushes back gently on a vague request, the way Priya asked to confirm which assets figure the consultant wanted before sending anything.

DealSpeak's Asset Management practice conversations give consultant relations teams a place to run this scenario against an AI counterpart that asks the same follow up questions a real consultant would, then scores how you handled the definitions and the deadline. The same discipline about defining terms before answering shows up in how you Answer Consultant ESG Data Requests by Defining the Terms, and it applies again when a consultant pushes you to compare your firm against a competitor, which is covered in Discuss Manager Differentiation Without Overstating the Case.

Close

A consultant database profile is not paperwork. It is the first conversation you have with a researcher, and it sets the tone for every conversation after it. Treat every field as a claim with an owner, a source, and a date, and the rest of the relationship gets easier to defend.