Managing investor communications in a continuation fund process
· 7 min read · Navys Team
Investor communications in a continuation fund transaction are the structured flow of notices, elections, and answers between the GP and every existing LP, from the first announcement to the election deadline. A GP manages them well by keeping one authoritative version of each notice, logging every investor question and its answer, and tracking where each LP sits against the deadline. The transaction asks hundreds of investors to make a binding decision (roll into the continuation vehicle, sell, or sometimes a mix) within a fixed window. The volume of individual questions is what breaks an ad hoc email approach.
This piece looks at what the communications actually involve, where email rounds fail, and what a tracked workflow changes.
What does a GP have to communicate in a continuation fund?
The communications sit on top of a transaction that is already complex: a lead secondary buyer, a price, a rollover option, and a deadline. The GP is asking existing LPs to decide what to do with their position, and every piece of information they need to decide comes from the GP or its advisers.
The core items are the transaction announcement, the detailed election notice with its terms and mechanics, the data room invitation, reminders as the deadline approaches, and the final confirmation of each investor's recorded election. Around those sit the ad hoc exchanges: an LP asking how the price was struck, a fund-of-funds needing an extension for its own investment committee, a compliance team wanting the notice in a particular format.
None of these is hard to write. The difficulty is that the same notice goes to a large group, each member of which may respond on a different day with a different question, and the GP has to keep track of who has seen what.
Why do email rounds break down at scale?
A transfer with five parties is manageable by email. A continuation vehicle with two or three hundred investors is not, and the reasons are structural rather than a matter of discipline.
| Problem with email rounds | What it costs the GP |
|---|---|
| No single version of the notice | LPs receive different drafts; corrections spawn fresh threads |
| Questions scattered across inboxes | The same question answered three ways by three people |
| No per-investor status | Nobody knows who has elected and who has gone quiet |
| Reminders sent blind | Investors who already responded get chased; silent ones are missed |
| Answers not reusable | A good answer to one LP is never seen by the next twenty asking the same thing |
The last point is the quiet one. In a large process, a handful of questions account for most of the volume: how distributions are apportioned, what happens if an LP does nothing, how the valuation was reached. Answering each privately means the GP writes the same paragraph dozens of times, with small variations that later look like inconsistency.
How should election notices be versioned and sent?
An election notice sets out the choices, the terms attached to each, and the deadline by which the LP must respond. It is the most important communication in the process, and it tends to change at least once after it first goes out, because a date moves or a term needs clarifying.
- Freeze a version. Give the notice a version number and date before it leaves the GP. Every later reference points to that version.
- Record who received which version. When a revision goes out, log which investors have the new one and which are still on the old.
- Make the deadline unambiguous. State the election deadline in one place, with the time zone, and repeat it in reminders rather than recalculating it.
- Separate the notice from the mechanics. Keep the binding terms in the notice and the how-to (where to click, who to email) in a short cover note, so a correction to one does not force a reissue of the other.
- Confirm receipt. A recorded acknowledgement from each LP removes the later argument about whether a notice was ever delivered.
The structure of the underlying decision is covered in the continuation fund investor election workflow. The communications job is to make sure every investor is acting on the current version of it.
How do you handle hundreds of individual investor questions?
The instinct is to answer each question as it arrives. At scale that produces inconsistency and burns adviser time. The better approach treats questions as a tracked queue with a shared answer bank.
Log every question when it comes in, against the investor who asked it. Draft the answer once, have counsel review it where it touches terms, then reuse it. When the same question recurs, the approved answer is already written, which keeps the GP consistent and fast. Questions that reveal a genuine gap in the notice feed back into the next version rather than being patched investor by investor.
Some questions are genuinely bespoke: a particular LP's side letter, a tax position specific to one jurisdiction. Those still need individual handling, but separating them from the repeat questions means the bespoke work gets proper attention instead of drowning in routine traffic. The parallels with keeping one authoritative document version in an LP transfer are close. The failure mode in both is many people working from different copies of the truth.
What should per-investor status tracking show?
The GP's central question through the process is simple and hard to answer by email: where does each investor stand. A status view answers it for every LP at once.
A useful tracker records, for each investor, which version of the notice they hold, whether they have acknowledged it, what questions they have open, what election they have made (or that they have not yet responded), and whether any documents are outstanding. From that, the GP can see the shape of the whole book: how many have elected to roll, how many to sell, how many are silent with the deadline approaching.
That visibility changes how reminders work. Instead of a blanket chase to everyone, the GP contacts only the investors who have not responded, with a message that reflects where they actually are. It also gives the lead buyer and the fund administrator a shared picture, so the people updating the register are working from the same statuses the GP sees.
How do communications connect to the rest of the transaction?
Investor communications are not a standalone workstream. The answers an LP needs often live in the data room, so the communication plan and the data room checklist have to line up: if a question points to a document, that document should be in the room and current.
The election results then drive the closing mechanics. Who rolled, who sold, and in what amounts determines what the administrator records and what the documents say. Communications tracked cleanly through the process hand over a clean set of results. Communications run across scattered inboxes hand over a reconciliation problem on a deadline. One structured workspace for notices, questions, and statuses, which is the approach Navys takes to continuation vehicle processes, keeps the communication record and the election record as a single source rather than two that have to be matched later.
Where to start
Navys gives GPs a structured workspace for continuation vehicle investor communications: versioned notices, tracked questions with reusable answers, and per-investor election status in one place. You can see how the election and communication workflow runs in Continuation Vehicles on Navys. If you are planning a process with a large investor base, talk to the team.