Keeping Team Biographies Accurate in an Asset Management RFP

A team biography looks like a formality until a prospect's investment committee reads it line by line and finds a claim that does not match the portfolio manager's actual record. Then it stops being a formality and becomes a compliance problem, and it lands on the RFP lead to explain. Getting the biography right takes more than copying last quarter's version into a new template. It takes a workflow you can defend if someone asks where a number came from.

Why This Conversation Goes Wrong

RFP coordinators pull requested fields directly from a prospect's questionnaire, and questionnaires often ask for things your approved materials do not track the same way. A coordinator might ask for ten years of experience with a strategy when your compliance approved bio describes the manager's tenure differently, counting time at the firm rather than time on the strategy, or counting a start date after a transition period. The mismatch is rarely deliberate. It happens because nobody owns the translation between what the prospect wants to hear and what your firm can actually verify.

The RFP lead usually feels pressure to fill the field and move on. The deadline is real, the coordinator is waiting, and a blank field looks worse on the page than a rounded number. That pressure is exactly what produces embellished bios, because a lead under time pressure will estimate rather than confirm. A biography is not a marketing paragraph. It is a factual statement about a specific person that a prospect can hold you to during due diligence or a live reference call.

How to Prepare Before the Coordinator Sends the Request

Build your defense before the request lands, not after. Start by mapping every biography field a prospect commonly asks for to the document that proves it. Tenure at the firm, tenure on the strategy, credentials, prior roles, and any performance attribution language should each trace back to an approved source with a date attached. If a portfolio manager changed roles in the last two quarters, flag that biography for review before it goes into the response library, so nobody pulls a stale version by accident.

Know who owns each type of change before you need them. Compliance usually owns credential language and disclosure requirements. The business unit or the individual's manager usually owns role history and responsibility descriptions. Someone in leadership owns any statement about who will service the account going forward, because that is a commitment, not a biography. Write down these owners now. Chasing them during a live RFP costs days you do not have.

Decide in advance what you will do when no approved source supports what the prospect asked for. The answer is not to guess. The answer is to use the wording your materials already support, or to ask the prospect's process for clarification on what they actually need. That is the position the next section will practice.

What to Say When the Biography Doesn't Match the Request

Here is how that conversation can go. The coordinator says, "Please include the lead portfolio manager's history with the strategy over ten years, that is what the prospect is asking for."

You check the current approved biography and see it describes the manager's tenure at the firm, not tenure on this specific strategy, and the numbers do not line up. You say, "The approved bio measures tenure at the firm, not tenure on this strategy, and I do not have a source that supports ten years on the strategy itself. Let me check with the portfolio owner and compliance before we submit anything."

You go to the portfolio owner and compliance and ask directly, "Which approved source supports the requested history, and how should we describe the role transition if the manager moved onto this strategy partway through that period." If they confirm a shorter, accurate number, you return to the coordinator with that number and an explanation, not an apology. You say, "The manager has been with the firm for the full period, but joined this specific strategy three years ago. I can offer that language, or we can note the full history and be specific about the strategy tenure separately. Either way, this is what we can defend if the prospect asks in diligence."

That last line matters. You are not just filling a field. You are giving the coordinator language your firm can stand behind if a due diligence call goes deep on the manager's background.

Mistakes That Turn a Biography Into a Liability

Do not add flattering adjectives that no document supports. Words like exceptional or seasoned are not facts, and a careful reviewer will cut them anyway, so do not waste time writing them in the first place.

Do not round up. A manager with eight and a half years on a strategy is not a ten year manager, and rounding in your favor is the kind of small choice that looks bad the moment someone checks it against a public record.

Do not describe future staffing as current fact. If the RFP asks who will service the account after the mandate is won, that is a staffing commitment, not a biography, and it needs sign off from whoever can actually make that promise. Route it separately.

Do not skip the paper trail. For every biography field in a live response, record the requested field, the source document, the date the source information applies to, the reviewer who confirmed it, and any exception you had to make. If someone asks six months from now why a bio said what it said, you want an answer that takes thirty seconds to find, not a reconstruction project.

Do not assume the coordinator understands the risk. Coordinators are often measured on completing the response, not on defending it later. Part of your job is to explain, briefly and without lecturing, why a specific field needs a source before it goes out.

How to Practice and Score This Conversation

This is a conversation worth rehearsing before it happens under deadline pressure. Set up a scenario where a coordinator asks for a biography detail that your approved materials do not directly support, and practice the exchange out loud. Notice whether you reach for a plausible number or whether you stop and name the gap first.

A useful exercise for a team is a red team review before final assembly. Give reviewers two versions of the same biography, one that matches the approved source and one with a small unsupported change, and ask them to find the difference and trace it to an owner. Score how quickly they catch it and whether they know who to ask. This kind of drill works because a short profile can carry a large representation, and the habit of checking is worth building before a real RFP is due.

DealSpeak's Asset Management practice conversations let an RFP lead rehearse this exact exchange with an AI coordinator, get pushed on vague answers, and see where the response would fall apart under scrutiny. For related ground rules on what you can claim about your firm more broadly, see Describe Firm Capabilities in an RFP Using Only Verified Facts. And if you want to see how this same discipline about verified facts carries into the relationship that follows, look at Plan an Annual Client Review Around Board Questions.

Treat every biography as a claim you may have to defend in a room with the prospect's board. Build the source map first, know the owners, and practice saying "let me confirm that" instead of guessing. That habit protects the whole submission, not just one paragraph.