What QRs contain, how to extract and normalise look-through data across asset classes, and why doing it at scale is harder than it looks.
Most Limited Partners receive Quarterly Reports (QRs) from their GPs, file them in a shared drive, and move on. The document arrived; the box is ticked.
A smaller number of LPs treat the QR as something more valuable: a structured data source that, if properly extracted and normalised, gives them exposure-level visibility into what they actually own across their entire portfolio. Not fund-level aggregates, but company-level detail — sector by sector, geography by geography, GP by GP.
The gap between these two approaches is widening. As private markets portfolios grow in size and complexity, the investment teams that have built systematic look-through capabilities are making better allocation decisions, identifying hidden risks earlier, and arriving at manager reviews with more pointed questions. Those who rely on fund-level data alone are, in effect, flying blind below the surface.
This guide covers what Quarterly Reports contain, which sections matter most for investment teams, how to extract and normalise look-through data across buyout, venture, credit, and real assets, and why the technical challenges of doing this at scale are more significant than they first appear.
This article is part of the Tamarix series on GP fund documents. For an overview of all four document types LPs receive, start with The LP's Guide to GP Fund Documents.
QRs are the most information-rich document in the LP's reporting stack — and the most variable in format and depth. A buyout fund QR from a large institutional GP may run to 60 or 80 pages with detailed company write-ups and audited valuations. A venture fund QR from a smaller manager may be a 10-page PDF with a one-line investment schedule and minimal commentary. The sections below represent what a well-structured QR typically contains — not what every GP delivers.
|
Section |
What It Contains |
Primary User |
|
Market commentary |
GP's view on macro conditions, sector trends, and portfolio implications |
Investment Team, CIO |
|
Fund activity summary |
Capital deployed in period, number of new investments, exits, dry powder remaining |
Investment Team, Operations |
|
Fund performance metrics |
Net and gross IRR, TVPI, DPI, RVPI — at fund level and sometimes by strategy or vintage |
CIO, Investment Team |
|
Investment schedule |
Table of all portfolio companies: cost, proceeds, fair value, sometimes sector and geography |
Investment Team, Accounting |
|
Portfolio company write-ups |
Narrative updates per company: financials, strategic highlights, recent developments, valuation notes |
Investment Team |
|
ESG / responsible investing update |
ESG metrics, portfolio company initiatives, regulatory compliance notes |
IR, Compliance (where required) |
For investment teams, the two sections that matter most are the investment schedule and the portfolio company write-ups. Everything else — performance metrics, fund activity, market commentary — is context. The investment schedule and write-ups are where the look-through data lives.
The standard objection to look-through analysis is familiar: 'It's a blind pool strategy. If I trusted the GP enough to commit, why am I second-guessing them every quarter?' It's a reasonable position — for a portfolio of two or three funds. It stops being reasonable at ten, fifteen, or twenty fund commitments.
At that scale, looking only at fund-level data means you don't know how much of your portfolio is exposed to a single sector, a single geography, or a single macro theme. You might have five GPs all concentrated in software, all using similar leverage, all marking to public comps that have since de-rated. Fund-level data won't tell you that. Look-through data will.
The most direct use of QR data is verifying that GPs are executing on their stated strategy. A GP who pitched mid-market healthcare in Western Europe should have a portfolio that reflects that. Comparing the actual investment schedule against the pitch deck is a basic accountability check — and one that LP investment committees increasingly expect their teams to perform.
Over time, look-through data enables attribution analysis: understanding whether returns are driven by earnings growth, debt paydown, or multiple expansion. This distinction matters for manager evaluation — and for understanding whether a GP's performance is repeatable or a function of a favourable market cycle.
It also supports re-underwriting decisions. By tracking how individual portfolio companies have evolved — in terms of revenue trajectory, margin development, valuation methodology, and exit progress — investment teams can form a more grounded view of whether to re-commit to the same GP in their next fund. Bottom-up company-level data is a more reliable input to that decision than fund-level returns alone, which can mask wide dispersion across individual investments.
Portfolio-level concentration risk is invisible at the fund level. An LP with commitments to five funds might appear well-diversified — different GPs, different vintages, different stated strategies. But if the underlying portfolios all have significant exposure to the same sector, the diversification is superficial.
Look-through analysis surfaces these concentrations before they affect performance. It also enables NAV validation: if a GP marks up an asset aggressively, cross-referencing the implied multiple against sector comps or the write-ups of other GPs holding similar assets provides a data-driven basis for asking harder questions in the next LP advisory committee meeting.
For LPs managing large, diversified private markets programmes, look-through data is the foundation of intentional portfolio construction. Without it, sector and geography allocation is a function of which managers you've committed to — not a deliberate expression of risk and return preferences.
With it, LPs can identify where they are overallocated — too much software exposure, not enough Asia — and adjust their commitment pacing accordingly. They can flag vintage year concentration risk. They can model how the portfolio will evolve as older funds harvest and new commitments deploy. This level of portfolio management is impossible without company-level data aggregated across all fund commitments.
The investment schedule is the most consistently available data source in a QR. Nearly every GP includes some version of it — a table listing portfolio companies with cost, value, and proceeds. It is the starting point for any look-through programme, regardless of asset class or strategy.
|
Field |
Description |
Notes for Normalisation |
|
Company name |
Name of the portfolio company |
Entity names change — track aliases across quarters; M&A and restructurings introduce new names for the same asset |
|
Investment date |
Date the fund first invested in the company |
Not always provided; useful for calculating hold period |
|
Cost / invested capital |
Total capital deployed into the company to date |
May be reported at cost or adjusted cost; confirm whether add-ons are included |
|
Proceeds to date |
Capital returned from the company (partial exits, income) |
Typically in QRs; often absent from FS; may net against cost or be shown separately |
|
Unrealised value |
Current GP mark on the investment |
Valuation methodology varies — public comps, DCF, cost; not always disclosed in QR (see FS) |
|
Sector |
Industry classification of the portfolio company |
No standard taxonomy — normalise to GICS or a consistent internal framework across GPs |
|
Geography |
Country or region of the portfolio company |
Varies from city-level to regional — normalise to ISO country codes or standard region groupings |
|
Fund ownership % |
The fund's ownership stake in the company |
Not always disclosed; important for co-investment tracking |
|
Status |
Active, partially exited, fully realised, written off |
GPs use different labels — standardise to a fixed taxonomy |
The investment schedule is where look-through data begins — and where most extraction programmes run into their first serious problem. The data is there, but it isn't standardised. Every GP uses their own sector taxonomy, their own geography classification, and their own naming conventions for the same underlying concepts.
Sector classification is the most common point of failure. One GP might classify a company as 'Software.' Another calls it 'Enterprise SaaS.' A third uses 'Technology — Application Software.' All three may be describing the same type of business — but without normalisation, they appear as three different sectors in any cross-portfolio analysis. The solution is to map every GP's sector tags to a consistent internal taxonomy — GICS Level 2 is a common choice — at the point of extraction.
Geography faces the same problem at different granularity levels. 'United States,' 'California, USA,' 'North America,' and 'San Francisco' have all appeared in investment schedules describing the same company's location. For exposure analysis, these need to be normalised to ISO country codes or a standard regional framework.
This normalisation work is not glamorous. But it is what separates a look-through programme that produces actionable insight from one that produces a pile of inconsistently tagged data that nobody trusts.
If the investment schedule gives you the map, the portfolio company write-ups give you the story. For buyout and growth equity funds in particular, this section of the QR contains the richest data available to an LP outside of a formal management meeting.
|
Field |
Typical Content |
Investment Team Use Case |
|
Company description |
Business model, market position, investment rationale |
Confirm mandate alignment; track thesis evolution |
|
Financial metrics |
Revenue, EBITDA, net debt — at entry and current; sometimes forward-looking |
Performance attribution: top-line growth vs. margin improvement vs. leverage |
|
Valuation methodology |
Methodology used to mark the asset (comps, DCF, cost) |
NAV validation; cross-reference against sector benchmarks |
|
Recent developments |
Add-ons, management changes, refinancings, market events |
Monitor portfolio activity between formal LP reporting cycles |
|
Key risks |
GP's view of material risks to the investment |
Risk monitoring; flag concentration or correlated risks across GPs |
|
Exit outlook |
Expected timeline and route to exit |
Liquidity forecasting; distribution pacing models |
Unlike the investment schedule — which is tabular, however inconsistently formatted — portfolio company write-ups are narrative text. Fields don't appear in fixed positions. Financial metrics are embedded in sentences. Valuation commentary may be in a footnote or a sidebar. The same metric — revenue, for example — might refer to trailing twelve months in one write-up, forward estimates in another, and bookings in a third.
This variability makes rule-based extraction useless and general-purpose OCR insufficient. Understanding that 'Revenue grew 32% YoY to $148M' means current revenue is $148M requires contextual language understanding, not pattern matching. It also requires knowing that the prior quarter's write-up reported $112M in revenue — so the 32% figure is consistent — which requires entity resolution across reporting periods.
Done well, write-up extraction transforms look-through from an exposure mapping exercise into an investment insight engine: enabling attribution analysis, GP benchmarking, and valuation validation at scale.
One of the most common mistakes in building a look-through programme is applying the same extraction schema across all asset classes. The investment schedule fields that matter for a buyout fund are materially different from those that matter for a private debt fund or an infrastructure manager. The table below captures the key differences.
|
Asset Class |
Investment Schedule Detail |
Company Write-Up Depth |
Key Metrics to Extract |
|
Buyout |
Most detailed — one line per company |
Extensive — revenue, EBITDA, net debt, valuation methodology |
Entry/current EV, EBITDA margin, net leverage, hold period |
|
Venture Capital |
Lightest — often just name, cost, fair value |
Sparse to moderate — KPIs over financials for early stage |
ARR, burn rate, runway, round valuation, ownership % |
|
Growth Equity |
Moderate — between buyout and VC in detail |
Revenue-focused; less consistent than buyout |
Revenue growth, EBITDA (if profitable), valuation multiple |
|
Private Debt |
Loan-level data: borrower, tranche, maturity, coupon |
Minimal narrative; compliance and performance focus |
Interest coverage, LTV, PIK vs. cash pay, maturity profile |
|
Real Estate |
Property-level: location, type, appraised value |
Occupancy, rental income, capex, tenant detail |
Occupancy rate, NOI, cap rate, appraised value vs. cost |
|
Infrastructure |
Asset-level: contract tenor, offtaker, revenue model |
Operational KPIs, ESG metrics, GRESB data |
Contracted vs. merchant revenue, uptime, DSCR |
The practical implication is that look-through infrastructure needs to be modular: a core schema of universal fields (company name, sector, geography, cost, fair value) that applies across all strategies, with asset-class-specific extensions layered on top. Forcing a single rigid schema across all asset classes either loses relevant data from specialised strategies or creates noise in the common fields.
The temptation when building a look-through programme is to extract everything — every field that appears in every QR, regardless of whether it will ever be used. This creates an unmaintainable data set that teams stop trusting within two or three quarters.
The right approach is to start with use cases. What decisions does the investment team need to make? What does the CIO need to report to the board? What risk monitoring does the risk committee require? Work backwards from those questions to define the minimum viable schema — then add fields only when a specific use case demands them.
A modular schema — universal core plus strategy-specific extensions — is the only architecture that scales across a multi-strategy portfolio without either losing data or creating noise. This also makes it easier to onboard new managers: the universal fields are always populated, the strategy-specific fields are populated where available.
GPs will not standardise their reporting to match your taxonomy. The normalisation burden sits entirely with the LP. This means building and maintaining a mapping layer: sector tags to GICS, geography tags to ISO codes, valuation methodology labels to a fixed taxonomy, company name variants to a single canonical entity. This mapping layer is one of the most valuable assets an LP operations function can build — and one of the hardest to recover once it has been allowed to degrade.
A portfolio of 30 fund commitments generates 120 QRs per year. Each QR may contain data on 10 to 50 portfolio companies. At 20 fields per company, a single reporting cycle can mean 60,000 to 180,000 data points that need to be extracted, validated, and normalised. This is not a spreadsheet problem. It is a data infrastructure problem.
GPs change their QR templates. Columns move. Sections are renamed. New KPIs are added; old ones disappear. A company that was reported as a single entity gets restructured and appears as two. Any extraction approach that relies on fixed template logic will break — regularly. Resilience to format drift is not a nice-to-have feature in a look-through programme; it is a prerequisite for reliability.
Tracking the same portfolio company across 12 to 16 quarterly reports — across name changes, restructurings, add-on acquisitions, and GP template updates — requires entity resolution logic that operates at the level of the whole dataset, not individual documents. Without it, point-in-time analysis is possible but time-series analysis breaks down. And time-series analysis — tracking how a company's financials evolve over a hold period — is where the most valuable investment insights live.
Investment teams want look-through data quickly — ideally within a week or two of QR receipt. Accounting teams want it accurately — with every field validated against the source document. These pressures pull in opposite directions. Manual workflows prioritise accuracy but sacrifice speed. Automated workflows can be fast but may sacrifice accuracy without human-in-the-loop review built in. Building a workflow that achieves both — fast and accurate, at scale — is the central design challenge of any look-through programme.
LPs have four main options for extracting look-through data from QRs. Each involves different trade-offs across accuracy, scale, auditability, and resilience to format changes.
|
|
Manual |
OCR |
General LLMs |
Private Markets AI |
|
Accuracy |
High (with skilled analyst) |
Moderate — breaks on complex layouts |
Variable — hallucination risk |
High — trained on PM documents |
|
Scale |
Low — bottleneck at 20+ funds |
Moderate — fast on clean PDFs |
Moderate — fast but needs verification |
High — built for volume |
|
Format resilience |
High — human adapts |
Low — breaks on template changes |
Moderate — context-aware but inconsistent |
High — adapts to GP-specific formats |
|
Auditability |
Full — analyst can trace every field |
Partial — output visible, logic opaque |
Low — no source tracing |
Full — every field traceable to source |
|
Normalisation |
Manual — analyst applies framework |
None — raw extraction only |
Partial — inconsistent across reports |
Built-in — taxonomy normalisation at extraction |
|
Best suited for |
Small portfolios (<15 funds) |
Supplementing manual on clean reports |
Ad hoc queries, not systematic workflows |
Portfolios of 15+ funds; systematic look-through |
For most LP organisations managing more than 15 fund commitments, the manual approach becomes a structural bottleneck within two to three years as the portfolio grows. OCR handles the easy cases but fails systematically on the complex ones — which, in private markets QRs, are the majority. General-purpose LLMs are fast but create a verification burden that often negates the time savings. Purpose-built private markets AI is the only approach that combines scale, accuracy, auditability, and format resilience — but it requires integration into LP workflows to realise its value.
Quarterly Reports are the richest source of look-through data an LP has access to — but the data doesn't extract itself. The teams that build systematic workflows around QR extraction don't just save time; they see things in their portfolios that fund-level reporting will never surface.
How Tamarix helps: Tamarix is purpose-built for private markets QR extraction — trained on the full range of GP report formats across asset classes. It extracts investment schedule data and company-level financials, normalises sector and geography tags to your internal taxonomy, resolves entity names across reporting periods, and delivers structured outputs directly into LP workflows — with full source traceability and a human-in-the-loop review layer. Book a call to learn more.
A Quarterly Report (QR) is a document issued by a General Partner (GP) to its Limited Partners (LPs) every quarter, providing an update on fund performance, portfolio activity, and the status of underlying investments. It typically includes fund-level performance metrics (IRR, TVPI, DPI), an investment schedule listing all portfolio companies with their cost and current fair value, narrative write-ups on individual portfolio companies, and a market commentary section. QRs are issued with a 45–90 day lag after quarter end and are the primary source of look-through data for LP investment teams.
A Quarterly Report is a management document produced by the GP — performance-oriented, narrative-rich, and designed to inform LPs about portfolio activity and fund progress. A Financial Statement is a formal accounting document — typically audited — governed by accounting standards (GAAP or IFRS) and covering the fund's balance sheet, income statement, and detailed schedule of investments. For investment teams, the QR is the primary monitoring document; for accounting and finance teams, the FS is the primary reference for valuation validation and audit purposes.
Look-through analysis is the process by which LPs extract and structure data on the underlying portfolio companies held by their GP-managed funds — going beyond fund-level metrics to understand company-level exposures, financials, and performance drivers. The primary data source for look-through is the investment schedule and portfolio company write-ups in Quarterly Reports. Look-through enables investment teams to monitor mandate alignment, identify hidden concentration risks across multiple GPs, perform performance attribution, and make more informed portfolio construction decisions.
The investment schedule is a table in the QR that lists all of the fund's portfolio companies, typically showing for each company: the cost (invested capital), proceeds received to date, current fair value, and often sector and geography classification. It is the most consistently available look-through data source across GP reporting styles — nearly every GP includes some version of it regardless of how detailed or sparse their overall reporting is. For LPs building look-through programmes, the investment schedule is the starting point for exposure mapping.
Normalising sector and geography data from QRs requires building a mapping layer that translates each GP's classification labels into a consistent internal taxonomy. For sectors, GICS (Global Industry Classification Standard) Level 2 is a widely used framework — you map each GP's label ('SaaS,' 'Enterprise Software,' 'Technology') to the corresponding GICS category ('Application Software'). For geography, ISO 3166 country codes provide a consistent standard — you map labels like 'United States,' 'USA,' 'North America' to the appropriate country code or regional grouping. This mapping needs to be maintained and updated as GPs change their labels and as you onboard new managers.
There is no standard answer — it varies by GP. Larger institutional managers with established investor relations functions tend to maintain consistent formats for extended periods; smaller or emerging managers may update their templates more frequently. Template changes can range from minor (a column renamed, a section reordered) to significant (a complete overhaul of the reporting format). Even minor changes break rule-based extraction logic, which is why resilience to format drift is a key criterion when evaluating any automated look-through solution.
Gross IRR measures the return generated by the fund's investments before the deduction of management fees, carried interest, and fund expenses — essentially the raw investment performance. Net IRR is the return actually received by LPs after all fees and costs have been deducted. The difference between gross and net IRR reflects the total cost of the GP relationship. Both figures are typically reported in the QR, and the spread between them is a useful input when comparing manager value for money. LPs should always use net IRR for performance comparisons and allocation decisions.
Three structural challenges make QR automation non-trivial. First, there is no standard format: every GP produces QRs differently, with different layouts, field labels, and levels of detail — meaning every document requires a bespoke extraction approach. Second, QR formats change over time as GPs update their templates, breaking any fixed extraction logic. Third, the most valuable data — company-level financials and narrative commentary — is unstructured text, not tabular data, requiring language understanding rather than pattern matching. Additionally, tracking the same company across multiple quarters requires entity resolution logic that operates across the entire dataset. General-purpose tools handle parts of this; purpose-built private markets AI handles all of it.