How LPs can prove control as portfolios scale

For most of the last decade, control looked like a set of activities. A quarterly review, a reporting pack for the committee and a call when a number looked wrong. Its evidence was the absence of unpleasant surprises.

That model is breaking down, not because LPs have grown less diligent but because their portfolios have outgrown it.

An allocator now sits across dozens of funds, multiple managers and several jurisdictions, while expectations from regulators, boards and beneficiaries tighten in parallel.

So the question has changed. It is no longer what happened in the portfolio, but whether the LP can demonstrate that oversight always happens, in the same way and would survive scrutiny.

Control is also fast becoming something an LP must prove: a standing property of the operating model rather than a recurring task.

The moment oversight fails is rarely loud. The real risk is not a botched audit or an unanswerable regulatory question. It is that LPs manage growth until, gradually, they do not.

An in-house team or a traditional administrator absorbs each new fund and each new regulatory ask, filling the gaps with extra hours, manual reconciliation and institutional memory. Quietly, systems proliferate alongside: fund administration in one place, portfolio monitoring in another, risk somewhere else. What emerges is not an integrated operating model but a patchwork of parallel records, each authoritative in its own silo and reconciled by hand at the seams.

The strain is real, but it is managed, and that is precisely the trap. A process that works for eight funds on a spreadsheet is not a smaller version of control at eighty; past a point, it is the absence of control that has not yet surfaced.

Trace the crackle far enough, and it returns to data debt: whether information is available, what it costs to source and process, and whether the team can stand behind it.

Understanding why that debt accumulated requires stepping back. Institutional allocators have steadily increased private markets exposure over the past decade, driven by return targets that public markets struggled to meet and the appeal of diversification beyond listed assets. That shift proved sticky, and the consequence is commitment fragmentation: LPs now manage positions across buyout, private credit, infrastructure and real assets, spread across vintages, geographies, jurisdictions and managers, each with its own reporting format, regulatory context and data convention. The portfolio grows, but so does the surface area that oversight must cover.

Several forces are turning that complexity into a structural problem. Three in particular stand out.

The first is regulatory. For the institutional capital behind private markets, supervision increasingly examines the process, not just the output.

Under Solvency II, an insurer's Own Risk and Solvency Assessment and the look-through treatment of fund holdings mean opacity carries a cost: where exposures cannot be seen at the required granularity, capital charges rise.

IORP II pushes pension schemes the same way, demanding evidence of a repeatable risk-management system rather than a one-off answer.

The second is investor expectation. A 2025 CSC study found close to half of LPs were not receiving the investment-level detail they needed, and roughly three-quarters now expect daily or on-demand access to performance. A quarterly pack assembled by hand cannot meet that standard. That expectation is already reshaping how GPs report: ILPA’s updated Reporting Template, landing for Q1 2026, reflects a market moving toward comparability and consistency as a baseline. For LPs, the transition period creates its own friction – formats are inconsistent across managers, ingestion workflows built around bespoke reports must adapt, and the operational burden falls on whoever reconciles the difference.

The third is retailisation. As private markets open to wealth and semi-liquid channels through vehicles like ELTIF 2.0, GPs are producing data at greater frequency and in greater detail than the institutional market ever required. For the LP, this is not a disclosure question but an operational one: more granular data arriving more often raises the bar for what it means to ingest, process and maintain a coherent portfolio view. An infrastructure built around quarterly packs was not designed for that cadence, and the gap shows.

In short, the trajectory is shared even where the pressure is uneven. The largest LPs feel it first and hold the most leverage to demand good data.

Smaller allocators reach the same point at a gentler pace, often driven less by external mandate than by leaders who want a more modern way of working.

If control is a property to be demonstrated, it helps to test it against your own operation rather than an ideal. Provable control is not a pile of dashboards but a dependency chain, and the order matters. Four questions locate where a portfolio actually sits.

The order is deliberate. Visibility built on inconsistent data is cosmetic; repeatability without visibility only produces the wrong picture faster, and auditability is the proof layer that the other three exist to support.

Where your first honest "no" appears is where the work starts, and for most LPs, that is earlier in the chain than they expect.

Here is the objection most discussions avoid. Building all of this internally is expensive and specialised, and most LPs, even large ones, do not attempt it alone.

They outsource parts of the operation to sustain scale. So has the LP simply handed control away?

The answer depends on the partner, and for most LPs the gaps in traditional solutions become visible precisely where the dependency chain demands most. Traditional solutions typically stop at reliable transaction-level processing: positions are recorded, valuations are captured and reports are produced. That is necessary but not sufficient.

What it rarely delivers is the enrichment layer: static data that gives context to positions, look-through capability that pierces fund-level NAVs to underlying exposures, and the granularity needed to satisfy risk and portfolio monitoring in a single coherent system. Beyond that sits the computation layer: a calculation engine that transforms consolidated data into meaningful portfolio intelligence: performance measurement, risk metrics and attribution that the LP can stand behind and trace to source. Without both, an LP can have clean data at the fund level and still be blind across the portfolio.

The LPs who scale without losing command choose differently. They select partners who combine genuine technology with institutional-grade service, so the allocator retains full ownership of its data and processes even as execution is shared.

Outsourcing the work is not the same as outsourcing the control. Done well, it is how command and transparency are retained.

Control at scale is no longer a workflow or a reporting cadence. It is infrastructure: a standing capability that produces consistent, traceable, auditable visibility, owned by the LP even where execution is shared.

The payoff is not tidier reporting but the ability to answer a regulator, board or auditor on their timeline and to keep doing so through the part of the cycle when improvised oversight tends to collapse. The LPs who navigate the next decade well will be the ones who could prove, mid-downturn and on an auditor’s timeline, that their oversight was never improvised – because they treated control not as something they did but as something they built.

This article was written in collaboration with The Drawdown