The cash waterfall is a governance mechanism

A cash waterfall allocates control over limited money. Its ordering determines which claims can be paid, which balances must be protected and when sponsors may receive distributions. The schedule is therefore a governance mechanism as well as a modelling convention. The financing team should reconcile the order to applicable terms and operating needs. A formula can route cash perfectly while implementing the wrong priority. The committee needs to know who authorises each use, what triggers a change in control and what happens when cash cannot satisfy every claim.

The starting pool must be defined before priorities are applied. Gross collections, unrestricted balances and cash available after required operating expenditure are different pools. A waterfall that begins after essential expenses assumes those expenses have already been handled elsewhere. A waterfall that begins with gross receipts needs to include them in its order. The model and financing documents should identify the same boundary. Otherwise an apparently complete payment sequence can omit a required claim or deduct it twice. The first governance question is what money enters the mechanism and under whose control.

Required operating payments should be distinguished from discretionary uses. The asset needs certain expenditure to maintain the service on which financing depends. It may also have optional expansion, sponsor fees or improvements whose priority depends on terms and choice. Classifying a use as operating does not automatically establish its seniority; classifying it as discretionary does not establish that it can legally be deferred. The financial analyst should obtain appropriate interpretation and retain unresolved questions. The waterfall should implement an accepted perimeter rather than settle legal or technical disputes by spreadsheet ordering.

Reserves introduce a balance obligation in addition to a payment obligation. Funding or restoring a reserve uses cash now to protect a later purpose. The model should distinguish the target, actual balance, permitted draw and replenishment rule. A shortfall in the target can change distribution permissions even when current service is paid. The committee should see whether the structure can restore protection from identified cash. An automatic replenishment entry without a funding subtraction creates a false sense that the reserve remains intact regardless of operations.

Mandatory service and optional prepayment should remain separate. Paying an obligation due under terms is different from using surplus cash to retire debt early. A sweep can improve future lender exposure but reduce liquidity or sponsor flexibility. The definition of sweep cash should account for required operating needs and protected balances under the agreed mechanism. If a model treats all residual money as excess without that reconciliation, it can sacrifice resilience while appearing to reduce leverage. The decision should state what future obligations the retained or prepaid cash is intended to address.

Distribution conditions can act as a warning mechanism. Restrictions may depend on financial tests, reserve status, defaults, reporting or other defined events. The analyst should distinguish a warning, a lock-up and an event requiring a different remedy. These categories can have very different cash and control consequences. The public paper does not define a universal covenant structure. It provides a specification process that asks what event matters, how it is measured, who confirms it and which payment permissions change. A threshold label without an action is incomplete governance.

Timing of tests matters when distributions precede later obligations. A project can appear compliant at a reporting date while committing cash that is needed for a known future replacement or service payment. A forward-looking distribution test can address some of that exposure if its terms and assumptions are accepted. The committee should identify the calendar over which cash must remain available. It should also know whether the test relies on forecast receipts, actual balances or both. A permission based on unsupported future collections can release protection before uncertainty is resolved.

Cure mechanisms require resources and authority. A sponsor contribution can restore a ratio or balance under specified terms, but the project should not assume that an unverified sponsor will always contribute. A waiver can permit an action without changing the underlying cash shortage. A revised obligation can alter the calendar while creating a new repayment dependence. The model should record the source and consequence of each cure. The committee should recognise whether resilience improved, an exception was granted or a finite support resource was consumed. Calling all responses cured can conceal materially different conditions.

Control arrangements should be designed for timely action. A collection account may help preserve payment priority, while approval processes can create delay during stress. Decision authority should be clear enough that the project can pay permitted essential uses and apply protection when conditions are met. The operating team needs to know which actions remain within its authority and which require escalation. A waterfall described only in lender language can fail operationally if it does not support the daily service requirements or if no accountable person can interpret a trigger when the payment date approaches.

Related-party claims deserve a transparent place in the sequence. Management, development, supply or service fees may be legitimate and contractually required. Their affiliation does not establish that they are subordinate or optional. The model should identify the payment basis, priority and deferral conditions, with appropriate review. The committee should also understand how these claims affect sponsor incidence and operating cash. A structure that shows sponsor distributions as restricted can still transfer cash through other permitted claims. Governance therefore needs a complete use-of-cash perimeter rather than a narrow focus on dividends.

Monitoring should compare actual cash routing with the specified mechanism. A report that shows service paid but omits reserve depletion, unpaid suppliers or permitted exceptions can conceal weakening protection. The operating record should identify receipts entering the pool, required uses, balance movements, discretionary uses and outstanding claims. Variance should explain whether cash generation changed or routing changed. This allows the financing parties to detect a shift in priorities before it becomes an unexplained shortfall. A waterfall can only perform its governance function if actual activity is reported in the same structure.

Scenario testing should include a cash insufficiency path. When the pool cannot meet all claims, the model should show the unpaid or deferred item rather than forcing the waterfall to balance through an unexplained negative account. The committee should identify the consequence of that item remaining unpaid and the party authorised to act. This exposes whether a financing structure preserves service during stress or protects a payment while allowing the asset to deteriorate. A complete downside is not merely a lower distribution output; it is an account of what cash control permits and what obligations remain unresolved.

The waterfall should preserve flexibility where flexibility is valuable and explicitly acceptable. Excessively rigid control can impede a small operating adjustment whose cost prevents a larger failure. Excessively broad discretion can allow cash to leave before known obligations are funded. The trade-off should be considered with the operating model and reporting quality. An accepted delegation can define permitted uses, documentation and escalation boundaries. The aim is a mechanism that responds coherently to the asset's needs while maintaining the protections on which financing relies, rather than either unrestricted discretion or blanket approval for every payment.

The chapter's output is a waterfall specification with interpretation questions. It states the pool, required uses, protected balances, service, optional actions, distributions and control triggers. Each unresolved priority has an owner and required evidence. The finance model then implements the accepted specification and exposes the consequences of insufficiency. This sequence keeps the spreadsheet from becoming an unauthorised contract interpreter. It also gives monitoring teams a stable structure for explaining actual cash and allows the committee to approve a defined allocation of control.