Removing a Manager From an SPV

Removing a manager from an SPV is an operating-agreement process—not a Slack vote and not a platform toggle. Paths usually include resignation, removal for cause (as defined), removal without cause if the OA allows it, death/dissolution of a manager entity, and appointment of a successor with authority to bind the vehicle, banks, and tax filings. Get counsel involved before you announce anything to LPs. This page is general information, not legal advice.

Allocations administers vehicles under productized SPV and fund workflows; manager identity and removal rights live in the OA and related instruments. Banking handoffs: banking. Fees remain commercial SKUs on fees—not a removal statute.

Start with the OA—not with vibes

Before any removal conversation, pull the live operating agreement and answer:

1. Who is the named manager (person vs entity)?

2. Can the manager resign, and what notice is required?

3. What is “cause,” if defined?

4. What member vote or consent removes the manager?

5. How is a successor appointed, and when does authority transfer?

6. What happens to economics (carry, management fee, promote) on removal?

7. Are there related documents (subscription POA, banking resolutions, side letters) that also name the manager?

If two PDFs disagree, stop and reconcile versions. Entity basics: Delaware LLC Act basics for SPVs (general info only).

Common paths (illustrative, not a menu you can DIY)

None of these rows replaces counsel. Some OAs make removal extremely hard by design—deal SPVs often concentrate control in the syndicate lead so the vehicle can act. That is a feature for closes and a constraint later.

Why LPs ask about removal before they wire

LPs do not plan to fire the manager on day one. They ask because:

• Key-person risk on a thin syndicate.

• Fear of orphaned SPVs after a lead goes silent.

• Side letters that promise consultation rights if the manager changes.

• Banking and K-1 continuity questions.

Address removal literacy in diligence with calm process language—not bravado (“you can never remove me”) and not false comfort (“the platform can just swap managers”). Platforms execute admin; they do not unilaterally rewrite OA control.

Successor appointment is the real work

Removal without a successor is how vehicles freeze: no one to sign bank forms, tax elections, or stock-transfer paperwork. A workable transition usually needs:

• Written appointment effective on a dated moment.

• Updated banking signers and resolutions (/banking).

• Notice to LPs as the OA requires (and as courtesy even when not required).

• Cap-table / ledger admin continuity (SPV investor onboarding checklist hygiene still applies to transfers).

• Tax preparer and registered-agent contact updates.

• Review of indemnity/exculpation for pre- vs post-transition conduct (SPV indemnification and exculpation—not legal advice).

Economics on the way out

OAs vary widely on whether a removed manager keeps carry, loses carry, or keeps carry only for deals closed before removal. Deal SPVs with a single asset often treat promote as tied to the investment outcome under the original waterfall—but do not assume. Side letters may add MFN complexity. Expense and fee trails must stay auditable so a dispute does not invent invoices: SPV expense policy what LPs expect.

Published Allocations cash admin (fetched 8 Sep 2026): Standard SPV $9,950; Premium SPV $19,500; Fund $19,500/year; 0% platform carry. Additional fees may apply. Confirm on /fees. Manager removal does not by itself rewrite platform SKUs—someone still has to pay for ongoing admin if the vehicle remains open.

Communication sequence that reduces panic

A calm sequence when counsel agrees a transition is happening:

1. Counsel + current manager + proposed successor align on OA mechanics and effective date.

2. Banking and admin providers get a documented signer change plan.

3. LPs receive notice consistent with the OA (facts, effective date, who to contact—not a novel).

4. Archive the old manager’s access responsibly; do not leave shared inboxes as the only “books.”

5. Confirm year-end tax contact list still works.

Emerging managers running many vehicles (/emerging-managers) should keep a playbook so each SPV does not invent transition lore from scratch.

What not to do

• Do not “remove” a manager by emailing the bank alone.

• Do not tell LPs a removal is done before successor authority and banking are real.

• Do not confuse platform admin changes with OA manager changes.

• Do not ignore side letters that require consent or notice.

• Do not treat this blog as a removal kit—not legal advice.

Amendment interaction

Sometimes the OA’s removal section is unusable for the fact pattern, and parties consider an amendment or restatement to appoint a new manager by consent. That is a different instrument with its own vote thresholds—see amendment vs restatement literacy (also not legal advice). Prefer the path the OA already provides when it works; inventing a parallel process creates two stories for LPs and banks.

Soft vs hard transitions

Not every manager change is adversarial. Soft transitions include a lead handing a vehicle to a partner inside the same management company, or a planned maternity/medical coverage period with a temporary authorized signer if the OA allows. Hard transitions include alleged cause, LP revolts, or silence after a lead disappears. Soft transitions still need paperwork; hard transitions need counsel early and fewer public messages until the OA path is clear.

If the manager is an entity (e.g., “ABC Management LLC”) and control of that entity changes, ask counsel whether the SPV OA cares about upstream ownership. Some LPs think they “removed the manager” by reshuffling the management company—when the SPV still names the same entity. Precision matters for banks and for LP notices.

Record retention after cutover

After a successor is in place, keep:

• The consent or resignation instrument.

• Banking change confirmations.

• LP notices sent and bounce list.

• A snapshot of the ownership ledger on the effective date.

• Outstanding invoice list (legal, tax, admin) so the new manager does not inherit mystery payables.

Orphaned Dropbox folders and personal Gmail threads are how K-1 season becomes archaeology. Productized admin helps (/spv), but only if credentials and vendor contacts actually transfer.

Practical checklist

1. Read the OA removal, resignation, and successor sections with counsel.

2. Inventory banking resolutions, tax contacts, and side letters that name the manager.

3. Line up successor authority before public LP messaging.

4. Document effective date and access cutover.

5. Keep admin fee and expense trails clean under live /fees quotes.

6. Archive consents and notices with the subscription pack.

FAQ

Can LPs remove an SPV manager by majority email?

Only if the operating agreement’s consent mechanics say so—and usually with formal written consent, not informal email chains. Ask counsel; this is not legal advice.

What happens to the SPV if the manager resigns with no successor?

Authority can freeze: banking, filings, and investment paperwork may stall until a successor is appointed under the OA. Plan the successor first.

Does the admin platform remove and replace managers?

No. Platforms provide productized administration (/spv). Manager identity is an OA legal designation.

Do Allocations fees change when a manager is replaced?

Cash admin SKUs are published on /fees (Standard $9,950; Premium $19,500; Fund $19,500/yr; 0% platform carry, fetched 8 Sep 2026). Removal does not invent a new fee schedule—confirm who pays ongoing admin after transition.

Should indemnity be reviewed in a removal?

Yes—with counsel. Pre-transition and post-transition conduct may be treated differently under the OA. See the indemnification/exculpation overview for vocabulary only—not advice.