LP Data Request Generator

Builds complete, structured data request packages for LPs to send to GPs at every stage of the relationship — initial due diligence, quarterly monitoring, annual review, and re-up evaluation. Output includes an itemized request table (with format, benchmark, and red flag trigger per item), a ready-to-send cover letter, a response tracking template, and an ILPA compliance gap analysis. Use it when preparing a new GP commitment, formalizing a monitoring framework, or structuring a re-up data request.

investor-relationsdue-diligencereporting

01 · Problem

LPs need to demand specific, comprehensive data from GPs at every stage of the relationship -- initial due diligence, quarterly monitoring, annual review, and re-up evaluation. Vague data requests produce vague responses that leave LPs without the information needed for informed allocation decisions. Most LPs lack standardized request templates, leading to inconsistent data collection across managers and missed red flags.

02 · Who & When

LP due diligence professionals, portfolio managers, and consultant advisors generate data requests during initial GP evaluation (100-200+ line items), quarterly monitoring (40-60 items), annual review (80-120 items), and re-up evaluation cycles. Initial DDQ requests are sent 3-6 months before commitment. Quarterly monitoring is ongoing for the life of the fund (7-12 years).

03 · How It's Done Today

LP teams maintain internal DDQ templates in Word or Excel, often based on ILPA Reporting Template v3.0. Each request is customized by fund type, strategy, and specific concerns. GP response tracking is manual -- comparing what was requested against what was provided. Sophisticated LPs track response completeness as a signal of GP transparency.

04 · What This Skill Changes

Excellent data request generator. The branching by request type (initial DD, quarterly, annual, re-up) and by fund characteristics (strategy, structure, asset class) produces appropriately scoped requests. The interrogation protocol ensures requests are targeted. The emphasis on specifying exact data fields, expected formats, and analytical purpose for each item produces requests that leave no room for GP evasion. Directly usable as a starting template for LP teams.

05 · Risks & Caveats

Low - Data requests are information-gathering tools, not compliance documents. The main risk is requesting data that is not relevant to the specific fund type or strategy, which wastes GP time and signals unsophisticated LP oversight. The branching logic mitigates this risk.