Cross-default clauses and risk across financed assets

A cross-default review begins with a directed map of obligations. The map should show which event under Loan A can become an event under Loan B, what threshold applies and whether notice or cure changes the sequence. A portfolio ownership chart alone does not show those connections.

The practical decision is which otherwise performing assets or financing plans become exposed when a specific problem arises. Distinguish contractual default status from the lender’s exercise of a remedy. Even where an event creates rights, it does not establish that every lender has exercised every right at the same moment.

Separate default links from collateral links

A cross-collateralization agreement dated February 23, 2018, filed with the SEC, addresses cross-default in Section 5 and remedies separately in Section 6. It is a historical negotiated example, not a standard applicable to all loans.

For the borrower’s own documents, make separate lists of obligations, pledged assets and event links. Shared collateral can support multiple debts without using the same trigger language as a cross-default clause. A shared guarantor can create another connection through liquidity or covenant requirements. Keep each link labeled with the operative document and amendment.

A clause may refer to a default, an event of default after notice and cure, unpaid indebtedness above a threshold or indebtedness that has actually been accelerated. Those formulations are not interchangeable. Counsel should determine their effect under the governing law and the full documents, including exceptions and defined terms.

Worked exhibit: three loans and two different arrows

Consider an entirely hypothetical structure. Loan A is a $2 million property loan. Loan B is a $3 million property loan whose invented clause is triggered only when qualifying Loan A debt is accelerated. Loan C is a $1 million facility whose invented clause is triggered by an uncured event of default under Loan B. Assume every referenced amount satisfies the relevant fictional threshold and no other links exist.

Represent the direction as A acceleration → B event of default → C event of default. This is not the same as A late payment → immediate acceleration of A, B and C. The following event map identifies where the analysis must pause.

The table is a reasoning exercise, not legal advice about automatic consequences. Its purpose is to stop an analyst from replacing a chain of conditions with one unsupported portfolio-wide conclusion.

Quantify exposure without pretending to quantify legal loss

Under the hypothetical map, the connected principal totals $6 million: $2 million plus $3 million plus $1 million. That is a reference amount potentially involved in the chain, not a prediction of loss or a statement that all $6 million is immediately payable.

Suppose B produces $90,000 of annual cash after scheduled debt service and C’s facility funds a $250,000 seasonal operating need. A problem beginning with A can therefore affect two different plans: distributions from B and access to C. Whether either restriction actually occurs depends on the relevant cash-control and funding conditions. Show those dependencies as separate conditional outputs rather than adding them to principal as another “loss.”

If the sponsor has $300,000 unrestricted liquidity and must reserve $250,000 for the seasonal need, only $50,000 remains for the modeled response to A before other commitments. This is a funding constraint, not permission to move money between entities. Confirm distribution and intercompany-transfer restrictions before identifying the source as available.

Build a document-backed incident record

For each arrow, preserve the exact clause reference, referenced obligation, amount threshold, notice mechanism, cure period and evidence of the triggering event. Assign someone to verify receipt dates. Distinguish a lender’s allegation from an agreed status, while ensuring that disputed notices are escalated promptly.

The map should also show what ends the connection. Does a cure reverse the downstream event? Is a written waiver required? Does the downstream loan have an independent reporting obligation once the upstream problem occurs? A waiver for one creditor should not be assumed to bind another creditor or erase another clause.

Include material affiliates and guarantees where the definitions require them, but do not map every company the sponsor owns merely because it exists. Overinclusive maps can make risk appear universal and obscure the specific problem that needs action.

Use the map before and after closing

Before execution, test a delayed payment, a reporting failure and a refinancing that does not close at maturity. Ask whether the proposed language captures the intended risk or unexpectedly connects unrelated assets. Negotiating the connection while alternatives remain is different from seeking relief after it triggers.

After closing, maintain the map with amendments, refinancings and releases. A retired loan may remain referenced through a defined replacement obligation, while an executed release may remove a link. The finished record should let the sponsor and counsel trace one concrete event through documented conditions, identify the next deadline and fund a response without assuming that good property operations alone isolate the asset.