GP consent in LP transfers: how it works and where it stalls
· 7 min read · Navys Team
GP consent is the fund manager's approval of a proposed transfer of a limited partner's interest, given under the fund's limited partnership agreement and required before the interest can change hands. LP transfers need it because interests in a private fund are not freely transferable. Almost every LPA restricts assignment and gives the manager discretion over who joins the register, since a new investor changes the tax, regulatory, and reporting position for the whole fund. Consent is the gate for everything that follows. Until it is granted, the diligence, drafting, and closing work is all provisional.
This piece explains why the restriction exists, what a manager reviews before consenting, the conditions commonly attached, and why the decision so often sits in a queue.
Why do LP interests need consent to transfer?
A limited partnership interest is not a listed security. It carries ongoing obligations (unfunded commitments, capital calls, adherence to the LPA), and it sits inside a structure assembled for a specific set of investors. Let one interest move without control and the manager loses the ability to protect the rest.
The restriction is contractual, not incidental. Most LPAs prohibit transfer except with the manager's prior written consent, and many add that consent may be withheld in the manager's sole discretion. Admitting a new limited partner can trigger consequences the manager is responsible for managing: a change in the fund's tax status, a breach of a regulatory threshold, or an investor whose presence conflicts with a side letter already in force. Consent is how the manager keeps those risks inside known limits.
What does the manager check before consenting?
Before approving a transfer, the manager runs a review that is part legal, part commercial, and part regulatory. The checks vary by fund, but the recurring ones are consistent.
| Check | What the manager is looking for |
|---|---|
| Eligibility | Whether the transferee qualifies to hold the interest under the LPA and applicable investor rules |
| Tax impact | Whether admitting the buyer changes the fund's tax status or creates withholding exposure for others |
| Regulatory fit | Whether the buyer's jurisdiction or status raises marketing, licensing, or sanctions concerns |
| Concentration | Whether the transfer creates an outsized position or an unwanted counterparty |
| Existing terms | Whether the buyer's side letter demands, if any, conflict with the fund's other arrangements |
| ERISA and plan-asset limits | For funds that track them, whether the transfer pushes benefit-plan holdings over a threshold |
Institutional buyers clear most of this quickly. The friction comes from the exceptions: a transferee in a jurisdiction the fund does not market into, a structure that alters the partnership's tax analysis, or a buyer whose standard side letter asks for something the manager cannot give a newcomer. Any one of those turns a routine approval into a negotiation.
What conditions do managers attach to consent?
Consent is rarely a clean yes or no. More often it is a yes with conditions, and those conditions shape the rest of the deal. The manager approves in principle, then specifies what has to be true before the transfer can close.
- Completed KYC and AML. The transferee must satisfy the fund's onboarding checks in full before consent takes effect. This is the most common condition and the one most likely to delay closing.
- Adherence to the LPA. The buyer signs a deed of adherence or a fresh subscription agreement, taking on the same obligations as any other limited partner.
- Tax forms and representations. Where the fund has US connections or other reporting exposure, the buyer provides withholding forms and confirms its status.
- Transfer fee and costs. Many LPAs let the manager recover the legal and administrative cost of processing the transfer, and consent is conditioned on payment.
- No side letter carry-over. The manager often confirms that the buyer does not inherit the seller's negotiated terms unless separately agreed.
These conditions are not obstacles for their own sake. They are how the manager makes sure the incoming investor is bound by the same framework as everyone already in the fund, and that the transfer does not quietly import terms the manager never agreed to.
Can a manager refuse consent outright?
Yes, and where the LPA grants sole discretion the manager usually does not have to give reasons. In practice outright refusals are uncommon, because a manager that blocks transfers without cause damages its standing with LPs who value liquidity. The more frequent outcome is a slow yes or a conditional yes rather than a flat no.
Legitimate grounds for withholding consent include adverse tax consequences for the fund or its other investors, a regulatory problem in the buyer's jurisdiction, and a conflict with the manager's other relationships. Some LPAs also give existing investors a right of first refusal. That is not a refusal by the manager, but it has the same effect on timing: the interest must be offered around before the proposed buyer can proceed. Where the fund's transfer provisions set out a prescribed notice, missing it can reset the clock even on a transfer everyone supports.
Why does the consent decision get stuck?
The decision itself takes a partner an hour. The elapsed time between request and answer is measured in weeks, and the reasons are almost always operational rather than substantive.
Consent sits with senior people who are also running fund launches, closings, and LP relations. A transfer request lands in that queue and waits its turn. It competes with work that has a harder deadline, so a decision that is straightforward on the merits can sit untouched for a fortnight simply because nothing forces it to the top of the pile.
The queue is made worse by fragmentation. The request often arrives by email to one person, the LPA review sits with counsel, the tax question goes to an adviser, and the KYC checklist lives with the administrator. Nobody holds the whole picture, so the manager cannot approve until several separate answers come back, and each answer waits on the last. As secondary volumes rise, more requests hit the same setup and the queue lengthens. The effect on the overall LP transfer timeline is larger than the legal work would ever suggest.
How can parties reduce consent delay?
The highest-value moves are unglamorous, and they happen before the request is even formal.
Agree the consent criteria early. If the seller and buyer know what the manager will check, they can assemble eligibility evidence, tax forms, and KYC before asking, so the request arrives complete rather than triggering a round of follow-ups. Confirm the LPA's notice requirements at the same time, because a defective notice is a self-inflicted delay.
On the manager's side, a standing consent checklist and a named owner for transfer requests keep decisions from disappearing into the general queue. Where a right of first refusal applies, running the offer period alongside the buyer's diligence rather than after it removes a serial dependency. None of this changes the substance of the decision. It changes how fast the pieces the decision depends on arrive.
Where to start
If you are working on transfer volume, the consent gate is where most of your elapsed time hides, so it is worth measuring what the surrounding process actually costs. Navys set out those numbers in The True Cost of LP Transfers, which measured a traditional transfer at roughly 23 hours of professional time under its stated assumptions. Start there, then map your own consent workflow against it.