TRUSTEE OS
← Journal · US

Executory contracts: build the operating decision before the legal list

Assumption and rejection affect future capacity, cure costs, and claims; they are not simply keep-or-delete commands.

A contract decision changes the business model

A restructuring team may inherit a spreadsheet of leases, licences, supply agreements, and customer arrangements marked keep or reject. That is a useful inventory, but it is not a finished decision. Section 365(a) permits assumption or rejection of executory contracts and unexpired leases subject to court approval and the section’s applicable rules. Whether an agreement falls within the relevant legal category is itself a question that deserves analysis.

The thesis is that the operating choice should be developed alongside the legal assessment. A contract may be loss-making on its face but necessary to deliver a profitable bundle of services. Another may have attractive pricing but depend on volumes the business no longer expects. A general cost-cutting target cannot resolve those dependencies. The decision package needs the agreement, amendments, performance history, and a forecast of how the reorganized operation would use it.

Avoid treating cure as a late-stage surprise

Section 365(b) sets requirements associated with assumption when there has been a default, including cure and adequate assurance where applicable. Those issues can determine whether keeping an agreement is financially possible. A forecast that assumes continued performance without the related cost can overstate the business’s runway. Assignment also has its own requirements under section 365(f), rather than following automatically from a buyer’s interest.

The opposing concern is flexibility. Overcommitting to agreements too early can burden a business whose final footprint remains uncertain, while waiting may harm counterparties and operations. Section 365 contains specific timing rules for particular agreement types, including nonresidential real property leases. The lesson is not to apply one generic deadline to every contract. It is to identify the relevant category and maintain a decision calendar that reflects the applicable text and case orders.

Link legal treatment to claims and the plan

Rejection should not be described as erasing history. Its consequences and the resulting claim require a separate analysis under section 365(g) and the relevant claims framework. The contract tracker should therefore distinguish operational termination assumptions, proposed legal treatment, court action, and the amount or status of any associated claim. These states may change at different times.

Section 1123(b)(2) also connects assumption or rejection to plan provisions, subject to section 365. A coordinated team can use that connection to align contract decisions with the future operating model, rather than defer every unresolved agreement until the plan is nearly complete. The practical review asks what capacity is required, what it costs to preserve it, and which alternatives are credible. A source-linked contract inventory helps answer those questions when it includes reasons and dependencies, not merely colours indicating preference. The value comes from making the legal choice and its financial consequences visible together.

Primary sources

  1. [1] 11 U.S.C. § 365 — official GPO edition — § 365(a), (b), (d), (f) and (g) ↗

    Assumption and rejection, defaults, assignment, timing for specified leases and rejection consequences.

  2. [2] 11 U.S.C. § 1123 — official GPO edition — § 1123(b)(2) ↗

    Plan provisions concerning assumption or rejection subject to section 365.