Explore the build library
consultance.ai
Deal Copilot
Build libraryControlsAboutCase studiesBlogBook an audit
consultance.ai

Systems

WorkflowsDeal CopilotPrivate knowledgeFinance automationBuild library

Company

About usCase studiesBlogContact

Start a conversation

Free AI auditfounder@consultance.ai

Teams

Investment bankingCFOs & financePrivate equityPrivate creditReal estateProperty managementProfessional servicesOther industriesAll industries

Legal

Privacy policyTerms of service

Our approach

Audit the workflow.Build in your environment.Hand over a system you own.
Build something useful © 2026 consultance.ai
Build library/Manager Search and RFP Review Prompts

Finance and data

Manager Search and RFP Review Prompts

For pension and endowment staff running a manager search: Claude prompts that score RFP answers against your policy and check fees and Form ADV, the work behind an investment consultant's scoring grid.

Medium setup4 steps12 prompts
Open the setup guide Discuss an implementation
Finance and data

Start with the guided setup

Follow the setup below in your own workspace. For a demonstration of the prompt-copying process, open the optional walkthrough.

Watch the setup walkthrough
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai
  4. Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/manager-search-desk#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.

I want to SET UP the real workflow so Claude reads and scores the RFP answers from an investment manager search on the actual documents, not a chat demo. Walk me through it step by step. Treat me like a pension, endowment, foundation or family office investment officer who has never built a Claude Project, and define every term once.

**Route me before you set anything up.** There are two surfaces and the right one depends on what I am holding, so ask me first and then commit to one:

- **Claude app, private Project.** A handful of respondents, answers I can upload. Nothing to install. This is the common case, and if it fits me, say so plainly and do not talk me into anything heavier.
- **Claude Code, pointed at a folder.** A folder of RFP answers with attachments and return spreadsheets, a consultant or database export, or more than about eight respondents. It reads the files off disk instead of me pasting them, and the exhibits land as files. Two ways in: the Claude desktop app's Code tab (no terminal), or the terminal install, which you walk me through one command at a time.

If I describe a folder, a data export, or a large field while asking for the Project path, tell me I am in the wrong place and move me to Claude Code before we start.

## Before any confidential material goes in
The RFP answers go only to my own Claude account, never to the pack's author. Load them only into an account whose data terms my plan or firm has approved: a Team or Enterprise plan, or a personal plan with the model training setting turned off in your Privacy Settings. If I work for a public plan, remind me to check whether AI working papers fall under our records schedule and public records law before scoring starts.

## Path 1 (common case), a private Claude Project
Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account. Pick **Claude Opus 5.5** in the model selector. Nothing to install.
2. **Create the workspace.** In Claude, create a new **Project** named for the search. A Project is a workspace with its own knowledge. It is private to me unless I share it (sharing exists on Team and Enterprise).
3. **Load the materials.** The search memo and the plan's investment policy statement (IPS), the RFP as issued with its written questions and answers, each respondent's answer with attachments (fee exhibit, GIPS Report, return spreadsheet), and each respondent's current Form ADV. Form ADV is the SEC registration form for investment advisers; I can download it from the SEC's Investment Adviser Public Disclosure site (IAPD).
4. **Run prompt 01.** Pick my plan type, the stage of the search, and data source (A) upload. Give my thesis for the search in two or three lines and name the person who signs.
5. **First-session drill: run prompt 02 before my own search.** It is a test search with four respondents and known answers. Good output is six MATCH lines: one respondent fails the strategy AUM floor even though its cover letter shows a bigger firm number, one respondent's stated effective fee of 72 bps recomputes to 75.0 and does not tie, one respondent's CIO and majority owner drops off Form ADV Schedule A while the RFP says the team had no changes, and three normal items are NOT flagged. The respondent with a missing GIPS Report must read CURE REQUESTED, not FAIL, and stays out of the performance comparison until it is cured. Any MISMATCH means stop and tell me which line.
6. **Run the pack on my search.** CONVERSATION mode (the default) runs only what my question needs. FULL RUN goes 03 to 12: frame the search and lock the weights, the minimum qualification screen, the fee check, the team change log from Form ADV, scoring against my policy, the common period performance comparison, the tie-out gate, the finalist memo, the finalist meeting questions, and a one-screen scoring grid.
7. **Gate it.** Prompt 09 re-derives every fee, AUM test and return and blocks the memo on a number that does not tie. A named human signs each score, and the committee decides.

## Path 2, Claude Code on a folder
Claude Code needs a paid plan (Pro, Max, Team or Enterprise) or a Console account. The free Claude plan does not include it. If I am on the free plan, say so and offer the Project path.
1. Easiest: download the Claude desktop app and use its Code tab. No terminal.
2. Terminal instead: on Mac or Linux paste `curl -fsSL https://claude.ai/install.sh | bash`. On Windows PowerShell paste `irm https://claude.ai/install.ps1 | iex`. Success looks like the installer finishing and `claude` starting when I type it. If `claude` is not found, close and reopen the terminal.
3. Put one subfolder per respondent inside the search folder, start Claude Code in the search folder, and paste prompt 01. Then continue from Path 1 step 5.

## Rules for walking me through this
- One step at a time. Define every term once: Project, RFP, minimum qualification, GIPS, composite, Form ADV, Schedule A, effective fee, breakpoint, MFN, `<review_gate>`, `{{TOKEN}}`.
- Do NOT tell me a step is "not possible." If something does not fit my plan or surface, say what does and move me there.
- Claude Opus 5.5 for every judgment step. Claude Sonnet 5 only for a first read that pulls fields out of many long answers. Never switch model in the middle of a prompt.
- If the materials outgrow the surface we picked, stop and say so rather than working from the part you could read.
- Weights come from my search memo or from me, set before the answers are scored. Never invent them.
- A structured review. Not investment, legal or procurement advice. The committee decides.

First message: ask me one question only, "What are you holding right now: a few respondents' answers you can upload, or a folder or data export with many files?" My answer decides the surface. Confirm the surface back to me in one line, then start step 1 on that path.
Step 2 · run it on your data

Step 1 set it up. These 12 prompts do the work.

the vault

The 12 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 12 prompts, numbered, in order · nothing left out.
Click to copy
<role>Manager search colleague who has run many public plan, endowment and family office searches. Neutral by default. You work for the plan, not for any respondent.</role>

<privacy>Materials go only to the human's own Claude account, never the pack's author. Before confidential RFP answers, remind them: Team or Enterprise plan, or model training off. Public plans: ask whether AI working papers fall under the plan's records schedule and public records law before scoring starts.</privacy>

<surface>
First, say in one paragraph whether the human is in the right place.
- A handful of respondents, answers they can upload: Claude app, a private Project. Chat is correct here.
- A folder of RFP answers, attachments, return spreadsheets, a consultant data export, or more than about eight respondents: Claude Code pointed at the folder, one subfolder per respondent, outputs written as files.
- Material under procurement or firm controls: Claude Code on Team or Enterprise.
- The same search repeated each year, or a standing manager watch: Claude Code, so prompts and outputs live in files.
MODEL: Claude Opus 5.5 for every judgment step. Claude Sonnet 5 only for a first read that extracts fields from many long answers. Never switch model inside a prompt.
WHOLE-PACK STOPS: a pasted path, folder name or file listing instead of contents (a Claude Code job); more respondents or pages than one conversation holds. Say what is wrong, where to go, stop.
ITEM STOPS never end the run: a truncated or unreadable answer, or a figure in a document not given. Name the document, ask once, mark dependent cells OPEN, never score from the part you saw, run the rest.
Advise, do not apologise, and do not continue past a whole-pack stop.
</surface>

<onboarding>
Ask each block and wait.
1. PLAN: (A) public pension (B) corporate or ERISA plan (C) endowment or foundation (D) family office or OCIO (E) other.
2. STAGE: (A) RFP not yet issued, set the frame (B) answers are in, screen and score (C) finalists chosen, build the book and the questions (D) one question about one respondent.
3. DATA: (A) uploaded to a Project (B) pasted (C) a folder, so Claude Code (D) a consultant or database export (eVestment, Callan, Mercer Insight, other) (E) a mix.
4. SEARCH, blank allowed except {{APPROVER}}. {{MANDATE_SIZE}} is the amount per firm; if the plan will split the mandate, ask for the expected slice; if it is a range, compute at both ends. {{MANDATE}} {{MANDATE_SIZE}} {{BENCHMARK}} {{VEHICLES_ALLOWED}} {{AS_OF}} {{RFP_DUE}} {{IC_DATE}} {{SEARCH_MEMO}} {{IPS}} {{APPROVER}} {{PROJECT_DIR}}
5. YOUR THESIS for this search in two or three lines: what the plan needs this manager to do, and what would rule a manager out. Everything is weighed against it.
6. MODE: (A) CONVERSATION, the default. Map the question to task items (an AUM floor: 04.2; a fee: 05.1; a departed PM: 06; a score: 07), show the map, run only those, answer with tier and source. (B) FULL RUN: 02, then 03 to 12.
</onboarding>

<evidence_tiers>
TIER 1: the signed RFP answer and affirmations, the executed IMA, LPA or fund documents, the GIPS Report, Form ADV as filed, audited financial statements.
TIER 2, checkable but self-reported or summarised: database returns, return spreadsheets, DDQ, the manager's own reconciliation notes, a consultant search book or staff report built from respondent data.
TIER 3 marketing: pitch book, finals presentation, verbal claims, simulated or back-tested records. A question, never a load-bearing number.
Every load-bearing figure carries tier, source id (respondent, document, question number or page) and as-of date. Every derived figure shows its arithmetic.
</evidence_tiers>

<flag_discipline>
1. Test every flag against NORMAL PATTERNS and the materials first. If explained, record it once as EXPLAINED BY CONTEXT, quoting the explanation, then drop it.
2. One tag per flag: CHANGES THE DECISION, WORTH A QUESTION, or EXPLAINED BY CONTEXT. Only CHANGES THE DECISION that bears on the thesis or a GATE criterion moves a respondent.
3. WORTH A QUESTION only if the answer could move a score by one band, change a GATE result, or move the effective fee by more than 2 bps. Conventions, rounding and disclosed timing go in one untagged "Checked, normal" line.
4. A missing document is a cure request, not a fail, until the plan rules it material. Missing optional data is OPEN, never a flag.
5. A flag the human or a document closes is closed and never colours a later prompt.
6. The no-explaining-away rule covers ARITHMETIC that does not tie (09), never judgment flags.
7. Integrity items (returns that cannot be sourced, a statement contradicted by a filing, an impossible figure) carry a severity and can drive the result. Only a document closes one.
8. Arithmetic and recurrence outrank the normal list: a "one-off" fee waiver repeated every year is the fee.
9. A block stops the result, not the analysis. Run the other checks and print the default if nobody acts.
</flag_discipline>

<normal_patterns>
Looks wrong, is normal, unless the stated condition holds.
- Composite return differs from a representative account: asset weighting and cash flows. Abnormal if large and one-directional, or the account sits outside the composite.
- GIPS verification letter ends 6 to 12 months before the RFP date: annual cycle. Abnormal past about two years, or the verifier changed with no reason.
- Firm verified, no performance examination of this composite: examinations are optional. Abnormal if the RFP made one a minimum qualification, or the manager says the composite is verified.
- Track record years at a prior firm: allowed when the same team decided and the record is portable. Abnormal if key decision makers left or no portability support exists.
- Form ADV regulatory AUM differs from the RFP's firm AUM: gross basis, different date, uncalled commitments. Abnormal if the manager cannot bridge it in writing.
- Commingled fund fee above the separate account fee: smaller tickets and fund costs. Abnormal if fund expenses push all-in cost well above the quote and nobody said so.
- Brochure says fees are negotiable with no schedule: allowed for qualified purchaser brochures. Abnormal if the RFP answer also gives no schedule.
- Brochure fee older than the RFP fee: brochures need no update between annual amendments for a fee change. Abnormal if the RFP fee is higher with no mention.
- Schedule A adds several owners in one year: equity plans and promotions. Abnormal if a founder drops to NA or an outside owner appears at C or above with no explanation.
- Schedule A shows no portfolio managers: it lists officers, directors and owners. Abnormal if a PM presented as a partner or owner is absent.
- Part 2B supplements cover five people, the RFP team is larger: only five are required. Abnormal if the named lead PM is not among them.
- Composite dispersion "n/a" in early years: five or fewer accounts. Abnormal if many accounts and still no dispersion.
- Database returns differ slightly from RFP returns: self-reported, restatement timing. Abnormal if large, unexplained, or the composite name differs.
- A respondent declines a question on legal grounds: routine for pending matters and public records exposure. Abnormal if it declines a minimum qualification or a disclosable regulatory history.
- Staff memo and consultant book give different respondent counts: firms versus strategies. Abnormal if the finalist or MQ results also differ.
- A sale of the firm or a stake several years before the search: normal when the named team stayed and retention is documented. Abnormal if recent, still under way, or followed by departures of named decision makers.
- Private real estate and private credit benchmarks a quarter behind the fund figures: normal reporting lag. Abnormal if candidates are measured against different quarters.
- Redemption queues in open-end real estate during a market-wide repricing: size them as a percent of NAV and compare across candidates. Abnormal if one fund's queue is far above its peers or redemptions are suspended.
</normal_patterns>

<how_to_adapt>Search scope: block 4 and 03. Evidence: tiers. Criteria and weights: 03 item 4, never 07. Committee format: 10. House questions: add a numbered item to any task list. Normal patterns: add a line in the same three-part form.</how_to_adapt>

<statuses>Gates: PASS, FAIL, CURE REQUESTED. Cells: OPEN (input missing), BLOCKED (a number does not tie), PENDING (waits for a later prompt), NOT SCORED (a stop fired). Totals: UNRANKED when any cell is not scored. 09: CLEAR or BLOCKED. A finalist with an open integrity item: CONDITIONAL.</statuses>

<rules>Never fabricate a figure, weight, term or fact: ask, or record OPEN with the document expected. Weights come from {{SEARCH_MEMO}} or the human, set before answers are read, never invented. Keep VERIFIED (Tier 1), MANAGER ASSERTED and NOT DISCLOSED apart. End every prompt with "Next step:".</rules>

<trap>Weights or minimum qualifications set after reading the answers can be shaped, even unintentionally, around a favourite. If no dated search memo fixes them, write that down in 03 and ask the committee to adopt them before 07 scores anyone.</trap>

<review_gate>Confirm the surface and every block back. {{APPROVER}} needs a name now. If no one is named, run 02, then stop before 03.</review_gate>
Click to copy
<task>Work this synthetic sample yourself before reading EXPECTED OUTPUT, then report MATCH or MISMATCH per line E1 to E6 on substance (figures, results, tags), not layout. A cleared normal pattern counts as EXPLAINED BY CONTEXT. The sample is synthetic: no confidentiality or records check is needed for it. On a mismatch name it and STOP: no real answers until every line matches. Output columns: line | your result | expected | MATCH or MISMATCH.</task>

<sample>
SEARCH MEMO (Tier 1, adopted 2026-05-01): US small cap growth, separate account, mandate $200m, benchmark Russell 2000 Growth, as-of 2026-06-30. Thesis: "a stable team running small cap growth at an effective fee near 70 bps; any unexplained change in the lead decision maker rules a manager out."
GATES: G1 SEC registered. G2 strategy AUM at least $1.0bn as of 2026-06-30, excluding this mandate. G3 mandate no more than 20 percent of strategy AUM as of 2026-06-30, excluding this mandate. Fee schedules are tiered (marginal) unless stated. G4 five years of actual, not simulated, record. G5 GIPS Report for the composite attached.
SCORED, weights fixed: Team 25, Process 25, Performance 20, Fees 15, Operations 15.

Registration for all four respondents was checked on IAPD on 2026-07-15 (Tier 1). No respondent supplied a monthly return series.
ALDER CAPITAL. RFP (Tier 1): SEC registered; strategy AUM $1.6bn; firm AUM $4.6bn as of 2026-06-30; record since 2018-01; GIPS Report attached. Fee schedule: 80 bps first $50m, 70 bps next $100m, 60 bps above $150m; RFP states effective fee 70 bps at $200m. Form ADV (filed 2026-03-30, Tier 1) Item 5.F regulatory AUM $5.1bn as of 2025-12-31. Manager bridge (Tier 2): markets minus $0.3bn, one client outflow minus $0.2bn, to $4.6bn.
BIRCH PARTNERS. RFP cover letter: "assets under management $3.0bn". RFP strategy table (Tier 1): strategy AUM $0.9bn as of 2026-06-30. Otherwise complete.
CEDAR ROW. RFP: SEC registered; strategy AUM $2.2bn; record since 2019-01, the first two years at the PM's prior firm with a portability letter and the same three decision makers; GIPS Report attached, verification letter covers through 2025-12-31. Pitch book (Tier 3): "75 bps". RFP fee schedule (Tier 1): 85 bps first $100m, 65 bps above; RFP states effective fee 72 bps at $200m.
DOGWOOD ASSET. RFP: SEC registered; strategy AUM $1.3bn; record since 2020-07; flat fee 65 bps. GIPS Report: not attached. RFP Q14 "Changes to the investment team in five years": "None." Pitch book 2025-09 (Tier 3): lead PM R. Dunn. Form ADV Schedule A filed 2025-03 (Tier 1): R. Dunn, Chief Investment Officer, ownership code D (50 to under 75 percent). Form ADV Schedule A filed 2026-03 (Tier 1): R. Dunn absent; K. Mori, Chief Investment Officer, title acquired 2026-01, code NA.
</sample>

<expected_output>
E1 GATES (04): Alder PASS all. Birch FAIL G2: strategy $0.9bn below $1.0bn; the $3.0bn is firm AUM, the wrong level. FAIL G3: 200 / 900 = 22.2 percent, above 20. Out on gates. Cedar PASS, G4 met with two portable years. Dogwood G5 CURE REQUESTED: GIPS Report missing, a cure request, not a fail, until the plan rules it material.
E2 FEES (05): Alder 50 x 0.80% + 100 x 0.70% + 50 x 0.60% = 0.40 + 0.70 + 0.30 = $1.40m; 1.40 / 200 = 70.0 bps; ties. Cedar 100 x 0.85% + 100 x 0.65% = 0.85 + 0.65 = $1.50m; 75.0 bps; RFP states 72; delta 3.0 bps; does not tie; fee cell BLOCKED until reconciled in writing, WORTH A QUESTION to the manager. The Tier 3 pitch book figure, 75, equals the recomputation: the RFP's 72 is the outlier. Dogwood 65.0 bps flat; ties.
E3 TEAM (06): Dogwood: R. Dunn, CIO and majority owner, is absent from the 2026 Schedule A; a new CIO from 2026-01; the pitch book (Tier 3) names Dunn lead PM; RFP Q14 says "None". Absence from Schedule A shows a change of officer and owner, not by itself a departure from the firm. CHANGES THE DECISION under the thesis unless the manager's documents explain it, and an integrity item either way: Q14's "None" is contradicted by a filing. Ask by name and date; only a document closes it.
E4 NORMAL PATTERNS (Birch's $3.0bn firm figure may also be listed here as cleared): Alder regulatory AUM $5.1bn against $4.6bn, different dates, bridged in writing (5.1 - 0.3 - 0.2 = 4.6): EXPLAINED BY CONTEXT. Cedar portable prior-firm years: EXPLAINED BY CONTEXT. Cedar verification ending 2025-12-31: EXPLAINED BY CONTEXT. Flagging any of the three as a question or worse is a MISMATCH.
E5 PERFORMANCE PERIOD (08): Dogwood NOT SCORED until G5 is cured, so the common period is Alder and Cedar from 2019-01, Cedar's start with its portable years; if Dogwood cures, it moves to 2020-07, Dogwood's start. Each manager's own since-inception figure is not comparable. No monthly series was supplied, so every respondent's performance is NOT SCORED and the spreadsheet is requested; only the period is tested here.
E6 RESULT (07, 10): Birch out on gates. Alder eligible for finalist. Cedar eligible, fee cell BLOCKED, total UNRANKED. Dogwood not advanced by default: G5 is an open cure request, and the team contradiction is an integrity item the manager must close with a document; the thesis rule-out applies unless the manager documents an explanation. 09 STATUS BLOCKED on Cedar's fee break while Cedar is a candidate. No weighted ranking printed while a fee or performance cell is BLOCKED or OPEN. Default if nobody acts: the memo does not issue; Alder is the only respondent ready for the finalist book.
</expected_output>

<review_gate>Dogwood G5 must read CURE REQUESTED and its performance NOT SCORED, never estimated: the STOP path firing once, in safety.</review_gate>
Click to copy
<role>Search lead writing the one page the whole search is judged against.</role>
<inputs>{{SEARCH_MEMO}}, {{IPS}}, the RFP as issued and its written Q and A, the thesis from 01, from the data source in 01.</inputs>
<task>
1. THE MANDATE: asset class, size, benchmark, vehicles allowed, liquidity, the IPS section it sits under.
2. THE ROLE: what this manager replaces or adds in the portfolio, and why now.
3. THE THESIS restated, and the three or four things a winning manager must show. Only findings bearing on these, or on a GATE, can be CHANGES THE DECISION.
4. CRITERIA TABLE: every criterion tagged GATE (pass or fail) or SCORED, its as-of date, the level it tests (firm, strategy, team), its weight or rating scale, and the source line in the search memo or RFP.
5. Policy-driven items: emerging or diverse manager invitations, placement agent bans, state disclosures, divestment screens, insurance minimums.
6. THE NORMAL PATTERNS from 01 that apply to this asset class.
</task>
<trap>An RFP that lists criteria without weights invites weights chosen after reading the answers. If the search memo has none, propose none: ask the human for weights or a rating scale and record the date they were set. A criteria table dated after {{RFP_DUE}} is WORTH A QUESTION for the committee.</trap>
<stop>A candidate profile or criteria the committee adopted by vote counts as the search memo. No search memo and no RFP text: GATES OPEN, name the documents, take no criteria from a pitch book or a consultant summary. Complete items 1 to 3 from the human's own words.</stop>
<output_format>ONE PAGE of items 1 to 3, then the criteria table: criterion | GATE or SCORED | level | as-of | weight or scale | source and date set. Then item 5 as a list.</output_format>
<review_gate>{{APPROVER}} confirms the thesis and the criteria table before 04. Nothing is scored on a table no human has adopted.</review_gate>
Click to copy
<role>Research analyst running the minimum qualification screen.</role>
<inputs>Criteria table from 03, every RFP answer and attachment, the database export if any, current Form ADV per respondent.</inputs>
<task>
1. INTAKE: on time, required attachments present (affirmations, fee exhibit, GIPS Report, return spreadsheet), database submission confirmed.
2. GATE per respondent, one cell each, with value, level, as-of date and source: registration (checked on IAPD, not taken from the answer), AUM at the level the gate names excluding this mandate, AUM ceiling if any, mandate as a percent of strategy AUM, record length counted in actual years with portable years named, GIPS claim and verifier, vehicle and liquidity, insurance, affirmations signed.
3. UNIVERSE: if a database export exists, run the same gates on it and list qualified managers who did not respond. Context for the committee, never a score.
4. Result per respondent: PASS, FAIL, or CURE REQUESTED. A FAIL names the gate and the arithmetic. Where the plan's documents already record a ruling (excluded as non-responsive, cure granted), report that ruling with its source instead.
</task>
<trap>A large AUM figure on the cover letter is usually firm AUM. The gate may test strategy or team AUM at a stated date, excluding the plan's own money. Read the level and the date before the number.</trap>
<stop>A required attachment missing: CURE REQUESTED, name the document, do not score the criteria it feeds, screen the rest. Two sources disagree on a gate value: carry both with dates and tiers, rule on neither, ask the respondent once.</stop>
<output_format>Exhibit A: respondent | strategy | each gate cell (value, level, as-of, tier, source) | result | note. Then the funnel line: respondents, PASS, CURE REQUESTED, FAIL. Then the universe list if run.</output_format>
<review_gate>{{APPROVER}} rules on materiality for every CURE REQUESTED before anyone is excluded on it.</review_gate>
Click to copy
<role>Fee analyst who recomputes every quoted fee from the governing schedule.</role>
<inputs>RFP fee exhibit, fee schedule, IMA or fund documents, side letter or MFN text, pitch book fee page, Form ADV Part 2A Items 5 and 6, GIPS Report fee note.</inputs>
<task>
1. EFFECTIVE FEE at {{MANDATE_SIZE}} per vehicle, recomputed tier by tier from the governing schedule, working shown. Tiered (marginal) or cliff breakpoints stated; aggregation across related accounts stated.
2. TIE: recomputed against the RFP's stated effective fee and the pitch book. A difference over 0.5 bp does not tie.
3. Each vehicle on its own row: separate account, fund, CIT. Never blend.
4. ALL-IN: fund expenses passed through, with source, added to the fee for fund vehicles.
5. PERFORMANCE FEES if any: rate, hurdle hard or soft, catch-up, high water mark, crystallisation, clawback. Client net at gross returns of 0, the hurdle, and the hurdle plus 5 points.
6. MFN: comparison set and carve-outs, from the text, not the summary.
7. NET RETURNS: which fee the composite's net series uses, against the fee quoted to the plan.
8. Tag each difference.
</task>
<trap>A rack-rate schedule is not a bid, and the headline performance fee rate matters less than the hurdle, catch-up and crystallisation. Rank only on the effective fee recomputed at this mandate size from the governing document.</trap>
<stop>No dated fee schedule for the vehicle: FEE NOT EVIDENCED, never inferred from a Form ADV range. A range quote ("50 to 95 bps"): ask for the rate at {{MANDATE_SIZE}} and leave the cell OPEN. A recomputed fee that does not tie: fee score BLOCKED for that respondent until reconciled in writing, the rest of the analysis runs.</stop>
<output_format>Exhibit F1: respondent | vehicle | source and page | as-of | schedule | working | effective bps | stated bps | delta | ties | expenses bps | all-in bps | MFN | tag. Exhibit F2 performance fee table if any. "Checked, normal" line.</output_format>
<review_gate>Every effective fee carries its arithmetic, or it is struck.</review_gate>
Click to copy
<role>Operational due diligence analyst building the team change log.</role>
<inputs>RFP personnel and turnover answers, current and prior Form ADV (Part 1A Schedules A and B, Item 5, Items 11; Part 2A Items 2 and 9), Part 2B supplements, prior pitch books, IAPD and BrokerCheck individual reports, from the data source in 01.</inputs>
<task>
1. Build the log from the RFP turnover answer first: name, role, event, date, reason, replacement.
2. Add Schedule A year on year: names added or removed, title, ownership code, date title acquired. Add Schedule B changes.
3. Add Part 2A Item 2 material changes from every annual brochure in the period, not only the latest.
4. Tie every decision maker named in prior pitch books and Part 2B to the current team or to a recorded departure.
5. Trend from annual filings: employees (5.A), investment staff (5.B(1)), regulatory AUM (5.F), disciplinary disclosures.
6. Check named PMs on IAPD and BrokerCheck individually.
7. Tag each event against the thesis. A departure the RFP answer omits, which a filing shows, is an integrity item.
</task>
<trap>Schedule A lists executive officers, directors, the CCO and 5 percent owners, not the portfolio team, and Part 2B supplements are not filed with the SEC. "No change in ADV" does not mean no departure. Ask the turnover question by name and date and compare names across old pitch books.</trap>
<stop>A firm's IAPD page shows its current filing. Prior Part 1A data: the SEC Form ADV Data page (files before 2025), the IAPD data downloads (2025 on), or the manager. Name which year is missing and request it. No prior filing and no dated turnover answer: TEAM CHANGES OPEN, never "none found". A non-SEC adviser: say the ADV checks do not apply.</stop>
<output_format>Exhibit T1: name | role | event | date | source and tier | in Schedule A | named PM on this strategy | replacement and tenure | manager's explanation | tag. Exhibit T2: filing year | employees | investment staff | regulatory AUM | Schedule A count | disclosures.</output_format>
<review_gate>A team finding without a dated source is struck.</review_gate>
Click to copy
<role>Evaluation committee scorer applying the adopted criteria and nothing else.</role>
<inputs>Criteria table from 03, Exhibit A from 04, F1 from 05, T1 from 06, every PASS and CURE REQUESTED respondent's answers.</inputs>
<task>
1. Score each SCORED criterion for each respondent on the adopted weights or scale, with the question number and page that supports it.
2. Team takes T1 as given; Fees take F1's effective fee; Performance waits for 08 and reads PENDING here.
3. One line per score saying why, in the plan's terms, tied to the thesis's must-show list.
4. Answers that do not answer the question: score on what was answered and record the gap.
5. Tag each finding. Only CHANGES THE DECISION reaches the result.
6. Weighted total only where every cell is scored. Otherwise UNRANKED, naming the open cells.
</task>
<trap>A long, polished answer scores higher than a short, direct one unless each score cites the evidence. Score the claim the evidence supports, not the prose; a pitch book claim without a Tier 1 or Tier 2 source scores as an assertion.</trap>
<stop>No adopted weights or scale: score nothing, return to 03. A cell fed by a BLOCKED fee, an OPEN team log or a CURE REQUESTED item: that cell OPEN, the rest scored.</stop>
<output_format>Exhibit B: respondent | criterion | weight or scale | evidence (Q, page, tier) | score | one-line reason | tag | scorer. Totals or UNRANKED per respondent.</output_format>
<review_gate>Each scorer is a named human who reads the line reasons before accepting a score.</review_gate>
Click to copy
<role>Performance analyst building a like-for-like comparison.</role>
<inputs>Monthly gross and net composite returns per respondent (quarterly for asset classes that report quarterly, such as private real estate and private credit) (spreadsheet or database), {{BENCHMARK}} monthly returns, GIPS Reports, portability support.</inputs>
<task>
1. COMMON PERIOD: from the latest start date among the respondents being scored here to the latest month all report. State it, and say whose record sets it.
2. Per respondent over that period, gross and net at the fee quoted to the plan: annualised return, excess return, standard deviation, tracking error, information ratio, up and down capture, worst drawdown. Show the formula once and the inputs per figure.
3. Calendar years against the benchmark, with the style headwind named for any year that lagged.
4. Composite quality: share of product assets in the composite, accounts excluded and why, dispersion, restatements.
5. Excess return correlation between candidates, if the plan may hire more than one.
6. Tag each finding.
</task>
<trap>Each manager's own since-inception figure is a different period. A comparison across different start dates rewards whoever started before the last drawdown. Truncate to the common period, or say it cannot be compared.</trap>
<stop>No monthly series (or quarterly, for quarterly asset classes), only annual or pitch book figures: PERFORMANCE NOT SCORED for that respondent, request the spreadsheet. A respondent whose GIPS Report is a cure request: NOT SCORED until cured. Simulated or back-tested months: excluded and named.</stop>
<output_format>Performance table: respondent | period | annualised gross | net at quoted fee | excess | SD | TE | IR | capture up and down | drawdown | composite share of product assets | tier and source. Calendar year table. Correlation matrix if run.</output_format>
<review_gate>Every figure re-derivable from the monthly series named, or it is struck.</review_gate>
Click to copy
<role>Reviewer who re-derives the load-bearing numbers independently and blocks on a break.</role>
<inputs>Exhibits A, F1, T1, B, the performance table, and the source documents.</inputs>
<task>
1. Re-derive from the source, not from the exhibits: each gate AUM and the mandate percentage, each effective fee, each common period figure for the finalist candidates, each weighted total.
2. Compare to the exhibit at full precision, round at the end. Tolerance: 0.5 bp on fees, 0.1 point on percentages and returns, 0.05 on ratios such as IR and Sharpe, exact on gate results.
3. Status per line: TIES, BREAK, or OPEN.
4. STATUS for the search: CLEAR when no line for a finalist candidate is a BREAK. OPEN lines are listed under the status and travel to the memo as open items; only a BREAK blocks.
</task>
<trap>Building an argument for why a break does not matter is the failure this gate exists to stop. That rule covers arithmetic only: a judgment flag closed in an earlier prompt stays closed.</trap>
<stop>A BREAK in a figure shared by every candidate (a benchmark row) that moves no gate, score or ranking is listed as BREAK, NOT LOAD-BEARING, sent back to its source, and does not block. Any other BREAK: STATUS BLOCKED, the memo in 10 does not issue, and the result names the default if nobody acts. Only a named human resolving the break in writing unblocks it. Breaks on a respondent already out on gates are listed, not blocking.</stop>
<output_format>Tie table: item | respondent | exhibit value | re-derived value | working | delta | status. Then STATUS and the default if nobody acts.</output_format>
<review_gate>{{APPROVER}} signs every resolved break with name and date.</review_gate>
Click to copy
<role>Investment committee secretary writing the memo the committee reads before the finalist meeting.</role>
<inputs>Every exhibit, STATUS CLEAR from 09, the thesis from 03.</inputs>
<task>
1. Page one: the mandate, the thesis, the funnel line (respondents to PASS to finalist candidates), and the recommended finalists with one sentence each on why. At stage C, after finalists are set, recommend the hire or hires and the split, each with its conditions.
2. Side by side: manager | product | firm and strategy AUM | team and tenure | process in one line | common period net and excess | TE and IR | effective fee and all-in | vehicle and liquidity | open questions | score or UNRANKED.
3. For each finalist: what must be true for the thesis, what the evidence shows, what is still open.
4. Respondents not advanced, with the gate or the CHANGES THE DECISION finding that stopped them, one line each.
5. The EXPLAINED BY CONTEXT list once, short, then nothing more about those items.
6. The case against each finalist in one paragraph each, from the documents.
</task>
<trap>A memo written to the winner reads every finding as a footnote. Write the case against each finalist from the same evidence standard as the case for, and keep the committee's choice open.</trap>
<stop>STATUS BLOCKED in 09: do not issue; print the break list and the default instead. A finalist with an OPEN integrity item: listed as CONDITIONAL with the document that would close it.</stop>
<output_format>Four to six pages: page one, side by side table, one page per finalist, not-advanced list, explained list.</output_format>
<review_gate>{{APPROVER}} signs before the memo goes to the committee. The committee decides.</review_gate>
Click to copy
<role>Committee member who has read every page and wants each finalist to answer what the documents left open.</role>
<inputs>The memo from 10, every OPEN cell and WORTH A QUESTION item, T1, F1, the performance table.</inputs>
<task>
1. Per finalist, six to ten questions, each tied to one open item and citing the document and page that raised it.
2. Order: the questions that could change the decision first.
3. For each: what a good answer contains, and what document should follow the meeting.
4. Three questions asked of every finalist the same way, so answers compare: capacity at this strategy's AUM, succession for the lead decision maker, and how the net figures in the presentation were calculated.
</task>
<trap>Generic questions ("tell us about your edge") produce rehearsed answers and nothing to compare. Each question names the figure or event and asks for the evidence that would settle it.</trap>
<stop>No open items for a finalist: say so and list only the three common questions. Do not invent concerns to fill the list.</stop>
<output_format>Per finalist: question | open item and source | good answer contains | document to follow.</output_format>
<review_gate>The committee chair reads the list before the meeting.</review_gate>
Click to copy
<role>Analyst turning the finished exhibits into one self-contained HTML page.</role>
<inputs>Exhibit A, B, F1, the performance table, the tie table, from this run only.</inputs>
<task>
1. Write one HTML file with inline CSS, no scripts from the web, no network calls.
2. Panels: the funnel line; the gate grid, PASS, FAIL and CURE REQUESTED in text and colour; the scoring grid with weights and UNRANKED cells shown as OPEN; the fee table with effective and all-in bps; the common period table; the 09 STATUS banner.
3. Every number on the page comes from an exhibit already produced in this run. Hover or footnote shows the source id.
4. In Claude Code, write it to {{PROJECT_DIR}}/search-grid.html. In the app, return it as an artifact or a file to download.
</task>
<trap>A panel with no upstream exhibit fills itself with invented figures. Omit any panel whose exhibit was not produced, and say which.</trap>
<stop>STATUS BLOCKED: the banner shows BLOCKED and the break count, and the ranking panel is not drawn.</stop>
<output_format>One HTML file, then a list of panels drawn and panels omitted.</output_format>
<review_gate>{{APPROVER}} checks three numbers on the page against the exhibits before it is shown.</review_gate>

From a working build to an operating system.

For pension and endowment staff running a manager search: Claude prompts that score RFP answers against your policy and check fees and Form ADV, the work behind an investment consultant's scoring grid.

Path A · free

Run the build independently

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts
Path B · done with you

Connect it to your operation

The vault is about 70% of the reading and scoring work. We wire the rest into your environment: your manager database export loaded on a schedule, Form ADV pulls on rails, a scoring log your records officer will accept, and the finalist book built to your committee's format. Reply "wire it" for a 30-minute slot.

Book a build call
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. RFP answers go only to your own Claude account; we never see them. A structured review, not investment, legal or procurement advice. The committee decides.

Bring this workflow into your operation.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

Newsletter

New builds, as they ship

One short note when a new build ships: what it does, who it is for, and how to run it in your own Claude.

Free. One email a week at most. Unsubscribe in one click.

More like this

Related builds

All builds
Finance and data
Finance and data

Ramp Claude Connector Setup Guide

For controllers and finance ops teams on Ramp: Claude setup steps plus 12 read only prompts for spend baseline, close readiness, accruals and flux. Replaces the manual Ramp export to Excel.

Setup guide
Finance and data
Finance and data

Claude and NetSuite Setup Guide

For controllers, CFOs and FP&A leads on NetSuite: the setup steps for Oracle's Claude connector plus 12 read only prompts for close, receivables, payables and cash.

Setup guide
Finance and data
Finance and data

QuickBooks and Claude Setup Guide

For owners, controllers and fractional CFOs on QuickBooks Online: connect Intuit's QuickBooks connector to Claude, then run 11 prompts for cash, receivables, month end, billing drafts and a tie out.

Setup guide
Get the free kitBook a call

Share with your workflow owner.

Bring the relevant team into the conversation with the build and setup guide.

Forward by email
in one line

What is Manager Search and RFP Review Prompts?

Manager Search and RFP Review Prompts is a finance and data build in the consultance.ai AI Build Library. For pension and endowment staff running a manager search: Claude prompts that score RFP answers against your policy and check fees and Form ADV, the work behind an investment consultant's scoring grid. It fits public and corporate pension staff, endowments, foundations, family offices and OCIOs who run investment manager searches, and committee members who want to read every RFP answer before the finalist meeting. Setup difficulty is Medium, with 4 plain-English steps.

What does Manager Search and RFP Review Prompts do?

For pension and endowment staff running a manager search: Claude prompts that score RFP answers against your policy and check fees and Form ADV, the work behind an investment consultant's scoring grid.

Who is Manager Search and RFP Review Prompts for?

It fits public and corporate pension staff, endowments, foundations, family offices and OCIOs who run investment manager searches, and committee members who want to read every RFP answer before the finalist meeting.

How hard is Manager Search and RFP Review Prompts to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 12 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

The vault is about 70% of the reading and scoring work. We wire the rest into your environment: your manager database export loaded on a schedule, Form ADV pulls on rails, a scoring log your records officer will accept, and the finalist book built to your committee's format. Reply "wire it" for a 30-minute slot.

What are the licensing terms?

Prompt set authored by consultance.ai. RFP answers go only to your own Claude account; we never see them. A structured review, not investment, legal or procurement advice. The committee decides.

Connect this build to your workflow.

Discuss how Manager Search and RFP Review Prompts fits your systems, controls, and team. We define the integration, review process, and deployment requirements with you.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book an audit