Redemption Rights in Open-End Funds: Notice, Gates, and Liquidity

How a Redemption Right Actually Works

A redemption right in an open-end private fund is a contractual process for getting your money back out of the fund, on the fund’s terms and timing, not a button you press to have cash hit your account the next morning. When an investor redeems, the fund buys back their interest at net asset value, and that payout is conditioned on notice periods, valuation dates, gates, and a handful of other mechanics we’ll get into. It’s closer to selling an asset back to the fund than withdrawing from checking.

The Mismatch Between Open-End Structures and Illiquid Assets

An open-end fund is one that lets capital come in and go out over the life of the fund, as opposed to a closed-end fund where investors commit at the start, the fund invests, and everyone waits for the exit. Open-end means there’s a mechanism for new money to subscribe and existing money to redeem on an ongoing basis. It does not mean that mechanism is fast.

A public mutual fund can let you out at the next day’s close because it holds liquid securities it can sell in the market that afternoon. A checking account can pay you instantly because the bank is sitting on reserves and short-term instruments built for exactly that. A private fund holding an apartment complex, a portfolio of operating companies, or a book of private loans is in a different position entirely, because selling a building or an operating company takes months, sometimes a year or more, and until that sale closes the capital is tied up in the asset. So paying a redeeming investor out takes time, because the money to pay them has to come from somewhere, and in an illiquid fund the only real sources are new subscriptions, operating cash flow, a refinance, or a sale.

The securities problem shows up when a sponsor papers over that reality. If your marketing or your PPM implies investors can get out quickly while the fund holds assets that can’t be sold quickly, you’ve created a mismatch between what the investor was told and what the fund can actually do. That’s a Rule 10b-5 problem, and it’s one of the cleaner fact patterns the SEC likes for an anti-fraud enforcement action, because the overpromise is right there in writing next to a portfolio that obviously can’t support it.

The Three-Year Hard Lockup

For a new fund, I’d start with a three-year hard lockup, meaning no redemptions at all for the first three years after an investor subscribes. A fund needs stable capital to buy and operate its assets, and a fund that’s bleeding redemptions in year one never gets its footing because every dollar of new money is going right back out the door. The lockup gives the portfolio time to mature before anyone can pull capital.

After the lockup, I’d back the redemption right with an early withdrawal fee, usually around 5% of the redeemed amount, that applies when someone exits ahead of schedule or outside the normal cadence. The fee does two things. It discourages investors from treating the fund like a savings account they dip into whenever something shinier comes along, and it covers the real administrative friction of processing an off-cycle exit so the cost doesn’t land on the investors who stayed.

Notice, Valuation, and Payout

A redemption runs through three separate dates, and keeping them separate is what makes the whole thing work. There’s the date the investor gives notice, the date you value their units, and the date you actually send the money. If you let those collapse into one event, you’ve promised something close to on-demand cash, and you can’t deliver that from a portfolio of buildings or operating companies.

The Notice Period and Pipeline Alignment

The notice period is the runway you give yourself to come up with the cash. An investor says “I want out,” and you need time to sell an asset, refinance one, or build the redemption up out of operating cash flow before you can pay them.

A lot of documents just pick a number. Ninety days. Sometimes a year. And the number is arbitrary, pulled off a shelf because it sounds reasonable, with no relationship to how long it actually takes to turn one of your assets into money.

I’d rather see the notice period built around the asset lifecycle. If your typical hold involves a refinance at month 36 or a sale somewhere in a two-to-three-year window, the notice period and the payout timing should line up with those events instead of fighting them. That’s what I mean by pipeline alignment. You’re structuring the exit so it lands near a liquidity event you were going to have anyway, rather than forcing an off-schedule sale to raise cash for one departing investor.

For a fund holding liquid securities, a short notice period is fine, because you can sell into the market in a day. The longer your assets take to convert, the longer your notice period needs to run. Match the two and you’re not writing a check your portfolio can’t cash.

Separating Valuation from Payout

Take Bob. Bob put in $250,000, and in Q1 he decides he wants out and submits his redemption notice.

His notice doesn’t fix his price, and it doesn’t trigger a payment. It starts the clock. Bob’s units get valued on a future valuation date (say the end of Q2), when the fund strikes its NAV, and that’s the number that determines what Bob’s interest is actually worth. If the portfolio moved between Q1 and Q2, Bob rides that movement up or down, because he’s still an investor in the fund until he’s paid out.

Then the cash goes out on a third date, mid-Q3, which gives you the runway between the valuation and the payment to execute whatever sale or refinance funds the check. You’re not selling an asset in a panic the week Bob filed his notice. You locked his number at the end of Q2, and you’ve got into Q3 to raise the money cleanly.

Keep those three dates apart in the document. When notice, valuation, and payout all sit on top of each other, the only way to honor the request is to have cash sitting idle or to dump an asset fast, and neither one is good for the investors who stayed.

Why 10% is the Limit for Illiquid Portfolios

A gate is the cap on how much capital can leave the fund in any single redemption period. Bob’s timeline tells you what happens to one investor, but the gate is what happens when thirty Bobs all file notices in the same quarter.

How a Fund-Level Gate Works

There are two kinds of gates, and they do different jobs. An investor-level gate limits how much of his own position any single investor can redeem in one period, so Bob can pull out 25% of his units this quarter but not all of them at once. A fund-level gate limits the total that can leave across everybody, usually stated as a percentage of the fund’s net asset value.

The fund-level gate is the one that actually stops a run, because it looks at the whole redemption pool rather than any individual request.

Say the gate is 10% of NAV and the fund is worth $50 million, so the quarterly ceiling is $5 million. If total requests that quarter come in at $8 million, the manager pays out the $5 million and everyone who asked gets scaled back pro-rata. Bob asked for $250,000, requests were 160% of the cap, so Bob gets paid roughly $156,000 this period and the rest of his request moves into the queue for next time.

The pro-rata part matters because it keeps the manager out of the business of deciding who gets paid first. Nobody jumps the line, nobody gets a phone call. Everyone who filed in that window takes the same percentage haircut, and that evenhandedness is most of what protects the manager if a disappointed investor ever complains.

All of this lives in the governing documents. The gate percentage, the exact math for scaling, and the manager’s authority to apply it all get drafted into the operating agreement and LPA legal package, because a gate you didn’t write down is a gate you don’t have.

Why 25% Gates Force Fire Sales

The common institutional default is a 25% quarterly gate, and for an illiquid portfolio I think that number is too high.

Run it out. A 25% gate on a $50 million real estate fund means the manager might have to produce $12.5 million in cash in a single quarter. You don’t raise $12.5 million from a portfolio of buildings in ninety days by being patient. You raise it by selling whatever will close fastest, at whatever price a buyer who smells urgency is willing to pay. That’s a fire sale, and the buyer on the other side knows exactly why you’re calling.

The investors who stay are the ones who eat that loss. The departing investors get paid out at an NAV that hasn’t yet caught up to the discounted sale, and the remaining investors are left holding a fund that’s smaller, more leveraged, and lighter on its best assets.

For illiquid portfolios I’d set the fund-level gate at 10%. It still gives investors a real and periodic exit, it keeps the quarterly cash demand at a number the manager can meet through ordinary refinancings and scheduled dispositions, and it protects the leverage and the asset values for the people who didn’t ask to leave. If the fund held mostly liquid securities I’d feel differently, because you can sell liquid positions into a deep market without moving the price. Real estate and operating companies don’t work that way.

What Happens to the Unpaid Balance

When a gate kicks in, the redemption requests don’t just disappear. Say Bob asked for his full $250,000 back, the gate scaled everyone pro-rata, and Bob only got $100,000 this period. The other $150,000 doesn’t reset to zero and it doesn’t force Bob to file a fresh request next quarter. It rolls into a queue.

Structuring the Mechanical Queue

The unfulfilled portion of a gated request carries forward automatically into the next redemption window. Bob’s remaining $150,000 sits at the front of the line, and when the next window opens and there’s room under the gate, his balance gets paid before anyone new is served.

That ordering is the part a manager has to track carefully. If the Operating Agreement is quiet on priority, you end up with an obvious fairness problem the first time a newer investor tries to jump ahead of someone who’s been waiting two periods. So the document should say plainly that queued balances get paid first, in the order they were submitted, before the manager grants any new redemptions out of available liquidity.

In practice this means you’re running a ledger, not just a calendar. Every gated request leaves a tail, and the tails stack up in sequence until the fund has the cash to clear them.

The Non-Prejudice Rule for Waiting Capital

While Bob’s $150,000 is sitting in the queue, waiting out a 12-month payout window or a couple of gated quarters, that money should keep earning.

If the fund pays a 7% preferred return, Bob’s unpaid balance keeps accruing at 7% until it’s actually paid out. I’d write that into the document and I wouldn’t leave it ambiguous, because the alternative is that Bob’s capital goes dead the moment he asks to leave, even though the fund is still using it. That’s not fair to Bob, and it’s not neutral to the investors who stay either.

Think about it from the remaining investors’ side. The fund still has Bob’s $150,000 deployed in the assets, generating whatever the portfolio generates. If Bob stops earning but the capital keeps working, the difference quietly benefits everyone else at Bob’s expense. Keeping the accrual running until payout keeps the exiting investor and the remaining investors on even footing, which is the whole reason you built a queue instead of just letting people out at random.

Suspending Redemptions as a Fiduciary Obligation

A suspension stops redemptions entirely, and it’s the tool a manager reaches for when processing redemptions at all would hurt the fund.

A manager can’t just decide one morning to stop paying people. The power to suspend has to be written into the governing documents as an explicit, unilateral right, sitting in both the Subscription Agreement the investor signed and the Operating Agreement that runs the fund. Without that language, a suspension is a breach, full stop. With it, you’ve got a contractual power the investor agreed to when they came in.

Drafting Unilateral Discretion

The reason this gets treated with suspicion is that it sounds like a way out of paying. It isn’t, when it’s drafted and used correctly.

Think about what a redemption actually does during a bad stretch. If the manager has to sell assets into a falling market to cash out the people leaving, every investor who stays is worse off, because the fund just liquidated at the bottom to fund an exit. The manager’s duty runs to the fund as a whole, which means there are moments where the honest, duty-bound move is to say nobody redeems right now. That’s not withholding money arbitrarily. That’s protecting the capital stack from unwinding at the worst possible time.

So the suspension right exists to let the manager choose the fund over the departing investor when those two interests genuinely collide. The drafting job is to give the manager that discretion in clear language, tie it to the fund’s interest rather than the manager’s convenience, and spell out notice and reinstatement so it reads as a protective tool and not a trapdoor. A sloppy version invites exactly the argument you’re trying to avoid, that the manager used it to stall.

The Two-Week Packaged Asset Blackout

There’s one scenario where I’d build in an automatic suspension rather than leaving it to discretion, and that’s the window right before a large packaged sale closes.

Say the fund is selling a portfolio of assets as a single package, and the closing is set for a Friday. An investor who knows that sale is coming (and in a fund with any transparency, they’ll have a sense of it) has every incentive to file a redemption the week before so they lock in the current NAV and skip the execution risk. If enough of them do it, you’ve got people cashing out at a valuation the fund hasn’t actually realized yet, funded by capital that was supposed to go toward closing the deal.

I’d put a hard two-week blackout in the Operating Agreement running up to any sale of a large packaged asset. No redemptions process in that window, period. It stops the opportunistic rush, it keeps the exit price honest for everyone, and because it’s written as a mechanical rule tied to a defined event, nobody can argue the manager invented it on the spot to freeze someone out.

Audit Holdbacks and In-Kind Payouts

The NAV you pay a redeeming investor on and the NAV the auditors confirm at year-end aren’t always the same number, and two tools at the back end of the redemption process exist to cover that gap.

The 10% Audit Holdback

Most funds value their assets a few times a year, and those interim valuations are estimates. A mid-year NAV might peg a property or an operating company at a value the year-end audit later walks back, because the appraiser was optimistic, a tenant left, or a comp came in soft.

So when Bob redeems in Q3 off a mid-year NAV, there’s a real chance the fund paid him on a number that turns out to be high.

That’s a problem for the investors who stayed, because every dollar Bob was overpaid came out of their equity. The fund can’t claw it back once the check clears, so you build the protection in up front by holding back part of the payout.

I’d hold back 5% to 10% of Bob’s redemption amount and release it after the year-end audit confirms the valuation. If the audited NAV is lower than the interim number, the holdback absorbs the difference and nobody who stayed subsidizes someone who left. If the audit confirms the number, Bob gets the holdback and he’s whole. The right to do this has to be written into the governing documents, with the percentage and the release trigger spelled out, because a holdback you didn’t reserve is just you shorting an investor.

The In-Kind Distribution Safety Valve

An in-kind distribution means you pay a redeeming investor with a fractional interest in the fund’s actual assets instead of cash. Bob wanted $250,000 back, and instead of a wire he gets a slice of the portfolio equal to that value.

This is messy, and I’d treat it as a last resort rather than a normal payout method. You’re handing an investor who wanted out a piece of an illiquid asset he now has to hold or figure out how to sell, which is rarely what he signed up for, and it creates its own set of valuation and transfer headaches.

But the reason you reserve the right anyway is default. If the gates, the queue, and the suspension right have all run and the cash genuinely isn’t there, an in-kind option means you can satisfy the redemption with assets instead of breaching the agreement and handing the investor a claim against the fund. It almost never gets used. You want it in the document so that the one time cash fully dries up, you have a legal way to close out the obligation instead of a lawsuit.