Operational Breakdowns That Kill Funds (Before Investors Notice)

NAV calculation is the most fundamental operational output of a hedge fund, and it is also the domain in which silent drift is most consequential. A valuation policy that treats a specific position type inconsistently across months, a pricing source that has stopped providing current data, a side pocket that has not been properly reconciled, or a fee accrual that is calculated on outdated commitment data each produces a NAV that is materially different from the correct number. Each of these drifts can persist for months without investor-visible consequence until an external event forces a full review.

The institutional defence is continuous NAV validation against multiple reference points, documented valuation policies that are actively applied rather than passively referenced, and administrator oversight that identifies anomalies rather than confirming manager-provided numbers.

A fund with more than a handful of investors accumulates side letters over time that contain specific commitments on fees, reporting, liquidity, MFN rights, and operational obligations. In funds without a systematic side letter management framework, these commitments get forgotten, contradicted, or overlooked. A fee breakpoint that is owed but not applied, an MFN right that should have triggered but was not recognised, a reporting election that was never implemented. Each of these becomes a compounding issue that surfaces catastrophically during ODD or annual allocator review.

The institutional defence is a structured side letter framework with systematic extraction of commitments, continuous cross-reference against fund operations, and AI-assisted monitoring of compliance with each commitment.

AML and onboarding files that were never fully completed, corporate structure verifications that stopped midway, source of wealth documentation that is outdated, or screening refreshes that were not performed. These gaps are invisible in the fund's current operations because the investor is already onboarded and operating. The gaps only become visible when CIMA conducts a review, when an allocator's ODD requires evidence, or when an issue arises that requires retrospective reconstruction of the onboarding record.

The institutional defence is continuous AML monitoring with documented evidence of completeness for every investor relationship, not a one-time onboarding exercise that is filed and forgotten.

Fund compliance policies are written and approved at launch but operational practice evolves over time. The fund expands into new strategies without updating the related policy. The fund adds new counterparty types that were not contemplated in the original framework. The fund enters new jurisdictions with regulatory obligations that the policy does not address. The drift between written policy and operational practice accumulates silently until a compliance event exposes the gap or a regulatory review identifies it.

The institutional defence is continuous policy review against actual operational practice, with periodic reconciliation and systematic updates. This is a governance discipline, not an annual administrative task. Our perspective is explored in authority architecture for crypto fund governance.

Funds typically work with multiple service providers, each of whom has their own view of the fund and their own reporting cycle. When the administrator, the auditor, the custodian, and the compliance officer are not operating from a shared data view, gaps emerge between providers. A position that is being custodied differently from how the administrator is recording it. A compliance filing that references an arrangement the service provider is no longer supporting. A counterparty relationship that has changed without all providers being updated. Each gap is individually small but collectively produces an operational framework that does not reconcile.

The institutional defence is coordinated service provider management with a shared data layer, regular provider alignment sessions, and proactive gap identification. Platform-level operations deliver this coordination by design.

Board meetings that proceed on schedule, with minutes approved and resolutions passed, but in which the substantive governance function has gradually eroded. The board pack contents become repetitive. Manager-provided narratives are accepted without substantive challenge. Independent directors do not have the informational independence required to question the narrative. The governance function is operating at the form level but not at the substance level, and the drift is invisible until a stress event requires the governance framework to function for real.

The institutional defence is active governance with independent information access, continuous interrogation of manager positions, and a board composition that is genuinely independent in practice rather than just in title.

Funds launch with authority matrices that specify who can authorise what type of action. Over time, the matrices erode through informal workarounds that seemed efficient in the moment. A trade authorised by someone without matrix authority because the authorised party was unavailable. A wallet transaction approved outside the documented multi-signature process because of urgency. A commitment made to an investor by a person without delegated authority. These workarounds solve an immediate problem while creating cumulative risk that surfaces dramatically when a dispute or external review interrogates the authority record.

The institutional defence is continuous authority discipline with real enforcement, not just documentation. Workarounds that bypass the matrix are identified and addressed rather than tolerated.