Investor Request Tracker for Private Equity Teams

An investor request tracker gives each limited partner request a fund or vehicle, a responsible team, a permission owner, an approved document version, and a visible fulfillment status. Use one row per request and vehicle. A contact's name alone is not enough to tell the person handling the request which materials may be shared.

The editable register below is for private equity teams coordinating requests from existing limited partners, or LPs: investors in a fund. It is not a fundraising pipeline, a due-diligence answer bank, or a substitute for your approved investor portal. Start with blank administrative records, then have the appropriate owners confirm the missing details.

Track the request, not just the relationship

A relationship record answers who the contact is and what conversations have happened. A request register answers what is outstanding, for which vehicle, who must act, and what counts as finished. Keep those tasks separate, even if your existing system supports both.

Carta describes its LP CRM as combining relationship history and fundraising pipelines with fund data. That scope is broader than this register. You do not need to copy financial data into a second sheet to coordinate a request for an already approved document.

For example, an LP contact might ask for a previously issued investor letter for two vehicles. Create two linked request rows, not one vague task called "send letter." Each row can then point to its own responsible owner and approved version. If one vehicle is ready and the other is waiting on permission confirmation, the first delivery should not make the second request disappear.

Define the administrative handoff before filling the sheet

Choose a request owner who maintains the record and follows up internally. Separately name the permission owner who confirms the authorized recipient and vehicle-specific access. The person who approves a document for release may be different again. Record those roles explicitly rather than assuming that being copied on an email grants authority.

InvestorFlow's investor services page describes request routing and document permissions at fund, vehicle, contact, and document-category levels. For this template, keep the distinction clear: a spreadsheet can record a confirmation, but the approved document system must enforce access.

Before using a real register, agree where it will live, who may see it, who updates it, and where the actual documents remain. Keep document contents, account credentials, banking instructions, identity documents, and private financial answers out of a general-purpose task log. Use references to approved systems rather than creating another document repository.

Use a separate field for every unresolved question

• Request ID and received date: a stable reference and the date the request reached the team.
• Requesting LP/contact reference: enough context for the authorized owner to identify the request, without copying unnecessary personal information.
• Fund/vehicle: the exact vehicle in scope. If uncertain, record "needs confirmation" and route it back to the owner.
• Requested document and period: what was asked for, not an assistant's interpretation of what should be disclosed.
• Responsible team and next check: who owes the next action and when the coordinator should check again. A next-check date is not a promised delivery deadline.
• Permission owner and confirmation reference: who confirmed the recipient's access and where the decision is recorded.
• Approved version/release reference: the owner-approved document identifier, version, or controlled link. "Latest" is not a useful version label.
• Status and delivery evidence: what remains open, or where the approved delivery is recorded.

In the working system, keep the authorized recipient explicit alongside the permission confirmation. If a request changes scope, return it to the relevant owner. Do not reuse approval for another vehicle, another reporting period, a new recipient, or a replacement file without confirmation.

Editable investor request register

Use invented references to try the tool. Each added row belongs to one vehicle. Entries remain only in this page's memory until reset or reload; CSV download saves a file on your device. This tool does not send requests, check permissions, open documents, or connect to an investor portal. Do not enter real LP details or confidential document links into this demonstration. Move the blank structure into your team's approved environment for operational use.

No requests added. CSV download includes the blank column structure.

Suggested statuses are New, Awaiting clarification, With responsible team, Awaiting permission, Awaiting approved version, Ready for approved delivery, Delivered, and Closed. Choose the status that describes the remaining action, not the one you hope will happen. Delivered means the approved route was used; Closed means the request owner has checked that nothing remains outstanding. The tool does not verify either event.

Walk through a multi-vehicle request

Illustrative example, not a client story: Contact A requests a previously issued letter for Vehicle A and Vehicle B. The coordinator creates rows REQ-01-A and REQ-01-B, records the requested period, and routes both to the investor relations owner. Neither row contains the letter itself.

The permission owner confirms Contact A's access for Vehicle A and points to the recorded decision. The release owner identifies the approved letter version. The coordinator records both references and the next action. For Vehicle B, recipient access remains unconfirmed, so that row stays Awaiting permission. Approval for Vehicle A does not resolve it.

After the authorized person delivers Vehicle A's approved material through the agreed channel, the coordinator records the delivery evidence reference. If the message bounces or the recipient cannot open the file, the task remains open with an access issue assigned to the system owner. The assistant does not widen permissions to finish the row.

Handle exceptions without answering beyond your authority

When a request asks for a new explanation of performance, a tax interpretation, a revised disclosure, or an unfamiliar document, record the request and route it to the designated principal or specialist. Do not draft a substantive answer from old materials or infer a disclosure obligation from a previous delivery.

Carta's investor relations article discusses communication between fund managers and LPs and the use of investor portals for documents. This register covers only the administrative handoff around approved materials. Investment analysis, financial reporting judgments, valuation, legal and tax advice, regulatory determinations, securities solicitation, and money movement stay outside it.

For a duplicate request, link the two IDs and have the owner confirm whether one delivery resolves both. For a withdrawn request, record that outcome instead of marking it delivered. For a corrected document, record the replacement version and obtain the required release confirmation. Preserve the history in the approved system rather than silently rewriting what was sent.

Make the register part of the assistant's full scope

At an agreed internal check-in, review rows waiting on clarification, permissions, approved versions, or delivery evidence. Ask a concrete question: who owes the next action? Use the register to prepare that conversation, not to decide which investor deserves a response or what the fund should disclose.

Early Bird provides a dedicated, full-time executive assistant with ongoing Early Bird support. Onboarding maps the full operating scope, people, systems, and decision boundaries before stabilizing one priority workflow at a time. Request coordination can sit alongside calendar management, meeting preparation, and approved follow-through rather than becoming an isolated task assignment.

Explore executive assistant support for private equity teams for the broader scope. For a related way to make authority explicit in a fund-partner role, see the fund-partner assistant role brief and scorecard; adapt the administrative boundaries to your own PE team rather than treating VC and PE roles as interchangeable.