Prepare for Consultant Operational Diligence With Source Discipline

An operational due diligence questionnaire from an investment consultant looks simple until you sit down to answer it. It arrives as a spreadsheet full of terms that mean something specific to that consultant's firm and something slightly different at yours. Answer from memory, or from last year's version of the same questionnaire, and you risk giving a confident answer to the wrong question. The safer approach is to build a controlled route from each question to a verified source, log who owns the answer and when it is due, and talk openly with the consultant about timing. What actually gets tested on these calls is rarely the substance of your operations. It is whether you check before you speak.

Why This Conversation Goes Wrong

Most people handling consultant relations feel pressure to sound certain right away. A consultant asks about oversight of service providers or exception handling, and the instinct is to answer in the room rather than admit you need to check. The problem is that operational due diligence questionnaires use precise language, and firms do not all use it the same way. One consultant's definition of an exception is another consultant's definition of a control gap. One firm's monitoring is another firm's oversight. Answer the term as you understand it rather than as the consultant defines it, and you can hand them an answer that is technically wrong even though it sounds fine in the moment.

The other failure mode is treating last quarter's answer as this quarter's truth. Operational details change. A vendor relationship ends, a control gets updated, a person named as the answer owner leaves the firm. A consultant who catches a stale or invented detail during committee review does not just correct the record. They start wondering what else in the questionnaire was answered the same way, and that doubt follows your firm into the next request, and often into the next product review as well.

How To Prepare Before The Consultant Calls

Read the full questionnaire before you respond to anything, not just the questions addressed to you directly. Mark which questions need input from operations, legal, information security, or compliance, since consultant relations rarely owns the answer alone. Note the due date, whether attachments are required, and whether the consultant accepts written clarification on ambiguous terms or expects a verbal answer on the spot. That last detail matters more than people give it credit for. A consultant who allows written follow up is telling you they expect precision over speed.

Build a source log that ties every proposed answer to a current approved document or a named evidence owner. This is the part people skip when they are busy, and it is exactly the part that saves you when a consultant asks a follow up question you did not expect. If you want a closer look at how to structure responses to the questionnaire itself, the post on Answering a Consultant Questionnaire for Operational Due Diligence walks through the format most firms use. Consultants also frequently ask how your firm gets classified against peers, and that question deserves the same source discipline, which the piece on Clarifying Peer Group Classification With Investment Consultants covers in more detail.

What To Say When The Consultant Wants An Answer Now

An operations lead on the consultant's team says, "This question asks about oversight of your service providers. Can you confirm there were no exceptions in the period?"

You reply, "I want to make sure I answer the term the way your questionnaire defines it rather than the way we use it internally. That question is with our operations owner right now, and they are reviewing the approved due diligence material before I send you wording. Do you need the answer by a calendar day, or does it need to land before your committee packet closes?"

The lead answers, "The packet closes Friday at noon."

You reply, "That gives us enough room. I will confirm with operations today and get you either the answer or a status update by tomorrow, so you are not waiting until Friday to find out where things stand."

Notice what did not happen in that exchange. You did not confirm the absence of exceptions before checking. You did not guess at what operations would say, and you did not fill the silence with a plausible sounding placeholder. You asked a real question about timing instead of assuming the consultant needs an answer immediately, and you closed with a specific commitment instead of a vague one. That is the entire skill. It is not about knowing every operational detail. It is about handling the gap between the question and the verified answer without pretending the gap does not exist.

Mistakes That Cost You Credibility

Describing an internal control or a remediation item before its owner approves the wording is the most common mistake, and it does the most damage. The words you choose in a live conversation become the words the consultant writes into their file, and you cannot walk them back cleanly once they are recorded. Confirming the absence of an exception without checking is a close second. It feels harmless when you are fairly sure the answer is no, but fairly sure is not the same as verified, and consultants remember which firms turned out to be wrong.

Promising a specific date without checking with the source owner first creates a different problem. You end up negotiating your own deadline down the road instead of the consultant's, and that reads as disorganized even when the underlying work is fine. Speaking for information security or compliance on a topic outside your own function is another version of the same mistake, since a confident answer from the wrong person carries no more weight than a guess. Treating every question as one that needs an immediate verbal answer is the failure underneath all the others. Consultants who run operational diligence for a living expect a firm to check before it speaks. A firm that never says I need to verify that looks less careful, not more responsive.

How To Practice And Score This Conversation

A manager can build a useful practice session in a few minutes. Hand the rep an unfamiliar questionnaire term, worded slightly differently than the firm's internal language, and set a rushed deadline. Then listen for three things. Does the rep ask what the term means in the consultant's context before answering it. Does the rep name a specific owner and route the question rather than answer from memory. Does the rep have an actual conversation about timing instead of accepting or promising a date without checking first.

Mark down any invented operational detail even when it sounds plausible, because plausible is exactly the kind of answer that gets a firm into trouble months later. Score the rep up when they ask a clarifying question under pressure instead of guessing, and score them up again when they give a specific, checked commitment rather than a soft one. DealSpeak's Asset Management practice conversations give consultant relations teams a way to run this exact scenario, with an AI counterpart that pushes for a fast answer the same way a real consultant does, so the rep makes the mistake in practice instead of in front of a client.

Operational due diligence rewards firms that check before they speak and log what they find along the way. Build the source discipline once, and every questionnaire after the first gets easier to answer. The consultant relationship holds up because the answers do too.