Skip to main content
Back to advisor outputs

Explain the wrapper before the return

This structure gives scheduled access to private-market exposure, but liquidity windows, fees, tax reporting, and source documents control the client experience.

Output routeAdvisor packet to document check to tool to controlled example.
4Say this6Source checks2Tools2Examples

Advisor Packet

Start with usable language, then prove the mechanics.

Say this
  1. 01
    Client-safe language

    The wrapper controls how money gets in, how liquidity windows work, what tax form appears, and which fees apply.

  2. 02
    Client-safe language

    Scheduled liquidity means the fund may offer repurchases, but requests can exceed available capacity.

  3. 03
    Client-safe language

    Before comparing returns, we should identify the share class, fee stack, and source documents.

  4. 04
    What to confirm first

    Wrapper type and liquidity mechanism.

Verify this
  • Semi-liquid alternatives

    Confirm the legal wrapper before reading the asset class.

  • Semi-liquid alternatives

    Find the stated liquidity window and any discretion language.

  • Semi-liquid alternatives

    Check whether tax form and subscription process match the client account.

  • Repurchase program

    Confirm the cap as a percentage of NAV or shares.

  • Repurchase program

    Find timing, notice, pricing, and board discretion language.

  • Repurchase program

    Compare stated capacity with accepted-versus-requested history.

Route the next stepUse the packet as the front door, then move into the exact Learn mode the question needs.
Use the outputLanguage first, then document route, lab, controlled example, and broader path.
  1. 01Advisor language
    Use the language

    This structure gives scheduled access to private-market exposure, but liquidity windows, fees, tax reporting, and source documents control the client experience.

    Client-safe summary
  2. 02Source check
    Verify the claim

    Confirm the legal wrapper before reading the asset class.

    Semi-liquid alternatives
  3. 03Tool
    Pressure-test the mechanic

    Use before applying strategy or performance claims so the wrapper does not get confused with the underlying asset class.

    Wrapper Matrix
  4. 04Controlled example
    Apply it to a model scenario

    Use a controlled BDC scenario to connect wrapper structure, servicing fees, and share-class comparison before discussing performance.

    MODEL-BDC-FEE: Model BDC wrapper and share-class economics
  5. 05Path
    Continue the workflow

    Explain what semi-liquid alternatives are and where they fit.

    Market foundations

Advisor Output

Use the language, then verify the source.

Client-safe language

This is education about the structure, not a recommendation or a liquidity promise.

  • The wrapper controls how money gets in, how liquidity windows work, what tax form appears, and which fees apply.
  • Scheduled liquidity means the fund may offer repurchases, but requests can exceed available capacity.
  • Before comparing returns, we should identify the share class, fee stack, and source documents.
What to confirm first

Anchor the explanation to facts the advisor can verify on AltHarbor or in the fund documents.

  • Wrapper type and liquidity mechanism.
  • Share class and servicing or distribution charges.
  • Current source document supporting the policy being explained.

Source Concepts

Terms and document proof behind this output.

Related Tools

Use the lab to pressure-test the language.

Controlled Examples

Apply the output to a model inspection case.

Private CreditMODEL-BDC-FEE
Non-traded BDC / fee stack

Model BDC wrapper and share-class economics

Use a controlled BDC scenario to connect wrapper structure, servicing fees, and share-class comparison before discussing performance.

Open Learn example
Private CreditMODEL-CREDIT-LIQUIDITY
Repurchase program

Hypothetical liquidity window versus client cash need

Use a hypothetical liquidity window to show what happens when requests exceed stated capacity.

Open Learn example
Related workflow

Continue from output to the learning surface that owns the mechanic.

Use when a client needs a concise explanation of what the wrapper controls before performance is discussed.

Open related workflow

Learning Paths

Where this output fits in the broader education system.