Build an Evidence Register Before Writing an Asset Management RFP

An RFP response falls apart during review, not during writing. Someone flags a claim about daily reporting or compliance monitoring, nobody can say where it came from, and the deadline is two days away. This is the moment an evidence register would have prevented, and building one before you touch the RFP form is the actual skill an RFP Lead has to practice.

Why This Conversation Goes Wrong

Most teams treat an RFP as a writing exercise. They open last year's response, copy the language that sounds right, and adjust the dates. Nobody stops to ask whether the underlying fact still holds. The investment process changes. Operations swaps systems and reporting platforms. A statistic in the firm overview goes stale within a year. When the RFP Lead does not force this question at the start, the team edits prose instead of verifying facts, and the response ends up stronger on style than substance.

The conversation goes wrong because it usually never happens. A writer pulls an old answer, assumes it is current because it sounds confident, and moves on. The lead who tries to catch this after the draft is finished is fighting an uphill battle. By that point the team has emotional investment in the language, and questioning a claim feels like questioning the writer, not the fact.

How to Prepare Before the Working Session

Build the register before anyone drafts a single sentence. For every question in the RFP, write down what fact is actually being asserted. Separate claims about the investment process from claims about firm statistics, operations controls, and legal representations. Each category has a different owner and a different standard of proof.

For each entry, record the verified source document, the internal owner who can confirm the fact is current, the date the information applies to, and the approval required before the answer goes final. This does not need special software. A shared spreadsheet works, as long as every writer treats it as the only place facts get sourced from, not a suggestion.

Send the register to section owners before the working session, not during it. Ask them to fill in what they can and flag what they cannot. A blank field is useful information. It tells you where the risk sits before a client ever sees the answer.

If fee or scope language shows up in the register, treat it with extra care. A separate piece on how to Clarify Assumptions About the Fee Schedule Before Completing an RFP Form covers how easily a general fee description turns into a commitment nobody meant to make. The same discipline applies here. A capability that exists in general does not mean it exists for this prospect's requested structure.

What to Say When a Source Is Missing

The working session is where the register earns its keep. A writer reaches for last year's answer because it is fast and familiar. Your job is to stop that reflex out loud, every time, without making it personal.

The writer says, "Last year's response says we provide daily position files, so I will reuse that line." You ask, "Who owns that claim now, and what is the current specification." The writer does not know. You say, "Then we do not use it yet. Assign it to operations and ask for the current format list before we draft this answer."

Operations comes back and says daily files are available, but only in two defined formats, and only for accounts on the current reporting platform. You say, "That is the answer. We state the two formats and the platform condition, and we offer to walk through implementation details if the prospect asks." The writer pushes back a little. "That sounds weaker than what we said last year." You answer plainly. "It is more precise, not weaker. A specific true statement holds up under diligence. A general one falls apart the moment someone asks a follow up question."

That exchange is the whole method. Name the claim, find the owner, get the current fact, write the precise version. Repeat it for every material statement in the response.

Mistakes That Undermine the Register

The most common mistake is building the register and then not using it. A lead sets it up, section owners fill in a few fields, and then the drafting happens in a separate document with no link back to the source. The register becomes a record of good intentions instead of a control.

Another mistake is letting a blank field sit unassigned. If nobody owns an unresolved fact, it stays unresolved until someone notices during final review, and by then the fix is rushed. Assign an owner the moment a gap appears, not the week before submission.

A third mistake is confusing a general capability with a contractual promise. A system can do something in principle for some clients and still not be available for the structure this prospect is requesting. Writers under deadline pressure round up. The lead's job is to round back down to what is actually verified for this specific request.

Do not let seniority substitute for a source. A senior partner asserting a fact confidently is not the same as a document proving it. Ask for the source anyway. It protects the partner as much as it protects the firm.

How to Practice and Score This Conversation

This is a conversation skill as much as a documentation skill, and it holds up better when you rehearse the exact moment a writer reaches for a stale answer. A manager reviewing an RFP Lead should listen for three things. Does the lead name the specific claim being asserted instead of letting a vague summary pass. Does the lead ask for an owner and a source before allowing language into the draft. Does the lead hold the line when a writer pushes back, without turning the correction into a criticism of the person.

Score a practice run on whether unresolved claims stayed visible or got buried. A good outcome is a register with every blank field assigned to someone, even if not every field is filled by the end of the session. A poor outcome is a draft that reads smoothly but rests on claims nobody can trace back to a source.

DealSpeak's Asset Management practice conversations let an RFP Lead run this exact scenario against an AI counterpart playing a writer under deadline pressure, then get scored on whether every claim got traced to a source before it reached the draft. Once the register habit is set, pair it with a check at the other end of the process. A companion piece on how to Run a Final RFP Review That Tests Evidence, Consistency, and Commitments covers what to test right before submission, when the draft is complete and the last chance to catch an unsupported claim is closing fast.

An evidence register will not write the response for you. It will stop your team from mistaking a familiar sentence for a verified fact, and that difference is what a client's diligence team actually tests.