If you run a fund with an outsourced administrator, a large share of what reaches your LPs passes through the admin's workflow. Capital calls, distributions, quarterly statements, audited financials, K-1s, ADV updates. All signed in your name, sent on your behalf.
The administrator handles execution; the manager holds the obligation. It's one of the most stable divisions of labor in fund operations, and most of the time it works exactly as designed.
But the obligation comes with a quieter duty: confirming that what goes out in your name actually went out, to the right investors, on time. That's the part managers don't always have full insight into.
What managers can see, and what they can't
Every one of those documents carries a delivery obligation. ADV updates have to reach clients. Audited financials have to be distributed. K-1s have to go out before investors need to file. Quarterly reports have to reach LPs on schedule. Capital calls have to reach the right LPs on the right date. Confirming each of those actually happened is part of the manager's oversight, even when the execution is delegated.
The admin knows what went out, to whom, and when. That visibility lives in the admin's system, because that's where the work happens. The manager typically sees a smaller slice of it, through two channels, and neither gives a full view.
The first is the LP portal, usually shared between manager and admin. It shows whether a document is posted, and sometimes who opened it. But view-tracking tells you which LPs engaged with a document, not which LPs were notified of it. An LP who never logs in generates no record at all.
The second is asking the admin directly. You email or call, and they confirm it went out or pull the details from their records, which can take days. That answers a one-off question, but it's reactive, and the records still sit with them, not you. Either way, the manager has no independent, ongoing view of which investors received which documents, whether the emails landed, or what evidence exists if someone asks later.
Neither answers the question oversight actually requires: did this specific document reach this specific investor, on time, and did it land?
This isn't a flaw in anyone's setup. It's a function of how the work is divided.
Where it shows up
In normal operations, none of this matters. Documents reach LPs, LPs are satisfied, the relationship runs smoothly.
The moments where it does matter share a common shape. An LP asks the manager about a specific document. An auditor wants evidence of delivery on the audited financials. An examiner asks how delivery to a specific investor on a specific date was documented. The question lands on the manager, and the answer lives in the admin's system.
Some of those moments touch regulation directly. The Custody Rule governs how audited financials reach investors in pooled vehicles relying on the audit exception. Rule 204-3 governs delivery of the Form ADV brochure. Rule 204-2 governs retention of the communications advisers send. AIFMD imposes parallel obligations for funds marketed in the EU. The admin operates inside these obligations, but the obligations themselves stay with the manager.
None of this is new to anyone running fund operations. What's easy to miss is how cleanly the gap can be closed.
A shared view
The fix isn't to pull communications back in-house, or to look over the admin's shoulder. It's to give the manager and the admin the same view of what's been sent: one shared record in the platform they already share. Same delivery record, two views. The admin sends, as they always have. The manager sees, in their own system, what the admin sent: document by document, investor by investor, with confirmation that each message reached its recipient.
Four pieces make this useful in practice:
- A record of what was sent. Every document, to which investor, on what date. Not a batch-level “the notices went out Tuesday,” but document by document, investor by investor.
- Proof it landed. Each record is reconciled against the actual email delivery status, so the manager knows the message reached the recipient, not just that it left the system.
- A record you can search. Filterable by fund, document type, investor, and date, so answering a side-letter question or producing records for an exam is a query, not a reconstruction.
- A real-time, manager-side timeline. Everything the admin sent on the manager's behalf, visible as it happens, not summarized weeks later at quarter-end.
A stronger operating layer
The strongest manager-admin relationships are built on shared oversight, both sides working from the same record. That helps everyone. Managers can answer LP questions faster. Admins spend less time fielding one-off status checks. And neither side is left reconciling execution in one system against oversight in another. When a question turns into a compliance question, whether an auditor's request, an examiner's inquiry, or an LP's side-letter check, that shared record is what lets the manager answer in their own system, at the moment it's needed.
The volume of LP communications keeps going one direction. LPs are getting more sophisticated about what they expect, and how fast someone can answer for it. AIFMD II took effect across the EU in April 2026, with further obligations phasing in through 2027. And even with the SEC's Private Fund Adviser Rules vacated, examiners continue to focus on how advisers document what they send.
The manager-admin division of labor isn't going to change because of any of that. What might change is the assumption that the manager's view has to be smaller than the admin's. Shared visibility doesn't replace the admin relationship; it makes both sides' work more legible to the other. Eleven builds this layer into the platform managers and admins already share. Same execution, same trust, cleaner record.