Tool & guide

Problems With Delaware Statutory Trust: Lease-and-Debt Event Calendar

By Sequoia ResearchPublished Read as Markdown

Lease-and-Debt Event Calendar

Users enter lease expirations, renewal options, debt maturities, and assumed exit dates. The calendar highlights overlapping events and distinguishes contractual dates from planning assumptions.

For an export, select Download in the tool, then Save file when it appears below. Your entries stay in your browser.

What Is This Article About?

This guide explains how to place lease dates, renewal notices, loan maturities and assumed sale dates on one calendar. The tool shows which entered dates fall close together within the same group. It keeps dates from documents separate from planning assumptions and leaves missing dates visible. A fictional example shows how the chosen time window changes the results without changing the underlying events.

Table of Contents

Why Lease and Debt Timing Deserve a Shared View

A lease expiration and a loan maturity answer different questions. The first concerns an occupancy agreement. The second concerns debt terms. When both dates approach, a reviewer may need to examine how leasing plans and the loan's repayment plan fit together. A calendar makes that sequence easier to see.

The OCC's refinance guidance explains why a debt balance due at maturity can require careful review. Replacing a loan depends on the borrower, the property and market terms. The guidance is written for banks; it does not say that a DST can always refinance or that a particular lender will extend a loan. OCC: Commercial Lending—Refinance Risk.

This tool handles the timing part of that review. It sorts entered dates, counts them by month and finds nearby pairs. It does not calculate the debt amount due, the cash needed for a vacant space or the proceeds from a sale. Those questions need other records and models.

A close pair can be worth discussing without proving that a problem exists. A sale may repay a loan before maturity, but a planned sale can fail to close. A lease may renew, but a calendar entry cannot confirm that the right was exercised. Keep the relevant conditions beside each date.

The result is a dated work record. It helps you see which questions should be addressed together. It is not an alarm service, a legal deadline calculator, a sponsor rating or a forecast of the investment's outcome.

Choose the Review Date and Calendar Groups

Enter the date of your review first. It cannot be after the current date on your device. The tool uses it to describe each known event as before, on or after the review date. Event dates themselves may be in the future; that is the main purpose of the calendar.

The date range is 1900 through 2200. The tool counts whole calendar days. It does not use business days, local closing times, holiday rules or delivery cutoffs. A date that appears before the review is not labeled a default or a missed deadline. The tool does not know whether the event already occurred.

Each event needs a calendar group and a label. Use a group for the property, offering or deliberately chosen set of events you want to examine together. Only records with the same group text are paired. Leading and trailing spaces are removed, and repeated spaces become one space. Letter case still matters.

For example, “Linden warehouse” and “Linden Warehouse” remain different groups. Correct accidental differences before interpreting an empty pair list. A broad group can compare events across several properties, but you should state why that broader view is useful. The tool does not infer common tenants, shared debt or linked guarantees.

Give each event a clear label, such as “North tenant renewal notice” or “Senior loan maturity.” Up to forty records can be entered. Avoid names such as “Lease date” when several leases or several dates in one lease could be involved.

Enter the Event and Its Date Basis

Select an event type: lease expiration, renewal-option or notice date, debt maturity, assumed exit, or other event. Then choose the basis of the date. The three choices are document-stated, planning assumption and unconfirmed.

Document-stated means you are recording a date you found in a document. It requires a source title and reference, such as a version, page or clause. The label does not mean the tool has read that document. It does not confirm signatures, later amendments, conditions or legal effect.

Planning assumption identifies a chosen future date for analysis. The assumed-exit type must use this basis. A projected sale date remains an assumption even if it appears in a sponsor presentation. A document can contain a plan; its existence does not turn the plan into a binding sale.

Unconfirmed is useful when a date has been reported but its support is still unresolved. If you enter that date, it can appear in a nearby pair. The pair retains an unconfirmed label. If the date itself is unknown, leave it blank; the record stays visible but cannot enter date calculations.

Record the source's issue date when known. It cannot be later than the review date. Leave it blank when unknown instead of using the day you downloaded the file. Add notes about conditions, missing pages and the person reviewing the issue. The tool does not fetch sources or verify their contents.

Keep Renewal Options Separate From Lease Expirations

An option notice date and a lease expiration can be separate events. A lease might require a notice before the term ends. The exact timing, recipient, delivery method and conditions must come from the applicable agreement and advice on that agreement. This tool does not derive those terms.

Enter each relevant date as its own record. Use the event label to state whether it is a notice date, a decision target or the term's end. A planning target for reviewing a renewal should use the planning basis. Do not label it document-stated just because it concerns a real lease.

A window for giving notice may have an opening date and a closing date. Enter those endpoints separately if they matter to your review. The tool treats them as two point dates. It does not shade a legally valid exercise period or determine whether notice given between them would be effective.

The distinction also matters for debt. A current maturity date, a deadline to request an extension and an assumed extended maturity are separate entries. An option to extend may have conditions. Do not replace the current maturity with a later assumed date and lose the original obligation from view.

IRS Revenue Ruling 2004-86 describes a particular trust arrangement with limits on changes to debt and leases. The legal powers of an actual structure need separate review. The calendar does not determine whether a manager may amend an agreement, refinance, or use another structure. IRS Revenue Ruling 2004-86.

How the Nearby-Event Window Works

Choose a whole-number window from zero to 365 days. Two dated events form a nearby pair when they share a group and their dates are no more than that many calendar days apart. The boundary is included. At ninety days, a pair ninety days apart is included; a pair ninety-one days apart is not.

Zero finds dates that are exactly the same. It does not mean “ignore timing.” Larger windows produce at least as many pairs from the same records. That change reflects your chosen review range, not new evidence or an increase in measured investment risk.

Each pair is listed once. The earlier date appears first. Events on the same day retain their entered order. One event can appear in several pairs, so the summary also shows the number of distinct events involved. Three pairs do not necessarily mean six different events.

The basis label follows the two entries. The output distinguishes two document-stated dates, two planning assumptions, a document-and-planning mix, and any pair that includes an unconfirmed date. A nearby pair does not become more reliable just because the dates match closely.

Pairing is direct, not a chain. If A is close to B and B is close to C, the tool still tests the actual gap from A to C. It does not treat all three as one overlapping period. These are point-date comparisons, not a model of how long leasing, financing or closing work takes.

Work Through the Fictional Linden Calendar

The example contains six invented records reviewed on October 16, 2026. None describes an actual trust or a verified contract. Four records concern dates in the Linden warehouse group. A fifth is a debt date for a separate Harbor property. The sixth is a Linden lease whose date is missing.

Fictional event Date Basis
Linden tenant renewal notice March 31, 2027 Document-stated
Linden assumed property sale June 15, 2027 Planning assumption
Linden loan maturity June 30, 2027 Document-stated
Linden tenant lease expiration September 30, 2027 Document-stated
Harbor loan maturity June 30, 2027 Document-stated
Linden small-tenant lease expiration Unknown Unconfirmed

With a ninety-day window, the tool finds two pairs. The renewal notice is seventy-six days before the assumed sale. The assumed sale is fifteen days before the Linden loan maturity. Both pairs mix a document-stated date with a planning assumption.

The notice and loan maturity are ninety-one days apart, so they fall outside that window. The loan maturity and lease expiration are ninety-two days apart. They also fall outside it. Raising the window to ninety-one adds the notice-and-loan pair. Raising it to ninety-two adds the loan-and-lease pair as well.

Harbor's debt date is the same as Linden's, but it is in a different group. The tool does not pair them. The undated Linden lease cannot be compared with any date. Neither exclusion means the event is harmless; it means the selected grouping or available dates do not support that calculation.

From the review date, the notice is 166 days away, the assumed sale 242, the loan maturities 257 and the known lease expiration 349. These are simple date gaps. The fifteen days between the assumed sale and maturity do not establish a reliable repayment cushion because the sale is only a planning input.

Read the Monthly Map and Missing-Date Record

The monthly map groups all known dates by calendar month across every group. In the example, March has one event, June has three and September has one. The missing lease date appears in the event record rather than a month. June's total includes Harbor even though Harbor is excluded from Linden's nearby pairs.

A monthly total is a count of entries. It is not weighted by rent, property value, loan balance or your investment amount. Three small leases and one large loan cannot be compared on economic importance from the count alone. Review the dollar exposure in a separate, clearly defined analysis.

The chronological record preserves the source, date basis and notes for each event. Known dates appear first; undated records follow. Flags identify missing dates, missing source fields and unconfirmed information. Document-stated entries also remind you that their evidence has not been checked by the tool.

Duplicate records can inflate counts and pairs. The calendar does not know whether two differently labeled entries describe the same lease clause. Remove a duplicate only after checking the source. Two genuine events on the same date should remain separate, with labels that explain the difference.

An empty nearby-pair list is a bounded result. It means no entered same-group dates meet the selected window. It does not mean the calendar is complete or that the investment has no timing risk. Missing dates, omitted events and group labels all affect that result.

Use the Calendar to Ask Better Debt and Exit Questions

Start with the events that support a business-plan assumption. If the plan expects a sale before loan maturity, ask what evidence supports the timing. Is there only a target date, or are there later steps with their own documents? Keep any expected investor payment date separate from the property's assumed closing date.

For a lease event near a debt date, ask how the current underwriting treats that lease. The calendar cannot tell you whether a lender requires a renewal, how vacancy would affect debt service, or whether cash reserves can cover a gap. It identifies a sequence worth examining with the actual terms.

Read the output alongside the offering's limits on transfers and liquidity. The SEC warns that private-placement investors may have difficulty reselling and may need to hold indefinitely. A date labeled “assumed exit” does not create a redemption right or establish when you can obtain cash. SEC private-placement bulletin.

Choose follow-up questions that can change the record. Ask for an effective amendment, a notice clause, evidence of an exercised option, or an updated planning assumption. Record what the response establishes. A new document may settle a date while leaving the financial effect unresolved.

Update the Evidence and Preserve Your Results

Build the calendar after entering or changing records. Any input change clears the prior results and disables export until you rebuild. A failed check preserves the entered fields so you can correct the issue. The tool does not silently replace an invalid date or a missing date with a guessed value.

Removing an event, clearing the calendar or loading the example requires confirmation inside the tool. Cancel keeps the current entries. Editing a field while confirmation is pending cancels that pending action. This helps prevent an old removal or replacement request from discarding newer work.

JSON and text exports include every current event, including undated entries, source notes and model limits. JSON also contains the monthly counts and full computed result. An export is a record of the current inputs and calculation. It is not an audit trail, a verified source packet or an importable backup in this version.

The tool has no automatic storage, import, reminders or monitoring. Save an export before leaving the page if you need a record. Keep prior exports with your own source files when dates change. A later comparison should explain whether the change came from an amendment, a corrected entry or a new assumption.

FAQ

Does a nearby pair mean the DST has a problem?

No. It means two entered dates in one group fall within your chosen window. The tool does not measure the money at risk or the likelihood of a bad outcome. Use the pair to guide a review of the actual terms and business plan.

Does document-stated mean the date is verified?

No. It is your classification and requires a source reference. The tool does not inspect the source, check amendments or decide whether a condition has been met. Keep those review limits in the notes.

Can I calculate a renewal notice deadline from the lease end?

This tool does not calculate legal notice deadlines. Enter the date established through a review of the agreement. It does not apply business-day rules, holidays, delivery requirements or different meanings of a stated notice period.

Why is a same-day event missing from the pair list?

Check its group label. Only exact matching groups are paired after whitespace is cleaned up; letter case remains significant. Also check that both dates are entered and that the calendar was rebuilt after your last edit.

What happens when the event date is unknown?

Leave it blank. Its record, source notes and missing-date flag remain visible and are exported. It cannot enter monthly counts or nearby pairs. The tool does not treat an unknown date as a distant event or as proof that no event exists.

Does an assumed sale before maturity prove that the loan can be repaid?

No. A planned sale date does not establish a buyer, closing, net proceeds or authority to complete the plan. Even an entered date close to maturity says nothing about the amount available for repayment. Review timing, legal powers and cash needs separately.

About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This library helps readers connect investment documents, calculations, and practical questions when reviewing real estate offerings.

Sources