Tool & guide

Delaware Statutory Trust Horror Stories: Case Timeline Builder

By Sequoia ResearchPublished Read as Markdown

Case Timeline Builder

Users add dated notices, cash flows, filings, and statements with source links. The timeline displays what was known at each point and avoids presenting chronological proximity as proof of causation.

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 a tool for arranging dated records about a DST case. It keeps an event's date separate from the source's issue date and the date that source first became available to your review. A historical view shows which entered records were available by a date you choose. The timeline helps readers follow the evidence without treating a sequence of events as proof that one caused another.

Table of Contents

What the DST Case Timeline Does

The tool holds one to thirty source records in a named case. Each record has an entity or subject, a short title, a type, an event status, three optional dates and a source reference. You can add a page location, cash annotation and notes about limits or unanswered questions.

The result provides two ways to sort the same records. One follows event or planned dates. The other follows when each source first became available to your review. You can show all records or focus on the records available by a selected historical date.

This is a manual research aid. It does not search for complaints, open sources, access an investor account or confirm that an event happened. A reference you enter remains text. A record described as reported to have occurred remains a sourced claim unless you have done separate work to verify it.

The distinction matters when researching a troubling investment story. A notice may describe an event weeks after it happened. A report received today may contain older figures. A planned maturity can appear beside an actual payment even though they are different kinds of information.

The SEC describes limited disclosure as one risk of private placements. A timeline of the records you possess does not become a complete history of the investment. It should make the boundary of that record set easier to see. SEC private-placement bulletin, updated September 21, 2026.

Set the Review Cutoff and Historical Date

Enter a case title that identifies the subject without assuming a conclusion. A name such as “Cedar Vale payment notices” is more precise than a title declaring a proven failure. The example in this tool uses an invented trust and invented records.

The review cutoff is the latest date included in the record review. It cannot be later than the current local date on the device running the tool. The historical as-of date must be on or before that cutoff. All dates must be real calendar dates from 1900 through 2200.

The historical date answers a narrower question: which sources, according to the entered availability dates, had reached this review by then? It does not establish what management, other investors or the public knew. Those people may have had different records at different times.

A source is included in the historical view when its first-available date is on or before the as-of date. An unknown availability date stays in a separate group. The tool does not guess it from the event date, the document's title or its position in the list.

Changing either review date clears the old result and disables exports until you build again. Saved source records remain in place. If the new cutoff conflicts with a record, the tool shows an error so you can review the dates rather than silently deleting evidence.

Enter One Source Record at a Time

Give the record the full legal entity name or the precise subject stated in the source. A sponsor, trust, property, master tenant and investor account can be different subjects. The tool does not merge them because their names are similar.

Choose Notice, Cash-flow record, Filing, Statement or Other. These are organizing labels, not reliability grades. A filing can contain allegations or estimates. A statement can repeat an earlier payment. The type alone does not prove the content.

Write a short title describing what the record says. Use the source reference and page field to make it findable. The reference can be a document name, file location or link. Enter enough detail to distinguish versions without pasting an entire private document into the notes.

The source review status is either Opened by reviewer or Not opened by reviewer. Opening a file does not verify its contents. The status only records whether you opened the referenced material. The output counts unopened records so that a reference-only entry does not disappear into a polished timeline.

Record important limits in the notes. Examples include an unavailable attachment, a cropped statement, an unclear entity name or a reported figure that has not been reconciled. An unanswered question can be useful evidence about the review's limits; it need not be forced into a true-or-false label.

FINRA's private-placement guidance discusses reviewing material representations and assessing the work of third parties with care. That guidance applies in its covered-member context. The tool supports an evidence trail, but completing it does not establish that anyone has fulfilled a regulatory duty. FINRA Regulatory Notice 23-08.

Keep Events, Plans and Unknown Dates Separate

Choose Reported as occurred when the source describes something that happened. Choose Planned / expected for a future schedule or an intended action. Use Timing unclear when the source does not support either treatment. None of these labels is an automated finding.

The event date is the date of the event described, or the planned date in a schedule. Leave it blank when unknown. The source issue date is the date on that particular notice, filing or statement. The first-available date is when that source became available to your review.

An issue date and first-available date cannot follow the review cutoff. When both are known, the source issue date cannot follow its first-available date. If a draft was available before a later final version, record the draft and final source separately with their own dates and references.

For a record reported as occurred, a known event date cannot follow its source issue date or first-available date when those fields are supplied. It also cannot follow the cutoff. These checks prevent an advance notice from being presented as proof of a later completed event.

A planned event can have a date after the cutoff. That is a future plan recorded in an existing source. If its planned date is before the historical as-of date, the output warns that the plan does not establish the outcome. Passing a date does not, by itself, prove completion, repayment or default.

An unclear event can retain the date stated in the source while preserving the unclear status. The tool does not infer occurrence from that date. Unknown dates remain blank and sort after dated records. It never inserts the first day of a month or uses today's date as a substitute.

Read the Historical Evidence View

The initial view shows records available by the selected as-of date. Switch to All records to see the full entered case. Not established by as-of shows records available later and records with an unknown availability date. That label concerns availability, not whether their claims are true.

The result counts those three availability groups separately. It also counts unopened sources and records with unknown event dates. These counts describe your file. They do not measure investment quality, the severity of a problem or the chance that a complaint is valid.

Sort by event date to follow the reported events and plans. Sort by first-available date to follow the arrival of evidence in your review. When dates match, stable record IDs provide a consistent display order. They do not establish which event happened first during that day.

A source received later may improve your present understanding of an earlier event. It should still remain outside an earlier historical knowledge view. This avoids using later evidence to imply that a reader had already seen it when making a past decision.

The tool does not delete records outside the selected view. Full exports include every saved record, every source note and all computed availability labels. Keep this distinction in mind when sharing a file: the downloaded review contains more than the currently visible cards.

Follow the Fictional Timeline Example

The example uses Cedar Vale DST, an invented entity. The review cutoff is October 17, 2026, and the historical date is June 1, 2026. Five invented sources illustrate the different clocks.

C1 is a notice issued May 3 about a repair event on May 1. It became available to this review on May 5. The event-to-known gap is four calendar days, while the source-to-known gap is two. It belongs in the June 1 historical view.

C2 is a bank receipt record for May 20, issued May 21 and available May 22. It contains a positive $1,000 cash annotation for the invented investor account. Its event-to-known gap is two days and source-to-known gap is one day.

C3 is a loan summary issued April 15 and available April 16. It lists a planned August 1 maturity. That source was available by June 1 even though the planned event was still in the future. Including the source does not mean the loan had matured on June 1.

C4 is a June 30 statement snapshot issued July 15 and available July 18. It repeats the $1,000 receipt already described in C2. It is outside the June 1 view because it arrived later. Its event-to-known gap is eighteen days, and its source-to-known gap is three.

C5 is an untraced online statement with a June 10 source date. The reviewer has not opened it. Its event date and first-available date are unknown. It stays in the unknown-availability group, even though a document date was entered.

The June 1 result has three sources available by that date, one available later and one with unknown availability. There is one unopened source and one unknown event date. Sorting by event date gives C1, C2, C4, C3 and then undated C5 across the full file.

Change the historical date to September 1. Four sources are now available by that date, and C5 remains unknown. C3's planned August 1 date has passed, so the tool flags the missing outcome. It does not mark the loan paid, extended or in default.

Use Cash Annotations Without Double Counting

A cash annotation is optional. Enter plain U.S. dollars with no commas or currency sign and no more than two decimals. A minus sign can describe an outflow. Each amount must be between negative $1 billion and positive $1 billion. Zero is a known entered amount; a blank remains unknown or not entered.

Every amount requires a scope and direction explanation. Identify the account or entity, what the amount measures, and whether another record may describe the same cash. A property receipt and an investor payment should not be merged merely because both use dollars.

The tool never adds cash annotations. In the example, C2 and C4 both contain $1,000, but C4 repeats C2's receipt. A $2,000 total would be wrong. The notes preserve that link without assuming all matching amounts refer to the same payment.

The SEC's financial-statement guide distinguishes cash flows from income measures and point-in-time balances. Apply the same care here: a statement balance, a projected payment and an actual receipt are different facts. The annotation helps identify them; it does not reconcile bank records or calculate investment return. SEC financial-statement guide.

Interpret Date Gaps With Care

For a reported occurrence with both dates known, the tool calculates calendar days from event to first availability. It also calculates source issue to first availability when both dates are present. The historical output records how many days an available source had been known by the as-of date.

These are elapsed calendar-day differences, not business-day deadlines. They contain no time of day, time zone, delivery method or contractual notice rule. Two records dated the same day have a zero-day difference; their order within that day remains unknown.

A long gap can prompt a question. It does not establish that someone withheld information or breached a duty. The file may be incomplete, the source may have reached someone else sooner, or the dates may refer to different steps. Keep the cause of a gap open until evidence supports it.

Likewise, a payment change after a repair notice does not prove the repair caused the change. Other events or obligations may matter. The timeline makes the sequence easier to inspect; a causal explanation requires more than nearby dates.

Edit Records and Save the Full Review

Save each record before building the timeline. An unfinished new record or an open edit blocks building, so unsaved changes cannot silently disappear from an export. A failed save leaves the form and existing records intact.

Each saved record has a stable ID. Removing one does not cause later records to reuse its ID. Editing replaces that record's saved contents; it does not preserve a revision history. Keep an earlier exported file if you need the prior version. Loading the example or clearing all entries starts a new review.

Removing a record, replacing unfinished work, loading the example and clearing entries use on-page Confirm and Cancel controls. Escape also cancels the displayed confirmation. Editing input while a confirmation is open cancels the pending action. Removing the record currently being edited also clears that record's unfinished edit after confirmation.

The saved normalized review is limited to 60,000 UTF-8 bytes. This is a byte limit, not a character count; some characters use several bytes. JSON and text exports each have a one-mebibyte limit, equal to 1,048,576 bytes. Shorten source notes if a limit is reached rather than removing important qualifications without explanation.

Both exports retain all saved records regardless of the display filter or sort. JSON includes the full input and computed report with a generation time. Text presents the complete file in event-date order. There is no import, automatic storage or online upload. Save files you need before leaving or refreshing the page.

Know What the Timeline Cannot Establish

The tool cannot confirm identities, verify a source, determine a legal duty or decide whether a claim is true. It cannot establish what a person knew outside the entered record set. It does not find missing filings or compare the case with other investments.

Use it to make a bounded review clearer: these are the records, these are their dates, and these are the gaps. Keep allegations attributed to their sources and avoid turning an unresolved sequence into a verdict. A clear timeline supports further research without pretending to complete it.

FAQ

Does Available by As-of Mean the Information Was Public?

No. It uses the date you entered for when that source became available to this review. It does not check publication, delivery or another person's knowledge. Document those facts separately if they matter.

Can I Include a Future Loan Maturity?

Yes. Use Planned / expected and enter the scheduled date. The source issue and first-available dates must still fit the review cutoff. A future plan can be known today without having occurred.

What Happens When the Availability Date Is Unknown?

The record stays in the file but is excluded from the available-by-as-of view. It appears in the unknown-availability count and full exports. The tool will not infer availability from its event or issue date.

Why Are Two Cash Amounts Not Added Together?

They may describe the same payment, different entities or different measures. The tool retains each annotation and its scope. A separate reconciliation is needed before treating entries as distinct cash flows.

Does a Large Date Gap Prove a Late Notice?

No. The tool computes calendar-day differences only. A notice duty may depend on terms, delivery rules and facts not entered here. The gap can guide a question without proving delay or responsibility.

Will Editing Keep an Audit History?

No. An edit replaces a saved record. Export the earlier version first if it matters to your work. Stable record IDs help follow the current file, but they are not a change log or proof that a record remained unchanged.

About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This educational library helps readers compare source documents, understand assumptions and prepare questions for qualified professionals.

Sources