- 01Questions to ask the manager
What was the lowest recent fill rate, and what drove excess requests?
- 02Questions to ask the manager
Were unfilled requests automatically carried forward, cancelled, or required to be resubmitted?
- 03Questions to ask the manager
What discretion does the board or manager have to reduce, suspend, or modify the program?
- 04Document checks
Repurchase policy, tender offer statement, or shareholder report for cap and cadence.
Ask what happens when demand exceeds capacity
What was the worst recent fill rate, how were unfilled requests handled, and which document proves the current cap, cadence, and discretion language?
Advisor Packet
Start with usable language, then prove the mechanics.
- Proration
Calculate accepted amount divided by requested amount.
- Proration
Check whether the document reports a proration factor directly.
- Proration
Look for resubmission rules or future-window treatment.
- Fill rate
Use the same basis for numerator and denominator.
- Fill rate
Check whether the source reports dollars, shares, or a proration factor.
- Fill rate
Compare recent fill rates across cycles before calling liquidity reliable.
Proration appears in AltHarbor when fill rate, proration factor, requested / accepted need plain-English explanation from the reference desk.
MetricFill rateFill rate appears in AltHarbor when fill rate, accepted / requested, repurchase event need plain-English explanation from the reference desk.
LiquidityRepurchase programRepurchase program appears in AltHarbor when repurchase cap, repurchase cadence, requested / accepted need plain-English explanation from the reference desk.
Show proration, deferred demand, and why a stated cap is not the same as a guaranteed exit.
LiveFiling Trail DecoderRoute an advisor from a product question to the document type most likely to prove it.
Use a hypothetical liquidity window to show what happens when requests exceed stated capacity.
Tender offer fundMODEL-PE-TENDER: Model tender-offer cycle and partial exit riskUse a model private-equity tender cycle to show why an exit window is not the same thing as daily liquidity.
Turn a fund pitch into a source-backed diligence agenda.
Core / 53 minLiquidity and exitsExplain what happens when a client asks for cash back.
Core / 41 minFees and performanceCompare performance after understanding what the return includes.
Intro / 62 minExplain it to a clientTranslate product mechanics into clear client language.
- 01Advisor languageUse the language
What was the worst recent fill rate, how were unfilled requests handled, and which document proves the current cap, cadence, and discretion language?
Manager questions - 02Source checkVerify the claim
Calculate accepted amount divided by requested amount.
Proration - 03ToolPressure-test the mechanic
Show proration, deferred demand, and why a stated cap is not the same as a guaranteed exit.
Liquidity Simulator - 04Controlled exampleApply it to a model scenario
Use a hypothetical liquidity window to show what happens when requests exceed stated capacity.
MODEL-CREDIT-LIQUIDITY: Hypothetical liquidity window versus client cash need - 05PathContinue the workflow
Turn a fund pitch into a source-backed diligence agenda.
Evaluate a first fund
Advisor Output
Use the language, then verify the source.
The goal is to separate normal operating mechanics from stress behavior.
- What was the lowest recent fill rate, and what drove excess requests?
- Were unfilled requests automatically carried forward, cancelled, or required to be resubmitted?
- What discretion does the board or manager have to reduce, suspend, or modify the program?
Each answer should point to the document that proves the current rule or event result.
- Repurchase policy, tender offer statement, or shareholder report for cap and cadence.
- Event notice or source trail for requested versus accepted amounts.
- Risk factor or board discretion language for suspension and gating authority.
Source Concepts
Terms and document proof behind this output.
Repurchase policy, tender offer, or repurchase results showing requested amounts, accepted amounts, proration factor, or capped fill.
- Fill rate
- Proration factor
- Requested / accepted
- Unfilled demand
Tender or repurchase result data with accepted and requested amounts, shares, dollars, or reported percentage.
- Fill rate
- Accepted / requested
- Repurchase event
- Demand pressure
Repurchase policy, prospectus liquidity section, tender documents, and accepted-versus-requested results.
- Repurchase cap
- Repurchase cadence
- Requested / accepted
- Liquidity history
Related Tools
Use the lab to pressure-test the language.
Controlled Examples
Apply the output to a model inspection case.
Hypothetical liquidity window versus client cash need
Use a hypothetical liquidity window to show what happens when requests exceed stated capacity.
Model tender-offer cycle and partial exit risk
Use a model private-equity tender cycle to show why an exit window is not the same thing as daily liquidity.
Continue from output to the learning surface that owns the mechanic.
Use when a fund has repurchase pressure, a partial fill, or a client asks what happens when requests exceed capacity.
Open related workflowLearning Paths