Building a Nonstandard Performance Exhibit for an RFP

A prospect's RFP asks for a performance exhibit that does not match anything your firm has ever published. Maybe the periods are odd quarters instead of full years. Maybe the return basis is different from your standard booklet. Maybe the template splits a composite into pieces nobody has approved separately. It looks like a formatting task, something a spreadsheet and a free afternoon can solve. It is actually a data governance task, and treating it like the first one is how RFP leads end up submitting numbers nobody at the firm can stand behind.

Why This Conversation Goes Wrong

The pressure comes from the calendar, not the math. A submission deadline sits three days out, the consultant analyst on the other end wants a fast answer, and you have a spreadsheet with annual returns that could, in theory, produce something close to a quarterly series. Close is the problem. Performance numbers in an RFP are not illustrations, they are representations a prospect can hold you to later, sometimes years later if the mandate gets awarded and someone audits the pitch materials against actual results.

RFP leads often treat the performance team as a bottleneck rather than a safeguard. That instinct makes sense when every other section of the response is under your control and this one depends on someone else's calendar. But the performance and compliance review exists precisely because a plausible number is not the same as a verified one. A quarterly figure derived from an annual return uses assumptions about the pattern of gains and losses within the year that nobody has checked. Present that as fact and you have created a number the firm cannot reconcile if the prospect asks for the underlying calculation later.

Prepare Before You Respond

Start by reading the request closely, not skimming it. Note the exact period end dates, the return convention, whether the benchmark is required, whether the figures should be gross or net of fees, and whether the portal specifies a template format. Then put that specification next to your approved performance booklet, line by line. If every element matches, you can use the approved table as is. If anything differs, even a single period end date, you have a gap that needs to go to the owner of performance data, not a gap you fill yourself.

Write the gap down before you contact anyone. A vague request like "can you get me quarterly numbers" travels slower through a performance team than a precise one. Specify the exact periods, the calculation basis, and the benchmark, then send that specification along with the submission deadline and a note that compliance review is required before release. Performance teams often work from a queue, and a well specified request with a real deadline moves differently than an open ended one.

If you are unsure whether a term in the portal or the RFP document means what you think it means, treat that uncertainty as its own task rather than guessing. The article on When an RFP Portal Uses an Unfamiliar Operational Term covers how to resolve that kind of ambiguity before it becomes a wrong answer baked into your exhibit.

What to Say When the Pressure Is On

Picture the consultant analyst pushing for speed. They ask, "Your booklet only has annual figures. Can you back into the missing quarters from those?"

You say, "No, and I want to explain why rather than just declining. Backing into quarterly numbers from annual figures assumes how gains and losses were distributed across the year, and that assumption isn't verified. If I hand you a derived number and it turns out to be wrong once our performance team checks it, that's worse for your evaluation than a short delay now. Can you confirm the exact period end dates and whether you need gross or net of fees? Once I have that, I'll send it to our reporting team and get you a reviewed figure."

The analyst replies, "We need quarter end dates for the last three years, net of fees, versus the benchmark listed in section four."

You say, "Got it. I'll log that and get it moving today. Given our review process, expect the verified table by end of day Thursday. I'll flag you immediately if anything in the request turns out to conflict with how we're able to report."

Notice what that exchange does. It refuses the shortcut without being defensive about it, it turns a vague ask into a specification the performance team can actually execute, and it commits to a timeline instead of leaving the analyst guessing. That last part matters. Analysts who hear "no" without a plan attached start to wonder if your firm can execute at all. Analysts who hear "no, and here is exactly what happens next" read that as discipline, not delay.

Mistakes That Undermine the Exhibit

A few patterns show up again and again in weak responses to this kind of request. First, calculating the missing figures yourself and presenting them as final, rather than as a placeholder pending review. Second, reusing an older approved exhibit because it looks similar, when the periods, return definitions, benchmark, or disclosure basis have actually changed. Third, sending a vague request to the performance team and hoping they infer the specification, which usually produces a second round trip and burns days you do not have. Fourth, forgetting to log the request and its owner in your response tracker, which means nobody notices if the reviewed data never comes back before the deadline. Fifth, treating a late change in requested format as a small edit rather than a new data request that needs its own review cycle.

That last one deserves its own mention because it happens often. A prospect revises the RFP template two weeks in, asking for a different cut of the same performance history. It feels like a small tweak. It is not. Any change to periods, calculation basis, benchmark, or disclosure triggers the same approval process as the original request, even if it looks like a cosmetic change from where you sit.

Practicing and Scoring This Conversation

A manager running a team drill should put a misleading table in front of the RFP lead, something like annual returns paired with a request for quarterly history, and watch what happens next. The score is not how fast someone produces a number. The score is whether the lead identifies the actual data definition being requested, resists the temptation to derive or estimate, and builds a timeline that leaves room for performance and compliance approval before the exhibit goes out the door.

This is also a good scenario to rehearse before it happens live with a client. DealSpeak's Asset Management practice conversations let an RFP lead run this exact exchange against an AI counterpart playing a pushy consultant analyst, then get scored on whether they held the line on verified data, asked for the right specifics, and communicated a realistic timeline instead of a vague promise. If the request also involves a new reporting commitment you have not made before, the piece on Coordinate Approval for a New Reporting Commitment in an RFP Addendum walks through how to get that approved without stalling the whole submission. Running the scenario a few times with DealSpeak before it shows up in a real deal builds the habit of separating a formatting request from a data governance one, which is the actual skill this situation tests.

The Bottom Line

A nonstandard performance exhibit is a test of judgment, not spreadsheet speed. Slow down enough to define the request precisely, route it to the people who can verify it, and tell the prospect exactly when they will have a number they can trust. That approach costs you a few days now and saves the firm from defending a figure it never actually checked.