River
Y CombinatorBacked by Y Combinator
FREE TEMPLATE

LP DDQ Response Template

Four documents and three sheets that mark an approved answer stale the day its underlying fact changes, not on whichever date review was next scheduled.

Free download  ·  No account needed

Question Bank

[Firm], [Fund] — DDQ Answer Bank

Every answer carries the specific facts it depends on. A row goes stale the day one of those facts changes, not on whichever date it was next due for review.

SectionQuestionTrigger DependencyLast ReviewedStatus

A row reviewed yesterday is exactly as stale as a row reviewed a year ago the moment the fact underneath it changes.

Ardnahoe Capital Partners approved nine Question Bank rows on 14 January 2027, naming MacRae Fenwick as a Senior Investment Professional and a named Key Person across three DDQ sections. Fenwick left the firm on 3 April. Ardnahoe's review cadence is semi-annual, so the next scheduled pass over those nine rows was not due until 13 July. The fundraise did not pause for that gap: eight more DDQs went out on the normal biweekly cadence, each carrying all nine now-wrong rows, 72 stale answer-instances a same-day trigger would have caught at zero.

Page one for this query is the ILPA DDQ itself, a couple of best-practice guides, and an LP-side checklist. All three agree the fix is to keep a living answer bank and update it on a schedule, quarterly or after each close. That schedule is exactly the gap in the worked example. The ILPA DDQ asks outright whether a Key Person event has occurred, which means an LP is going to ask the one question a scheduled review answers correctly for 101 days after it stopped being true.

One relationship manager corrected two of the nine rows by hand on a call, and the fix never went back into the bank. Fourteen days later the next prospect received the old text for the same two questions, in writing. Two LPs now hold two different answers to the same question, which a merely late answer never produces. Federal law already treats a fraud or deceit on a prospective client as unlawful for an investment adviser. The Prospect Register exists to catch that gap before an LP does.

One departure, nine rows, and the check that catches it the same day

The Question Bank, the trigger-versus-review-date comparison, and the Prospect Register.

Question Bank

Illustrative. Ardnahoe Capital Partners, raising Fund III. Nine rows across three sections name MacRae Fenwick, Senior Investment Professional and a named Key Person.

RowSectionTrigger DependencyLast ReviewedStatus, as of 18 Apr
Q-0143. Key PersonsMacRae Fenwick employment2027-01-14Stale, superseded 2027-04-03
Q-0419. TeamMacRae Fenwick employment2027-01-14Stale, superseded 2027-04-03
Q-09114. Track RecordMacRae Fenwick employment2027-01-14Stale, superseded 2027-04-03
Rows naming Fenwick, all sections9 of 187
Q-0163. Key PersonsNone2026-11-02Current
Q-10714. Track RecordNone2026-09-30Current

Reviewed and approved 14 January, the same date as every row above. The nine Fenwick rows and the two shown with no dependency were equally “current” by the calendar right up to 3 April. Only a dependency check tells them apart.

Date-Based Review vs. a Same-Day Trigger

Semi-annual, 180-day review cadence. Approved 14 Jan 2027; next scheduled review 13 Jul 2027. Fenwick departs 3 Apr 2027, 101 days before that review.

MeasureDate-based reviewSame-day trigger
Days the 9 rows read “current” after the departure1010
DDQs sent during that gap, of 16 sent all fundraise8 of 160 of 16
Stale answer-instances actually shipped (8 sends × 9 rows)720
DDQSentProspectStatus
#62027-03-21Dalmellington Pension TrustCorrect, pre-departure
#72027-04-04Loanhead Insurance GroupHand-corrected on the call, 2 of 9 rows only
#82027-04-18Ardgour Family OfficeAll 9 rows sent stale
#142027-07-11Blairgowrie University EndowmentAll 9 rows sent stale
#152027-07-25Kirriemuir Municipal EmployeesCorrect, post-review refresh

The first stale send is DDQ #7, the day after the departure. A same-day trigger flags all nine rows on 3 April itself, before DDQ #7 goes out at all.

Prospect Register: the Inconsistency a Trigger Prevents

Two prospects, eleven days apart, asked the same Question Bank rows.

ProspectSentQ-014, Key PersonsQ-041, Team tenure
Loanhead Insurance Group2027-04-04Hand-corrected verbally: Fenwick departedHand-corrected verbally: Fenwick departed
Ardgour Family Office2027-04-18Bank text: Fenwick active, Key PersonBank text: Fenwick active, 11 years tenure

The correction given to Loanhead on a call never made it back into the Question Bank, so Ardgour received the pre-departure text fourteen days later, in writing. Two LPs now hold two different answers to the same two questions.

What's in the pack

01

DDQ Response Library

The assembled response to an incoming questionnaire, section by section, copied from current Question Bank rows instead of redrafted. Section 13 tracks the same governance facts your annual fund audit revisits every year.

02

Question Bank

One row per question the firm has been asked, with the approved answer, the date it was last reviewed, and the specific facts that answer depends on.

03

Prospect Register

Which version of the bank each prospect actually received, so a later trigger event can be checked against what a specific LP was told, not against what the bank currently says.

04

Custom Request Log

The questions no bank row covers yet, tracked from the date received to the date folded into the bank as a standing row.

05

Track Record Presentation

Deal-by-deal detail with the IRR and TVPI methodology stated on the same page as the numbers, pulled from the reconciled deal list in a track record pack rather than assembled fresh for each DDQ.

06

Reference Coordination Note

Who has been asked for a reference this fundraise, by whom, and what they were told to expect, so no reference takes the same call four times unwarned.

07

LP Pitch Outline

An outline for the firm's own deck software that traces every slide's claim back to a Question Bank row, the Track Record Presentation, or a figure already sent in the quarterly LP letter.

How it works

  1. 1

    Open in River, or download it

    Open the pack in River and let the agent build the bank from your own documents, or download the blank Word and CSV files instantly.

  2. 2

    Send what you already have

    A completed DDQ, team bios, and your track record. The agent drafts each Question Bank row and names the specific facts the answer depends on.

  3. 3

    Log what's about to change

    A departure, a final close, a new fund launch. Logging it the day it happens finds every row that depends on it, the same real-fact-over-convention check the K-1 and tax package pack runs before allocating a gain.

  4. 4

    Answer the next DDQ from the bank

    Match incoming questions to bank rows, correct anything stale before it goes out, and log which version each prospect received.

Frequently asked questions

Is this template free?

Yes. The Question Bank, Prospect Register and Custom Request Log sheets, plus the DDQ Response Library, Track Record Presentation, Reference Coordination Note and LP Pitch Outline documents, download free with no account and no time limit. Edit with AI opens the same pack in River with an agent already primed to build the bank from your own fund's documents.

What does 'Edit with AI' actually do?

It creates a free account, installs this exact pack as a private space, and opens it with River already primed to ask for your most recent DDQ, team bios and track record. Nothing is shared with other firms, and no answer is marked current until you confirm it yourself.

What counts as a trigger event?

A trigger is any fact a Question Bank row depends on: a named person's employment, a fund's AUM band, whether a strategy change has happened. Logging one searches every row's dependency list and marks every match stale the same day, rather than waiting for that row's next scheduled review to notice.

Who decides whether a departure counts as a Key Person event?

Whatever the firm's own documents say it is. A Key Person event is usually defined in the LPA's key person provision, and that definition decides whether a specific departure counts. This pack does not decide that question; it propagates whatever the firm confirms has happened to every row that names it.

Does this replace the ILPA DDQ?

No. The ILPA DDQ is the questionnaire an LP sends; this pack is the bank a firm answers it from. Section 3 of the ILPA DDQ asks directly whether a Key Person event has occurred, and that is the exact question a stale row answers wrong for as long as it stays stale.

What format are the downloaded files?

Word documents for the DDQ Response Library, Track Record Presentation, Reference Coordination Note and LP Pitch Outline, and CSV for the three sheets. The documents open in Word, Pages and Google Docs. The sheets open in Excel, Numbers and Sheets with every column intact.

Find out which of your Question Bank rows a departure would touch

Send your last completed DDQ, team bios, and your track record. The first pass builds the bank with every answer's trigger dependencies named.

Edit with AI