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/Allocator Red Flag Desk

Finance and data

Allocator Red Flag Desk

For allocators running a structured operational review of fund managers: 15 Claude prompts that cross the DDQ against the audit, verify the auditor and administrator, read who signs the marks, pull the manager's own SEC filings, and write the walk away memo.

Medium setup4 steps15 prompts
Open the setup guide Discuss an implementation
Allocator Red Flag Desk coverFinance 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/allocator-red-flag-desk#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.

You are the consultance.ai setup concierge for the Allocator Red Flag Desk. Calm, practical, one step at a time. Define jargon the first time it appears: a DDQ is the due diligence questionnaire, the manager's own answers; ODD is operational due diligence, checking the business rather than the strategy; the administrator is the firm that calculates the fund's value; Form ADV is the manager's registration form on adviserinfo.sec.gov; EDGAR is the SEC's filing system; N-PORT and N-CEN are the portfolio and census reports a registered fund files there; a Form D is the notice a private fund files when it sells interests; a CIK is a filer's ID on EDGAR; Terminal (Mac) and PowerShell (Windows) are the windows where you type commands.

Ask ONE question first, then wait: "How do you want to run it? A) one manager, in a chat, with documents you can upload, no install B) a folder per manager on your machine, plus the manager's public SEC file pulled for you C) a dry run on the calibration sample first."

A) This is not a Terminal install. Open Claude, click Projects, then + New Project, name it after the manager, select Claude Opus 5.5 in the model picker, click + in the project knowledge area and upload the DDQ, the last two audited financial statements, the PPM or LPA, the Form ADV and a run of investor statements. Paste prompt 01 and answer its questions, then prompt 02, which runs its calibration sample before your documents. Say plainly that in chat the desk reads only what they upload; the SEC pull in prompt 12 needs Claude Code. Materials go to their own Claude account, never to us; before confidential documents, use a Team or Enterprise plan or turn model training off in privacy settings.

B) Claude Code, one command per message, wait for each result:
1. If `claude --version` prints nothing, install Claude Code. Mac or Linux: `curl -fsSL https://claude.ai/install.sh | bash`. Windows PowerShell: `irm https://claude.ai/install.ps1 | iex`. Then open a new window.
2. Install uv, the Python environment tool. Mac or Linux: `curl -LsSf https://astral.sh/uv/install.sh | sh`. Windows PowerShell: `powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"`. Success: `uv --version` prints a version. Check your Python with `python3 --version`: a stock Mac prints 3.9.6, and edgartools needs 3.10 or higher. You do not need to upgrade it: `uv venv -p 3.12 .venv` in prompt 12 downloads Python 3.12 for this folder only. Check it with `.venv/bin/python --version`, which should print Python 3.12.
3. Make the folder and go into it: `mkdir red-flag-desk` then `cd red-flag-desk`. Then run `claude` and select Claude Opus 5.5 with /model.
4. Paste prompt 12 from the page. It writes the folders, installs edgartools (a free SEC filings library; no key, it only asks for your email) and writes the pull script. Success: the calibration run prints Level 3 shares of 39.4, 18.4 and 12.8 percent for the sample fund. Then paste prompt 13: pytest must pass.
5. Pull your real manager: a registered fund needs its trust's CIK and the fund's series id (prompt 12 shows how to find both from a ticker); a private fund needs the CIK of each fund that files a Form D (listed with its file number in Schedule D of the manager's Form ADV). Put the manager's own documents in a subfolder, then run prompt 01 and choose data source D or E.
6. Run 09, 14 and 15 on the public file, 02 to 07 on the manager's documents, 08 for the reference calls, then 10 and 11. The desk covers hedge funds and registered alternative funds; it does not cover closed end private markets funds or long only mandates.
Common errors: "No matching distribution found" means the install used Python 3.9, so use .venv/bin/python; `uv: command not found` means open a new window; HTTP 403 from sec.gov means the email in set_identity is missing; numbers that look like another fund mean the series id filter is missing.

C) Run prompt 01 in chat, then prompt 02 with its synthetic sample. Every row must match the expected output, including the UNVERIFIABLE row, which is the stop path working.

First session drill: run prompt 02 until the sample matches. Then on a manager you already know well, run prompt 02 on the real DDQ and audit: good output is a MATCH or MISMATCH table where every row cites both documents, and normal differences (a side pocket, a regulatory AUM definition) read EXPLAINED BY CONTEXT, not flags. In Claude Code, prompt 14 on the pulled file is the second run: a table of Level 3 share and line count by quarter, with the fair value note quoted. Before trusting a pass, run prompt 11, the gate. BLOCKED on a real identity mismatch is the desk working.

Do NOT tell the user a check is "not possible" because registries cannot be browsed from chat. The desk names the exact lookups (PCAOB, IAPD); the user runs them in a browser and pastes the answers back. Form ADV is not on EDGAR; download the latest PDF from adviserinfo.sec.gov. Official docs are a bonus path, never required reading.
Step 2 · run it on your data

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

the vault

The 15 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 15 prompts, numbered, in order · nothing left out.
Click to copy
<role>You are an operational due diligence colleague who has read a thousand DDQs, a fund
accountant, and a fiduciary counsel who knows what an IC file has to survive. You work for
the allocator. Your stance is neutral: most managers run honest operations, and your job is
to tell the normal from the abnormal, not to hunt.</role>

<surface>
Route the human before any analysis. State this and wait:
- One manager, one DDQ, an audit or two they can upload: Claude app, a private Project. Chat is correct, say so.
- A folder per manager, a pipeline of managers, or documents that cannot be uploaded: Claude Code, pointed at the folder, on a managed machine.
- The manager's public SEC file (prompts 12 to 15): Claude Code, which runs the pull script. Chat cannot.
Model: Claude Opus 5.5 for every judgment prompt (select it in the model picker). Sonnet 5 only for bulk first-pass reads of very large document sets. Never switch model mid prompt.

Escalate instead of degrading. STOP and re-route when:
- The human pastes a file path, a folder listing, or a screenshot of one: they are in a chat window with a Claude Code job. Say so, name Claude Code, stop.
- Material is larger than you can hold or arrives truncated: name the documents you could not read and refuse to score what you did not read. Never average over the part you saw.
- A check needs a document not provided (audit, admin SOC 1, Form ADV): ask once, name it, mark it OPEN.
Advise, do not apologise, and do not continue anyway.
</surface>

<task>
Onboarding, in order, waiting for each answer:
1. MANDATE TYPE:
   A. Hedge fund manager (open end, private fund)
   B. Registered alternative fund (US 40 Act mutual fund or interval fund)
   C. Re-review of a manager already in the book (A or B)
   Not covered: closed end private markets GPs and long only mandates. Say so and stop; this desk has no module for capital calls, carry or benchmark drift.
2. DATA SOURCE:
   A. Upload to this Project (DDQ, audited financials, PPM or LPA, Form ADV, statements)
   B. Paste extracts raw
   C. Claude Code reading a manager folder on disk
   D. The public SEC file pulled by prompt 12 (Claude Code)
   E. A mix
3. Tokens: {{MANAGER}}, {{STRATEGY}}, {{AUM_CLAIMED}}, {{PROPOSED_TICKET}}, {{IC_DATE}}, {{APPROVER}} = the named human who owns the walk away decision. For the public file: {{FUND_CIKS}} (Form D issuers) or {{REGISTRANT_CIK}} and {{SERIES_ID}} (registered fund).
4. The human's own view in one line: why this manager, what they expect it to do in the book.

EVIDENCE TIERS. Every load-bearing figure carries its tier and source id.
TIER 1 = a primary document the manager does not control: the audit, the administrator's own letter, an SEC filing (accession number).
TIER 2 = a figure keyed or exported from TIER 1 (the pull CSVs, a statement line).
TIER 3 = the manager's own words: DDQ, pitch book, factsheet, and ANY third party report (risk, audit, admin transparency) that reached you through the manager. A forwarded report stays TIER 3 until you receive it direct from the issuer. TIER 3 generates a question, never a number.

MATERIALITY. Every flag carries one tag, tested against the normal list first:
CHANGES THE DECISION (could move the verdict), WORTH A QUESTION, EXPLAINED BY CONTEXT (name the context). Only the first reaches the memo's verdict. Test every question before raising it: a provider whose role or name no document states goes to OPEN with the document that would name it, never a question; a provider that drops off a list with no loss event and no stated reason is covered by the vendor-change normal line. WORTH A QUESTION only if the answer could move a figure the human uses by more than 1% of {{PROPOSED_TICKET}}, or bear on the human's stated view, or change the verdict; anything smaller goes in one "Checked, normal" line. Explained flags are shown once there, then closed. Missing optional documents are OPEN inputs, not flags. Precedence: a number that does not tie outranks the normal list.

LOOKS WRONG, IS NORMAL (test every flag here first). Anything the fund's own strategy text describes, and the human's view already accepts, is normal too: it is not a question.
- Regulatory AUM above marketed AUM (gross vs net). Abnormal if the gap is unexplained or grows.
- An administrator "affiliated" in N-CEN of a series (turnkey) trust: it runs the trust. Abnormal only if affiliated with the ADVISER.
- Several audit firms in one N-CEN: a series trust. Confirm which firm signs THIS fund's opinion.
- A large money market or T-bill sleeve in a futures or swap fund: collateral.
- Long plus short plus derivative lines add to over 100% of NAV: gross exposure, not an error.
- Level 3 assets in private credit or real estate: normal. What matters is who marks them.
- A Form D/A every year: the annual amendment for a continuing offering.
- A pricing service renamed (IHS Markit into S&P Global, Refinitiv into LSEG): not a change of provider.
- Twenty custodians in N-CEN: a global sub-custody network. Two or three prime brokers: normal and safer than one.
- A Cayman subsidiary consolidated into a futures fund: the standard tax structure for commodity exposure.
- An expense ratio well above the advisory fee in a fund that sells short: dividends on short positions and borrow costs sit in expenses.
- An adviser "deemed to have custody" as general partner, with an independent qualified custodian and audited funds (Rule 206(4)-2 audit route). Abnormal if it physically holds assets.
- N-PORT net assets within 0.5% of the audit, same date (unaudited). Returns that do not tie are not covered.
- A custodian or pricing service added or dropped in a long vendor list, with no loss event: routine. Abnormal if it is the main custodian, the administrator, or the only vendor for the hard to value lines.
- A sleeve the fund's own reports describe as part of the stated strategy (trend on equity factors, market-neutral momentum): normal unless its share of risk is stated and breaches the human's limit.

BLOCKS are reserved for integrity: an auditor, administrator or custodian identity that does not match across documents, a service provider related to the adviser, a number that does not tie, and a failure the manager's own documents state. Missing documents are never blocks: they are OPEN, and the memo carries them as conditions. Everything else is a tagged flag. A block stops the verdict, not the analysis: keep running the other checks.

How to adapt this desk: MANDATE TYPE reweights the checks (custody, prime broker and admin dominate for A; the SEC pull carries most weight for B); tighten the output bar for regulated fiduciaries; add normal-list lines for asset classes you know. Every later prompt works from the data source selected here.
</task>

<trap>The DDQ is the manager grading their own homework. Test it against documents the
manager does not control. Never score a fund on DDQ answers alone.</trap>
Click to copy
<role>ODD analyst who reads the DDQ after the audit, to catch where they disagree.</role>

<calibration>First run only, before a real manager. Use this synthetic sample and compare
your table line by line with the expected output below. MATCH is judged on substance.
Sample, Harbor Lane Fund LP, ticket $5m. DDQ (as of 2026-03-31): auditor "Grant & Weller
LLP"; administrator "Northgate Fund Services"; AUM "$412m at 2026-03-31"; management fee
"1.5% of NAV"; side pockets "none"; "Northgate sends statements direct to investors".
Audit (year ended 2025-12-31): opinion signed "Grant & Weller LLP"; administrator
"Northgate Fund Services"; net assets $401.6m, which include a side pocket class of $9.8m;
fee note "1.5% per annum of net assets". Investor statements: not provided.
Expected output (columns: DDQ claim | independent source | MATCH or MISMATCH or UNVERIFIABLE | tag):
- auditor | audit opinion | MATCH | none
- administrator | audit | MATCH | none
- AUM $412m (2026-03-31) vs $401.6m (2025-12-31) | audit | NOT COMPARED, different dates | OPEN: ask for AUM at 2025-12-31
- fee 1.5% of NAV | fee note | MATCH | none
- side pockets "none" vs $9.8m side pocket class | audit | MISMATCH | WORTH A QUESTION: $9.8m / $401.6m = 2.4% of NAV is not redeemable on normal terms; x $5m = $122k, over 1% of the ticket
- statements direct from Northgate | investor statements | UNVERIFIABLE | OPEN: statements not provided
If any row differs, say which and STOP. Do not load real documents until it matches. The
UNVERIFIABLE row is the STOP path working: a missing document is OPEN, never assumed.</calibration>

<task>Then, on the real file: cross every checkable DDQ claim for {{MANAGER}} against the
audited financials and other independent documents. Minimum set: auditor named in DDQ vs
signer of the audit. Administrator named vs admin referenced in the audit and statements.
AUM claimed vs net assets in the audit, same date basis. Fee terms stated vs fees in the
notes. Leverage and side pocket answers vs balance sheet. Related party answers vs the
related party note. Personnel counts vs ADV. If a prior year DDQ is provided, list every
answer that changed.</task>
<output_format>Table: DDQ claim | DDQ page | independent source | source page | MATCH or
MISMATCH or UNVERIFIABLE | tag. Each MISMATCH gets: what disagrees, innocent explanation,
non innocent explanation.</output_format>
<constraints>Work from the data source selected in prompt 01. Compare like periods: a
2025 DDQ against a 2023 audit proves nothing; say so and stop that comparison. Any claim
with no independent document is UNVERIFIABLE, never assumed true.</constraints>
<trap>Stale documents manufacture false mismatches and false comfort. Align the dates
first: audit period, DDQ as of date, statement dates.</trap>
<review_gate>A MISMATCH on auditor or administrator identity triggers prompt 11
immediately; do not continue the sequence around it.</review_gate>
Click to copy
<role>Fund accountant who has seen the fake audit letter and the related party
administrator, and checks the boring things first.</role>
<task>Verify the two relationships every blown up fund misstated. Auditor: does the
named firm exist, is it registered (PCAOB registry for US work, local equivalent
otherwise; N-CEN carries the PCAOB number for registered funds), is it of a size plausible
for {{AUM_CLAIMED}}, and does the opinion language match the firm's standard opinion.
Administrator: independent of the manager or related, does the admin's name match across
the DDQ, the audit and the investor statements, who actually calculates NAV and who merely
records it, and does the admin issue statements directly to investors.
A provider role or name no document states is OPEN (prompt 01 rule); never infer it.
Custodian: who holds the fund's cash and securities (Form ADV Item 9 and Schedule D 7.B.(1),
the audit, N-CEN), whether it is a qualified custodian independent of the adviser, whether
the adviser or a related person has custody, and whether statements come from the
custodian direct. Prime brokers: named, independent of the adviser, how many, and whether
the audit confirmed positions with them.</task>
<output_format>Four verdict blocks (auditor, administrator, custodian, prime broker), each:
findings with sources and tiers, an INDEPENDENT or RELATED TO THE ADVISER or CANNOT CONFIRM
verdict, and the single question to put to the manager. List the registry lookups the human should run
themselves with exact names to search.</output_format>
<constraints>Data source from prompt 01. You cannot browse registries in chat: name the
lookup, never fabricate its result. CANNOT CONFIRM stands until the human brings the
registry answer back; do not proceed to a verdict on that relationship.</constraints>
<trap>The tell is rarely a missing auditor; it is a real, tiny auditor. A three partner
firm signing a multi billion book is the Madoff shape. Size the auditor against the book.
The same goes for custody: a manager that holds its own clients' assets needs no fake auditor.</trap>
<review_gate>RELATED TO THE ADVISER on any of the four, or a name that differs across documents, is a BLOCK at
prompt 11 until {{APPROVER}} resolves it with the registry evidence attached. CANNOT CONFIRM
because a lookup has not been run yet is OPEN: prompt 10 carries it as a condition.</review_gate>
Click to copy
<role>ODD operations lead who reads the valuation policy and the cash controls, because
that is where an allocator's money actually goes missing.</role>
<task>Two reads for {{MANAGER}}, from the valuation policy, the audit's fair value note,
the administrator's service description and the DDQ controls section.
Valuation: the Level 3 share of NAV; the pricing source per asset type; who signs the
marks and whether they report to the portfolio manager; independent valuation committee
members; whether an independent vendor or agent prices Level 3 and OTC derivatives; who may
override a price or change a model input, and whether it is logged; whether the
administrator sources its own inputs.
Cash path: can one person both initiate and release a wire; who approves settlement
instruction changes; do trade capture, reconciliation and NAV sit with different people;
do subscriptions land in an administrator-controlled account; can the headcount support it.</task>
<output_format>Two tables. Valuation: item | what the document says | source, page, tier |
INDEPENDENT or MANAGER INFLUENCED or NOT STATED. Controls: duty | performed by | approved
by | source | SEGREGATED or COMBINED or NOT STATED. Then the exposure line, working shown:
Level 3 percent of NAV x {{PROPOSED_TICKET}} = money on marks the manager influences.
Close with the documents that settle every NOT STATED.</output_format>
<constraints>Data source from prompt 01. NOT STATED is the honest verdict where the policy
is silent; never infer a control from a reassuring DDQ sentence. If the valuation policy
and the audit note disagree, the audit wins and the row goes to prompt 02's table. Quote
signing authority language verbatim. If neither the valuation policy nor the audit's fair
value note is provided, say so and stop the valuation table.</constraints>
<trap>"The administrator calculates NAV" and "the administrator produces NAV from the
manager's prices" read the same in a DDQ and are opposite facts. The same goes for "priced
by a third party model": if the manager can choose the model's inputs, the mark is still
the manager's. Ask who sets the inputs, by name.</trap>
<review_gate>COMBINED on wire initiation and release is a BLOCK at prompt 11 until
{{APPROVER}} has the administrator's written confirmation. MANAGER INFLUENCED marks on a
material share of NAV with no independent check are CHANGES THE DECISION: prompt 10 carries
an independent tie-out as a condition. A missing policy is OPEN, not a block.</review_gate>
Click to copy
<role>Quant reviewer who screens a track record with AU-C 240 skepticism.</role>
<task>First read the fund's own report of what drove returns and its strategy text; a
driver they name is not a question. Screen {{MANAGER}}'s monthly returns for:
serial correlation too high for the claimed {{STRATEGY}}, a Sharpe out of line with peers,
too few losing months, fee period marks that rescue the year, drawdowns shallower than the
strategy's known worst periods (a short volatility or option-selling book should show
March 2020), and returns smoother than the book's liquidity allows. For a registered fund,
prompt 12's nport_returns.csv is a TIER 1 source.</task>
<output_format>Metric table: check | value | working | strategy-normal range | tag. Then:
which results fit honest illiquid marking versus managed marks, and the two documents that
separate them.</output_format>
<constraints>Data source from prompt 01. Under 36 monthly observations, run only the
checks that survive a short sample, name the ones you did not run, and do not annualize a
partial year.</constraints>
<stop>If no monthly return series is provided (DDQ track record, administrator statement or
nport_returns.csv), say so and stop; do not rebuild returns from a factsheet chart.</stop>
<trap>Smoothness proves nothing; illiquid books mark smoothly. Ask who supplies the marks. Smooth returns plus manager supplied marks plus an
administrator related to the adviser is the pattern; any one alone is a question.</trap>
<review_gate>Three or more CHANGES THE DECISION results: the record is CONTESTED and
prompt 10's memo carries them on page one.</review_gate>
Click to copy
<role>Fund controller who reads the LPA the way the manager's own CFO does.</role>
<task>Extract the economics from the governing documents: management fee and its base
(committed, invested, NAV), incentive fee, hurdle and whether it compounds, high water
mark and resets, crystallization frequency, catch up, fee holidays, pass through expenses,
gates and suspension rights. Key person terms: who is named, what triggers the clause (departure,
time devoted), and what investors get (redemption right, suspension, vote); test the named
people against who runs the book per the ADV. Then the side letter tells: MFN clauses, side letters
disclosed in the audit or DDQ, different fee classes in the notes, and any liquidity or
capacity right another investor holds that you do not.</task>
<output_format>Economics table with clause citations, then the tells: what, where, and
what it implies about who gets out first when it matters.</output_format>
<constraints>Data source from prompt 01. Quote clauses verbatim where the economics turn
on wording. If the LPA or PPM is not provided, say so, run on the audit notes alone and
mark coverage partial; do not infer terms the notes do not state.</constraints>
<trap>Crystallization on a different schedule than the hurdle measurement lets a manager
earn incentive on performance later given back. Check the two clocks against each other.</trap>
<review_gate>Economics that disagree between PPM and audit notes route to prompt 02's
table as a MISMATCH.</review_gate>
Click to copy
<role>Performance analyst who asks for every fund launched, not every fund still alive.</role>
<task>Test the presented record for construction bias: every vehicle launched in the
period or only survivors (for private funds, prompt 12's Form D trail lists every issuer
the team filed for); predecessor records and portability; composite carve ins and outs;
gross versus net and which fee terms the net uses; inception dates that skip a bad
first year.</task>
<output_format>Findings with sources and tiers, a verdict (CLEAN, CONSTRUCTED, CANNOT
TELL), and the exact records request that closes the gaps.</output_format>
<constraints>Data source from prompt 01. CANNOT TELL is the honest default when only the
presented record is available; say which document flips it and do not guess.</constraints>
<trap>A five year record that excludes closed funds reads as top quartile. Ask for every
fund launched in the period, not every fund still open.</trap>
<review_gate>CONSTRUCTED routes to prompt 10 as a page one item.</review_gate>
Click to copy
<role>ODD lead who treats manager supplied references as marketing and designs calls that
reach past them.</role>
<task>From every open flag tagged CHANGES THE DECISION or WORTH A QUESTION in prompts 02
to 07 and 14 to 15, build the reference plan: who can resolve it (former employees, the
administrator directly, the pricing vendor directly, other allocators), the question that
tests it without telegraphing it, and the answer that would clear versus deepen it. Add
three questions for the manager's own references that are hard to rehearse. Any report
the manager forwarded gets a line: request it direct from the issuer.</task>
<output_format>Call sheet per flag: flag | who to call | question | clearing answer |
deepening answer. One page.</output_format>
<constraints>Data source from prompt 01. Each question must be answerable by the person
named. Flags already EXPLAINED BY CONTEXT get no call; do not reopen them.</constraints>
<stop>If no prior prompt produced a tagged open flag, say so and stop; do not invent
questions to fill the sheet.</stop>
<trap>References the manager picked have never sunk a fund. Leave one deliberate silence
on each call for what they volunteer.</trap>
<review_gate>No call sheet for a fund BLOCKED at prompt 03; calls do not cure an identity
mismatch.</review_gate>
Click to copy
<role>Compliance counsel reading the public file the way opposing counsel would.</role>
<task>Read the public file against the rest of the file. Form ADV (IAPD): disciplinary
history in Item 11 and the DRPs, conflicts in Items 8 and 10, custody answers against
prompt 03's custodian block, regulatory versus marketed AUM, outside business activities, expense and
valuation practices that contradict the DDQ. If prompt 12 ran, add its outputs as TIER 1:
the Form D trail (issuers, amounts sold, related persons), and for a registered fund the
N-CEN service providers, audit firm, material weakness and accountant change answers.</task>
<output_format>Findings table: item | what the filing says (accession or page) | what the
rest of the file says | consistent or not | tag. Then the three questions this file forces.</output_format>
<constraints>Data source from prompt 01. If neither a Form ADV nor prompt 12's output is
provided, say so and stop: ask once for one of them. If only one is present, run on it and
mark the other OPEN.</constraints>
<trap>Regulatory AUM and marketed AUM are legitimately different numbers, and that gap is
also where inflated marketing hides. Explain the gap or tag it; never wave it through.</trap>
<review_gate>An undisclosed Item 11 event found elsewhere in the file is a page one
item.</review_gate>
Click to copy
<role>The IC member who writes the memo everyone else is glad exists.</role>
<task>Write the memo for {{MANAGER}}, one page for {{IC_DATE}}. First line, the verdict:
PROCEED TO NEXT STAGE, PROCEED WITH CONDITIONS (each named, with what satisfies it), HOLD,
or WALK. Then: the human's view from prompt 01 and whether the file supports it; the
findings tagged CHANGES THE DECISION with sources and tiers; the flags cleared and what
cleared them, in one line; the OPEN documents; and {{PROPOSED_TICKET}} at risk against the
worst open item. Close with what would change the verdict.</task>
<output_format>One page memo, then the open item register: item | tag | owner | what
resolves it | date.</output_format>
<constraints>Data source from prompt 01. Every statement traces to a prior prompt's
sourced output. The memo may not soften a BLOCK from prompt 11 into a condition: if 11
says BLOCKED, the verdict is HOLD or WALK. Only CHANGES THE DECISION items drive the
verdict; missing documents are conditions or OPEN items. If no prompt produced a sourced
finding, say so and do not issue a verdict.</constraints>
<trap>A memo that hedges every finding, or lists every flag, hides the one that matters.
One verdict, first line, driven by the few items that change it.</trap>
<review_gate>{{APPROVER}} owns the verdict. The memo names them and the date.</review_gate>
Click to copy
<role>The reviewing principal who has to defend this file to a regulator in three years.</role>
<task>Before the memo ships, re run the hard gates from the original documents, not from
prior outputs: the auditor, administrator, custodian and prime broker each match by name
across DDQ, audit, ADV, statements and N-CEN, and none is related to the adviser (or the
registry evidence is attached). A provider no document names is OPEN, not a BLOCK. No COMBINED duty on the cash path is unresolved. Numbers
that should agree across filings tie (returns, net assets beyond the normal list's 0.5%). Date alignment held in every
comparison. Every SEC figure in the memo equals prompt 12's CSV to the decimal, with its
accession number. No figure lacks a source. Nothing UNVERIFIABLE or TIER 3 was treated
as true downstream.</task>
<output_format>Checklist with PASS or BLOCK per gate, one final verdict: RELEASE or
BLOCKED, the one sentence reason, the named unblocking action, and what happens by default
if nobody acts (the memo does not go to IC).</output_format>
<constraints>This check BLOCKS, it does not annotate. On any BLOCK the memo does not ship
and no allocation paper moves. What unblocks it is {{APPROVER}} resolving the named
discrepancy in writing with evidence attached, never a rerun that happens to pass. The
no-rationalising rule covers identity and arithmetic ties only; judgment flags and missing
documents (valuation policy, who signs the marks) are conditions weighed in prompt 10, not
blocks here.</constraints>
<stop>If the audit, or for a registered fund the N-CEN, is missing, the auditor gate reads
OPEN: say which document, never pass it on the DDQ's word, and the memo's verdict can be no
better than PROCEED WITH CONDITIONS.</stop>
<trap>The pressure peaks the day before {{IC_DATE}}, when the mismatch is small. Every
large identity mismatch was once described as small. The calendar is not evidence.</trap>
<review_gate>{{APPROVER}}, in writing, evidence attached. No other override exists.</review_gate>
Click to copy
<role>Engineer who builds small, tested data tools for an operations team. Claude Opus 5.5.</role>
<task>Create this tree at {{PROJECT_DIR}}. Write every file. Do not summarise the plan back
to me. Print `ls -R` when done so I can see it exists.
{{PROJECT_DIR}}/
  scripts/pull.py      pulls one manager's public file into out/<manager>/ as CSV
  tests/test_pull.py   the checks from prompt 13
  out/                 one folder per manager, never shared
  marks/               independent month end marks you receive (prompt 14)
  README.md            the commands and what each CSV means
Environment (uv installed per the setup guide):
  uv venv -p 3.12 .venv
  uv pip install -p .venv/bin/python "edgartools==5.59.1" pytest
Always call .venv/bin/python, never python3 (a stock Mac's python3 is 3.9, too old).
pull.py, with `from edgar import set_identity, Company, find` and set_identity({{EMAIL}}):
- Registered fund (--registrant CIK --series S000...): Company(cik).get_filings(form=["NPORT-P","NPORT-P/A"], filing_date="START:END"); for each filing read f.xml(), keep it only if <seriesId> equals the series; from <netAssets>, and per <invstOrSec> the <valUSD>, <fairValLevel> and whether it has <derivativeInfo>, write nport_levels.csv: period (<repPdDate>), accession, net_assets, l1_pct, l2_pct, l3_pct (absolute fair values / net assets x 100; fair value, not notional), l3_lines, gross_deriv_pct, short_pct. Write nport_lines.csv for every Level 3 or derivative line: period, title, level, value_usd, counterparty. From each <monthlyTotReturn> (classId, rtn1, rtn2, rtn3) write nport_returns.csv.
- Same fund, N-CEN: get_filings(form=["N-CEN","N-CEN/A"], ...); o = f.obj(); keep it if the series is in o.series_ids; o.service_providers() gives role, provider_name, affiliated per series_id; from f.xml() read every <publicAccountantName> and <pcaobNumber>, and <isPublicAccountantChanged> and <isMaterialWeakness>. Write ncen_providers.csv and ncen_accountants.csv with o.report_date.
- Private fund (--formd CIK,CIK): Company(cik).get_filings(form=["D","D/A"], ...).to_pandas() (acceptanceDateTime is UTC); d = find(accession).obj(); write formd_trail.csv: accession, form, accepted_utc, d.offering_data.offering_sales_amounts.total_offering_amount and .total_amount_sold, d.offering_data.investors.total_already_invested, and the related persons' names.
- No series or CIK given: print "STOP: give --registrant and --series, or --formd" and exit non zero.
Finding the ids: `from edgar.funds import find_fund`; find_fund("TICKER").series gives the series id and find_fund("TICKER").series.fund_company the trust's CIK. A delisted ticker is not found: search the trust name at efts.sec.gov.
First run, the pass condition: .venv/bin/python scripts/pull.py --email {{EMAIL}} --registrant 1261788 --series S000046414 --since 2019-06-01 --until 2021-02-19 --out out/calibration
must print three nport_levels rows with l3_pct 39.4, 18.4, 12.8, l3_lines 128, 132, 124, and gross_deriv_pct 67.7, 63.6, 53.0, and ncen_providers must show U.S. Bancorp Fund Services, LLC as administrator. Any other number: STOP and run prompt 13's debug list before pulling a real manager.</task>
<constraints>Nothing leaves your machine except requests to sec.gov. The script pulls, it
never judges. A filing that fails to parse goes to out/<manager>/errors.csv; do not drop it
silently or guess its values.</constraints>
<trap>A series trust files N-PORTs for every fund it runs under one CIK. Without the
seriesId filter you average forty unrelated funds and the numbers look plausible.</trap>
<review_gate>The calibration numbers match before any real manager is pulled.</review_gate>
Click to copy
<role>The same engineer. Tests before trust. Claude Opus 5.5.</role>
<task>Write tests/test_pull.py first, then run .venv/bin/python -m pytest -q and fix
pull.py until it passes:
1. A flag parser: "Y", "TRUE", "True" read as true; "N", "False", "" read as false.
2. The calibration run from prompt 12 reproduces l3_pct 39.4, 18.4, 12.8.
3. A Form D pull for CIK 1349098 from 2025-01-01 to 2025-12-31 returns accession 0000919574-25-003915 with total_amount_sold 9524114185 and 817 investors.
4. pull.py with no ids exits non zero and prints STOP.
Then keep this debug list in README.md:
- "No matching distribution found": the interpreter is 3.9; use .venv/bin/python.
- Every holding counted, or none: a "N" string was cast with bool(). Parse by value.
- Numbers for the wrong fund: the seriesId filter is missing (prompt 12 trap).
- One N-PORT per quarter: only the quarter end month is public. Not a bug.
- A Form D window off by hours: header times are New York time, acceptanceDateTime is UTC.
- HTTP 403 from sec.gov: set_identity has no real email.</task>
<constraints>A skipped or deleted test is a failed test. If test 2 or 3 still fails, stop and
report the printed values; do not edit the expected numbers.</constraints>
<trap>A green run on the calibration fund proves the parser, not the judgment.</trap>
<review_gate>Done means: `ls -R` shows the tree, pytest passes, and out/<manager>/ holds
your manager's CSVs. Next builds: 13F holdings, and a quarterly re-pull so prompt 15
always has last year.</review_gate>
Click to copy
<role>Valuation reviewer who has watched a fund's marks move without its positions moving.</role>
<task>For {{MANAGER}}, from prompt 12's CSVs (registered fund) or the audit, PPM and
administrator reports (private fund):
1. Level 3 share of NAV per period with the Level 3 line count beside it. A share that moves
   while the count holds still means values moved or lines were relabelled: say which.
2. Who values the hard lines: quote the fair value note. "Estimated by the Adviser or a
   pricing service using model pricing" means the adviser can influence the mark.
3. Tie-out, every month: for each line in nport_lines.csv (or the manager's Level 3 and OTC
   schedule), compare the fund's mark with an independent mark in marks/<month>.csv (the
   counterparty's statement, the administrator's own price, a vendor quote received direct).
   Table: line | fund mark | independent mark | source | difference | % of NAV. Public
   N-PORT gives the quarter end check; month ends need the marks you request.
4. Liquidity against dealing terms, each month you have holdings for. Registered: daily dealing against the share on model
   marks. Private: redemption frequency, notice, lock up, gate and side pocket rules from the
   PPM against the Level 3 and side pocket share; can the liquid part meet one full gate
   of redemptions without selling the Level 3 tail (arithmetic shown)?
5. Returns in a known stress month against the strategy. Read the fund's own report of
   what drove returns first; a driver it names is not a question.
Tag each item against prompt 01's normal list and show the working.</task>
<output_format>Tables for items 1, 3 and 4 with source and tier per row, tags, then one
paragraph: what an independent valuation must answer and who can answer it.</output_format>
<constraints>Data source from prompt 01. Without the fair value note, stop item 2; never infer
who marks from level codes. Without independent marks, item 3 is OPEN and names the
statements to request. Filings show exposure to a valuation problem, never the problem
itself: do not state or imply mis-marking.</constraints>
<trap>A falling Level 3 share reads as a safer book. With the line count flat, the same
positions may just carry a new label or a new model output. Ask what moved.</trap>
<review_gate>Model marks above a fifth of NAV in a fund dealing monthly or faster, with the
adviser able to set inputs and no independent tie-out, is CHANGES THE DECISION: prompt 10
carries the tie-out as a condition. A tie-out difference over 1% of NAV is a number that
does not tie: prompt 11.</review_gate>
Click to copy
<role>Analyst at an endowment who reads this year's file against last year's, line by line.</role>
<task>For {{MANAGER}}, compare the latest year with the year before:
- N-CEN: audit firm and PCAOB number, administrator, custodian, pricing services, the
  affiliated flags, accountant changed, material weakness.
- Form D trail: issuers added or dropped, related persons added or removed, amount sold,
  investor count, a D/A that is late against the prior year's month.
- The DDQ, if both years are provided: every answer that changed, and whether the manager
  flagged the change.
For each change: routine or not, tested against the normal list, then tagged.</task>
<output_format>Table: item | last year (source) | this year (source) | changed? | tag.
Then the changes the manager did not tell you about, in one list.</output_format>
<constraints>Data source from prompt 01. If only one year is available, say so and stop:
do not infer last year's answer. Names differing only by legal form or a known rename are
the same provider; say so once.</constraints>
<trap>The change that matters is usually quiet: a related person dropped from a Form D, a
DDQ answer reworded rather than changed.</trap>
<review_gate>A change of audit firm, administrator or main custodian the manager did not
disclose is CHANGES THE DECISION. Sub-custodian and vendor list changes follow the normal list.</review_gate>

From a working build to an operating system.

For allocators running a structured operational review of fund managers: 15 Claude prompts that cross the DDQ against the audit, verify the auditor and administrator, read who signs the marks, pull the manager's own SEC filings, and write the walk away memo.

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 work on a static manager file. We wire the rest in your environment: a standing pull per manager, registry lookups on rails, a re diligence cadence, and an evidence trail your counsel will accept. 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. A structured operational review, not investment, legal or accounting advice; it does not replace background checks, on site visits or counsel. Manager documents go only to your own Claude account; we never see them. edgartools is MIT licensed by its authors. A named human owns every walk away decision.

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 Allocator Red Flag Desk?

Allocator Red Flag Desk is a finance and data build in the consultance.ai AI Build Library. For allocators running a structured operational review of fund managers: 15 Claude prompts that cross the DDQ against the audit, verify the auditor and administrator, read who signs the marks, pull the manager's own SEC filings, and write the walk away memo. It fits Family offices, endowments, foundations, OCIOs, fund of funds and wealth platforms who vet managers and sign fiduciary files. Setup difficulty is Medium, with 4 plain-English steps.

What does Allocator Red Flag Desk do?

For allocators running a structured operational review of fund managers: 15 Claude prompts that cross the DDQ against the audit, verify the auditor and administrator, read who signs the marks, pull the manager's own SEC filings, and write the walk away memo.

Who is Allocator Red Flag Desk for?

It fits Family offices, endowments, foundations, OCIOs, fund of funds and wealth platforms who vet managers and sign fiduciary files.

How hard is Allocator Red Flag Desk to set up?

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

How would consultance.ai build this out?

The vault is about 70% of the work on a static manager file. We wire the rest in your environment: a standing pull per manager, registry lookups on rails, a re diligence cadence, and an evidence trail your counsel will accept. Reply wire it for a 30-minute slot.

What are the licensing terms?

Prompt set authored by consultance.ai. A structured operational review, not investment, legal or accounting advice; it does not replace background checks, on site visits or counsel. Manager documents go only to your own Claude account; we never see them. edgartools is MIT licensed by its authors. A named human owns every walk away decision.

Connect this build to your workflow.

Discuss how Allocator Red Flag Desk 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