Define the high-water mark before enforcing drawdown

Drawdown compares current equity with a defined peak, called the high-water mark. We would require the mandate to specify the equity series, peak observation schedule and treatment of deposits before compiling a drawdown restriction. A threshold without those definitions can react to account funding rather than trading losses.

Consider an illustrative cash-flow-free series of $10,000, $11,000 and $10,450. The high-water mark is $11,000 and current drawdown is ($11,000 - $10,450) / $11,000 = 5%. A 4% restriction therefore triggers under this fixture. Using starting equity instead would describe a different quantity, because current equity still exceeds $10,000.

A deposit changes the comparison

Suppose the owner deposits $2,000 immediately after the peak. Raw equity becomes $13,000, then falls to $12,450. A raw-balance peak gives about 4.23% drawdown. A chosen cash-flow-adjusted series can remove the deposit from subsequent equity, recovering the $11,000 to $10,450 comparison and its 5% drawdown. These are different accounting contracts, each of which needs an explicit rule.

We would implement a documented adjustment method, such as a unitized equity series, rather than repeatedly subtracting arbitrary historical cash flows. Unit issuance at the deposit price preserves per-unit performance. Withdrawals then redeem units under the same convention. Fees, funding and unrealized valuation remain inside the selected equity measure.

The review fixture should contain a deposit, withdrawal and a new genuine peak. Record the watermark before and after every event, the adjustment identity and the trigger result. Check whether the mandate observes marks continuously or at scheduled snapshots. A sampled peak can miss an intraday maximum, which changes the interpretation of the restriction.

Finally specify the response: block additional exposure, request review or invoke an separately authorized exit procedure. A drawdown calculation alone supplies no instruction to liquidate. Our acceptance record would keep the measurement and the permitted response in separate fields.

For a first local review, we would preserve the original owner wording beside the typed fields and ask a second reviewer to derive the expected result independently. Any disagreement identifies an ambiguity to resolve before execution. The saved fixture should contain both accepted and rejected cases so a procedure that rejects everything cannot receive credit for useful compliance.

Our mandate compiler provides the wider instruction-to-action framework for this drawdown accounting rule. The published controls research supplies its historical background. DXAP publicly describes the corresponding separation between model proposals and external policy checks.