Draft Side Letter For Strategic Limited Partner

---
name: draft-lp-side-letter-strategic
task_id: corporate-ma/draft-side-letter-for-strategic-limited-partner
description: Guides drafting of a private equity fund side letter for a strategic limited partner, with each negotiated provision cross-checked against the fund’s governing agreement for conflicts, authority limits, and interactions with other investor rights.
activates_for: [planner, solver, checker]
---

# Skill: LP Side Letter Drafting — Strategic Limited Partner

## 1. Subject-matter triage

- Treat the LPA as the controlling baseline, then reconcile the subscription package, investor policy, negotiation emails, and any fund precedent against it.
- Separate investor-specific accommodations from terms that would require broader consent or a formal amendment; do not assume the GP can grant every requested right unilaterally.
- Determine at the outset whether the investor is a private nonprofit, a tax-exempt institution, or another non-governmental holder, because that classification drives which requested protections are legally meaningful.
- If multiple negotiated items appear in the source set, enumerate them first and assess each one separately before drafting.

## 2. Failure modes the skill is correcting

- Excuse or opt-out provisions are drafted without checking whether the mechanism conflicts with the fund’s existing excuse, exclusion, or withdrawal procedures, creating parallel and potentially irreconcilable remedies.
- MFN clauses are drafted using negotiation-specific thresholds without reconciling those thresholds against the governing agreement’s definition and election mechanics.
- Provisions designed for governmental investors are included for a private nonprofit investor, where those protections are legally inapplicable or commercially mismatched.
- Advance notice provisions tied to internal events are drafted without assessing whether early disclosure would create confidentiality, information-control, or fiduciary-duty issues.
- Affiliate transfer rights are inserted without checking transfer restrictions and consent requirements in the governing agreement.
- Side letter language is drafted as if it can override the LPA, rather than as a limited investor-specific modification.
- The draft is produced without a parallel issues memo that explains conflicts, risks, and requested resolutions.

## 3. Legal frameworks / domain conventions that apply

- Side letter hierarchy: a side letter modifies the LP’s rights under the fund’s governing agreement for that investor alone; every side letter provision must be assessed against the governing agreement for conflicts, authority limits, and interactions with other investor rights.
- Governing-agreement supremacy: if the LPA, subscription documents, or policy documents restrict a term, the side letter should either conform to those limits or flag the need for a broader consent or amendment.
- MFN practice: the clause must define scope, election mechanics, timing, and carve-outs with precision, and it must be reconciled with any existing MFN regime in the LPA.
- Tax-exempt investor relief: relief from investments that create adverse tax consequences must fit within the fund’s existing excuse and exclusion architecture and should not create a separate inconsistent pathway.
- GP authority limits: terms that alter economics, operational discretion, or investor rights beyond delegated authority may require advisory committee approval or other consent.
- Government-style immunity or public-records concepts generally do not transfer to a private nonprofit investor; if the investor is not a governmental entity, those concepts usually lack a legal hook.
- Advance notice of internal events can implicate confidentiality, information-control, and fiduciary-duty constraints; any obligation should preserve required non-disclosure and fair-treatment principles.
- ESG or mission-based excuse: any carve-out tied to mission, ethics, or ESG screens must be defined with objective measurement language and administrable criteria.
- Affiliate transfer rights remain subject to transfer-restriction provisions, consent rights, and any conditions tied to permitted transferees.

## 4. Analytical scaffolds

- Map each negotiated term to the specific LPA, subscription, policy, or precedent provision that addresses the same subject.
- For each term, ask four questions in sequence: does the source agreement already address this point; does the requested language conflict with that mechanism; is the GP authorized to grant it alone; and what downstream rights or duties does it affect.
- For an excuse or exclusion request, test it against the existing withdrawal, excuse, and mandatory-transfer architecture and draft only a harmonized mechanism.
- For MFN language, align the threshold or trigger with the LPA’s defined terms, specify the election window, and carve out intended exclusions.
- For transfer rights, verify whether affiliate transfers require notice, consent, or a condition precedent and reflect that in the draft.
- For notice rights, assess whether the requested timing would require disclosure of confidential or nonpublic information and whether the draft needs a non-disclosure safeguard or a delayed-notice trigger.
- For any provision that resembles a governmental-investor protection, determine whether the investor’s status supports it; if not, flag it for removal or replacement.
- Where a provision may exceed unilateral authority, identify the consent body or amendment path that would be needed.

## 5. Vertical / structural / temporal relationships

- The LPA controls the deal architecture; the side letter should operate as an investor-specific overlay, not a wholesale rewrite.
- Provisions may interact across documents: an MFN term in the side letter can be affected by the LPA’s general MFN clause, a transfer right can be constrained by the LPA’s transfer section, and a notice obligation can be limited by confidentiality provisions in the subscription package or policy.
- If the same concept appears in more than one document, reconcile the documents into a single operative approach rather than drafting duplicative or inconsistent language.
- Temporal mechanics matter: notice periods, election windows, and cure periods should be internally consistent and should not begin before the triggering event is adequately defined.

## 6. Output structure conventions

- Produce two deliverables: a draft side letter and a separate issues memorandum.
- The draft side letter should use standard contract form, with clear operative provisions, defined terms only where needed, and no commentary embedded in the text.
- The issues memo should be advisory and issue-based, not a recital of the documents.
- For each issue, identify the controlling source section or provision, explain the conflict or risk, and state the recommended resolution.
- Use an explicit severity label for each issue, applied consistently across the memo.
- Close each issue with a concrete recommendation that names the responsible role and a timing anchor tied to signing, execution, or closing.
- Where a proposition turns on a legal or structural rule, cite the controlling authority or document provision by name and section rather than asserting the conclusion bare.
- Before finishing, ensure the side-letter file is the primary work product and is complete, then complete the issues memo as the secondary deliverable.