An incident register distinguishes what happened, what is alleged and what counsel has established; a separate credit ledger prevents overlapping claims from being added twice.
A delegated transaction can create several apparent loan issues before anyone has determined which legal triggers, if any, occurred. Keep an incident sequence separate from a claim calculation. The example below follows a bookkeeper’s cash transfer and an affiliate officer’s ownership document, then reconciles hypothetical recoveries without declaring an automatic cure or double-counting the same loss.
A nonrecourse loan description is incomplete without its exceptions. The borrower and guarantor need to understand which conduct can create a claim for specified losses, which events can change recourse more broadly and which separate obligations continue under other documents. These are different exposures and should not be compressed into one “bad acts” summary.
The practical goal is an operating control map. Identify who handles cash, signs leases, approves ownership changes, manages insurance and communicates with the lender. Connect those responsibilities to the actual documents and an escalation process. Good intentions do not replace compliance with an expressly required consent or reporting step.
Read the consequence as carefully as the trigger
The Block 40 agreement dated June 1, 2022, Section 10.1, distinguishes specified recourse liabilities from events that make obligations fully recourse. This is a historical negotiated structure, not a universal list or an opinion on enforceability.
Have counsel identify the person bound, the conduct covered, any knowledge or materiality qualification, permitted exceptions, cure provisions and the resulting remedy. A borrower covenant and a guarantor obligation may be related without being identical. Check the guarantee itself and incorporated definitions rather than assuming the loan agreement tells the whole story.
Separately list environmental indemnities, completion support, carry support and other guarantees. A nonrecourse limitation in one instrument does not establish that every other instrument has the same limit. Conversely, the presence of an exception does not prove it has been triggered in a particular situation.
Worked exhibit: different consequences require different models
Consider a fictional $4 million loan. Assume one invented clause creates liability for proven loss caused by an unauthorized use of specified funds. A separate invented clause makes the outstanding debt fully recourse following a defined prohibited transfer. These are hypothetical formulations used to distinguish the analyses; no actual liability is determined here.
If $80,000 is improperly applied and the stipulated covered loss is $80,000 plus $10,000 of included expenses, the modeled claim is $90,000 under the first clause. That number is not automatically the entire loan balance. It also should not be assumed to be the claim if causation, mitigation, coverage or legal defenses remain unresolved.
Under the second hypothetical clause, the event could expose the defined $4 million debt rather than only the transfer’s transaction cost. The model must then consider the operative debt definition, credits, recoveries and enforceability. It should not add $4 million and $90,000 mechanically if they represent overlapping obligations or recoveries.
The distinction changes the operating response. Both issues warrant prompt legal review, but the relevant facts and potential consequences are different. A risk register that labels both merely “covenant breach” loses the information needed to prioritize a decision.
Build controls around real borrower actions
| Action or responsibility | Evidence to check before acting | Practical control |
|---|---|---|
| Distribute property cash | Permitted-distribution provisions and current restriction status | Approval record tied to a reconciled cash ledger |
| Add debt or grant collateral | Debt, lien and intercreditor restrictions | Counsel review before commitment or filing |
| Change ownership or control | Transfer definitions, exceptions and required consent | Updated ownership diagram with approval evidence |
| Handle tenant deposits or insurance proceeds | Separate account and application requirements | Segregated tracking and authorized disbursement record |
| Renew insurance and pay taxes | Required coverage, due dates and escrow responsibilities | Calendar with proof of payment or coverage |
| Respond to distress or insolvency issues | Full documents and governing law | Immediate qualified counsel involvement |
The table suggests a workflow; it is not a statement that each action is prohibited under every loan. The controlling rule must be extracted from the transaction’s own documents. An action that is permitted with notice should not be treated as prohibited, and an action needing consent should not be completed on the assumption that notice is enough.
Make delegation visible
Property managers, bookkeepers and affiliate officers may perform tasks that affect compliance. Give them clear, relevant instructions and an escalation contact. They do not need to interpret a guarantee independently, but they should know when a transfer, refund, distribution or new obligation needs review.
Preserve supporting evidence in a controlled record: bank reconciliations, consent letters, insurance certificates, tax confirmations and executed amendments. A current record helps distinguish an actual failure from a missing document and supports a timely response to questions. Avoid backdating or reconstructing approvals as if they existed when they did not.
If an apparent problem is discovered, document the facts and obtain counsel’s guidance promptly. Do not assume that returning funds or reversing an internal entry automatically cures every legal consequence. At the same time, do not declare full recourse merely because an issue has been raised. The operative trigger, status and remedy need analysis.
Trace a delegated-action incident before totaling claims
Extend the fictional $4 million loan example. Assume a bookkeeper sends $80,000 of designated tenant-deposit cash to an affiliate after an asset manager mistakenly marks a distribution as approved. Separately, an affiliate officer signs an ownership-transfer document. Whether that document became effective, satisfied a permitted-transfer exception, or required prior consent is unresolved. None of these stated facts alone establishes the result under an actual guarantee.
| Event | Responsible actor and preserved evidence | Question requiring resolution | Register status |
|---|---|---|---|
| Day 1: $80,000 wire posts | Treasury preserves bank record, account restriction and approval ticket | Was use prohibited, and what covered loss resulted? | Cash movement verified; liability unresolved |
| Day 2: transfer document discovered | Entity secretary preserves signed version, conditions and ownership ledger | Was a transfer effective and outside a permitted exception? | Possible trigger alleged; facts incomplete |
| Day 3: $30,000 returned | Controller reconciles bank receipt to the original wire ID | What loss is reduced, and does any other consequence remain? | Recovery verified; no automatic cure recorded |
| Day 4: counsel compares documents | Counsel reviews definitions, knowledge qualifications, notices, consent and remedies | Which claimed event and obligation are actually supported? | Separate conclusions required for each allegation |
| Before the next distribution | Asset manager and treasury require the designated written approval | Is this next action permitted under current restrictions? | Hold pending the identified review, not a claimed contractual cure |
This workflow preserves original evidence and separates an internal authorization error from a contractual consent. An officer cannot create retroactive lender approval by correcting the company’s ticket. Equally, an unsigned consent file does not establish that a document-defined prohibited transfer occurred. Counsel must determine the facts and operative provisions; the register should preserve disputed and unresolved states.
Now stipulate a separate, conditional recovery illustration after the parties have agreed how amounts overlap. Assume the $80,000 funds issue plus $10,000 included expense initially produces a $90,000 claim. The verified $30,000 return leaves $60,000: $50,000 of remaining funds loss and $10,000 expense. Assume, solely for this example, full-debt recourse is also established, net collateral recoveries are $3.2 million, and that $3.2 million already includes the returned $30,000. The remaining debt is $800,000; do not deduct the same $30,000 again.
| Agreed reconciliation item | Amount | Treatment in the combined ledger |
|---|---|---|
| Remaining defined debt after $3.2 million net recovery | $800,000 | Included once |
| Remaining funds-loss component | $50,000 | Stipulated to overlap the remaining debt; not added again |
| Included expense outside that debt definition | $10,000 | Added once under the assumed agreement |
| Combined unpaid amount before later payment | $810,000 | Not $860,000 from adding $800,000 and $60,000 |
| Later sponsor payment applied to that combined amount | ($100,000) | Recorded once with receipt and allocation |
| Remaining modeled amount | $710,000 | Conditional arithmetic, not a liability opinion |
The overlap and expense treatment are explicit assumptions for teaching reconciliation, not a rule that every loss-based claim is absorbed into principal. If counsel or the agreed settlement assigns different obligations, credits or expenses, rebuild the ledger. If full-debt recourse is not established, the $800,000 row cannot simply remain as a guarantor claim. Record claim IDs, credited recovery IDs and allocation authority so one receipt is neither omitted nor applied twice to the same aggregate obligation.
Revisit the map when the transaction changes
A refinancing, ownership transfer, manager replacement or amendment can change who acts and what is required. Update the control map and preserve superseded versions so the relevant period can be reconstructed. Pay particular attention to decisions made under time pressure, when the person authorizing an action may not be the person maintaining the covenant record.
The useful outcome is a short, transaction-specific set of action controls supported by counsel’s interpretation and reliable evidence. It allows the sponsor to operate the asset responsibly while understanding the actual limitations of the nonrecourse structure, without treating a marketing label as a complete risk assessment.
Sources and evidence
- SEC-filed Block 40 loan agreement, June 1, 2022Section 10.1: Exculpation; Borrower’s Recourse Liabilities; Springing Recourse Events · Checked 2026-10-21 · Individual historical agreement; no legal determination or nationwide standard is supplied.
Source dates and applicability matter. Report an error or a changed source.