Liquidity Risk Management Program

Rule 22e-4 requires every open-end investment company to adopt and implement a written Liquidity Risk Management Program (LRMP) designed to meet shareholder redemptions without significant dilution. Operationally, you need governance, portfolio liquidity classification, limits on illiquid holdings, a highly liquid investment minimum, testing/monitoring, exceptions handling, and board reporting. (17 CFR § 270.22e-4)

Key takeaways:

• You must run a documented program, not a one-time analysis, with ongoing monitoring and escalation. (17 CFR § 270.22e-4)
• Core mechanics include classifying each portfolio position into four liquidity buckets and enforcing an illiquid investment limit. (17 CFR § 270.22e-4)
• The board expects regular, decision-useful reporting on adequacy and effectiveness, backed by defensible records. (17 CFR § 270.22e-4)

A Liquidity Risk Management Program is an operating requirement, not a policy binder. Examiners and auditors will test whether your program actually constrains risk-taking and supports timely redemptions under normal and stressed conditions, without disadvantaging remaining shareholders. Rule 22e-4 is specific about what must exist: a written program, portfolio investment classification into liquidity categories, limits around illiquid investments, a minimum of highly liquid investments, and board reporting on the program’s adequacy and effectiveness. (17 CFR § 270.22e-4)

For a CCO or GRC lead, the fastest route to “exam-ready” is to translate the rule into: (1) accountable roles and governance, (2) repeatable classification and monitoring workflows that connect to trading and portfolio management, (3) predefined escalation actions when limits or minimums are breached, and (4) evidence that the board receives and reviews meaningful program reporting. Done well, your LRMP becomes a control system that shapes portfolio construction decisions, supports liquidity disclosures and filings, and reduces operational scramble during periods of market stress. (17 CFR § 270.22e-4)

Regulatory text

Regulatory excerpt: “Open-end investment companies must adopt and implement a written liquidity risk management program to manage the risk of not being able to meet redemption requests without significant dilution.” (17 CFR § 270.22e-4)

What the operator must do (requirement-level):

1. Adopt and implement a written LRMP that is tailored to the fund’s liquidity risk. “Implement” means it drives day-to-day processes and decisions, not just documentation. (17 CFR § 270.22e-4)
2. Classify each portfolio investment into one of four liquidity categories: highly liquid, moderately liquid, less liquid, and illiquid. (17 CFR § 270.22e-4)
3. Maintain a minimum percentage of highly liquid investments (a fund-set minimum), with monitoring and remediation when the fund falls below. (17 CFR § 270.22e-4)
4. Limit illiquid investments to no more than a meaningful percentage of net assets, with controls to prevent and correct breaches. (17 CFR § 270.22e-4)
5. Report to the board at least annually on the program’s adequacy and effectiveness. (17 CFR § 270.22e-4)

Plain-English interpretation (what the rule is really asking)

You need a defensible, repeatable way to answer five questions at any point in time:

• Can we pay redemptions on time under normal conditions without selling positions at fire-sale prices?
• What assets are truly liquid given market depth, settlement, and size of the position?
• How much “hard-to-sell” exposure do we have, and is it constrained by design?
• If liquidity gets tight, who decides what happens and how quickly do controls force action?
• Can we prove it with records that show classification logic, monitoring, escalation, and board oversight? (17 CFR § 270.22e-4)

Who it applies to (entity and operational context)

In scope entities

• Open-end investment companies subject to Rule 22e-4. (17 CFR § 270.22e-4)

Functions that must participate (operational reality)

• Portfolio management / trading: classification inputs, liquidity assumptions, order sizing, and remediation trades.
• Risk management: independent challenge, stress considerations, dashboards, breach response.
• Fund operations: cash forecasting, settlement cycles, swing pricing considerations where relevant to operations (keep your LRMP aligned with actual redemption mechanics).
• Compliance: program ownership, testing, documentation, board materials, exception governance.
• Fund administration / accounting: NAV impacts, net asset calculations used for limit testing.

What you actually need to do (step-by-step)

1) Establish governance and ownership

Create a clear operating model:

• Name a program owner (often Compliance or Risk) responsible for the written LRMP, annual review package, and audit/exam coordination. (17 CFR § 270.22e-4)
• Define decision rights for: liquidity classification methodology changes, setting the highly liquid minimum, approving exceptions, and triggering remediation actions. (17 CFR § 270.22e-4)
• Set escalation paths to senior management and to the board for material issues. Tie escalation to defined triggers: illiquid limit risk, falling below the highly liquid minimum, data quality failures, or repeated classification overrides. (17 CFR § 270.22e-4)

Practical tip: write a one-page LRMP RACI that an examiner can read in two minutes.

2) Write the LRMP so it matches how the fund runs

Your written program should include:

• Scope statement (funds covered, asset classes, any sub-advisers).
• Liquidity risk factors you consider (keep it concrete and linked to your holdings and redemption profile).
• Classification methodology: inputs, assumptions, frequency, override rules, and validation.
• Limits and minimums: illiquid investment limit and your highly liquid minimum, plus how you measure them. (17 CFR § 270.22e-4)
• Monitoring cadence and reporting: daily/weekly/monthly dashboards and who receives them.
• Breach management: what constitutes a breach, required notifications, remediation steps, and documentation requirements.
• Program review: how you test the program’s adequacy/effectiveness and prepare board reporting. (17 CFR § 270.22e-4)

3) Build and run the liquidity classification process

Operationalize classification as a controlled workflow:

• Inventory all portfolio positions and ensure each position receives one of the four categories in a system-of-record. (17 CFR § 270.22e-4)
• Define data sources (pricing, volumes, dealer quotes, internal execution history) and how they feed classification.
• Set a reclassification cadence and event-driven triggers (e.g., market dislocation, rating downgrade, widening bid-ask spreads, large shareholder activity).
• Control overrides: require documented rationale, approval, and a lookback review to confirm overrides do not systematically bias liquidity upward.

Evidence that matters: change logs, override tickets, and a periodic validation report.

4) Implement the illiquid investment limit control

Rule 22e-4’s illiquid limit is bright-line:

• Measure illiquid investments as a percentage of net assets using a consistent calculation approach, aligned with your classification system-of-record. (17 CFR § 270.22e-4)
• Pre-trade controls where feasible: block or require approval for trades that would push the fund toward or over the limit.
• Post-trade surveillance: daily monitoring with alerts to Compliance/Risk.
• Breach workflow: document cause, immediate containment actions, remediation plan, and communications to governance stakeholders.

Your goal is to show: “We would detect this quickly, we would act, and we can prove each step.”

5) Set and monitor the highly liquid investment minimum

Operationalize the minimum as an explicit portfolio constraint:

• Document how the minimum is set (who proposes, who approves, what portfolio and redemption considerations are evaluated). (17 CFR § 270.22e-4)
• Monitor against the minimum using the same category data used for classification.
• Define remediation actions if the fund falls below the minimum: increase cash/highly liquid exposures, adjust trading plans, reduce less-liquid exposures, or other measures consistent with the LRMP. (17 CFR § 270.22e-4)
• Record each shortfall event and the steps taken.

6) Board reporting and annual program review package

Build a board-ready package that is decision-useful:

• Annual report addressing adequacy and effectiveness, with key metrics, issues, and changes to methodology. (17 CFR § 270.22e-4)
• Material events: breaches/shortfalls, root causes, time-to-remediate, and corrective actions.
• Challenges and limitations: data gaps, hard-to-price assets, and how you mitigated them.

Avoid vague assurances. Include exhibits: dashboards, trend charts, and a short list of “what changed this year and why.”

Required evidence and artifacts to retain

Keep artifacts in a single LRMP evidence repository (GRC tool or controlled drive) with retention aligned to your broader books-and-records practice.

Minimum set:

• Written LRMP and revision history. (17 CFR § 270.22e-4)
• Liquidity classification methodology document and any model documentation.
• Position-level classification outputs by date (system extracts) and change logs. (17 CFR § 270.22e-4)
• Illiquid investment limit monitoring reports and alerts; breach tickets and remediation evidence. (17 CFR § 270.22e-4)
• Highly liquid minimum approval memo, monitoring reports, and shortfall documentation. (17 CFR § 270.22e-4)
• Governance artifacts: RACI, committee minutes, approvals for methodology changes and exceptions.
• Board materials: annual LRMP report, minutes reflecting discussion and follow-ups. (17 CFR § 270.22e-4)
• Testing/audit workpapers: control tests, QA of classifications, reconciliation checks between holdings and classification feeds.

Practical note: Daydream can help you standardize evidence requests, map controls to Rule 22e-4 obligations, and keep a clean audit trail of approvals and exceptions without rebuilding workflows in spreadsheets.

Common exam/audit questions and hangups

Expect these lines of questioning:

• “Show me your written program and who owns it.” They will test accountability and governance. (17 CFR § 270.22e-4)
• “Walk me through how a position gets classified.” They will look for consistency, data lineage, and override controls. (17 CFR § 270.22e-4)
• “How do you prevent exceeding the illiquid limit?” They will expect monitoring plus a credible remediation playbook. (17 CFR § 270.22e-4)
• “How was the highly liquid minimum set?” They will look for rationale and approval records. (17 CFR § 270.22e-4)
• “What did you report to the board, and what did the board do with it?” Minutes matter as much as the deck. (17 CFR § 270.22e-4)
• Data integrity hangup: holdings feeds, stale classifications, and inconsistent treatment across sleeves/sub-advisers.

Frequent implementation mistakes (and how to avoid them)

• Mistake: treating classification as a quarterly exercise. Fix: make classification updates event-driven and controlled, with monitoring that can catch liquidity deterioration quickly. (17 CFR § 270.22e-4)
• Mistake: overrides without governance. Fix: require written rationale, second-line approval, and periodic analysis of override patterns.
• Mistake: illiquid limit monitoring that is purely after-the-fact. Fix: add pre-trade checks for known illiquid buckets and near-limit alerts.
• Mistake: a highly liquid minimum that no one can explain. Fix: maintain a concise approval memo that ties the minimum to portfolio composition and redemption considerations. (17 CFR § 270.22e-4)
• Mistake: board reporting that is generic. Fix: include exceptions, trend metrics, and program changes, plus evidence of management actions. (17 CFR § 270.22e-4)

Enforcement context and risk implications

No public enforcement cases were provided in the source catalog for this page, so do not assume how the SEC has charged similar matters. The practical risk remains clear from the rule itself: weak liquidity controls can lead to redemption harms and dilution, plus regulatory findings tied to failure to adopt, implement, or evidence the required program elements. (17 CFR § 270.22e-4)

Practical execution plan (30/60/90-day)

Use this as an execution sequence. Adapt based on fund complexity and data maturity.

First a defined days (stabilize and baseline)

• Inventory funds in scope and confirm the current state of any LRMP documentation. (17 CFR § 270.22e-4)
• Publish LRMP governance: owner, committees, RACI, escalation routes.
• Identify system-of-record for holdings and classification outputs; confirm you can produce position-level classifications on request. (17 CFR § 270.22e-4)
• Implement a basic monitoring pack: illiquid percentage, highly liquid percentage, exceptions log. (17 CFR § 270.22e-4)

Day 31–60 (operationalize controls)

• Finalize written LRMP aligned to real workflows (classification, monitoring, remediation, reporting). (17 CFR § 270.22e-4)
• Deploy an approvals-based override process for classification changes.
• Implement alerting for approaching illiquid limit and falling below highly liquid minimum; assign owners for response steps. (17 CFR § 270.22e-4)
• Run a tabletop exercise: simulate a liquidity shock and a large redemption day, and document decisions and artifacts created.

Day 61–90 (prove effectiveness and prep board-ready reporting)

• Conduct a control effectiveness check: sample classifications, validate data lineage, test breach workflow end-to-end.
• Draft the annual board report template and populate it with the last period’s monitoring results. (17 CFR § 270.22e-4)
• Close evidence gaps: missing minutes, missing approvals, inconsistent data extracts.
• If you use Daydream, configure a Rule 22e-4 control map, evidence collection workflows, and exception tracking so audits don’t become email archaeology. (17 CFR § 270.22e-4)

Frequently Asked Questions

Does Rule 22e-4 require a written program even if our fund invests mainly in highly liquid assets?

Yes. The rule requires open-end funds to adopt and implement a written liquidity risk management program. (17 CFR § 270.22e-4)

What evidence is most persuasive that the program is “implemented,” not just written?

Examiners look for ongoing classification outputs, monitoring reports, exception/breach tickets with remediation steps, and board materials that reflect oversight and follow-up. (17 CFR § 270.22e-4)

How do we handle sub-advisers or multiple sleeves with different processes?

Put a single fund-level LRMP over the top, require consistent classification categories and reporting, and enforce common exception and escalation rules across all sleeves. (17 CFR § 270.22e-4)

What should trigger reclassification of an asset’s liquidity bucket?

Use both scheduled reviews and event-driven triggers tied to observable market and position factors, and document the triggers and approvals in the LRMP so the process is repeatable. (17 CFR § 270.22e-4)

What’s the fastest way to get board reporting into a defensible format?

Standardize a board deck template that includes the required adequacy/effectiveness assessment plus exhibits for classifications, illiquid limit monitoring, highly liquid minimum monitoring, and exceptions with management actions. (17 CFR § 270.22e-4)

Can our LRMP live in our GRC tool, or does it have to be a standalone policy document?

The rule requires a written program and evidence of implementation; a GRC tool can host the program, approvals, exceptions, and evidence as long as you can produce coherent, dated records on request. (17 CFR § 270.22e-4)