Planning an Asset Management RFP Award Debrief

An award notice from a prospect closes one RFP cycle, but it also opens a chance to fix real problems before the next one starts. Losing a mandate stings, and plenty of RFP leads let the file close without asking a single question afterward. That is a mistake. A short, respectful debrief conversation with the procurement officer or search consultant can tell you exactly where your proposal lost ground, as long as you ask for it the right way and stay inside the boundaries the prospect sets.

Why the debrief conversation goes wrong

Most RFP leads either skip this conversation entirely or handle it badly. Some skip it because losing feels personal, and picking up the phone to ask why feels like reopening a wound. Others request the debrief but treat it as an appeal, pushing the officer to reconsider or defending each section of the proposal point by point. That approach burns the relationship and guarantees the officer gives you nothing useful next time they run a search.

A third failure mode is asking for information the prospect cannot legally or ethically share. Scoring sheets, evaluator names, and details about the winning firm's pricing or team are usually protected, especially for public plans bound by procurement rules. Asking for them puts the officer in an awkward position and marks your firm as one that does not respect process. None of these failures come from bad intent. They come from treating the debrief as a chance to win the deal back instead of a chance to learn something for the next one.

How to prepare before you ask

Start by checking the prospect's stated procurement process. Public pension plans and many institutional searches spell out whether a debrief is available and what form it takes, a written summary, a short call, or nothing at all. Do not ask for more than the process allows. If the process is silent, a brief written request is fine, something close to what one lead sent after a municipal plan search, "Thank you for the opportunity to participate. If your process allows a debrief, we would value high level feedback on our response and presentation."

Before any call happens, decide internally what you actually want to learn. Vague requests get vague answers. Write down three or four specific questions about clarity, completeness, or how your team came across in finals, and drop anything that sounds like you are fishing for confidential detail. Align your internal team ahead of time on how any feedback will be used and who owns follow up on each theme. And prepare yourself to hear something unflattering without getting defensive on the call. The officer is doing you a favor by talking at all.

What to say during the call

Keep your opening short and let the officer set the pace. One lead started a scheduled debrief this way, "We appreciate you making time for this. I have a few quick questions about how our submission came across, nothing about the winning firm or your internal scoring."

When the officer offers something general, like "Your team was strong, but a couple of sections were harder to evaluate than others," resist the urge to ask which firm won or what they offered instead. Stay on your own submission. A useful follow up sounds like, "That's helpful. Which part of our written response was hardest to evaluate, and was it the content or how we presented it?"

If the officer gives a concrete answer, for example, "Your operational due diligence section read more like a checklist than a direct answer to our questions," write it down word for word and thank them without arguing the point. You can close with something forward looking rather than defensive, "That's good to know. We'll take a hard look at how we structure that section going forward." That sentence costs you nothing and leaves the door open for the next search this officer runs.

Mistakes to avoid

Do not challenge the outcome or ask the officer to justify the decision. The award is final, and arguing only confirms you cannot take feedback well. Do not request protected scoring records, evaluator notes, or details about the winning firm unless the formal process explicitly provides them. Do not treat one debrief as the full truth. A single officer's comments are one data point, not a verdict on your entire proposal process, so record what was said as a direct quote and separate it clearly from any internal guesses about what it means.

Do not let the feedback sit in a shared inbox and die there. Assign each usable point to an owner, whether that is your content library, your evidence gathering process, your presentation preparation, or how your team qualifies opportunities before committing resources. Set a date for each owner to report back. And if the prospect declines a debrief outright, accept that answer immediately and keep the relationship warm for the next cycle rather than pushing for a reason.

How to practice and score it

This conversation is easy to get wrong live because it mixes disappointment with the need to sound calm and professional. Rehearse it before the real call happens. Practice a debrief role play against a procurement officer persona who offers limited, somewhat vague feedback, and force yourself to ask sharp follow up questions without arguing or fishing for protected information. DealSpeak's Asset Management practice conversations include this scenario alongside related RFP moments, so you can run it as many times as you need before it counts for real.

A manager can score the resulting debrief note against three things, direct quotes from the officer kept separate from internal interpretation, clearly labeled assumptions rather than facts stated as certainty, and named owners with dates attached to each action item. If your team also struggled to get straight answers earlier in this same RFP, the piece on Use an RFP Clarification Call to Find the Real Decision Criteria covers how to ask sharper questions before scoring happens instead of after. And if the debrief points to weak evidence rather than weak writing, Building a Verified Response to an RFP Business Continuity Question shows what a properly sourced answer looks like, which is often the gap officers are describing without naming it directly.

What a good debrief does for you next time

A loss with no debrief teaches you nothing. A loss with a respectful, well prepared debrief hands you specific, sourced feedback you can act on before the next search lands on your desk. Ask for it inside the rules, keep the conversation on your own submission, and turn whatever you get into owned, dated work instead of a note nobody reads again.