Draft Markup Of Side Letter

---
name: draft-markup-of-side-letter
task_id: funds-asset-management/draft-markup-of-side-letter
description: Redline a proposed side letter on behalf of an LP client by reference to the LP's investment policy, the governing fund documents, and prior fund precedent, producing a marked-up draft with a cover memo that prioritizes changes and identifies the LP's policy basis for each position.
activates_for: [planner, solver, checker]
---

# Skill: LP-Protective Side Letter Redline with Negotiation Cover Memo

## 1. Subject-matter triage (only if applicable)

- Identify the governing side letter, the fund documents, the LP investment policy, and any prior side letters or precedent the LP expects to reuse.
- Determine whether the LP is a private, public, governmental, or regulated institutional investor, because disclosure, confidentiality, and records-law issues may change the markup.
- Confirm whether the proposed side letter touches fee offsets, reporting, ESG or sustainability obligations, confidentiality, transfer/assignment rights, MFN-style treatment, or any bespoke consent right.
- If multiple precedent documents or multiple investor policies are in scope, enumerate them before comparing terms so each source is tested separately against the proposal.

## 2. Failure modes the skill is correcting

- Drafter redlines the side letter without checking the governing fund documents and prior precedent, missing conflicts, drafting gaps, or available support for the LP position.
- Drafter accepts aspirational or “best efforts” language where the LP negotiated for a binding commitment.
- Drafter fails to identify provisions that are less protective than the LP’s policy or prior fund treatment.
- Drafter leaves confidentiality language too broad for an LP with public-records or statutory disclosure obligations.
- Cover memo lists issues without sorting them by negotiation importance or tying each position to policy, precedent, or law.
- Markup relies only on visual edits that can be lost in conversion instead of using text-based redline conventions.

## 3. Legal frameworks / domain conventions that apply

**Fee offset and expense allocation.** Read the fee-offset language against the fund agreement and the LP policy together. Check what categories are credited, whether affiliate or related-party charges are included, and whether the offset applies automatically or only on request. Where the LP policy is more protective than the draft, align the side letter to the policy and widen the defined fee bucket only as needed to capture the intended economics.

**Confidentiality and disclosure compliance.** If the LP is subject to public-records, freedom-of-information, audit, supervisory, or similar disclosure duties, a blanket nondisclosure covenant can conflict with mandatory disclosure law. The markup should preserve compliance with applicable law, permit disclosure when legally required, allow advance notice to the GP when practicable, and avoid conditions that would block prompt statutory compliance. Cite the controlling statute, regulation, or disclosure rule as it applies to the LP’s status.

**Post-termination confidentiality duration.** A confidentiality covenant that survives the LP’s exit should be time-limited and commercially workable. If the proposal is indefinite or open-ended, cap the tail period in years and align the survival language with the fund’s information-sensitivity and market practice.

**ESG / impact / sustainability commitments.** If the LP bargained for reporting, screening, stewardship, or exclusion commitments, convert aspirational phrasing into mandatory language. Replace “may,” “intend,” or “best efforts” formulations with binding covenants where that matches the client instruction and the fund’s operational reality.

**Prior fund precedent.** Earlier side letters granted to the same LP, or materially similar LPs, can serve as practical negotiating anchors. Where the current draft is less favorable, the memo should flag the delta and use the earlier wording as support for the requested revision, while respecting any known business or regulatory differences.

**Fund document hierarchy.** A side letter should not silently override core fund mechanics unless that is expressly intended. Check consistency with the LPA, investment policy statements, and any side-letter carveout or supremacy language, and draft any override carefully so the affected clause is precisely identified.

## 4. Analytical scaffolds

**Step 1 — Build the comparison set.** List the relevant source documents and, if more than one policy or precedent is in play, enumerate them before analysis. Compare each proposed side-letter clause to the controlling fund language and the LP’s instructions.

**Step 2 — Spot the pressure points.** For each clause, ask whether the draft is:
- weaker than the LP’s policy,
- inconsistent with prior precedent,
- too vague to enforce,
- too broad for the LP’s legal obligations, or
- missing a required carve-out or operational detail.

**Step 3 — Draft the markup.** Use clear text-based redline conventions that survive export:
- [DELETED: …]
- [INSERTED: …]
- [REPLACED: old → new]
Add a short rationale comment to each substantive change so the reader can tell why the change was made without relying on formatting alone.

**Step 4 — Make each issue actionable.** For every material point in the memo, state:
- the severity on a uniform ordinal scale defined once at the top,
- the source basis from the LP policy, fund document, prior precedent, or applicable law,
- the operational or economic consequence if the point is not changed,
- and the exact drafting move needed to fix it.

**Step 5 — Prioritize negotiation.** Sort issues into must-have, important, and preferred positions. Reserve must-have for items driven by law, core policy, or a direct inconsistency with governing documents; use lower tiers for economic refinements or market-flex positions.

**Step 6 — Frame recommendations.** End the memo with concrete actions directed to the relevant role, such as legal counsel or the deal lead, and tie each action to a timing anchor linked to the signing or circulation milestone.

## 5. Vertical / structural / temporal relationships (only if applicable)

- If a side letter modifies the LPA, identify the exact relationship between the two documents and avoid drafting that creates ambiguity over which clause controls.
- If a provision is intended to survive termination, state the survival period clearly and check whether it should also survive disclosure to regulators or under law.
- If the draft contains notice-and-response mechanics, ensure the timing works against the LP’s legal deadlines, not just against the GP’s preference.
- If the proposal is meant to carry forward prior-fund language, confirm whether the same wording still works in the current fund structure before transplanting it.
- If there are multiple parties or multiple investor types, analyze each separately rather than treating them as interchangeable.

## 6. Output structure conventions

- Produce two deliverables: a marked-up side letter and a cover memo.
- The marked-up side letter should contain operative text, not a description of the changes, and every substantive edit should be visible in plain text as well as in tracked-style markup language.
- The cover memo should open with a brief severity key, then present issues in descending priority, with one concise paragraph or bullet cluster per issue.
- For each issue in the memo, include the governing source basis and the practical consequence of leaving the draft unchanged.
- Use the source documents’ terminology where possible, but do not copy unnecessary internal phrasing or names.
- Close the memo with a Recommended Actions block that assigns each next step to the responsible role and ties it to the next negotiation or signing milestone.
- Before finishing, confirm that the markup file is the primary deliverable, that it is non-empty, and that the memo is secondary to the completed redline.