Set the Right Boundary for an RFP Question About an Operational Exception

A reviewer running operational due diligence can ask a question that sounds simple but carries real risk if you answer it yourself. They mention an unresolved remediation item or an operational exception, and they phrase it in a way that assumes the worst. As the RFP lead, you do not have the authority to characterize that item. You were not in the room when it was opened, you do not know where it stands today, and you cannot promise language you have not cleared. Your job is not to answer the question. Your job is to define exactly what is being asked, get the right owners to answer it, and keep the reviewer informed while that happens.

Why This Question Throws RFP Leads Off

Operational due diligence reviewers often use terms that go beyond a standard questionnaire. "Exception," "control failure," and "remediation" carry specific meaning inside your firm and a different, often broader meaning to someone outside it. A reviewer might ask about an exception meaning any deviation from a documented control, while your operations team might use the same word only for a formally logged incident. If you answer using your own guess at the definition, you can accidentally confirm something that was never confirmed, or deny something you have no basis to deny.

The pressure comes from timing. Reviewers want an answer now, and a pause feels like an admission. Rushing to fill that silence with a reassuring answer is the real danger here. You are not equipped to decide whether an internal review item qualifies as a control failure, and pretending otherwise puts words in your legal and operations teams' mouths that they may not be able to support later in writing. The same dynamic shows up when a reviewer uses an unfamiliar operational term in an RFP portal question, which is worth reading about separately in When an RFP Portal Uses an Unfamiliar Operational Term. In both cases the fix is the same. Stop, define the term, and route the question before you respond.

Prepare Before the Reviewer Asks

Before you sit down with any reviewer, know what open items exist and who owns each one. Ask operations, legal, and compliance for a short list of anything currently under internal review that could plausibly surface in due diligence. You do not need the substance of each item. You need the name of the owner and a sense of how long their review typically takes, so you can set a realistic deadline when a question comes in.

Build a response template that separates three categories clearly. First, facts that are already verified and approved for external use. Second, items still under internal review that cannot be characterized yet. Third, items that require a discussion outside the written RFP process entirely, such as a call with compliance. Confirm in advance who signs off on the final wording before it goes back to the reviewer, so you are not guessing under time pressure. This kind of upfront coordination is the same discipline described in Building a Nonstandard Performance Exhibit for an RFPwhere the lead also has to gather approved material from the people who actually hold it rather than assembling it alone.

What to Say When the Question Comes

The reviewer asks, "Does this remediation item mean your controls failed?"

You say, "I cannot characterize an item that is currently under internal review. What I can do is confirm the exact definition you are using for exception, and get approved wording from our operations and legal owners. Can you tell me what period this covers and whether you need a public statement, a written control response, or a separate discussion with our compliance team?"

The reviewer answers, "We need a written response covering the last twelve months, consistent with our standard control questionnaire."

You say, "That is clear. I will route this to operations and legal today with that exact wording and get you a response within three business days. If they need more time, I will tell you before the deadline passes, not after."

Notice what this exchange does. It never denies, never confirms, and never guesses. It asks for the definition instead of assuming one. It gets a concrete scope, a period, and a format, so the people who actually own the facts can respond to something specific. And it sets a date, which turns an open ended worry into a tracked commitment.

Mistakes to Avoid

The most common mistake is defensive denial. Saying "our controls did not fail" before you know the facts can contradict what operations later confirms in writing, and that gap damages credibility far more than a delayed answer ever would. The second mistake is oversharing. An anxious lead sometimes fills silence with internal detail, timelines, or names that were never cleared for external use, because it feels like proof of good faith. It is not. It is a confidentiality breach.

The third mistake is treating the reviewer's wording as fixed. If they say exception and you assume you know what they mean, you might answer a question they never asked. Always get their definition in their own words before you route anything. The fourth mistake is silence without a plan. Telling a reviewer "I will get back to you" with no date attached reads as avoidance. A dated commitment reads as process.

Last, do not let the response plan blur verified fact and internal detail into one paragraph. Keep them visibly separate in the draft, and name who approves the final version before it goes out. That approval step is not bureaucracy. It is what keeps you from submitting language your legal team cannot stand behind later.

Practice the Exchange and Score It

This is a conversation worth rehearsing before it happens for real, because the instinct to reassure is strong and hard to unlearn in the moment. Have a rep answer a loaded question with deliberately limited facts, the same way the exchange above starts. Watch whether they deny, guess, or hold the line and ask for the definition instead.

A manager scoring the exercise should check for four things. Did the rep avoid characterizing the item without authority. Did the rep extract a clear definition, period, and format from the reviewer. Did the rep set a specific date rather than an open ended promise. Did the rep name who internally needs to approve the final wording. A rep who does all four while still sounding calm and cooperative, not cagey, has handled it well. DealSpeak's scored role play exercises are built for exactly this kind of pressure test, and the Asset Management practice conversations library has more scenarios drawn from actual RFP and due diligence situations.

This conversation is won or lost in the first ten seconds, before any facts are exchanged. Hold the boundary, get the definition, set the date, and let the people who own the facts answer with the facts. Do that consistently and reviewers learn to trust your process even when the answer takes a few days to arrive.